Dialing out using X-Lite 4 / GV / IPKall / Sipsorcery / Simple Dial Plan, rings once, then one way audio

[GoogleCodeExporter]

What steps will reproduce the problem?
1.dial out using X-Lite 4 soft-phone (I've tried other soft-phones with the 
same result)
2. single audible ring during indicated "Connecting" phase, followed by no 
audio at "Call Established phase"
3. Phone being called rings, can be answered and can hear audio originating 
from soft-phone, however not vise versa

What is the expected output? What do you see instead?
I expect to hear audio both ways when I dial out.
I can hear audio both ways if I dial inbound to the soft-phone via the IPKall 
number or my GV number (forwarded to IPKall number)

What version of the product are you using? On what operating system?
X-Lite 4, OSX 10.6.5

Please provide any additional information below.
DialPlan 06:16:43:868 sip1(9440): New call from tcp:66.41.178.103:52277 
successfully authenticated by digest.
DialPlan 06:16:43:899 sip1(9440): Using dialplan default for Out call to 
sip:9528265994@sipsorcery.com.
NewCall 06:16:43:899 sip1(9440): Executing script dial plan for call to 
9528265994.
DialPlan 06:16:44:024 sip1(9440): ** Call from "sipsorcery allamericangeek" 
<sip:allamericangeek@sipsorcery.com>;tag=7ff97824 to 9528265994 **
DialPlan 06:16:44:024 sip1(9440): Calling 19528265994 via Google Voice
DialPlan 06:16:44:024 sip1(9440): SDP on GoogleVoiceCall call had RTP socket 
mangled from 192.168.0.99:63324 to 66.41.178.103:63324.
DialPlan 06:16:44:024 sip1(9440): UAS call progressing with Ringing.
DialPlan 06:16:44:024 sip1(9440): Logging into google.com for 
a.fantastic.family@gmail.com.
DialPlan 06:16:44:071 sip1(9440): Google Voice pre-login page loaded 
successfully.
DialPlan 06:16:44:071 sip1(9440): GALX key NFLuZysi2tg successfully retrieved.
DialPlan 06:16:44:899 sip1(9440): Google Voice home page loaded successfully.
DialPlan 06:16:44:977 sip1(9440): Call key K5yLyPOF6lWYg3mQXu9fvmyRkRw= 
successfully retrieved for a.fantastic.family@gmail.com, proceeding with 
callback.
DialPlan 06:16:44:977 sip1(1704): SIP Proxy setting application server for next 
call to user allamericangeek as udp:69.59.142.213:5070.
DialPlan 06:16:45:071 sip1(9440): Google Voice Call to 19528265994 forwarding 
to 13602276590 successfully initiated, callback timeout=30s.
DialPlan 06:16:47:118 sip1(1704): SIP Proxy directing incoming call for user 
allamericangeek to application server udp:69.59.142.213:5070.
DialPlan 06:16:47:149 sip1(9440): Google Voice Call callback received.
DialPlan 06:16:47:180 sip1(9440): Answering client call with a response status 
of 200.
DialPlan 06:16:47:258 sip1(9440): Google Voice Call was successfully answered 
in 3.23s.
DialPlan 06:16:47:258 sip1(9440): Dialplan cleanup for allamericangeek.
DialPlan 06:16:47:539 sip1(9440): Dial plan execution completed with normal 
clearing.

Original issue reported on code.google.com by A.Fantas...@gmail.com on 20 Dec 2010 at 6:25

[GoogleCodeExporter]

Everything is okay with your account and dialplan settings. This problem is 
known as "1-way audio or no audio" and typically related to the codec and/or 
NAT router.

The codec problem usually can be fixed by limiting supported codecs to A-law 
and u-law (PCMA and PCMU). As to the NAT problems, try putting your computer 
into DMZ of the router.

Original comment by mte...@gmail.com on 20 Dec 2010 at 8:04

• Changed state: Started
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Okay, on the soft-phone I'v confirmed I am using G711 aLaw & G711 uLaw, which 
leads me to follow your logic/advice on NAT / DMZ, and the "RTP socket mangled" 
log entry from the sipsorcery console.

I just tried using fring, an iPhone soft-phone app, over 3G and it works. I 
realize this is pointless, as there is a Google Voice app, but it was a testing 
method.

I did not end up with "RTP socket mangled"

DialPlan 14:01:08:022 sip1(9836): New call from udp:208.122.63.106:28311 
successfully authenticated by digest.
DialPlan 14:01:08:085 sip1(9836): Using dialplan default for Out call to 
sip:6122342762@sipsorcery.com.
NewCall 14:01:08:116 sip1(9836): Executing script dial plan for call to 
6122342762.
DialPlan 14:01:08:194 sip1(9836): ** Call from 
<sip:allamericangeek@sipsorcery.com>;tag=028009890503191097b6d64e7add07b7 to 
6122342762 **
DialPlan 14:01:08:194 sip1(9836): Calling 16122342762 via Google Voice
DialPlan 14:01:08:210 sip1(9836): SDP on GoogleVoiceCall call had public IP not 
mangled, RTP socket 208.122.63.106:60262.
DialPlan 14:01:08:210 sip1(9836): UAS call progressing with Ringing.
DialPlan 14:01:08:210 sip1(9836): Logging into google.com for 
a.fantastic.family@gmail.com.
DialPlan 14:01:08:241 sip1(9836): Google Voice pre-login page loaded 
successfully.
DialPlan 14:01:08:241 sip1(9836): GALX key E6zdHUzCTVg successfully retrieved.
DialPlan 14:01:09:257 sip1(9836): Google Voice home page loaded successfully.
DialPlan 14:01:09:335 sip1(9836): Call key K5yLyPOF6lWYg3mQXu9fvmyRkRw= 
successfully retrieved for a.fantastic.family@gmail.com, proceeding with 
callback.
DialPlan 14:01:09:335 sip1(1704): SIP Proxy setting application server for next 
call to user allamericangeek as udp:69.59.142.213:5070.
DialPlan 14:01:09:429 sip1(9836): Google Voice Call to 16122342762 forwarding 
to 13602276590 successfully initiated, callback timeout=30s.
DialPlan 14:01:12:694 sip1(1704): SIP Proxy directing incoming call for user 
allamericangeek to application server udp:69.59.142.213:5070.
DialPlan 14:01:12:710 sip1(9836): Google Voice Call callback received.
DialPlan 14:01:12:710 sip1(9836): Answering client call with a response status 
of 200.
DialPlan 14:01:12:819 sip1(9836): Google Voice Call was successfully answered 
in 4.61s.
DialPlan 14:01:12:819 sip1(9836): Dialplan cleanup for allamericangeek.
DialPlan 14:01:13:085 sip1(9836): Dial plan execution completed with normal 
clearing.

Original comment by Jason.Sh...@gmail.com on 20 Dec 2010 at 2:06

[GoogleCodeExporter]

If IP address in the SDP is not public (such as 192.168.xxx.xxx), Sipsorcery 
will replace it with external IP address. In the other words, it works like a 
STUN server.

Again, everything is okay with your Sipsorcery setup and you have just proven 
it by calling via Fring. The problem is local and should be dealt with as a 
such.

Original comment by mte...@gmail.com on 20 Dec 2010 at 7:00

[GoogleCodeExporter]

Original comment by easter...@gmail.com on 8 Feb 2011 at 12:50

• Changed state: Invalid