[Freeswitch-users] calls ending with MEDIA_TIMEOUT

Fri Jul 23 10:23:34 PDT 2010

Thanks Anthony, that seems to have fixed my issue. 

Dan- 
From: "Anthony Minessale" <anthony.minessale at gmail.com> 
To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org> 
Sent: Thursday, July 22, 2010 10:22:38 AM 
Subject: Re: [Freeswitch-users] calls ending with MEDIA_TIMEOUT 

try setting the sofia profile param disable-rtp-auto-adjust to true 
or export disable_rtp_auto_adjust=true in the dialplan on a per call basis. 

On Thu, Jul 22, 2010 at 10:10 AM, Dan < freeswitch-users at digitaldan.com > wrote: 

The tcpdump was fairly large, I filtered it based on the ip addresses of the freeswitch box and the media gateway. The packets between them were just noise: 

41 3.194979 192.168.24.22 ssh 192.168.24.19 59344 SSH Encrypted response packet len=176 
42 3.194980 192.168.24.22 ssh 192.168.24.19 59344 SSH [TCP Out-Of-Order] Encrypted response packet len=176 
43 3.195069 192.168.24.19 59344 192.168.24.22 ssh TCP 59344 > ssh [ACK] Seq=1 Ack=561 Win=501 Len=0 TSV=4130917090 TSER=4108877879 

From: "Peder" < peder at networkoblivion.com > 

To: "FreeSWITCH Users Help" < freeswitch-users at lists.freeswitch.org > 
Sent: Thursday, July 22, 2010 8:15:44 AM 

Subject: Re: [Freeswitch-users] calls ending with MEDIA_TIMEOUT 

In the good call, what happens between packets 40 and 44? You left that part out. Hard to analyze a trace with only some of the packets…. 

From: freeswitch-users-bounces at lists.freeswitch.org [mailto: freeswitch-users-bounces at lists.freeswitch.org ] On Behalf Of Dan 
Sent: Thursday, July 22, 2010 9:00 AM 
To: FreeSWITCH Users Help 
Subject: Re: [Freeswitch-users] calls ending with MEDIA_TIMEOUT 

I appologize if I'm not making sense or barking up the wrong tree, I'm hoping that this will be obvious to someone else. 

I'm comparing a call that succeeds and one that times out. 

With both calls I see that after the initial invite from the far end device, freeswitch sends a 180 and attempts to reach the device's advertised RTP port before sending a 200 OK. 

With the call that times-out its interesting that it sends these two packets ( src port 27176 to dest port 27176) but then send 2 more with the same source port but to a different destination port that I don't see negotiated anywhere (src port 27176 to dest port 19488). The call that succeedes (see below below) does not have this behavior. 

The boxes have full visibility to each other, there is no nat-ing or firewalls between the two internal networks (just a router). Any thoughts? 

Media timeout call 

No. Time Source Source Port Destination Dest Port Protocol Info 
1 0.000000 192.168.21.4 56397 192.168.24.22 onscreen SIP/SDP Request: INVITE sip:3103568788 at 192.168.24.22:5080 , with session description 
2 0.000367 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying 
3 0.000369 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying 
4 0.007171 192.168.24.22 27176 192.168.24.22 27176 UDP Source port: 27176 Destination port: 27176 
5 0.017542 192.168.24.22 27176 192.168.24.22 27176 UDP Source port: 27176 Destination port: 27176 
6 0.017613 192.168.24.22 27176 192.168.21.4 19488 UDP Source port: 27176 Destination port: 19488 
7 0.017616 192.168.24.22 27176 192.168.21.4 19488 UDP Source port: 27176 Destination port: 19488 
8 0.017809 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description 
9 0.017810 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description 
10 0.020167 192.168.21.4 56397 192.168.24.22 onscreen SIP Request: ACK sip:3103568788 at 192.168.24.22:5080;transport=udp 
11 0.186076 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10837, Time=1575317876, Mark 
12 0.186121 192.168.24.22 27176 192.168.21.4 16752 RTP PT=ITU-T G.711 PCMU, SSRC=0x33CF6C8, Seq=5202, Time=240, Mark 
13 0.186126 192.168.24.22 27176 192.168.21.4 16752 RTP PT=ITU-T G.711 PCMU, SSRC=0x33CF6C8, Seq=5202, Time=240, Mark 
14 0.216085 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10838, Time=1575318116 
15 0.246105 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10839, Time=1575318356 
16 0.276137 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10840, Time=1575318596 
17 0.306164 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10841, Time=1575318836 
18 0.336178 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10842, Time=1575319076 
19 0.366208 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10843, Time=1575319316 
20 0.396232 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10844, Time=1575319556 
21 0.426256 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10845, Time=1575319796 
22 0.456276 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10846, Time=1575320036 
23 0.486311 192.168.21.4 16752 192.168.24.22 27176 RTP PT=ITU-T G.711 PCMU, SSRC=0x21B51504, Seq=10847, Time=1575320276 
.....many more of 192.168.21.4 to 192.168.24.22 
57 1.477101 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable) 
58 1.477101 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable) 
.... RTP pattern repeats 

Good Call 

