Got it

Astra 6731i cannot register U1981

Latest reply: Sep 6, 2018 15:11:04 1049 1 1 0 0

Hi, Community!

Good day to you!

This topic describes the solution to Astra 6731i cannot register U1981.

Issue Description

We have an IP PBX Huawei U1981 and cannot register to it an Astra IP Phone 6731i, but a Polycom IP Phone is registering without any technical difficulties.

When Astra IP Phone is trying to register to the U1981 PBX, the PBX is returning a "403 Forbidden" SIP error message to the REGISTER packet.


transparent.gifAlarm Information

When Astra IP Phone is trying to register to the U1981 PBX, the PBX is returning a "403 Forbidden" SIP error message to the REGISTER packet.


Handling Process

I captured network packets for both Astra and Polycom IP Phones to make a comparison on their Register packets so I can observe the differences.


transparent.gifRoot Cause

In the below image we can see the Register packets, in the left for Astra phone and in the right side the packet from the Polycom phone.


Astra's 403 Forbidden response:


b71aea68f2e04732b70b866b72e65ba7


Polycom's 200 OK response:


97a5a73e0a144ddda5cc0413b2e5ba7e


43320bdad4fc47f8acb1ba9ea1b526d9


From the above we have identified two abnormal lines in Astra's registering packet:


1. Astra IP Phone has the same user ID/calling ID "2002", the same as the Polycom IP Phone, which is leading to a conflict registration for Astra

2. Astra's registering packet does not contain any "Expires: xxxx" line in order to know at which interval should renew the registration with the registrar server


transparent.gifSolution

Because I identify two problems in Astra's register packet I resolved them in the following order:


First, I have changed the user ID/calling ID from "2002" into "2003" in order to get rid of the conflict with the Polycom phone


b40ba2a92d3f479b9854e8df499406e9


After this change was saved, I have restarted the Astra phone and made a SIP trace directly into the U1981's CLI interface, and also captured Polycom's registration packet.


The output was the below:


POLYCOM Register packet:

REGISTER sip:IP Address:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP IP Address;branch=z9hG4bK71cb0c6b69F4C9E
From: "2002" <sip:2002@IP Address>;tag=6F93312D-1897D830
To: <sip:2002@IP Address>
CSeq: 1 REGISTER
Call-ID: 643f9589-460a91ec-13594a87@IP Address
Contact: <sip:2002@IP Address;transport=tcp>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"
User-Agent: PolycomSoundPointIP-SPIP_320-UA/3.x.x.0069
Accept-Language: es-es,es;q=0.9,en;q=0.8
Max-Forwards: 70
Expires: 3600
Content-Length: 0

.

SIP/2.0 200 OK

Via: SIP/2.0/TCP IP Address;branch=z9hG4bK71cb0c6b69F4C9E
Call-ID: 643f9589-460a91ec-13594a87@IP Address
From: "2002"<sip:2002@IP Address>;tag=6F93312D-1897D830
To: <sip:2002@IP Address>;tag=amgavdws
CSeq: 1 REGISTER
Contact: <sip:2002@IP Address:5060>;expires=3600
Expires: 3600
Server: eSpace U1981/V200R003C20SPC300B015
Content-Length: 0


ASTRA Register packet:

REGISTER sip:IP Address:5060 SIP/2.0
Via: SIP/2.0/TCP IP Address:5060;branch=z9hG4bK45a9929be07c0ba21
Max-Forwards: 70
From: "2003" <sip:2003@IP Address:5060>;tag=e3f3473660
To: "2003" <sip:2003@IP Address:5060>
Call-ID: 1baf0d32cf961815
CSeq: 10938 REGISTER
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE, PRACK, SUBSCRIBE, INFO
Allow-Events: aastra-xml, talk, hold, conference, LocalModeStatus
Contact: "2003" <sip:2003@IP Address:5060;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-000-8000-00085D341FDA>"
Supported: path, gruu
User-Agent: Aastra 6731i/3.x.x.2234
Aastra-Line: 1
Content-Length: 0


SIP/2.0 400 Bad Request

Via: SIP/2.0/TCP IP Address:5060;branch=z9hG4bK45a9929be07c0ba21
Call-ID: 1baf0d32cf961815
From: "2003"<sip:2003@IP Address:5060>;tag=e3f3473660
To: "2003"<sip:2003@IP Address:5060>;tag=fxax5yw4
CSeq: 10938 REGISTER
Server: eSpace U1981/V200R003C20SPC300B015
Content-Length: 0


According to the above logs, we can see that Astra's caller ID has been changed, and the response has changed from "403 Forbidden" into "400 Bad Request"


Now we ran into the second problem I have observed initially: the lack of the "Expires: 3600" field which is missing in Astra's REGISTER packet as per the above trace.


The solution was to implement the "Expires" line into the Astra Phone from its web interface as per below:


c29fb76dfff844b5b0b9bd51dc0edb49


After this change the registration problem of the Astra phone was resolved, as per the below SIP trace:

REGISTER sip:IP Address:5060 SIP/2.0
Via: SIP/2.0/TCP IP Address:5060;branch=z9hG4xxK45a9929be07c0ba21
Max-Forwards: 70
From: "2003" <sip:2003@IP Address:5060>;tag=e3f3473660
To: "2003" <sip:2003@IP Address:5060>
Call-ID: 1baf0d32cf961815
CSeq: 10938 REGISTER
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE, PRACK, SUBSCRIBE, INFO
Allow-Events: aastra-xml, talk, hold, conference, LocalModeStatus
Contact: "2003" <sip:2003@IP Address:5060;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-1000-8000-00085D341FDA>"
Supported: path, gruu
User-Agent: Aastra 6731i/3.3.x.2234
Aastra-Line: 1
Expires: 3600
Content-Length: 0


SIP/2.0 200 OK

Via: SIP/2.0/TCP IP Address:5060;branch=z9hG4bK45a9929be07c0ba21
Call-ID: 1baf0d32cf961815
From: "2003"<sip:2003@IP Address:5060>;tag=e3f3473660
To: "2003"<sip:2003@IP Address:5060>;tag=fxax5yw4
CSeq: 10938 REGISTER
Contact: <sip:2003@IP Address:5060>;expires=3600
Expires: 3600
Content-Length: 0

transparent.gif 

Suggestions

As a suggestion, you need to be very careful about the configuration of the IP Phones and to pay attention to what other IP Phones you have in the LAN to avoid conflicts.


Thanks for reading!

Hi @Alexandru_Ghita As I can see, this was a complex issue. Congrats for the resolution and thanks for sharing with us. Regards!!!
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.