Jump to content

7940 Registration fails with 403


Recommended Posts

Hi

I'm trying, unsuccessfully, to get a Cisco 7940 to register with PBXnSIP ver 3.4.0.3201 (Win32). My X-Lite client works fine with the extension but the 7940 fails to register. I'm using Cisco SIP 8.6. Has anyone any suggestions?

 

Log file extract below:

 

[7] 2010/01/11 20:19:14: SIP Rx udp:192.168.100.101:50185:

REGISTER sip:192.168.100.70 SIP/2.0

Via: SIP/2.0/UDP 192.168.100.101:5060;branch=z9hG4bK0c9ec82f

From: <sip:169@192.168.100.70>;tag=0011bb30ad5e00020aea758b-584239fd

To: <sip:169@192.168.100.70>

Call-ID: 0011bb30-ad5e0002-42fdaa96-627f04db@192.168.100.101

Max-Forwards: 70

CSeq: 101 REGISTER

User-Agent: Cisco-CP7940G/8.0

Contact: <sip:169@192.168.100.101:5060;user=phone;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0011bb30ad5e>";+u.sip!model.ccm.cisco.com="8"

Content-Length: 0

Expires: 3600

 

 

[9] 2010/01/11 20:19:14: Resolve 176: aaaa udp 192.168.100.101 5060

[9] 2010/01/11 20:19:14: Resolve 176: a udp 192.168.100.101 5060

[9] 2010/01/11 20:19:14: Resolve 176: udp 192.168.100.101 5060

[7] 2010/01/11 20:19:14: SIP Tx udp:192.168.100.101:5060:

SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.100.101:5060;branch=z9hG4bK0c9ec82f

From: <sip:169@192.168.100.70>;tag=0011bb30ad5e00020aea758b-584239fd

To: <sip:169@192.168.100.70>;tag=1bcb2c1707

Call-ID: 0011bb30-ad5e0002-42fdaa96-627f04db@192.168.100.101

CSeq: 101 REGISTER

User-Agent: pbxnsip-PBX/3.4.0.3201

Content-Length: 0

 

Regards,

Nigel

Link to post
Share on other sites
Hi

I'm trying, unsuccessfully, to get a Cisco 7940 to register with PBXnSIP ver 3.4.0.3201 (Win32). My X-Lite client works fine with the extension but the 7940 fails to register. I'm using Cisco SIP 8.6. Has anyone any suggestions?

 

Log file extract below:

 

[7] 2010/01/11 20:19:14: SIP Rx udp:192.168.100.101:50185:

REGISTER sip:192.168.100.70 SIP/2.0

Via: SIP/2.0/UDP 192.168.100.101:5060;branch=z9hG4bK0c9ec82f

From: <sip:169@192.168.100.70>;tag=0011bb30ad5e00020aea758b-584239fd

To: <sip:169@192.168.100.70>

Call-ID: 0011bb30-ad5e0002-42fdaa96-627f04db@192.168.100.101

Max-Forwards: 70

CSeq: 101 REGISTER

User-Agent: Cisco-CP7940G/8.0

Contact: <sip:169@192.168.100.101:5060;user=phone;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0011bb30ad5e>";+u.sip!model.ccm.cisco.com="8"

Content-Length: 0

Expires: 3600

 

 

[9] 2010/01/11 20:19:14: Resolve 176: aaaa udp 192.168.100.101 5060

[9] 2010/01/11 20:19:14: Resolve 176: a udp 192.168.100.101 5060

[9] 2010/01/11 20:19:14: Resolve 176: udp 192.168.100.101 5060

[7] 2010/01/11 20:19:14: SIP Tx udp:192.168.100.101:5060:

SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.100.101:5060;branch=z9hG4bK0c9ec82f

From: <sip:169@192.168.100.70>;tag=0011bb30ad5e00020aea758b-584239fd

To: <sip:169@192.168.100.70>;tag=1bcb2c1707

Call-ID: 0011bb30-ad5e0002-42fdaa96-627f04db@192.168.100.101

CSeq: 101 REGISTER

User-Agent: pbxnsip-PBX/3.4.0.3201

Content-Length: 0

 

Regards,

Nigel

 

 

Not to worry. I found I'd not configured the phone extension correctly. Just couldn't see the wood for the trees.

Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...