Outbound 3CX with OBi202

[CoopNYC]

I am setting up an OBi202 with 3cx. Inbound calls make it to the 3CX system perfectly, but outgoing calls (testing from the 3CX app) do not make it to the OBi.

The OBi202 does not show a record of the call in the history.

3CX gives the following error in the activity log...
08/05/2019 4:45:49 PM - Call to T:Line:10000>>1323xxxxxxx@[Dev:sip:[email protected]:5061] from L:6.1[Extn:411] failed, cause: Cause: 486 Busy Here/INVITE from 192.168.21.251:5061
08/05/2019 4:45:49 PM - [CM503003]: Call(C:6): Call to <sip:[email protected]:5061> has failed; Cause: 486 Busy Here/INVITE from 192.168.21.251:5061

Anyone have the outgoing calls from 3CX working and can lend a hand?

Thanks!

 

[cobaltit]

Is 192.168.21.251 the OBI? If so, then clearly calls are making it to the OBI. You'd need to figure out why the OBI is rejecting them.

These threads may help:

https://www.3cx.com/community/threads/3cx-with-google-voice-via-obi200.62660/page-2

https://www.3cx.com/community/threads/3cx-w-obihai-202.47692/

 

[CoopNYC]

Thanks for the info. In that first link it seems the user got to the same place I'm at - calls in work. Calls out don't and looks like he gets the same error with no resolution in that post. I was actually hoping the users in that first post found the solution eventually and could post here!

I assumed that the Obi would show the rejection in the call logs, but nothing shows on the Obi - so I figured the issue was somewhere else.

I'll dig into the CallCentric article that's listed in the second post you mention above and see if I can get info that will help.

That said, if anyone got the specific Obi202 with GV working with 3cx, would love to hear how you got it working!

 

[CoopNYC]

Got it working! This article had the changes that got me over the line.
http://nerdvittles.com/?p=25846

 

[leejor]

I've had it working on a 202 for a while (and previously on an Obi110, until it was no longer supported by GV), but missed your post.

 

[CoopNYC]

Seems to be working well for.

Only thing I have not figured out (if possible) is to pass the GV caller ID through to 3CX so that specific DIDs can route to specific extensions. I have 3 numbers coming into the Obi (SP1, SP2 and SP3) and then using SP4 to route to 3CX.

If you have input on that, I'm all ears!

 

[leejor]

I have incoming caller ID working, but Obi will not send DID information, as far as I'm aware. You could route based on Caller ID. Let me know if the actual caller ID is not working for you.

I haven't used the Obi for anything other than GV. If it were capable of DID, then it would take the phone line phone number, that you set in a field against each line, and send that in the DID field. You could use Wireshark to see if a number, other than caller ID is being sent.

 

[CoopNYC]

I misspoke. Caller ID is working.

What I'd like to do is route calls to extensions based on which line the call came through the Orbi. Ie:
Call on SP1 -> extension x on 3CX
Call on SP2 -> extension y on 3CX
Call on SP3 -> extension z on 3CX

You know if this is possible?

 

[leejor]

As I said, haven't tried it. DID is a typically a business offering and the Obi is more of a residential device. If it is going to work, it will be based on a phone number you must datafill against each line. The Obi must then send that in the field that 3CX looks for the DID number. Wireshark can be used to see the Invite send to 3CX from the Obi to determine if that phone number is being sent. You might want to make use of Google to see if anyone else has found a way to make it work.