Nicholas Blasgen
2008-Jul-21 23:18 UTC
[asterisk-users] RTP Packets Going To Wrong IP Address
I have a user behind a firewall who's had no issues in the past connecting though his firewall. He's registered just fine. But when he places a call, a large number of them have no audio on either side of the connection. No one can hear him, he can't hear anyone as well. After a lot of poking around (and changing many settings) I noticed that Asterisk is communicating the RTP packets to an internal IP address. My server has no internal IP address, only an external address, so it's not like we're trying to route this anywhere else. As can be seen below, I've already identified the host as being behind a firewall and therefor to not trust packets from it. Anyone have a suggestion? Name/username Host Dyn Nat ACL Port Status Realtime jfabriquer/jfabriquer 75.36.34.98 D N 55266 OK (145 ms) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Asterisk SVN-branch-1.4-r118365 -- Nicholas Blasgen nicholas at blasgen.com 408.497.9796 (c) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080721/5594a744/attachment.htm
Gordon Henderson
2008-Jul-22 05:33 UTC
[asterisk-users] RTP Packets Going To Wrong IP Address
On Mon, 21 Jul 2008, Nicholas Blasgen wrote:> I have a user behind a firewall who's had no issues in the past connecting > though his firewall. He's registered just fine. But when he places a call, > a large number of them have no audio on either side of the connection. No > one can hear him, he can't hear anyone as well. After a lot of poking > around (and changing many settings) I noticed that Asterisk is communicating > the RTP packets to an internal IP address. My server has no internal IP > address, only an external address, so it's not like we're trying to route > this anywhere else. > > As can be seen below, I've already identified the host as being behind a > firewall and therefor to not trust packets from it. Anyone have a > suggestion?Ask them if they're replaced their router recently? If so, see if it's got a broken SIP ALG... (Some Draytek, Cisco, Zyxel for example) Get them to remove all port-forwarding on their firewall, remove all fancy port/ip address settings on their phone and use a STUN server. If they are using STUN, make sure it's working. Gordon
Darryl Dunkin
2008-Jul-22 06:05 UTC
[asterisk-users] RTP Packets Going To Wrong IP Address
What does the call setup look like on this? You can either debug sip in the console or 'ngrep -s 1500 -T -W byline host 75.36.34.98' From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Nicholas Blasgen Sent: Monday, July 21, 2008 16:19 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] RTP Packets Going To Wrong IP Address I have a user behind a firewall who's had no issues in the past connecting though his firewall. He's registered just fine. But when he places a call, a large number of them have no audio on either side of the connection. No one can hear him, he can't hear anyone as well. After a lot of poking around (and changing many settings) I noticed that Asterisk is communicating the RTP packets to an internal IP address. My server has no internal IP address, only an external address, so it's not like we're trying to route this anywhere else. As can be seen below, I've already identified the host as being behind a firewall and therefor to not trust packets from it. Anyone have a suggestion? Name/username Host Dyn Nat ACL Port Status Realtime jfabriquer/jfabriquer 75.36.34.98 D N 55266 OK (145 ms) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Sent RTP P2P packet to 192.168.1.64:38826 (type 00, len 000160) Asterisk SVN-branch-1.4-r118365 -- Nicholas Blasgen nicholas at blasgen.com 408.497.9796 (c) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080721/8312e3c2/attachment.htm