I'm testing out a Polycom 8002 that crashes quite frequently with an "Assert memory.c" error, which Polycom says is typical on this handset when there are multiple packets being sent that confuse the phone.
The phone will crash 30 seconds or so after being booted up. A tcpdump from the router's wireless interface shows that there are several SIP OPTIONS packets being sent around this time. The traffic looks like: Phone -> Server: "Request: OPTIONS ..." Server -> Phone: "Request: OPTIONS ...;x-sipX-nonat;sipXecs-CallDest=INT" Server -> Phone: "Request: OPTIONS ...;x-sipX-nonat;sipXecs-CallDest=INT" (resent) Server -> Phone: "Request: OPTIONS ...;x-sipX-nonat;sipXecs-CallDest=INT" (resent) Server -> Phone: "Request: OPTIONS ...;x-sipX-nonat;sipXecs-CallDest=INT" (resent) Server -> Phone: TCP SYN Phone -> Server: "Request: OPTIONS ..." (resent) Server -> Phone: "Status: 100 Trying" Server -> Phone: "Status: 200 OK" Then a few more TCP SYN packets to the phone which I think has crashed at that point. If I look at the flow in the SIP Viewer, the phone sends OPTIONS to the proxy, the proxy sends OPTIONS to the registrar, the registrar sends back "302 Moved Temporarily", and the registrar sends the "nonat" packets as above. So does anyone know if this is normal SIP traffic? Any idea why these packets are being resent? -- _____________ David Minor _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
