Jump to content

Phone calls disconnected now


eyeless
 Share

Recommended Posts

Hi,

 

Tried to post in the Snom phones forum section, but could not find out any way in which to do so as I could not login there no matter what ... (but not sure this problem is about the Snom phones after all).

 

Since some weeks back (before we upgraded to the latest version of the SnomOne server) and continuing now after upgrade, phone calls are dropped every now and then (seems like 1 in 5 calls during the day) on all types of Snom phones. It is not exactly acceptable ... . This has only started to happen recently (as far as I can make out). Since the latest version of SnomOne started to make e-mail functionality working, I today also received a message when a call was dropped, but when I later today got a call from one of the users which also got dropped (I could not hear her, but she could hear me - voice out got cut), I received no message about this. So we have all sorts of problems going on here every hour.

 

Here's the full log from the e-mail reporting the dropped call - (what phone and firmware that is used seems to be of no relevance as some are updated and some are not and all have problems now).

 

The call between sip:031109430@opensips.teleman.com;user=phone and sip:0708442407@sip.teleman.com;user=phone has been disconnected because of media timeout (120 seconds), 390/7393 packets have been received/sent

2011/6/20 08:30:06 Rx: udp:213.131.156.66:0 (1055 bytes)

INVITE sip:031109430@10.0.3.10:5060;transport=udp;line=c81e728d SIP/2.0

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKd1eb.5655e011.0

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-acf0121eefbbdd47-1---d8754z-;rport=5060

Max-Forwards: 69

Contact: <sip:0708442407@212.3.0.165:5060;transport=udp>

To: "031109430"<sip:031109430@opensips.teleman.com;user=phone>

From: "0708442407"<sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 1 INVITE

Allow: INVITE, ACK, BYE, CANCEL

Content-Type: application/sdp

User-Agent: LEICA-1.8.31.4

X-Ecan: On

Content-Length: 352

 

v=0

o=- 691105141 0 IN IP4 213.50.90.4

s=-

c=IN IP4 88.131.158.234

t=0 0

m=audio 40312 RTP/AVP 8 0 18 101

a=fmtp:18 annexb=yes

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sqn: 0

a=cdsc: 1 audio RTP/AVP 8

a=cdsc: 2 image udptl t38

a=cpar:T38FaxUdpEC:t38UDPRedundancy

a=cpar:T38FaxVersion:0

a=cpar:T38MaxBitRate:14400

a=sendrecv

2011/6/20 08:30:06 Tx: udp:213.131.156.66:5060 (485 bytes)

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKd1eb.5655e011.0

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-acf0121eefbbdd47-1---d8754z-;rport=5060

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

From: "0708442407" <sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

To: "031109430" <sip:031109430@opensips.teleman.com;user=phone>;tag=5576c1abba

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 1 INVITE

Content-Length: 0

 

2011/6/20 08:30:06 Tx: udp:213.131.156.66:5060 (1071 bytes)

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKd1eb.5655e011.0

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-acf0121eefbbdd47-1---d8754z-;rport=5060

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

From: "0708442407" <sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

To: "031109430" <sip:031109430@opensips.teleman.com;user=phone>;tag=5576c1abba

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 1 INVITE

Contact: <sip:031109430@10.0.3.10:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snom-PBX/2011-4.2.0.3981

Content-Type: application/sdp

Content-Length: 302

 

v=0

o=- 653521262 653521262 IN IP4 10.0.3.10

s=-

c=IN IP4 10.0.3.10

t=0 0

m=audio 57840 RTP/AVP 0 8 18 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=rtcp-xr:rcvr-rtt=all voip-metrics

a=sendrecv

2011/6/20 08:30:26 Tx: udp:213.131.156.66:5060 (1057 bytes)

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKd1eb.5655e011.0

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-acf0121eefbbdd47-1---d8754z-;rport=5060

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

From: "0708442407" <sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

To: "031109430" <sip:031109430@opensips.teleman.com;user=phone>;tag=5576c1abba

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 1 INVITE

Contact: <sip:031109430@10.0.3.10:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snom-PBX/2011-4.2.0.3981

Content-Type: application/sdp

Content-Length: 302

 

v=0

o=- 653521262 653521262 IN IP4 10.0.3.10

s=-

c=IN IP4 10.0.3.10

t=0 0

m=audio 57840 RTP/AVP 0 8 18 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=rtcp-xr:rcvr-rtt=all voip-metrics

a=sendrecv

2011/6/20 08:30:26 Rx: udp:213.131.156.66:0 (613 bytes)

ACK sip:031109430@10.0.3.10:5060;transport=udp SIP/2.0

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKd1eb.5655e011.2

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-23e25602506f0c2b-1---d8754z-;rport=5060

Max-Forwards: 69

Contact: <sip:0708442407@212.3.0.165:5060;transport=udp>

To: "031109430"<sip:031109430@opensips.teleman.com;user=phone>;tag=5576c1abba

From: "0708442407"<sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 1 ACK

