Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

7942G phone setup

Hello,

Not sure but my post never made it into the discussion

I am trying to setup the 7942G and have not been able to setup this phone no matter whatever configurations I have done.

Here is the setup:

Phone (Behind Router with Private IP - 192.168.0.25) -> Public IP (99.2.230.21 - Router DMZ forwarded to phone) -> Firewall (Completely Open for the IPs) -> Asterisk Server (24.228.146.155)

I see the SIP communication between the server and the phone. The client registers, supplies SIP credentials and get knocked off with the only message that seems relevant:

Reason: SIP;cause=200;text="cisco-alarm:25 Name=SEPXX4F5794EY1E Load=SIP42.8-5-4S Last=initialized"

Expires: 3600

I have never had any problems deploying any other phone on the network and the new plans was to introduce cisco phones into our existing setup for folks working from home. I spent considerable amount of time trying to debug the issue and at this point need help or have to give up. I have been trying to find any 3rd party or someone doing partime that is available to help debug and fix issue?. Since the phone was purchased from a retail web front, I am not even sure how to purchase the support as well.

SIP Debug on Phone

1289: DBG 12:19:57.768081 JVM: LINE 51/1: sipTransportSendMessage            : Stopping reTx timer

1290: DBG 12:19:57.768702 JVM: LINE 51/1: ccsip_register_retry_timer_start   : Starting reTx timer (1000 msec)

1291: DBG 12:19:57.840293 SYSMSG: pid 14 wrote msgqueue cdp_msg_que

1292: DBG 12:19:57.840794 SYSMSG: pid 14 read msgqueue cdp_msg_que

1293: DBG 12:19:57.841223 SYSMSG: pid 14 sleep on read msgqueue cdp_msg_que

1294: DBG 12:19:58.740179 SYSMSG: pid 29 wrote msgqueue SIPQ

1295: DBG 12:19:58.750889 SYSMSG: pid 29 read msgqueue SIPQ

1296: DBG 12:19:58.751340 JVM: SIPTaskProcessListEvent: cmd = 0x0

1297: DBG 12:19:58.751866 JVM: ccsip_register_timeout_retry

1298: DBG 12:19:58.752430 JVM: ccsip_register_send_msg: cmd=0x5c

1299: DBG 12:19:58.753014 SYSMSG: pid 29 wrote msgqueue SIPQ

1300: DBG 12:19:58.753468 SYSMSG: pid 29 read msgqueue SIPQ

1301: DBG 12:19:58.753871 JVM: SIPTaskProcessListEvent: cmd = 0x5c

1302: DBG 12:19:58.754470 JVM: LINE 51/1: --0x0039e930--                     : SIP_REG_STATE_REGISTERING <- E_SIP_REG_TMR_RETRY

1303: DBG 12:19:58.755063 JVM: ccsip_handle_ev_tmr_retry: Resending message: #2

1304: DBG 12:19:58.755698 JVM: sipTransportSendMessage: ccb <51>: config <24.228.146.155>:<5060> - remote <24.228.146.155>:<5060>

1305: DBG 12:19:58.756315 JVM: sipTransportSendMessage: Got handle 24

1306: DBG 12:19:58.757346 JVM: sipTransportSendMessage: Sent SIP message: handle=<24>,length=<686>, message=

1307: DBG 12:19:58.757912 JVM: REGISTER sip:24.228.146.155 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.25:5060;branch=z9hG4bKe5d415c2

From: <sip:7045@24.228.146.155>;tag=f84f5794400e00150a4a3e5e-9ba354d2

To: <sip:7045@24.228.146.155>

Call-ID: f84f5794-400e0002-db288b58-2876f10c@192.168.0.25

Max-Forwards: 70

Date: Sat, 14 Sep 2013 16:19:57 GMT

CSeq: 120 REGISTER

User-Agent: Cisco-CP7942G/8.5.3

Contact: <sip:7045@192.168.0.25:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-f84f5794400e>";+u.sip!model.ccm.cisco.com="434"

Supported: (null),X-cisco-xsi-7.0.1

Content-Length: 0

Reason: SIP;cause=200;text="cisco-alarm:25 Name=SEPXX4F5794EY1E Load=SIP42.8-5-4S Last=initialized"

Expires: 3600

