Google Voice can't reach SIPGate DID

[joeg]

My PIAF classic setup broke a couple of days ago. Totally standard settings but for a fleet of secure passwords. I did not change anything, it just stopped working. I'm using a local Google Voice number that lights up a SIPGate DID-Trunk. That in turn is my DID into my PIAF.

Details - it manifested itself when outgoing calls stopped working. The typical Allison "Please wait while we place your call," then spacey music, and then no interruptions to the spacey music. It goes for about 40 seconds and then quits with an Allison "Good-bye."

Calls direct to my SIPGate DID work fine (i.e., no Google Voice in the chain). Simulated incoming calls on the PBX work perfectly. So the PBX seems to be fine and the SIPGate inbound trunk seem to be fine.

When I manually dial from Google Voice to my SIPGate DID, it rings itself out for about 30 seconds and gives up. Naturally, when I try to verify the SIPGate DID from Google Voice, it cannot reach the SIPGate number and thus can't verify it.

When I set this up about two months ago, this Google-SIPGate linkage was *no* problem. It worked fine for those couple of months. Any thoughts or suggestions? Google Voice didn't turn around and give us SIPGate-PIAF users the shaft, did they?

 

[completetech]

I had the same issue a little bit ago round the same time it seems as you. seemed to clear it self up after a few reboots though. it showed on the box as it was attemping to register and then showed on sipgates end that it did register. but could not call in to it. kept getting alison saying the number is not in service once it hit the box

 

[steve54301]

This is the exact behavior I was having (cropped up one day and never resolved itself) with an IPcomms DID that I had been using in conjunction with google voice.

I haven't noticed this yet with my sipgate DID.

 

[joeg]

I did reboot several times but it definitely hasn't cleared itself up. Either my SIPGate DID stubbornly refuses to answer or my Google Voice stubbornly refuses to reach my SIPGate number. The result is the same - my Google voice number refuses to ring into my PBX. How did y'all clear things up, just by rebooting and praying?

 

[amygrant]

I've notices SIPGATE has been having intermittent uptime issues. If your sipgate trunk went offline, then you it could cause the result you are getting.

It would be helpful if, during the problem, you posted the relevant log snippets.

 

[rossiv]

I, too, am experiencing this issue as well.

 

[The Deacon]

Add me to the list too.

 

[wardmundy]

Growing pains, I'm afraid.

 

[mtennant]

I'm having the same problem. Here is the critical log entry.

[2010-07-16 11:16:29] WARNING[3580] app_dial.c: Unable to create channel of type 'SIP' (cause 3 - No route to destination)
[2010-07-16 11:16:29] WARNING[3580] app_dial.c: Unable to create channel of type 'SIP' (cause 3 - No route to destination)
[2010-07-16 11:16:29] WARNING[3580] app_dial.c: Unable to create channel of type 'SIP' (cause 3 - No route to destination)
[2010-07-16 11:16:29] WARNING[3580] app_dial.c: Unable to create channel of type 'IAX2' (cause 3 - No route to destination)
[2010-07-16 11:16:29] VERBOSE[3592] logger.c: == Manager 'admin' logged off from 127.0.0.1
[2010-07-16 11:16:29] VERBOSE[3580] logger.c: -- SIP/701-09bf2048 is ringing
[2010-07-16 11:16:30] WARNING[3211] chan_sip.c: Maximum retries exceeded on transmission [email protected] for seqno 103 (Critical Response)
[2010-07-16 11:16:30] WARNING[3211] chan_sip.c: Hanging up call [email protected] - no reply to our critical packet.

 

[mtennant]

Is this guy onto something?

http://www.pmarks.net/posted_links/google-voice-dialout.agi

# Changes:
# - 2010-06-27: Ignore explicit ":443" in redirect.

 

[joeg]

As a followup, it's all working beautifully right at the moment. It's been busticated (intermittent, really) for several weeks and for the last day or so it's been working quite well.

I don't mind the "good things come to those who wait" nature of the situation as long as it stays up! BTW, does anybody have any theories as to whether this was SIPGate's or Google Voice's fault?

The reason I ask is to assess if this could be fixed permanently with a Vitelity or other trunk, or whether it's a Google problem.

 

[mtennant]

still not working here. same error message in the logs that I posted before.

it tries to connect, and actually does, but then it terminates a few seconds into the call.

 

[jrglass]

Is your server registering with sipgate? I can not get my server to regester.

Thanks,

Jeff

 

[mtennant]

Yes, it is registered. I can even call my Sipgate number. The stealth attendant on PBX in a Flash answers, and the call is transfered to an extension. But it disconnects shortly thereafter. Very strange. Ward, any ideas?

 

[mtennant]

does this thread have an impact on this problem?

http://pbxinaflash.com/community/threads/sipgate-dropped-calls-and-asterisk-id-question.4823/?t=4823

 

[mtennant]

after chasing many rabbits down many endless holes, I finally rebooted EVERYTHING, AGAIN.

Cable modem, router, PBXIaF server. Everything is working fine now.

I've done this before, without solving the problem.

I guess you just have to do it several times until the problem is solved.

I was beginning to think my Asus WL-520gu Tomato flashed router with the latest USB support on Kernel 2.6 was the problem.

Right now everything is ok.

Did the other posters finally get their Sipgate/GV combo to work again?

 

[joeg]

It's broke again

Hi all,

Yeah, it was all working perfectly for a couple of weeks and now it's broke again. Same problem, same mystery. I rebooted everything and it's still doing it. Quite baffling. Still don't know whether it's SIPGate or Google Voice or some combination, but GV just won't ring through to my SIPGate DID.

Guess I just have to wait and hope it sorts itself out shortly.

 

[mtennant]

Went bad on me too again today. Glad I have many other solutions. Can't wait for the native GV solution from Google.

 

[txcas]

All of a sudden I am having the same problem.