No. Time Source Src Port Destination DesT Port Protocol Info 
7 3.170800 192.168.21.4 57394 192.168.24.22 onscreen SIP/SDP Request: INVITE sip:3103568788 at 192.168.24.22:5080 , with session description 
8 3.171165 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying 
9 3.171171 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying 
36 3.185636 192.168.24.22 19472 192.168.24.22 19472 UDP Source port: 19472 Destination port: 19472 
40 3.194949 192.168.24.22 19472 192.168.24.22 19472 UDP Source port: 19472 Destination port: 19472 
44 3.195565 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description 
45 3.195568 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description 
46 3.197975 192.168.21.4 57394 192.168.24.22 onscreen SIP Request: ACK sip:3103568788 at 192.168.24.22:5080;transport=udp 
140 3.320438 192.168.24.22 19472 192.168.21.4 17148 RTP PT=ITU-T G.711 PCMU, SSRC=0x287D4E7, Seq=11773, Time=240, Mark 
141 3.320441 192.168.24.22 19472 192.168.21.4 17148 RTP PT=ITU-T G.711 PCMU, SSRC=0x287D4E7, Seq=11773, Time=240, Mark 
192 3.450347 192.168.21.4 17148 192.168.24.22 19472 RTP PT=ITU-T G.711 PCMU, SSRC=0x6B1504, Seq=36119, Time=96783955, Mark 
199 3.480344 192.168.21.4 17148 192.168.24.22 19472 RTP PT=ITU-T G.711 PCMU, SSRC=0x6B1504, Seq=36120, Time=96784195 
200 3.480393 192.168.24.22 19472 192.168.21.4 17148 RTP PT=ITU-T G.711 PCMU, SSRC=0x287D4E7, Seq=11774, Time=480 
201 3.480395 192.168.24.22 19472 192.168.21.4 17148 RTP PT=ITU-T G.711 PCMU, SSRC=0x287D4E7, Seq=11774, Time=480 
213 3.510382 192.168.21.4 17148 192.168.24.22 19472 RTP PT=ITU-T G.711 PCMU, SSRC=0x6B1504, Seq=36121, Time=96784435 
..... RTP pattern repeats for duration of call 

From: "Dan" < freeswitch-users at digitaldan.com > 
To: "FreeSWITCH Users Help" < freeswitch-users at lists.freeswitch.org > 
Sent: Wednesday, July 21, 2010 9:14:01 AM 
Subject: Re: [Freeswitch-users] calls ending with MEDIA_TIMEOUT 

Gotcha, if I sort wireshark by source freeswitch sends 2 RTP packets and then a handful if ICMP errors, this pattern repeats for the entire call (2 voice packets and 5+ icmp errors). 

192.168.24.22 = freeswitch 
192.168.21.4 = endpoint 

ID Time Source Src Port Destination Dest Port 
12 0.186121 192.168.24.22 27176 192.168.21.4 16752 RTP PT=ITU-T G.711 PCMU, SSRC=0x33CF6C8, Seq=5202, Time=240, Mark 
13 0.186126 192.168.24.22 27176 192.168.21.4 16752 RTP PT=ITU-T G.711 PCMU, SSRC=0x33CF6C8, Seq=5202, Time=240, Mark 
57 1.477101 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable) 
92 2.467948 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable) 
93 2.467949 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable) 
194 5.465388 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable) 

The ICMP erros have the ports reversed, is this normal ? 

Thanks, 
Dan- 

From: "Brian West" < brian at freeswitch.org > 
To: "FreeSWITCH Users Help" < freeswitch-users at lists.freeswitch.org > 
Sent: Wednesday, July 21, 2010 8:30:40 AM 
Subject: Re: [Freeswitch-users] calls ending with MEDIA_TIMEOUT 

NO that would mean that it was sending RTP to that IP and the firewall returned and ICMP port unreachable. 

/b 

On Jul 21, 2010, at 8:43 AM, Dan wrote: 

> I was able to pull the box out yesterday and try some load testing under tcpdump. It looks like under load freeswitch was trying to ping the far end RTP port which was failing: 
> 
> 57 1.477101 192.168.24.22 192.168.21.4 ICMP Destination unreachable (Port unreachable) 
> 
> I'm guessing this is part of auto nat detection? Is this a tunable option? I don't need stun/nat functionality at this point so I'm running freeswitch with the -nonat flag right now to see if its playing a part here. 
> 
> I have the tcpdump of a call if anyone is interested. 
> 
> Thanks 
> Dan- 

_______________________________________________ 
FreeSWITCH-users mailing list 
FreeSWITCH-users at lists.freeswitch.org 
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users 
UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users 
http://www.freeswitch.org 

_______________________________________________ 
FreeSWITCH-users mailing list 
FreeSWITCH-users at lists.freeswitch.org 
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users 
UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users 
http://www.freeswitch.org 
_______________________________________________ 
FreeSWITCH-users mailing list 
FreeSWITCH-users at lists.freeswitch.org 
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users 
UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users 
http://www.freeswitch.org 

_______________________________________________ 
FreeSWITCH-users mailing list 
FreeSWITCH-users at lists.freeswitch.org 
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users 
UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users 
http://www.freeswitch.org 

-- 
Anthony Minessale II 

FreeSWITCH http://www.freeswitch.org/ 
ClueCon http://www.cluecon.com/ 
Twitter: http://twitter.com/FreeSWITCH_wire 

AIM: anthm 
MSN:anthony_minessale at hotmail.com 
GTALK/JABBER/ PAYPAL:anthony.minessale at gmail.com 
IRC: irc.freenode.net #freeswitch 

FreeSWITCH Developer Conference 
sip:888 at conference.freeswitch.org 
googletalk:conf+888 at conference.freeswitch.org 
pstn:+19193869900 

_______________________________________________ 
FreeSWITCH-users mailing list 
FreeSWITCH-users at lists.freeswitch.org 
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users 
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users 
http://www.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100723/1e96e631/attachment-0001.html 