ResetCDR

Hi, I'm having a problem with outbound calling using gtalk and sipdroid. Been working fine until this afternoon, now I get the "try the call again later" message.

RE: ResetCDR

Try calling a different number. Our service is working as usual.

RE: ResetCDR

I am also unable to place GTalk/Google Voice calls on two different accounts.

EDIT:
I have tried 2 different PBXes accounts, for a total of 4 different Google Voice accounts. I have verified all passwords, re-registered the GTalk trunks by saving them again, and restarted my service by selecting "Submit and start" from the personal information screen. None of this has helped. I have also been able to successfully make calls through another Google Voice/SIP gateway, which worked flawlessly. So with all due respect to the moderator who said it was not on PBXes' end, it definitely appears to be on PBXes end.

For what it's worth, here is what I get in the log:
Sep 25 13:34:07 VERBOSE[126359] logger.c: -- Called [redacted]@gmail.com/+18004444444@voice.google.com
Sep 25 13:34:07 VERBOSE[126359] logger.c: -- Gtalk/+18004444444@voice.google.com-4fbe is ringing
Sep 25 13:34:07 VERBOSE[126359] logger.c: == Everyone is busy/congested at this time (1:0/0/1)

This post has been edited 1 time(s), it was last edited by z28 on 25.09.2013 at 20:47.

RE: ResetCDR

I am also having issue with outbound calls via Google Voice (CDR Reset) and other providers.

Sep 25 11:02:31 VERBOSE[7917] logger.c: -- Called xxxxxxxx@from-internal/n
Sep 25 11:02:31 NOTICE[8038] app_dial.c: Unable to create channel of type 'SIP' (cause 3 - No route to destination)
Sep 25 11:02:31 VERBOSE[8038] logger.c: == Everyone is busy/congested at this time (1:0/0/1)

RE: ResetCDR

I've spent several hours on this now and getting nowhere. I've gone through all my settings, making new trunks, re-entering passwords, you name it, tried calling different numbers but it's not working, something changed somwhere either with google or pbxes...
EDIT: I'm also getting
VERBOSE[100004] logger.c: == Everyone is busy/congested at this time (1:0/0/1)

This post has been edited 1 time(s), it was last edited by ptr on 25.09.2013 at 21:58.

RE: ResetCDR

Also unable to make outbound calls on GVoice trunks. "Your call cannot be completed as dialed".

Incoming calls through GVoice trunks are working fine though...

RE: ResetCDR

Zitat:

Originally posted by i-p Try calling a different number. Our service is working as usual.

Sir,

There are 4 of us in this thread, as well as another gentleman in this thread (http://www1.pbxes.com/forum/thread.php?threadid=1380093365), who all have this issue.

Is PBXes' official stance still that there are no problems?

Everyone else,

If you feel like taking the time to set it up, I found another Google Voice to SIP gateway that is working fine. It is located here:
https://simonics.com/gvgw/

Rob

This post has been edited 1 time(s), it was last edited by z28 on 26.09.2013 at 13:24.

RE: ResetCDR

We accessed our Google Voice from www1 where our PBXes account is hosted. This can be changed on PBXes in Personal Data.

Moving to www4 lead to the same error as you observed. Try changing to www1 to solve the issue.

RE: ResetCDR

The same issue is still present. I tried changing to another datacenter (the 'datacenter / timezone' option under personal information) but www4, www2 and www7) all have the same errors in the logs...

Reset CDR
no route to host

I have been using PBXes for years! Something has changed...

RE: ResetCDR

Please try changing to www1. www2, www4 and www7 all seem to be blocked by Google for outgoing calls. Do you guys have loaded credit into your Google Voice accounts?

RE: Google Voice Outbound (was ResetCDR)

Just changed to www1. Yes, I have over $10 credits in Google voice. After changing to www1, Google sent me a 'suspicious activity' notice and I was forced to change my password. Spent the last 10 minutes updating all my devices, browsers and trunks with the new password.

Will test and let you know.

RE: ResetCDR

Zitat:

Originally posted by i-p We accessed our Google Voice from www1 where our PBXes account is hosted. This can be changed on PBXes in Personal Data. Moving to www4 lead to the same error as you observed. Try changing to www1 to solve the issue.

Sorry for a stupid question, but how do I change to www1? I can't find it in the drop down...

RE: Google Voice Outbound (was ResetCDR)

Same issse on www1

