Hi, Community!
Today I will share with you the solution to Third-party registration with the U1900 fails..
Issue Description
The customer encountered an issue in register a third party analog gateway OpenVOX GW1202 that was connected to the same switch and in the same VLAN. U1981 unified gateway rejected the registration information with a SIP 403 Forbidden client failure response code. The SIP user configured on the unified gateway is 660001.
Firmware version: eSpace U1981/V200R003C30SPC500B011
Handling Process
In order to troubleshoot the reported issue we requested from the customer the firmware version of the unified gateway; screenshot of how the user is configured on the unified gateway, and a SIP trace using LMT collection that contains the Request/Response sequence to check the REGISTER message sent.
After this information was provided we have asked the customer to attempt to log the same SIP user to another device and attempt to register. In this case, the customer was now using a 3CX Phone.
REGISTER sip:10.4.1.12:5060 SIP/2.0 Via: SIP/2.0/TCP 10.1.1.47:63500;branch=z9hG4bK-d8754z-fc1137444f6c1252-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:660001@10.1.1.47:63500;rinstance=1f5b90cffdd4c5ab;transport=TCP> To: "660001"<sip:660001@10.4.1.12:5060> From: "660001"<sip:660001@10.4.1.12:5060>;tag=411db40e Call-ID: Y***ZWQwYzJlMTQwZTE3M2E0NjlkMWI3MjZkMmQ2ZGQ. CSeq: 1 REGISTER Expires: 120 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Supported: replaces User-Agent: 3CXPhone 6.0.26523.0 Content-Length: 0 . [70][0x0000002c][2018-06-11 10:54:27.30][sstpdmgmt.c 2077]TptDSendOrientlinkData [95][0x0000002c][2018-06-11 10:54:27.30][sstpdmgmt.c 1424]VComJudgeLinkValid: ConId[1] LinkId[2] is valid [448][0x0000002c][2018-06-11 10:54:27.30][sipstktptdhalftc.c 637]--Sip Msg Send-- IsCallMsg:[N], Direction:[10.4.1.12--->10.1.1.47] SIP/2.0 403 Forbidden Via: SIP/2.0/TCP 10.1.1.47:63500;branch=z9hG4bK-d8754z-fc1137444f6c1252-1---d8754z-;rport=60097 Call-ID: Y***ZWQwYzJlMTQwZTE3M2E0NjlkMWI3MjZkMmQ2ZGQ. From: "660001"<sip:660001@10.4.1.12:5060>;tag=411db40e To: "660001"<sip:660001@10.4.1.12:5060>;tag=rzc16x61 CSeq: 1 REGISTER Content-Length: 0
The issue was still present.
Below is the initial request/response sequence when the customer was using the VoxStack Analog Gateway as a user agent.
[491][0xffffffff][2018-06-11 10:49:13.52][sipstktptdhalftc.c 1109]--Sip Msg Recv-- IsCallMsg:[N], Direction:[10.4.1.23--->10.4.1.12] REGISTER sip:10.4.1.12 SIP/2.0 Via: SIP/2.0/UDP 10.4.1.23:5060;branch=z9hG4bK744cf86f;rport Max-Forwards: 70 From: <sip:660001@10.4.1.12>;tag=as47e49ca7 To: <sip:660001@10.4.1.12> Call-ID: 545c634747c8718f14d321e87880db49@0.0.0.0 CSeq: 102 REGISTER User-Agent: VoxStack Analog Gateway Expires: 120 Contact: <sip:660001@10.4.1.23:5060> Content-Length: 0 . [392][0xffffffff][2018-06-11 10:49:13.52][sipstktptdhalftc.c 637]--Sip Msg Send-- IsCallMsg:[N], Direction:[10.4.1.12--->10.4.1.23] SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 10.4.1.23:5060;branch=z9hG4bK744cf86f;rport=5060 Call-ID: 545c634747c8718f14d321e87880db49@0.0.0.0 From: <sip:660001@10.4.1.12>;tag=as47e49ca7 To: <sip:660001@10.4.1.12>;tag=3xzxs165 CSeq: 102 REGISTER Content-Length: 0
In the provided log we have noticed other Huawei terminals that could register without any issues and noticed that in the REGISTER request coming from third-party devices the unified gateway did not challenge the authentication with a normal 401 Unauthorized containing the WWW-Authenticate field in the message header and as such there were no credentials included in the REGISTER request.
Root Cause
The root cause of this issue is that the unified gateway does not accept third party authentication REGISTER requests when the soft parameter function option 286 is enabled by default. This option is used to inspect the user agent in the requests sent and as such it rejected the authentication directly without challenging it.
Solution
Advised the customer to check the 286 soft parameter function on the unified gateway using CLI commands:
show softargu configinfor id 286
You have to make sure that this option is set to 0 (disable). You can disable it by using the below command:
config softargu type 286 value 0
Thanks for reading!
