I followed the instruction from here:http://nerdvittles.com/?p=26971
6. To create a GVSIP trunk, choose Trunks -> Add SIP Trunk. Enter a Trunk Name and your Google Voice account name (without @gmail.com) for Username. Click Get Password for Google Voice button. Google then will prompt you for your credentials to login to your Google account. Once logged in, your OAuth credentials will be generated for you, and you will be returned to the Trunk template. Enter your 10-digit Google Voice number as Outbound CallerID. Set Maximum Channels and Maximum Outbound Channels to 2. Set Dial Rule to NXXNXXXXXX. Click Submit Changes and click the Red Bar to reload your dialplan. In the left column, your new GVSIP trunk should appear under the Trunks option. You can also verify the registration by choosing the Status option.

The registration is OK.
I can receive call but no way to call out,
always "ResetCDR" for any GV call.

I had my outbound proxy port set 5060 for a few days until the registration started failing. I then switched it to port 36999 and it worked again for a few days. But I keep having to switch the outbound proxy port between 5060 and 36999 every few days. Why does this keep happening? Is there a port that is more stable?

After the last update (where you asked us to delete the gvoice trunk, then 'submit & start', etc.), Everything was working smoothly, I can also tell the you either upgraded some systems or got the load issues worked out, too.

Only issue I am having is that bug where you only get 4 rings on outgoing calls before you hear a busy signal and then a hang up...

That problem had gone away for a while, actually... but just popped up again. The only recent change I made was changing the password on my main SIP extension, which I doubt is related.

So it's back to calling people, if they don't answer at 4 rings (when the system seems to go busy and then hang up), I have to text people to let them know why I called, lol.

I tried removing, readding the trunk a couple of times, and also tried hitting 'submit & start' again just for kicks... nothing seems to help.

If anyone has solved this, or if anyone else is still experiencing this glitch, do advise

Note: the CallerID setting is for NAME, not number.
GV already sends your assigned number.
If using a SIP phone, that CallerID name may
over-ride the PBXes CallerID name, depending
on phone/PBX SIP settings.

Hello, I am following the same post but I have trouble with this instruction:

username-extnumber:extension-password@pbxes.org/DID-number

Can you explain what exactly I need to se for "DID-number"?

Thanks so much!

Zitat:

Originally posted by pie
I followed the instruction from here:http://nerdvittles.com/?p=26971
6. To create a GVSIP trunk, choose Trunks -> Add SIP Trunk. Enter a Trunk Name and your Google Voice account name (without @gmail.com) for Username. Click Get Password for Google Voice button. Google then will prompt you for your credentials to login to your Google account. Once logged in, your OAuth credentials will be generated for you, and you will be returned to the Trunk template. Enter your 10-digit Google Voice number as Outbound CallerID. Set Maximum Channels and Maximum Outbound Channels to 2. Set Dial Rule to NXXNXXXXXX. Click Submit Changes and click the Red Bar to reload your dialplan. In the left column, your new GVSIP trunk should appear under the Trunks option. You can also verify the registration by choosing the Status option.

The registration is OK.
I can receive call but no way to call out,
always "ResetCDR" for any GV call.

My google voice trunk no longer works as of yesterday. Worse, I tried deleting everything including the trunk and the obihai phone in Google Voice legacy settings, now I can recreate the trunk but it no longer recreates a obihai phone in google voice legacy settings. Anyone else can comment?

EDIT: I did the "Submit and Start" in Personal Data before recreating the trunk and lo and behold it worked! The Obihai phone reappeared in Google Voice Legacy settings and the trunk connected successfully. Hooray!

This post has been edited 1 time(s), it was last edited by lpm on 12.12.2018 at 10:28.