<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>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. <br><br>I'm comparing a call that succeeds and one that times out. <br><br>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. <br><br>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.<br><br>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?<br><br>Media timeout call<br><br>No. Time Source Source Port Destination Dest Port Protocol Info<br> 1 0.000000 192.168.21.4 56397 192.168.24.22 onscreen SIP/SDP Request: INVITE sip:3103568788@192.168.24.22:5080, with session description<br> 2 0.000367 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying<br> 3 0.000369 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying<br> 4 0.007171 192.168.24.22 27176 192.168.24.22 27176 UDP Source port: 27176 Destination port: 27176<br> 5 0.017542 192.168.24.22 27176 192.168.24.22 27176 UDP Source port: 27176 Destination port: 27176<br> 6 0.017613 192.168.24.22 27176 192.168.21.4 19488 UDP Source port: 27176 Destination port: 19488<br> 7 0.017616 192.168.24.22 27176 192.168.21.4 19488 UDP Source port: 27176 Destination port: 19488<br> 8 0.017809 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description<br> 9 0.017810 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description<br> 10 0.020167 192.168.21.4 56397 192.168.24.22 onscreen SIP Request: ACK sip:3103568788@192.168.24.22:5080;transport=udp<br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> .....many more of 192.168.21.4 to 192.168.24.22<br> 57 1.477101 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable)<br> 58 1.477101 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable)<br> .... RTP pattern repeats<br><br><br>Good Call<br><br>No. Time Source Src Port Destination DesT Port Protocol Info<br> 7 3.170800 192.168.21.4 57394 192.168.24.22 onscreen SIP/SDP Request: INVITE sip:3103568788@192.168.24.22:5080, with session description<br> 8 3.171165 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying<br> 9 3.171171 192.168.24.22 onscreen 192.168.21.4 sip SIP Status: 100 Trying<br> 36 3.185636 192.168.24.22 19472 192.168.24.22 19472 UDP Source port: 19472 Destination port: 19472<br> 40 3.194949 192.168.24.22 19472 192.168.24.22 19472 UDP Source port: 19472 Destination port: 19472<br> 44 3.195565 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description<br> 45 3.195568 192.168.24.22 onscreen 192.168.21.4 sip SIP/SDP Status: 200 OK, with session description<br> 46 3.197975 192.168.21.4 57394 192.168.24.22 onscreen SIP Request: ACK sip:3103568788@192.168.24.22:5080;transport=udp<br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> 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 <br> ..... RTP pattern repeats for duration of call<br><hr id="zwchr"><b>From: </b>"Dan" <freeswitch-users@digitaldan.com><br><b>To: </b>"FreeSWITCH Users Help" <freeswitch-users@lists.freeswitch.org><br><b>Sent: </b>Wednesday, July 21, 2010 9:14:01 AM<br><b>Subject: </b>Re: [Freeswitch-users] calls ending with MEDIA_TIMEOUT<br><br><mce:style><!--
p { margin: 0; }
--></mce:style><mce:style mce_bogus="1"><!--
p { margin: 0; }
--></mce:style><mce:style mce_bogus="1"><!--
p { margin: 0; }
--></mce:style><style mce_bogus="1"><!--
p { margin: 0; }
--></style><div style="font-family: Times New Roman; font-size: 12pt; color: rgb(0, 0, 0);" mce_style="font-family: Times New Roman; font-size: 12pt; color: #000000">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). <br><br> 192.168.24.22 = freeswitch<br>192.168.21.4 = endpoint<br><br>ID Time Source Src Port Destination Dest Port <br>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 <br>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 <br>57 1.477101 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable)<br>92 2.467948 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable)<br>93 2.467949 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable)<br>194 5.465388 192.168.24.22 16752 192.168.21.4 27176 ICMP Destination unreachable (Port unreachable)<br><br><br>The ICMP erros have the ports reversed, is this normal ?<br><br>Thanks,<br>Dan-<br><hr id="zwchr"><b>From: </b>"Brian West" <brian@freeswitch.org><br><b>To: </b>"FreeSWITCH Users Help" <freeswitch-users@lists.freeswitch.org><br><b>Sent: </b>Wednesday, July 21, 2010 8:30:40 AM<br><b>Subject: </b>Re: [Freeswitch-users] calls ending with MEDIA_TIMEOUT<br><br>NO that would mean that it was sending RTP to that IP and the firewall returned and ICMP port unreachable.<br><br>/b<br><br>On Jul 21, 2010, at 8:43 AM, Dan wrote:<br><br>> 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:<br>> <br>> 57 1.477101 192.168.24.22 192.168.21.4 ICMP Destination unreachable (Port unreachable)<br>> <br>> 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. <br>> <br>> I have the tcpdump of a call if anyone is interested.<br>> <br>> Thanks<br>> Dan-<br><br><br>_______________________________________________<br>FreeSWITCH-users mailing list<br>FreeSWITCH-users@lists.freeswitch.org<br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org</div><br>_______________________________________________<br>FreeSWITCH-users mailing list<br>FreeSWITCH-users@lists.freeswitch.org<br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org</div></body></html>