Miguel Costa Posted February 17, 2011 Report Share Posted February 17, 2011 My users have been complaining of constant disconnects the last week or so. I'm also getting User disconnect emails to my admin account from the PBX. Here's the email content - any ideas what would cause this? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> One side of the call between sip:442095058@sbc.voipdnsservers.com;user=phone and sip:9417804421@sbc.voipdnsservers.com;user=phone did not receive media for 2.5 s and the other side of the call disconnected the call. The address of the other side was 76.79.172.170 (User-Agent=Linksys/SPA941-5.1.8). You may use this email as hint for a potential problem. The SIP messages are attached. Rx: udp:76.79.172.170:31537 (756 bytes) INVITE sip:9417804421@pbxserver.com SIP/2.0 Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-f6f91006 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com> Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 101 INVITE Max-Forwards: 70 Contact: "149" <sip:149@192.168.5.121:5060> Expires: 240 User-Agent: Linksys/SPA941-5.1.8 Content-Length: 215 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 10341343 10341343 IN IP4 192.168.5.121 s=- c=IN IP4 192.168.5.121 t=0 0 m=audio 16468 RTP/AVP 18 101 a=rtpmap:18 G729a/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv Tx: udp:76.79.172.170:31537 (328 bytes) SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-f6f91006;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 101 INVITE Content-Length: 0 Tx: udp:76.79.172.170:31537 (542 bytes) SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-f6f91006;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 101 INVITE User-Agent: pbxnsip-PBX/4.0.1.3499 WWW-Authenticate: Digest realm="pbxserver.com",nonce="6de691eb06c88b47d08550d9cfdc5303",domain="sip:9417804421@pbxserver.com",algorithm=MD5 Content-Length: 0 Rx: udp:76.79.172.170:31537 (419 bytes) ACK sip:9417804421@pbxserver.com SIP/2.0 Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-f6f91006 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 101 ACK Max-Forwards: 70 Contact: "149" <sip:149@192.168.5.121:5060> User-Agent: Linksys/SPA941-5.1.8 Content-Length: 0 Tx: udp:76.79.172.170:31537 (327 bytes) SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Content-Length: 0 Tx: udp:76.79.172.170:31537 (859 bytes) SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tx: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Tr: udp:76.79.172.170:31537 (845 bytes) SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.5.121:5060;branch=z9hG4bK-c3f8ef2;rport=31537;received=76.79.172.170 From: "149" <sip:149@pbxserver.com>;tag=f2ec483d80c68b45o0 To: <sip:9417804421@pbxserver.com>;tag=5b3fa43d56 Call-ID: 40e1659d-d3e50d65@192.168.5.121 CSeq: 102 INVITE Contact: <sip:149@74.208.77.157:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.0.1.3499 Content-Type: application/sdp Content-Length: 266 v=0 o=- 55038 55038 IN IP4 74.208.77.157 s=- c=IN IP4 74.208.77.157 t=0 0 m=audio 55164 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:30 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv Quote Link to comment Share on other sites More sharing options...
gotvoip Posted February 28, 2011 Report Share Posted February 28, 2011 Looks like the service provider is not sending an ACK back to the 200 OKs. You see the Tr in the log file? That means we sent the 200 OK and resent it and not response so the call is dropping since there is no ACK coming back. Did you open up a ticket with your provider? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 28, 2011 Report Share Posted February 28, 2011 Looks to me more like trouble with the phone. While is still answers the challenge (401), it does not response to the 200 after the call connects. This does not look like a problem with the firewall, because the 401 obviously makes it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.