OSS PBX End Point Manager & Cisco CP-7962G returning 401 Unauthorized

FreePBX
1

Server Environment:

  • Appliance: SNG7-PBX-64bit-1805-1
  • Asterisk: 13.21.1
  • FreePBX: 14.0.3.6
  • OSS PBX End Point Manager 13.0.7.18

Handset:

  • Phone: Cisco CP-7962G
  • Phone Firmware: SIP42.9-4-2SR3-1S

Problem:

  • Cisco Phone receives 401 Unauthorized upon registration

Additional info:

  • Password is 18 characters, and have tried very short passwords, with no change in results
  • Settings on SPA112 are same and it registers and places calls with no problems.

tcpdump of Cisco phone’s unsuccessful registration

    10.0.4.150.49386 > sangomaos01.network.lan.sip: [udp sum ok] SIP, length: 932
	REGISTER sip:10.0.4.4 SIP/2.0
	Via: SIP/2.0/UDP 10.0.4.150:5060;branch=z9hG4bK6798cfa0
	From: <sip:[email protected]>;tag=0024c40c049100088620c4fa-42a89598
	To: <sip:[email protected]>
	Call-ID: [email protected]
	Max-Forwards: 70
	Date: Sat, 04 Aug 2018 21:46:15 GMT
	CSeq: 105 REGISTER
	User-Agent: Cisco-CP7962G/9.4.2
	Contact: <sip:[email protected]:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0024c40c0491>";+u.sip!devicename.ccm.cisco.com="SEP0024C40C0491";+u.sip!model.ccm.cisco.com="404"
	Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-6.0.0,X-cisco-xsi-8.5.1
	Content-Length: 0
	Reason: SIP;cause=200;text="cisco-alarm:14 Name=SEP0024C40C0491 Load=SIP42.9-4-2SR3-1S Last=cm-closed-tcp"
	Expires: 3600
	
07:47:22.447485 IP (tos 0x60, ttl 64, id 61516, offset 0, flags [DF], proto UDP (17), length 531)
    sangomaos01.network.lan.sip > 10.0.4.150.49386: [bad udp cksum 0x1eaa -> 0x577c!] SIP, length: 503
	SIP/2.0 401 Unauthorized
	Via: SIP/2.0/UDP 10.0.4.150:5060;rport=49386;received=10.0.4.150;branch=z9hG4bK6798cfa0
	Call-ID: [email protected]
	From: <sip:[email protected]>;tag=0024c40c049100088620c4fa-42a89598
	To: <sip:[email protected]>;tag=z9hG4bK6798cfa0
	CSeq: 105 REGISTER
	WWW-Authenticate: Digest  realm="asterisk",nonce="1533419242/1e612154dcc3ec68289428d213a5ab5d",opaque="04e6f1207f797903",algorithm=md5,qop="auth"
	Server: FPBX-14.0.3.6(13.21.1)
	Content-Length:  0

tcpdump of SPA112 successful registration

07:32:19.889521 IP (tos 0x60, ttl 64, id 51420, offset 0, flags [DF], proto UDP (17), length 425)
  sangomaos01.network.lan.sip > 10.0.4.11.sip: [bad udp cksum 0x1db5 -> 0xcece!] SIP, length: 397
OPTIONS sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.4.4:5060;rport;branch=z9hG4bKPj1cd0d445-6bdf-4f74-b0ea-0b54b5fcd21c
From: <sip:[email protected]>;tag=8ca6f090-4f2a-487b-a6e0-c68f61b55d1b
To: <sip:[email protected]>
Contact: <sip:[email protected]:5060>
Call-ID: 4347edf8-2e64-49d7-a1a3-db93369abac0
CSeq: 59726 OPTIONS
Max-Forwards: 70
User-Agent: FPBX-14.0.3.6(13.21.1)
Content-Length:  0

07:32:19.892831 IP (tos 0x60, ttl 64, id 51422, offset 0, flags [DF], proto UDP (17), length 425)
  sangomaos01.network.lan.sip > 10.0.4.11.sip: [bad udp cksum 0x1db5 -> 0x7d6f!] SIP, length: 397
OPTIONS sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.4.4:5060;rport;branch=z9hG4bKPj009e8f53-b0e5-4a8c-9634-257b45a871d5
From: <sip:[email protected]>;tag=eef50563-a86d-49b4-b261-5f2b2bf695f6
To: <sip:[email protected]>
Contact: <sip:[email protected]:5060>
Call-ID: 9303d157-8e7b-4207-a8f1-2f5e447312d7
CSeq: 22661 OPTIONS
Max-Forwards: 70
User-Agent: FPBX-14.0.3.6(13.21.1)
Content-Length:  0