1308: DBG 12:19:58.758767 JVM: LINE 51/1: sipTransportSendMessage            : Stopping reTx timer

1309: DBG 12:19:58.759416 JVM: LINE 51/1: ccsip_register_retry_timer_start   : Starting reTx timer (2000 msec)

1310: DBG 12:19:58.840598 SYSMSG: pid 14 wrote msgqueue cdp_msg_que

1311: DBG 12:19:58.841103 SYSMSG: pid 14 read msgqueue cdp_msg_que

1312: DBG 12:19:58.841530 SYSMSG: pid 14 sleep on read msgqueue cdp_msg_que

1313: DBG 12:19:59.190161 SYSMSG: pid 29 wrote msgqueue SIPQ

1314: DBG 12:19:59.210146 SYSMSG: pid 29 read msgqueue SIPQ

1315: DBG 12:19:59.210636 JVM: SIPTaskProcessListEvent: cmd = 0x0

1316: DBG 12:19:59.211241 SYSMSG: pid 29 wrote msgqueue SIPQ

1317: DBG 12:19:59.211702 SYSMSG: pid 29 read msgqueue SIPQ

1318: DBG 12:19:59.212106 JVM: SIPTaskProcessListEvent: cmd = 0x67

|== Syslogd TNP== Sat Sep 14 12:19:59 2013

====================================================

1321: DBG 12:19:59.843802 SYSMSG: pid 14 sleep on read msgqueue cdp_msg_que

1322: DBG 12:20:00.000177 SYSMSG: adjtime complete, count = f44db

1323: DBG 12:20:00.740377 SYSMSG: pid 29 wrote msgqueue SIPQ

1324: DBG 12:20:00.740973 SYSMSG: pid 29 read msgqueue SIPQ

1325: DBG 12:20:00.741383 JVM: SIPTaskProcessListEvent: cmd = 0x0

1326: DBG 12:20:00.741917 JVM: ccsip_register_timeout_retry

1327: DBG 12:20:00.742438 JVM: ccsip_register_send_msg: cmd=0x5c

1328: DBG 12:20:00.743024 SYSMSG: pid 29 wrote msgqueue SIPQ

1329: DBG 12:20:00.743486 SYSMSG: pid 29 read msgqueue SIPQ

1330: DBG 12:20:00.743898 JVM: SIPTaskProcessListEvent: cmd = 0x5c

1331: DBG 12:20:00.744499 JVM: LINE 51/1: --0x0039e930--                     : SIP_REG_STATE_REGISTERING <- E_SIP_REG_TMR_RETRY

1332: DBG 12:20:00.745137 JVM: ccsip_handle_ev_tmr_retry: Resending message: #3

1333: DBG 12:20:00.745787 JVM: sipTransportSendMessage: ccb <51>: config <24.228.146.155>:<5060> - remote <24.228.146.155>:<5060>

1334: DBG 12:20:00.746369 JVM: sipTransportSendMessage: Got handle 24

1335: DBG 12:20:00.747418 JVM: sipTransportSendMessage: Sent SIP message: handle=<24>,length=<686>, message=

1336: DBG 12:20:00.747977 JVM: REGISTER sip:24.228.146.155 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.25:5060;branch=z9hG4bKe5d415c2

From: <sip:7045@24.228.146.155>;tag=f84f5794400e00150a4a3e5e-9ba354d2

To: <sip:7045@24.228.146.155>

Call-ID: f84f5794-400e0002-db288b58-2876f10c@192.168.0.25

Max-Forwards: 70

Date: Sat, 14 Sep 2013 16:19:57 GMT

CSeq: 120 REGISTER

User-Agent: Cisco-CP7942G/8.5.3

Contact: <sip:7045@192.168.0.25:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-f84f5794400e>";+u.sip!model.ccm.cisco.com="434"

Supported: (null),X-cisco-xsi-7.0.1

Content-Length: 0

Reason: SIP;cause=200;text="cisco-alarm:25 Name=SEPXX4F5794EY1E Load=SIP42.8-5-4S Last=initialized"

Expires: 3600

SIP Debug on Server

<------------->

--- (14 headers 0 lines) ---.168.0.25

vp*CLI> sip set debug ip 192.168.0.25

SIP Debugging Enabled for IP: 192.168.0.25

