3CX with Google Voice via Obi200 Settings

[Josh237]

I have read over a similar post on here for this here https://www.3cx.com/community/threads/3cx-with-google-voice-via-obi200.62660/ and this worked for the most part.

The one thing I am having an issue with and not sure if anyone has had this issue but, when I try and change the SP1 inbound call rout from ph the the sp2(10000) setting It always reverts back to ph

Can anyone tell me why or how to fix this as I think everything will work as soon as I can get that to stick.

Thanks
Josh

 

[Josh237]

I might have to start over but this is what I get.

12/19/2019 2:40:12 PM - Call to T:Line:10000>>14xxxxxxxx@[Dev:sip:[email protected]:5061] from L:36.1[Extn:807] failed, cause: Cause: 408 Request Timeout/INVITE from local

12/19/2019 2:40:12 PM - [CM503003]: Call(C:36): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local

 

[Josh237]

ok think I'm making progress getting this now

12/19/2019 2:43:49 PM - Call to T:Line:10000>>14xxxxxxxx@[Dev:sip:[email protected]:5061] from L:38.1[Extn:807] failed, cause: Cause: 486 Busy Here/INVITE from 192.168.1.100:5061

12/19/2019 2:43:49 PM - [CM503003]: Call(C:38): Call to <sip:[email protected]:5061> has failed; Cause: 486 Busy Here/INVITE from 192.168.1.100:5061

 

[leejor]

If you look in the Obi call log, do you see a call attempt? Can you confirm that X_InboundCallRoute is correct...your trunk number, and outer brackets are curly.

 

[Josh237]

It looks like its not even hitting the Obi I see the inbound calls hitting.
All inbound is working properly just outbound from the 3cx. I see it hit the 3cx and getting that last error I send in here.

 

[Josh237]

Sweet I looked around and found a solution that worked. I actually have to change the inbound SP2 to {>(<1:>xx.):SP1} and then all worked like a charm.

Thanks for all your help

 

[leejor]

The statement should be a catch-all dial-plan to sent any number 3CX sends, onto the correct GV port on the Obi. I'm sure that there are a number of combinations that will work. I only used, what I posted, as it was working on my Obi110 for a long time so i saw no need to change it. I had also used exactly the same settings on a second 200, with no issue.
Glad you got it working.

 

[Dominic Rizzo]

I tried that inbound and seem to be having the same issue, the calls aren't hitting the OBi

 

[leejor]

So...this is another issue, or you simply tried the configuration I used, and are reporting that it doesn't work for you?

 

[Dominic Rizzo]

I tried the configuration you used and the inbound route that Josh237 provided and nothing worked for outbound calls from 3CX. Inbound calls work like a charm.

 

[leejor]

I will have to look (tonight, or this weekend) to see what digits I have 3CX sending to the Obi

 

[Dominic Rizzo]

Never mind, got it working!

 

[leejor]

I send 1+10 digits to the Obi.

Here is a link to the DigitMap Tutorial if you haven't come across it
https://www.obitalk.com/info/documents/admin_guide/OBi-DigitMapCallRoute-Tutorial-v1-1.pdf