Re: [asterisk-users] Polycom 501 Phones Rebooting
Finally, press and hold all 4 arrow keys until the phone bleeps, then capture the log files dumped to your provisioning server one last time. If the problem's not obvious from reading the logs, escalate these logs to your Polycom reseller and ask them to open a ticket with Polycom on your behalf. Of course they might recommend upgrading to 2.x ;-) Well, here is what I got. Have no idea how to read these.. 0924095418|so |2|177|soToneStop: Stopping host tone 0x10b892a4 (dial). [0x0] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateSetup (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateSetup, Start Timer: 1000 msecs 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateOverlap (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateOverlap, Start Timer: 3 msecs 0924095418|sip |2|177|SipCallMake 8605654321 0924095418|sip |2|177|doDnsNaptrLookup: '192.168.1.1' is an IP, bailing 0924095418|sip |2|177|SipOnEvCallNewState 10edbff0,10b42844 2,Proceeding 0924095418|so |2|177|[SoMediaSessC]: MsgPpsCallStateInd Usr(0x10b42844) Net(0x10edbff0) St(3) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateOverlap) - Event (SoMediaSessEvLclNetProceeding) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateProceeding (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateProceeding, Start Timer: 6 msecs 0924095418|sip |3|177|407 challenge received 0924095418|sip |2|177|doDnsNaptrLookup: '192.168.1.1' is an IP, bailing 0924095418|sip |2|177|SipOnEvCallNewState 10edbff0,10b42844 2,Proceeding 0924095418|so |2|177|[SoMediaSessC]: MsgPpsCallStateInd Usr(0x10b42844) Net(0x10edbff0) St(3) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateProceeding) - Event (SoMediaSessEvLclNetProceeding) 0924095418|so |2|177|[SoNcasC]: Receiving MsgType 0x848 0924095418|sip |2|177|SipOnEvCallNewState 10edbff0,10b42844 3,NULL 0924095418|so |2|177|[SoMediaSessC]: MsgPpsCallStateInd Usr(0x10b42844) Net(0x10edbff0) St(4) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateProceeding) - Event (SoMediaSessEvLclNetRingback) 0924095418|so |2|177|soToneStop: Stopping host tone 0x10b892a4 (dial). [0x0] 0924095418|so |2|177|soToneStop: Stopping host tone 0x10b892a4 (dial). [0x0] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateRingBack (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateRingBack, Start Timer: 6 msecs 0924095418|sip |2|177|SipOnEvNewCodec 101a8c0,0 PCMU/8000 18536,2232 ptime=0,dir 2 index 0 0924095418|so |2|177|[SoMediaSessC]: [0x10b42844] pps[0x10edbff0] i[0x0] d[2] p[0] pn[0] lp[2232] rip[192.168.1.1] rp[18536] dp[30333] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateRingBack) - Event (SoMediaSessEvLclNetMediaInfoInd) 0924095418|sip |2|177|SipOnEvNewCodec 101a8c0,101 telephone-event/8000 18536,2232 ptime=0,dir 2 index 0 0924095418|so |2|177|soStreamAddrSet DestIP: local RTP port=2232 dest IP=192.168.1.1 dest port=18536 (10B359C0) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: receive-only (10B359C0) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|[SoStreamC]: 1st rtp pkt rx now. 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: send-and-receive (10B359C0) 0924095418|so |2|177|[SoMediaSessC]: [0x10b42844] pps[0x10edbff0] i[0x0] d[2] p[120] pn[6] lp[2232] rip[192.168.1.1] rp[18536] dp[101] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateRingBack) - Event (SoMediaSessEvLclNetMediaInfoInd) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: receive-only (10B359C0) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: send-and-receive (10B359C0) 0924095418|so |2|177|[SoStreamC]: 1st rtp pkt tx now. 0924095423|sip |2|177|SipOnEvNewCodec 101a8c0,0 PCMU/8000 18536,2232 ptime=0,dir 2 index 0 0924095423|so |2|177|[SoMediaSessC]: [0x10b42844] pps[0x10edbff0] i[0x0] d[2] p[0] pn[0] lp[2232] rip[192.168.1.1] rp[18536] dp[30333] 0924095423|so |2|177|[SoMediaSessC]: Ignoring Media Info - No Critical Change Detected 0924095423|sip |2|177|SipOnEvNewCodec 101a8c0,101 telephone-event/8000 18536,2232 ptime=0,dir 2 index 0 0924095423|so
Re: [asterisk-users] Polycom 501 Phones Rebooting
Douglas Garstang wrote: Wow. Polycom phones are STILL doing that? I haven't been involved with Polycom phones since before January, and it was a problem back then too. Jeez... Doug -- he's using 1.6.7 firmware. -Stephen- ___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Polycom 501 Phones Rebooting
Hi, Greg: I really can't recommend upgrading to a 2.x firmware highly enough. Many people had the spontaneous reboot problems and I think they were all solved by going to current 2.x firmware. -Stephen- Gregory Boehnlein wrote: Finally, press and hold all 4 arrow keys until the phone bleeps, then capture the log files dumped to your provisioning server one last time. If the problem's not obvious from reading the logs, escalate these logs to your Polycom reseller and ask them to open a ticket with Polycom on your behalf. Of course they might recommend upgrading to 2.x ;-) Well, here is what I got. Have no idea how to read these.. 0924095418|so |2|177|soToneStop: Stopping host tone 0x10b892a4 (dial). [0x0] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateSetup (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateSetup, Start Timer: 1000 msecs 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateOverlap (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateOverlap, Start Timer: 3 msecs 0924095418|sip |2|177|SipCallMake 8605654321 0924095418|sip |2|177|doDnsNaptrLookup: '192.168.1.1' is an IP, bailing 0924095418|sip |2|177|SipOnEvCallNewState 10edbff0,10b42844 2,Proceeding 0924095418|so |2|177|[SoMediaSessC]: MsgPpsCallStateInd Usr(0x10b42844) Net(0x10edbff0) St(3) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateOverlap) - Event (SoMediaSessEvLclNetProceeding) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateProceeding (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateProceeding, Start Timer: 6 msecs 0924095418|sip |3|177|407 challenge received 0924095418|sip |2|177|doDnsNaptrLookup: '192.168.1.1' is an IP, bailing 0924095418|sip |2|177|SipOnEvCallNewState 10edbff0,10b42844 2,Proceeding 0924095418|so |2|177|[SoMediaSessC]: MsgPpsCallStateInd Usr(0x10b42844) Net(0x10edbff0) St(3) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateProceeding) - Event (SoMediaSessEvLclNetProceeding) 0924095418|so |2|177|[SoNcasC]: Receiving MsgType 0x848 0924095418|sip |2|177|SipOnEvCallNewState 10edbff0,10b42844 3,NULL 0924095418|so |2|177|[SoMediaSessC]: MsgPpsCallStateInd Usr(0x10b42844) Net(0x10edbff0) St(4) 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateProceeding) - Event (SoMediaSessEvLclNetRingback) 0924095418|so |2|177|soToneStop: Stopping host tone 0x10b892a4 (dial). [0x0] 0924095418|so |2|177|soToneStop: Stopping host tone 0x10b892a4 (dial). [0x0] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - New State: SoMediaSessStateRingBack (Real) 0924095418|so |2|177|[SoMediaSessC]: 0x10b42844: State: SoMediaSessStateRingBack, Start Timer: 6 msecs 0924095418|sip |2|177|SipOnEvNewCodec 101a8c0,0 PCMU/8000 18536,2232 ptime=0,dir 2 index 0 0924095418|so |2|177|[SoMediaSessC]: [0x10b42844] pps[0x10edbff0] i[0x0] d[2] p[0] pn[0] lp[2232] rip[192.168.1.1] rp[18536] dp[30333] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateRingBack) - Event (SoMediaSessEvLclNetMediaInfoInd) 0924095418|sip |2|177|SipOnEvNewCodec 101a8c0,101 telephone-event/8000 18536,2232 ptime=0,dir 2 index 0 0924095418|so |2|177|soStreamAddrSet DestIP: local RTP port=2232 dest IP=192.168.1.1 dest port=18536 (10B359C0) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: receive-only (10B359C0) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|[SoStreamC]: 1st rtp pkt rx now. 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: send-and-receive (10B359C0) 0924095418|so |2|177|[SoMediaSessC]: [0x10b42844] pps[0x10edbff0] i[0x0] d[2] p[120] pn[6] lp[2232] rip[192.168.1.1] rp[18536] dp[101] 0924095418|so |2|177|[SoMediaSessC]: Call (0x10b42844) - State (SoMediaSessStateRingBack) - Event (SoMediaSessEvLclNetMediaInfoInd) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: receive-only (10B359C0) 0924095418|so |2|177|soStreamNetConn attempt to re-connect RTP stream to network 0924095418|so |2|177|soStreamNetConn attempt to re-open RTCP port 0924095418|so |2|177|soStreamLclTermConn: send-and-receive (10B359C0) 0924095418|so |2|177|[SoStreamC]: 1st rtp pkt tx now. 0924095423|sip |2|177|SipOnEvNewCodec 101a8c0,0 PCMU/8000 18536,2232 ptime=0,dir 2 index 0 0924095423|so |2|177|[SoMediaSessC]:
Re: [asterisk-users] Polycom 501 Phones Rebooting
Gregory Boehnlein [EMAIL PROTECTED] wrote: Hello, At one of our locations, we have started to see Polycom 501s (running 1.6.7 firmware) randomly reboot. We have taken packet traces of the phones to determine if there is something odd in the Layer 2 or 3 of the network that might cause it, and have not seen anything strange. There are no errors on the ports. This appears to be affecting POE powered as well as AC powered phones. The Polycom Logs for the phones don't seem to provide any clarity. Where should I troubleshoot this next? You've probably already done all of this, but just in case In the SIP.CFG file set the values from 4 to 2 for the following applications' logging levels: 1. log.level.change.so 2. log.level.change.sip Remove all logs from your provisioning server. Then reboot the phone that you're testing with so that it takes the new logging levels. Save the log files generated from the clean boot for information, and for comparison purposes. Wait for the phone to experience the problem and reboot. It will write diagnostic information about the crash to the provisioning server. Capture and move those logs (if you're using TFTP logs keep getting overwritten) Finally, press and hold all 4 arrow keys until the phone bleeps, then capture the log files dumped to your provisioning server one last time. If the problem's not obvious from reading the logs, escalate these logs to your Polycom reseller and ask them to open a ticket with Polycom on your behalf. Of course they might recommend upgrading to 2.x ;-) -Darren -- Darren Nickerson Senior Sales Support Engineer Telephony Depot www.telephonydepot.com +1.215.825.8710 ext 8106 (office) +1.215.243.8335 (fax) ___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Polycom 501 Phones Rebooting
On 9/21/07, Gregory Boehnlein [EMAIL PROTECTED] wrote: Hello, At one of our locations, we have started to see Polycom 501s (running 1.6.7 firmware) randomly reboot. We have taken packet traces of the phones to determine if there is something odd in the Layer 2 or 3 of the network that might cause it, and have not seen anything strange. There are no errors on the ports. This appears to be affecting POE powered as well as AC powered phones. The Polycom Logs for the phones don't seem to provide any clarity. Where should I troubleshoot this next? Greg - Is the phone's app log uploaded back up to the central provisioning server showing anything of value? -- Bird's The Word Technologies, Inc. http://www.btwtech.com/ ___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Polycom 501 Phones Rebooting
On Fri, 2007-09-21 at 17:36 -0400, Gregory Boehnlein wrote: At one of our locations, we have started to see Polycom 501s (running 1.6.7 firmware) randomly reboot. Upgrade the firmware on the phones. I see this all the time with the Polycom phones, especially the IP-430 and IP-330 models. At least 90% of the time, upgrading the firmware solves the problem. -Jared ___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Polycom 501 Phones Rebooting
Wow. Polycom phones are STILL doing that? I haven't been involved with Polycom phones since before January, and it was a problem back then too. Jeez - Original Message From: Gregory Boehnlein [EMAIL PROTECTED] To: asterisk-users@lists.digium.com Sent: Friday, September 21, 2007 2:36:02 PM Subject: [asterisk-users] Polycom 501 Phones Rebooting Hello, At one of our locations, we have started to see Polycom 501s (running 1.6.7 firmware) randomly reboot. We have taken packet traces of the phones to determine if there is something odd in the Layer 2 or 3 of the network that might cause it, and have not seen anything strange. There are no errors on the ports. This appears to be affecting POE powered as well as AC powered phones. The Polycom Logs for the phones don't seem to provide any clarity. Where should I troubleshoot this next? ___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Polycom 501 Phones Rebooting
Where should I troubleshoot this next? You've probably already done all of this, but just in case [deleted] Darren, We have NOT done that yet, but I'm getting right on it. This is exactly the type of information that I needed! THANK YOU! ___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Polycom 501 Phones Rebooting
On Fri, 2007-09-21 at 17:36 -0400, Gregory Boehnlein wrote: At one of our locations, we have started to see Polycom 501s (running 1.6.7 firmware) randomly reboot. Upgrade the firmware on the phones. I see this all the time with the Polycom phones, especially the IP-430 and IP-330 models. At least 90% of the time, upgrading the firmware solves the problem. Jared, I have over 350 IP 501s deployed, running the exact same firmware. This particular network segment is the ONLY one where this problem exists, which leads me to believe it may be a layer 2 or layer 3 issue. I'm going to follow the earlier responders suggestions about getting more intense log dumps and see what I can find out. There has to be a reason that this is happening.. It's just a matter of finding it out! :) ___ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
