<div dir="ltr">Hi All,<br><br>I've been pulling my hair out over this problem and hopefully someone on this list will be able to help.<br><br>Here is the situation: <br><br>Staging:<br>I've had an asterisk staging machine set up for a couple of months in preparation for going live with a project. It is running Ubuntu Server 8.04 x86 with asterisk 1.4.17-dfsg.2ubuntu1<br>
It is connected via voxbone to the PSTN network and everything is working fine. <br><br>Production:<br>I have just installed our production box which is on a different network but is connected straight to the internet - no firewalls etc.<br>
It is running Ubuntu Server 8.04 amd64 with asterisk 1.4.17-dfsg.2ubuntu1 and an identical configuration (I copied all the files across directly as part of debugging this problem)<br>I can connect to this box via sip - and I can see the call happening but the rtp is going to the wrong destination.<br>
<br>I have be working with voxbone to try to resolve this but it looks like the asterisk server on the production machine is not responding correctly with it's RTP streams. The voxbone number is part of their new configuration where the SIP connection comes from a central SBC server (<a href="http://81.201.82.39">81.201.82.39</a>) but the RTP is transmitted to and from the local POP - in snippet below from working server (<a href="http://81.201.84.141">81.201.84.141</a>). <br>
<br>When connections are coming to the Production box it is incorrectly sending the RTP traffic to the sip originating box, i.e.81.201.82.39 instead <a href="http://81.201.84.141">81.201.84.141</a> and so no audio is working.<br>
<br>NOTE: I am using the exact same voxbone number - I have reconfigured it between tests to see if it was a problem with their new configuration but my staging machine seems to work perfectly but the production one does not.<br>
<br>Questions from this are:<br> - Could this be a problem with the AMD64 build or is this very unlikely.<br> - How can I get more information to debug this better?<br> - Could this possibly be a bug in asterisk only on AMD64 builds?<br>
<br>I've attached some traces from the calls below:<br><br>RTP data flow from working server:<br> 17.328338 <a href="http://203.206.181.174">203.206.181.174</a> -> <a href="http://81.201.84.141">81.201.84.141</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x670F1498, Seq=19838, Time=32000 <br>
17.348335 <a href="http://203.206.181.174">203.206.181.174</a> -> <a href="http://81.201.84.141">81.201.84.141</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x670F1498, Seq=19839, Time=32160 <br> 17.368336 <a href="http://203.206.181.174">203.206.181.174</a> -> <a href="http://81.201.84.141">81.201.84.141</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x670F1498, Seq=19840, Time=32320 <br>
17.388337 <a href="http://203.206.181.174">203.206.181.174</a> -> <a href="http://81.201.84.141">81.201.84.141</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x670F1498, Seq=19841, Time=32480 <br> 17.408337 <a href="http://203.206.181.174">203.206.181.174</a> -> <a href="http://81.201.84.141">81.201.84.141</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x670F1498, Seq=19842, Time=32640 <br>
17.428337 <a href="http://203.206.181.174">203.206.181.174</a> -> <a href="http://81.201.84.141">81.201.84.141</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x670F1498, Seq=19843, Time=32800 <br><br>But the RTP data from the production (non working) server sends the RTP to <a href="http://81.201.82.39">81.201.82.39</a><br>
<br> 9.673564 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> SIP/SDP Request: INVITE <a href="mailto:sip%3A61390015580@63.138.188.91">sip:61390015580@63.138.188.91</a>, with session description<br>
9.673961 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> SIP Status: 100 Trying<br> 9.674207 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> SIP/SDP Status: 200 OK, with session description<br>
9.918465 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> SIP Request: ACK <a href="mailto:sip%3A61390015580@63.138.188.91">sip:61390015580@63.138.188.91</a><br> 10.716189 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34349, Time=160 <br>
10.735624 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34350, Time=320 <br> 10.755612 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34351, Time=480 <br>
10.775612 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34352, Time=640 <br> 10.795612 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34353, Time=800 <br>
10.799790 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> ICMP Destination unreachable (Port unreachable)<br> 10.815611 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34354, Time=960 <br>
10.818728 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> ICMP Destination unreachable (Port unreachable)<br> 10.835608 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34355, Time=1120 <br>
10.839226 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> ICMP Destination unreachable (Port unreachable)<br> 10.855605 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34356, Time=1280 <br>
10.859224 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> ICMP Destination unreachable (Port unreachable)<br> 10.875612 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34357, Time=1440 <br>
10.879217 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> ICMP Destination unreachable (Port unreachable)<br> 10.895612 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34358, Time=1600 <br>
10.899216 <a href="http://81.201.82.39">81.201.82.39</a> -> <a href="http://63.138.188.91">63.138.188.91</a> ICMP Destination unreachable (Port unreachable)<br> 10.915610 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34359, Time=1760 <br>
10.935609 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34360, Time=1920 <br> 10.955611 <a href="http://63.138.188.91">63.138.188.91</a> -> <a href="http://81.201.82.39">81.201.82.39</a> RTP PT=ITU-T G.711 PCMA, SSRC=0x68265F0D, Seq=34361, Time=2080 <br>
<br>Any help or suggestions greatly appreciated.<br>Thanks,<br>Mark<br>-- <br>OnScreen and Voice Learning and Assessment<br><a href="http://www.learnosity.com">www.learnosity.com</a><br><br>
</div>