Sending to 192.168.0.25 : 5060 (no NAT)

vp*CLI>

<--- Transmitting (no NAT) to 192.168.0.25:5060 --->

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.0.25:5060;branch=z9hG4bKe5d415c2;received=99.2.230.21

From: <sip:7045@24.228.146.155>;tag=f84f5794400e00150a4a3e5e-9ba354d2

To: <sip:7045@24.228.146.155>;tag=as74d49af6

Call-ID: f84f5794-400e0002-db288b58-2876f10c@192.168.0.25

CSeq: 120 REGISTER

User-Agent: Asterisk PBX 1.6.0.9-samy-r27

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="7b9a6dba"

Content-Length: 0

<------------>

Scheduling destruction of SIP dialog 'f84f5794-400e0002-db288b58-2876f10c@192.168.0.25' in 32000 ms (Method: REGISTER)

Sending to 192.168.0.25 : 5060 (no NAT)

vp*CLI>

<--- Transmitting (no NAT) to 192.168.0.25:5060 --->

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.0.25:5060;branch=z9hG4bKe5d415c2;received=99.2.230.21

From: <sip:7045@24.228.146.155>;tag=f84f5794400e00150a4a3e5e-9ba354d2

To: <sip:7045@24.228.146.155>;tag=as74d49af6

Call-ID: f84f5794-400e0002-db288b58-2876f10c@192.168.0.25

CSeq: 120 REGISTER

User-Agent: Asterisk PBX 1.6.0.9-samy-r27

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="7b9a6dba"

Content-Length: 0

<------------>

Scheduling destruction of SIP dialog 'f84f5794-400e0002-db288b58-2876f10c@192.168.0.25' in 32000 ms (Method: REGISTER)

Sending to 192.168.0.25 : 5060 (no NAT)

vp*CLI>

<--- Transmitting (no NAT) to 192.168.0.25:5060 --->

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.0.25:5060;branch=z9hG4bK4cb88a6d;received=99.2.230.21

From: <sip:7045@24.228.146.155>;tag=f84f5794400e00166c328ba0-d69266e7

To: <sip:7045@24.228.146.155>;tag=as74d49af6

Call-ID: f84f5794-400e0002-db288b58-2876f10c@192.168.0.25

CSeq: 121 REGISTER

User-Agent: Asterisk PBX 1.6.0.9-samy-r27

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="06c0e682"

Content-Length: 0

<------------>

Scheduling destruction of SIP dialog 'f84f5794-400e0002-db288b58-2876f10c@192.168.0.25' in 32000 ms (Method: REGISTER)

Sending to 192.168.0.25 : 5060 (no NAT)

vp*CLI>

<--- Transmitting (no NAT) to 192.168.0.25:5060 --->

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.0.25:5060;branch=z9hG4bK4cb88a6d;received=99.2.230.21

From: <sip:7045@24.228.146.155>;tag=f84f5794400e00166c328ba0-d69266e7

To: <sip:7045@24.228.146.155>;tag=as74d49af6

Call-ID: f84f5794-400e0002-db288b58-2876f10c@192.168.0.25

CSeq: 121 REGISTER

User-Agent: Asterisk PBX 1.6.0.9-samy-r27

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="06c0e682"

Content-Length: 0

<------------>

Scheduling destruction of SIP dialog 'f84f5794-400e0002-db288b58-2876f10c@192.168.0.25' in 32000 ms (Method: REGISTER)

Sending to 192.168.0.25 : 5060 (no NAT)

vp*CLI>

<--- Transmitting (no NAT) to 192.168.0.25:5060 --->

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.0.25:5060;branch=z9hG4bK4cb88a6d;received=99.2.230.21

From: <sip:7045@24.228.146.155>;tag=f84f5794400e00166c328ba0-d69266e7

To: <sip:7045@24.228.146.155>;tag=as74d49af6

Call-ID: f84f5794-400e0002-db288b58-2876f10c@192.168.0.25

CSeq: 121 REGISTER

User-Agent: Asterisk PBX 1.6.0.9-samy-r27

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="06c0e682"

Content-Length: 0

Thanks
Simon

Everyone's tags (1)
1 REPLY
Hall of Fame Super Gold

7942G phone setup

Duplicate post.

293
Views
0
Helpful
1
Replies