05-22-2019 05:07 PM
I'm attempting to register a SPA112 to our Alcatel OmniPCX enterprise PBX. When attempting to register the SPA112, the PBX returns a 501 Not Implemented.
Register message from SPA112:
REGISTER sip:172.16.10.200 SIP/2.0
Via: SIP/2.0/UDP 172.16.10.14:5059;branch=z9hG4bK-3266dc1e;rport
From: <sip:249@172.16.10.200>;tag=55b03fd7916ad1fo0
To: <sip:249@172.16.10.200>
Call-ID: cef48bc7-f70550e1@172.16.10.14
CSeq: 48784 REGISTER
Max-Forwards: 70
Contact: <sip:249@172.16.10.14:5059>;expires=120
User-Agent: Cisco/SPA112-1.4.1_SR3
P-Station-Name: ;mac=701f530b473f; display=""; sn=CCQ22250K14
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Reponse from PBX
SIP/2.0 501 Not Implemented User-Agent: OXO030/055.001 GW_030/069.001 To: <sip:249@172.16.10.200>;tag=0cd24ad1609d8af716047d9b3e247848 From: <sip:249@172.16.10.200>;tag=cec30765ff78dad9o0 Call-ID: 2b9b298d-e57eddd2@172.16.10.14 CSeq: 44626 REGISTER Via: SIP/2.0/UDP 172.16.10.14:5059;received=172.16.10.14;branch=z9hG4bK-4d454a29;rport=5059 Content-Length: 0
I can rule out the PBX not registering the account, as I'm able to connect via Linphone:
REGISTER sip:172.16.10.200 SIP/2.0 Via: SIP/2.0/UDP 172.16.10.60:5059;branch=z9hG4bK.pKox65dXU;rport From: <sip:249@172.16.10.200>;tag=1KXMTajh1 To: sip:249@172.16.10.200 CSeq: 20 REGISTER Call-ID: c2iJZShg5K Max-Forwards: 70 Supported: replaces, outbound Accept: application/sdp Accept: text/plain Accept: application/vnd.gsma.rcs-ft-http+xml Contact: <sip:249@172.16.10.60:5059;transport=udp>;+sip.instance="<urn:uuid:a1579d3f-ef78-4994-a785-afa7e20623ef>" Expires: 600 User-Agent: Linphone Desktop/4.1.1 (belle-sip/1.6.3)
Which successfully responds with an unauthorized:
SIP/2.0 401 Unauthorized WWW-Authenticate: Digest qop="auth",nonce="a3dc6b21a60b95a4d0c5d57f8fed266c",realm="172.16.10.200" To: sip:249@172.16.10.200;tag=c93e2ac6b6a0773d8676fd57c43eeb86 From: <sip:249@172.16.10.200>;tag=1KXMTajh1 Call-ID: c2iJZShg5K CSeq: 20 REGISTER Via: SIP/2.0/UDP 172.16.10.60:5059;received=172.16.10.60;branch=z9hG4bK.pKox65dXU;rport=5059 Content-Length: 0
Once authenticated I can go on to make calls, all of which work successfully. The SPA112 is unable to connect however.
Given that the differences in headers are minimal, I'm guessing that the PBX doesn't know what to do with the P-Station-Name. Is there a workaround or a way to disable the header from being sent in the REGISTER message?
05-22-2019 10:59 PM
Option Caller ID Header
Read documentation for details if necessary/interested.
09-09-2022 12:13 PM
i know this is quiet old , but by any chance you were able to disable the P-Station-Name ?
09-05-2023 10:11 AM - edited 09-05-2023 10:26 AM
None of the options of Caller ID Header affects P-Station-Name header in REGISTER , is there any way to remove it?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide