Incoming outgoing calls connect No voice

[GoogleCodeExporter]

What steps will reproduce the problem?
1.incoming call answer connect no voice on the other end
2.outgoing call dials out and connects but no voice
3.

What is the expected output? What do you see instead?
see below...

What version of the product are you using? On what operating system?
GV-Sipgate-Sipsorcery
PAP2 or softphone

Please provide any additional information below.
New call from udp:76.216.0.34:5060 successfully authenticated by digest.
DialPlan 18:09:27:363 sip1(6240): Using dialplan default for Out call to 
sip:XXXXXXXXXX@sipsorcery.com.
NewCall 18:09:27:379 sip1(6240): Executing script dial plan for call to 
XXXXXXXXXX.
DialPlan 18:09:27:410 sip1(6240): ** Call from 
<sip:XXXX@sipsorcery.com>;tag=90f7ae4c1733f1f0o0 to XXXXXXXXXX **
DialPlan 18:09:27:426 sip1(6240): Calling 1XXXXXXXXXX via Google Voice
DialPlan 18:09:27:426 sip1(6240): SDP on GoogleVoiceCall call had public IP not 
mangled, RTP socket 76.216.0.34:16446.
DialPlan 18:09:27:426 sip1(6240): UAS call progressing with Ringing.
DialPlan 18:09:27:426 sip1(6240): Logging into google.com for XXXX@gmail.com.
DialPlan 18:09:27:519 sip1(6240): Google Voice pre-login page loaded 
successfully.
DialPlan 18:09:27:519 sip1(6240): GALX key QjrVGyZB2YI successfully retrieved.
DialPlan 18:09:28:957 sip1(6240): Google Voice home page loaded successfully.
DialPlan 18:09:29:379 sip1(6240): Call key RB0Zn64JIDETp7O8Gs1MnEO4XmQ= 
successfully retrieved for XXX@gmail.com, proceeding with callback.
DialPlan 18:09:29:379 sip1(1812): SIP Proxy setting application server for next 
call to user forepj as udp:69.59.142.213:5070.
DialPlan 18:09:29:723 sip1(6240): Google Voice Call to 1XXXXXXXXXX initiated, 
callback #1XXXXXXXXXX, phone type 1, timeout 30s.
DialPlan 18:09:33:676 sip1(1812): SIP Proxy directing incoming call for user 
forepj to application server udp:69.59.142.213:5070.
DialPlan 18:09:33:676 sip1(6240): Google Voice Call callback received.
DialPlan 18:09:33:676 sip1(6240): Answering client call with a response status 
of 200.
DialPlan 18:09:33:738 sip1(6240): Google Voice Call was successfully answered 
in 6.31s.
DialPlan 18:09:33:738 sip1(6240): Dialplan cleanup for forepj.
DialPlan 18:09:34:113 sip1(6240): Dial plan execution completed with normal 
clearing.
DialPlan 18:11:10:380 sip1(6240): Matching dialogue found for BYE to 
sip:69.59.142.213:5060 from udp:69.59.142.213:5060.

Original issue reported on code.google.com by for...@gmail.com on 28 Nov 2011 at 6:20

[GoogleCodeExporter]

This is the classic "no sound" issue, which is almost always related to 
networking issues. The logs above show that all of the software pieces that we 
assembled here are working.. notice 18:09:33:676 onward. All of that means 
everything we support at this website is working perfectly. The fact that you 
can't hear any sound means that your Internet connection is having trouble 
supporting or maintaining your SIP connection.

I know its scary, but have you tried connecting your computer with the 
softphone directly to your cable or DSL modem? If it works when connected that 
way, your router is causing the issue. If not, then something may be happening 
somewhere at your ISP or the path between your SIP gateway provider and your 
Internet connection.

Sorry, but the scripts we provide and support here at this website are working 
perfectly and you proved that in the log you attached. Don't be offended by the 
ticket being marked "Invalid". I recognize that its a real problem you are 
experiencing, but its just not coming from the pieces and parts we gave you.

Original comment by easter...@gmail.com on 28 Nov 2011 at 6:55

• Changed state: Invalid

[GoogleCodeExporter]

Thanks.  I experienced this issue before and connected my PAP2
directly to my 2Wire RG and it worked.  Now I guess I'm at the end of
the line.  Oh well.  It worked like  charm for two years.  Thanks for
all the support.

On Mon, Nov 28, 2011 at 10:56 AM,
<google-voice-sipsorcery-dialplans@googlecode.com> wrote:

Original comment by for...@gmail.com on 28 Nov 2011 at 10:14

[GoogleCodeExporter]

I'm sorry that's what it is. It may not be completely over for you, however. Is 
Comcast your provider? They have recently moved their IPv6 rollout to the early 
stages of the "general population". If you're not familiar with it, IPv6 will 
flatten the next generation of Internet connectivity and give the world an 
Internet experience only a relative handful of us have seen before.. every 
single device will have its own public IP address.

Back in 1994 when I worked at New York University, I used to be able to walk 
into any university library, break out of their card catalog software and 
telnet directly to the box sitting on my desk in New York City to check my 
mail. Luckily the memory won't completely fade before I'll be able to do that 
again ;)

Good luck!

Original comment by easter...@gmail.com on 28 Nov 2011 at 10:20

[GoogleCodeExporter]

Actually, since you mention a 2Wire, I'm guessing DSL. Only my friends/family 
with DSL use 2Wire. Sorry!

Original comment by easter...@gmail.com on 28 Nov 2011 at 10:21

[GoogleCodeExporter]

I've rest my modem, reset the IP.  Nothing. This could be the last
straw.  Yes, it's DSL and I'm pretty sick of how AT&T has treated me.
 I was looking into Comcast.  Have always heard worse things about
them.  Wish we had FIOS here in the SF Bay Area

On Mon, Nov 28, 2011 at 2:24 PM,
<google-voice-sipsorcery-dialplans@googlecode.com> wrote:

Original comment by for...@gmail.com on 28 Nov 2011 at 10:36

[GoogleCodeExporter]

Yes, Comcast grew a little too quickly in their early days and they did not 
play along very well with the Internet at large. So much so that they suffered 
the rare "USENET death penalty" whereby they were permanently banned from 
participating in the global NNTP community. I still have to pay for USENET from 
a provider to this day. 

That being said, they have come A LONG WAY since then, and I've been happy with 
them for 10 years. My cable company was the last in the area to roll out cable 
modems, but when Comcast took over they got right to work. They eventually got 
caught up, and my area is now wired for 105Mbps service. My town was the second 
or third in the nation to be cabled up for FiOS, with Verizon striking right in 
Comcast's backyard.

Beyond all that, Comcast took the extraordinary step of creating a custom 
firmware for routers (based on OpenWRT) that used 6RD for IPv6 tunneling at 
first, but *automatically* switched over to "native dual stack" when an IPv6 
network assignment was detected. Considering where they came from, that is an 
absolutely amazing jump forward and did the world some good by helping to ramp 
up IPv6 adoption. I ran OpenWRT for a while on an old WRT54G but the router 
would freeze up every time I maxed out my DOCSIS 3 modem. I moved to Buffalo 
running DD-WRT and now the router keeps up with the modem no problem.

It just may be time for a change of scenery at your end. Of course, I live 20 
miles from Comcast's HQ in Philadelphia, so YMMV.

Original comment by easter...@gmail.com on 28 Nov 2011 at 10:50