Content-Length: 0

P-hint: rr-enforced

 

2011/6/20 08:30:26 Rx: udp:213.131.156.66:0 (1050 bytes)

INVITE sip:031109430@10.0.3.10:5060;transport=udp SIP/2.0

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKa1eb.9d1e5d45.0

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-4e5cd45fb2852121-1---d8754z-;rport=5060

Max-Forwards: 69

Contact: <sip:0708442407@212.3.0.165:5060;transport=udp>

To: "031109430"<sip:031109430@opensips.teleman.com;user=phone>;tag=5576c1abba

From: "0708442407"<sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 2 INVITE

Allow: INVITE, ACK, BYE, CANCEL

Content-Type: application/sdp

User-Agent: LEICA-1.8.31.4

X-Ecan: On

Content-Length: 325

P-hint: rr-enforced

 

v=0

o=- 691105141 1 IN IP4 213.50.90.4

s=-

c=IN IP4 88.131.158.234

t=0 0

m=audio 40312 RTP/AVP 0 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sqn: 0

a=cdsc: 1 audio RTP/AVP 0

a=cdsc: 2 image udptl t38

a=cpar:T38FaxUdpEC:t38UDPRedundancy

a=cpar:T38FaxVersion:0

a=cpar:T38MaxBitRate:14400

a=sendrecv

2011/6/20 08:30:26 Tx: udp:213.131.156.66:5060 (986 bytes)

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKa1eb.9d1e5d45.0

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-4e5cd45fb2852121-1---d8754z-;rport=5060

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

From: "0708442407" <sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

To: "031109430" <sip:031109430@opensips.teleman.com;user=phone>;tag=5576c1abba

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 2 INVITE

Contact: <sip:031109430@10.0.3.10:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snom-PBX/2011-4.2.0.3981

Content-Type: application/sdp

Content-Length: 231

 

v=0

o=- 653521262 653521262 IN IP4 10.0.3.10

s=-

c=IN IP4 10.0.3.10

t=0 0

m=audio 57840 RTP/AVP 0 101

a=rtpmap:0 pcmu/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=rtcp-xr:rcvr-rtt=all voip-metrics

a=sendrecv

2011/6/20 08:30:26 Rx: udp:213.131.156.66:0 (613 bytes)

ACK sip:031109430@10.0.3.10:5060;transport=udp SIP/2.0

Record-Route: <sip:213.131.156.66;lr=on;ftag=252a9b6a>

Via: SIP/2.0/UDP 213.131.156.66;branch=z9hG4bKa1eb.9d1e5d45.2

Via: SIP/2.0/UDP 212.3.0.165:5060;branch=z9hG4bK-d8754z-ee1c8d3d713a886d-1---d8754z-;rport=5060

Max-Forwards: 69

Contact: <sip:0708442407@212.3.0.165:5060;transport=udp>

To: "031109430"<sip:031109430@opensips.teleman.com;user=phone>;tag=5576c1abba

From: "0708442407"<sip:0708442407@sip.teleman.com;user=phone>;tag=252a9b6a

Call-ID: Y2YyOGYwYWQwYjcxNmZjODE4MmI5MzA1ZGM0OTY5MjU.

CSeq: 2 ACK

Content-Length: 0

P-hint: rr-enforced

Link to comment
Share on other sites

Well, there is something in the middle: 213.131.156.66. Usually, the PBX should receive registrations directly from the endpoint (and also INVITE requests). This can be the source for the trouble. What is also strange is that it advertized two different IP addresses in the SDP (213.50.90.4 and 88.131.158.234), which is also suspicious...

 

The PBX does receive traffic in the beginning. This is a good sign. There is a Re-INVITE, obviously because the other side wants to enforce symmetrical codecs. Maybe you can set the flag "Lock codec during conversation" (admin/settings/ports/rtp) to make sure that both side always talk the same codec and avoid the Re-INVITE.

Link to comment
Share on other sites

Well, there is something in the middle: 213.131.156.66. Usually, the PBX should receive registrations directly from the endpoint (and also INVITE requests). This can be the source for the trouble. What is also strange is that it advertized two different IP addresses in the SDP (213.50.90.4 and 88.131.158.234), which is also suspicious...

 

The PBX does receive traffic in the beginning. This is a good sign. There is a Re-INVITE, obviously because the other side wants to enforce symmetrical codecs. Maybe you can set the flag "Lock codec during conversation" (admin/settings/ports/rtp) to make sure that both side always talk the same codec and avoid the Re-INVITE.

 

Sounds like something to follow up on (yes, now that you point it out it is strange with the two IPs - will look into that). However, soon after I somewhat frustrated posted this, I got learn about a problem at the telephony station affecting our DSL connection (strange organisational arrangements at the location), which may be the reason why this has started to happen recently (as far as I can make out). I get back here if I find out something more of relevance as the problems might have different parts ... .

Link to comment
Share on other sites

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.

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.

 Share

×
×
  • Create New...