This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

one way audio with SIP

0

For the past 3 years I have been using Linksys PAP2T phone adapter behind RV082 router with UDP port forwarding without any problems, until recently I started getting fast busy on all outgoing calls. Called the provider (ViaTalk) and was told they have to change the proxy setting on their end which fixed fast busy, but introduced ONE WAY audio on all incoming calls, however outgoing calls don’t seem to have this problem. ViaTalk’s solution to one way audio was changing SCTP port from 5061 to 5081 in the phone adapter, but as it made NO difference they blamed it on my router (which was working fine for the past 3 years) and hung up.

I was able capture phone adapter traffic using my laptop (nic in promiscuous mode), but to see the whole picture I think I need to do another capture between the cable modem and the router, just not sure what to capture.

The capture I got from behind the router looks like this. (66.147.235.3) sip:[email protected] communicates with my PAP2T (192.168.20.240) via 5061 and 5060 once connection is established, 192.168.20.240 communicates with 209.244.30.233 IP (G.711). Src Port: 16412 (16412), Dst Port: 60858 (60858) As I put my laptop with wireshark between the router and a cable modem, I am assuming 192.168.20.240 will not show up in the capture and the only IPs I can configure a filter for are 209.244.30.233 & 66.147.235.3?

Also I am guessing I will see something in the conversation with 209.244.30.233 in front on the router that I don’t see behind?

Thank you for your help

asked 25 Jan '12, 08:07

net_tech's gravatar image

net_tech
116303337
accept rate: 13%

edited 27 Jan '12, 13:21

Well, what did you see? There's little we can tell before you tried it.

(27 Jan '12, 14:57) Jaap ♦

Is it correct to assume that the missing audio part is gonna be in communication with 209.244.30.233 IP?

This is what I get if I follow UDP stream to bumblebee server. Link

(30 Jan '12, 12:09) net_tech

That assumption seems plausible. Was this UDP stream captured before the router? Are the RTP endpoint addresses properly translated by the NAT helper?

(30 Jan '12, 23:10) Jaap ♦

The proxy should be directing you and the remote endpoint to each other (you talk to bumblebee to get the call details, it then directs you to the remote endpoint (209.244.30.233) to open a hole on your firewall to allow traffic coming into 16412 ) and this is where the disconnect is. When you say 1-way - you are able to hear them, or they are able to hear you? Judging by the sip.txt file you linked to it appears that the call controller is detecting an unhealthy connection and closing it - but I can't tell. Have you tried setting the PAP as your DMZ host?

(01 Feb '12, 07:53) GeonJay

Jaap,

UDP stream was captured after the router and the translation rules have not changed I have 2 ranges set up (5060-5080) & (10000-20000). More ports that I will ever need, but that's what ViaTalk wants.

(01 Feb '12, 12:32) net_tech

GeonJay,

Sorry I didn’t clarify one way audio. With incoming calls I can’t hear the caller, but the caller can hear me. Tried PAP2T in the DMZ port, but didn’t get a link light on the port. May have a bad DMZ port in the router, but I haven’t tested with other devices in the DMZ. Don’t think there is anything unhealthy with the connection. I did a quick capture (5-10 sec) and hung up.

(01 Feb '12, 12:46) net_tech
1

Strangely enough I no longer have the one way audio issue. Keep in mind that I made no changes and it started working again.

Based on the research I made in the past few days, the problem is on the (VOIP) provider end. Not sure how I never had this problem before, apparently everyone who has ViaTalk faced this issue at some point

link

While they blame my equipment, their techs fix the problem behind my back.

(01 Feb '12, 12:48) net_tech
showing 5 of 7 show 2 more comments