Has anyone got any suggestions on what I can troubleshoot on the cisco phone to get it to register properly?

2

Are you sure that your phones connecting to the right SIP Port?

5060 Default PJSIP
5160 default Chan_SIP

As i know OSS EPM V13 does not change the port string to the correct port if you do not manually change it.

1 Like
3

What is the default port for OSS EPM V13?
I’ve got my other devices, such as Cisco SPA112 connecting via 5060, also softphones are using 5060. All the extensions are configured as PJSIP on 5060.

4

Sorry i corrected my posting

5060 Default PJSIP
5160 Default Chan_SIP

OSS Endpointman is using Port 5060 by default.
On OSS Endpointman V14 i integrated the Feature that the port will be calculated from the Extension settings.

But PJSIP and older Devices like a SPA112 also made me headace. I still use this devices on Chan_SIP

5

Also, some people report better results with the SIP load on the TCP side of the PJ-SIP port. We’ve also heard anecdotal reports that the 7940/7960 will only work with Chan-SIP. IIRC, there’s a problem with the UDP packet length - one of the ends send packets that are too big for the other end.

The 7960 only supports a SUPER short password (I think 8 or 9 characters). The 7962 may support a few more character than that, but not many. The password issue, by the way, is one of the primary reasons I don’t use 7940/7960 series phones in SIP mode.

6

My environment has PJSIP running on 5060 and Chan_SIP running on 5160

I’ve tried the following:

  • Created a Chan_SIP extension (9003) with a 4 character password
  • I looked for any instance of “5060” in /tftpboot/SEP0024C40C0491.cnf.xml and changed it to 5160

This is what tcpdump shows now. I get a 403 forbidden instead.

07:11:39.970277 IP (tos 0x60, ttl 64, id 2103, offset 0, flags [none], proto UDP (17), length 957)
    10.0.4.150.49538 > sangomaos01.network.lan.sip: [udp sum ok] SIP, length: 929
	REGISTER sip:10.0.4.4 SIP/2.0
	Via: SIP/2.0/UDP 10.0.4.150:5060;branch=z9hG4bKce585e6e
	From: <sip:[email protected]>;tag=0024c40c049100093e3ddb5d-6686f748
	To: <sip:[email protected]>
	Call-ID: [email protected]
	Max-Forwards: 70
	Date: Mon, 06 Aug 2018 21:10:33 GMT
	CSeq: 106 REGISTER
	User-Agent: Cisco-CP7962G/9.3.1
	Contact: <sip:[email protected]:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0024c40c0491>";+u.sip!devicename.ccm.cisco.com="SEP0024C40C0491";+u.sip!model.ccm.cisco.com="404"
	Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-6.0.0,X-cisco-xsi-8.5.1
	Content-Length: 0
	Reason: SIP;cause=200;text="cisco-alarm:14 Name=SEP0024C40C0491 Load=term62.default Last=cm-closed-tcp"
	Expires: 3600
	
07:11:39.971312 IP (tos 0x60, ttl 64, id 23660, offset 0, flags [DF], proto UDP (17), length 381)
    sangomaos01.network.lan.sip > 10.0.4.150.49538: [bad udp cksum 0x1e14 -> 0x917d!] SIP, length: 353
	SIP/2.0 403 Forbidden
	Via: SIP/2.0/UDP 10.0.4.150:5060;rport=49538;received=10.0.4.150;branch=z9hG4bKce585e6e
	Call-ID: [email protected]
	From: <sip:[email protected]>;tag=0024c40c049100093e3ddb5d-6686f748
	To: <sip:[email protected]>;tag=z9hG4bKce585e6e
	CSeq: 106 REGISTER
	Server: FPBX-14.0.3.6(13.21.1)
	Content-Length:  0
7

I posted the message before this before I went to work and just left the phone to run all day looping through whatever. I arrived back only to find the phone registered. I have no idea what happened, but I tried to add another extension and test the long/short password issues, and now the phone is looping again.

update, I waited 10 more minutes and it worked

I’ll continue to refine my settings and report back.

Observations
Strong passwords are allowed by this model of phone
Seemed unable to receive inbound calls unless
<voipControlPort>5060</voipControlPort> was set, so had to change back from 5160

8

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.