Sep 26 18:58:14 VERBOSE[50861] logger.c: -- Called xxxx@from-internal/n
Sep 26 18:58:14 NOTICE[51037] app_dial.c: Unable to create channel of type 'GTALK' (cause 0 - Unknown)
Sep 26 18:58:14 VERBOSE[51037] logger.c: == Everyone is busy/congested at this time (1:0/0/1)
Sep 26 18:58:14 VERBOSE[51037] logger.c: -- Playing 'cannot-complete-as-dialed' (language 'en')
Sep 26 18:58:14 VERBOSE[50861] logger.c: -- Local/123456789@from-internal/n-a494,1 answered SIP/12345666-f05f
Sep 26 18:58:14 VERBOSE[50861] chan_sip.c: Hangup call SIP/qwerty-398c, SIP callid 1a2872323cf7b9696ff2c61c677f92c6@188.40.65.170
Sep 26 18:58:14 VERBOSE[22150] chan_sip.c: SIP response 100 to standard invite
Sep 26 18:58:17 VERBOSE[51037] logger.c: -- Playing 'pls-try-call-later' (language 'en')
Sep 26 18:58:20 VERBOSE[50861] chan_sip.c: Hangup call SIP/14383383457-f05f, SIP callid 6543211@208.x.a.66~o~o

RE: Google Voice Outbound (was ResetCDR)

Having same issue, problem started 2-3 days ago and persists. I'm on www2. Yes, I have credit on my Google voice account and I can make calls with Google through the web interface - but no longer through PBXes. Incoming calls are still working fine and are routed normally to my extensions connected to PBXes. Problem happens on all extensions and no matter what number I call. SIP trace shows the same "Everyone is busy/congested at this time" error that other users have reported.

Sep 26 11:09:18 VERBOSE[66171] logger.c: -- Called editedout@gmail.com/+15032271234@voice.google.com
Sep 26 11:09:18 VERBOSE[66171] logger.c: -- Gtalk/+15032271234@voice.google.com-9cec is ringing
Sep 26 11:09:18 VERBOSE[66171] logger.c: == Everyone is busy/congested at this time (1:0/0/1)

EDIT: outgoign calls on SIP trunks still work fine, only the GTALK trunk is causing problems.

This post has been edited 1 time(s), it was last edited by lpm on 26.09.2013 at 20:13.

RE: Google Voice Outbound (was ResetCDR)

i-p, thanks for looking into this.

no www1 was listed as a choice in the drop down menu on my personal data, so i changed to european server, which happens to be www3.

still same issue!

i'm afraid this could be the end of PBXES and google voice peering. it has been a great couple of years...

RE: Google Voice Outbound (was ResetCDR)

When changing to the other server (go to Personal Data, www1 and www3 both work), Google will first reject this for security reasons.

You have to login to google.com/voice and confirm that there is no unauthenticated access - no need to change passwords.

Then restart your PBX in Personal Data by clicking Submit & Start.

RE: Google Voice Outbound (was ResetCDR)

I moved to www3 and outgoing calls are working now. Yay! but how can we help PBXes? Obviously, we all want Google to unblock www2, www7 et al. IP, please advise if you want us to contact Google or if you suggest another course of action.

RE: Google Voice Outbound (was ResetCDR)

Yes, please contact Google. As I understand many of you have paid credits on their accounts, and want to use them. Google is not the company that wants to make money by blocking their payments from use. This must be some software bug.

Our fault might have been that we lowered our checks for free accounts which made Gtalk registrations from the servers increase. We have now rerun all checks to turn off some free users using double accounts. This might help to get registrations load down again.

RE: Google Voice Outbound (was ResetCDR)

Zitat:

Originally posted by lpm I moved to www3 and outgoing calls are working now. Yay! but how can we help PBXes? Obviously, we all want Google to unblock www2, www7 et al. IP, please advise if you want us to contact Google or if you suggest another course of action.

Did you have to do anything else to get it working? I switched to www3, confirmed the security alert on my Google account page, hit submit and start, and still can not make outgoing calls. (Same error in the log, everyone is busy/congested, although the call list shows no trunk associated with the call attempt).

Also, are you noticing any degradation in the call quality? I made a test call with a non-Google trunk while I was on www3 and the quality was horrible, I assume due to the long distance between me and the www3 server.

RE: Google Voice Outbound (was ResetCDR)

www3 is not working for me either, submitted personal data on pbxes and verified the "suspicious" activity with google, no luck.