News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Obi 202 with 3CX Outbound calling issues

Started by jholme004, April 30, 2020, 08:11:04 PM

Previous topic - Next topic

jholme004

Hello! I am trying to configure an Obi202 with three GV accounts to work with 3CX in a personal set-up (formerly a Nortel Admin, doing this as a hobby). Inbound calling for all three work, and are set-up as DIDs, and route to the proper destinations. For the time being, I have the trunk set to 3 simultaneous calls and have verified that works inbound as well. My trouble is outbound calling.
When dialing out, I get dead air followed by SIT tones. I've followed several of the posts here and on 3CX, but still cannot figured out why it is not working. In the Obi Dashboard, SP4 shows as "Registered". I'm guessing that although I am using 3CX< since it is a SIP trunk, the obi config would be the same regardless of the platform.

Here are the 3CX logs when I place a call (Using a Toll-free for public posting; local/long lines has the same result):
04/29/2020 6:55:01 PM - Call to T:Line:10002>>18004377950@[Dev:sip:10002@10.172.17.207:5083] from L:27.1[Extn:184] failed, cause: Cause: 404 Not Found/INVITE from 10.172.17.207:5083
04/29/2020 6:55:01 PM - [CM503003]: Call(C:27): Call to <sip:18004377950@10.172.17.207:5083> has failed; Cause: 404 Not Found/INVITE from 10.172.17.207:5083

Attached my SP4 config (Also tried {10002>(xx.):SP} for X_InboundCallRoute) and ITSP Profile D Config (all not shown are set to "ObiTalk Settings"

Any thoughts or guidance is greatly appreciated!!

-Jason

drgeoff

Try starting with just

sp1

as the SP4 InboundCallRoute.

Have a look at the OBi's Call History.

Have a look at the OBi's Call Status during the call attempt.  That page does not auto update - you need to keep clicking the link.

The OBi can send debug info to a syslog server.  Search the Admin Guide for syslog.  Obihai previously offered a server on the downloads page. I have attached it to this post.

jholme004

I changed to just  "sp1" and still receiving SIT with the 3cx logs saying "failed, cause: Cause: 404 Not Found/INVITE from 10.172.17.207:5083" The Obi call History doesn;t show an attempt nor did the call status during the attempt. I alos tok al look back at the outbound rules and added a CallCentrix trunk to the rules as the second trunk. Received the 404 Not Found error in the logs, but the call went through via CallCentric, so I don't think it is a "rules" issue. It almost seems like the Obi is just refusing to connect, but I can't figure out why. Both (3CX & Obi) are on the same network - 3CX has a reserved DHCP address, Obi has a static IP outside that range. My physical SIP Phones are also static, and my iphone (with softphone) is DHCP. Results are the same regardless of endpoint (3CX Soft Phone, Physical Phone, Zoiper Softphone)

I have all Macs, so I'll see what I can do to set up a syslog server.
-Jason

jholme004

I downloaded a syslog app for a mac - here is what happens when I attempt to place a call through 3CX via SP4 to GV on SP1:

Date   Priority                                            Host            Message
2020-05-01 13:44:14   Kernel.Debug   10.172.17.207    OB:<==CRLF 1
2020-05-01 13:44:14   Kernel.Debug   10.172.17.207    OB:<==CRLF
2020-05-01 13:44:14   Kernel.Debug   10.172.17.207    OB==>CRLFCRLF
2020-05-01 13:44:14   Kernel.Debug   10.172.17.207    OB:<==CRLF 1
2020-05-01 13:44:14   Kernel.Debug   10.172.17.207    OB:<==CRLF
2020-05-01 13:44:14   Kernel.Debug   10.172.17.207    OB==>CRLFCRLF
-Jason

azrobert

You said:
QuoteResults are the same regardless of endpoint (3CX Soft Phone, Physical Phone, Zoiper Softphone)
Does the OBi202 attached phone work? If not, I doubt an IP client will work.

Did you follow option 2?
www.obitalk.com/forum/index.php?action=dlattach;topic=12895.0;attach=2230

Are you using the 3CX PBX or softphone? I'm confused because you need X_Proxy enabled to register a client to the OBi202, so I'm thinking you're registering to the 3CX PBX.

There was a bug that prevented some devices from registering to the OBi2xx. I don't know if the bug was fixed. The circumvention is disabling X_Proxy and changing the client to call without registration.

jholme004

#5
Thank you for that information and looking things over.

Yes, phone on PH1 and ph2 work properly.

I am using the 3CX PBX to the Obi202; all endpoints I mentioned go via the 3CX.

I've followed a bunch of different directions found online - they all seem to be slightly different. I went and double checked what I had to option 2 and made the following chnages:
     SP4/X_RegisterEnable = no (or unchecked)
     SP4/X_Proxy = yes (or checked)
     3CX Trunk 10001 Register = yes
Placed test call and still getting SIT and the following mesage in the 3CX logs: cause: Cause: 404 Not Found/INVITE from 10.172.17.207:5083  (I even held my breath and cocked my head when I dialed).

Obi Logs:
Date   Priority   Host   Message
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB:<==CRLF 1
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB:<==CRLF
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB:<==CRLF 1
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB:<==CRLF
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB:<==CRLF 1
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB:<==CRLF
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB==>CRLFCRLF
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB==>CRLFCRLF
2020-05-01 16:06:04   Kernel.Debug   10.172.17.207    OB==>CRLFCRLF

Looks pretty similar to the last set of logs. Now, in the ObiDashboard, it shows the 3CX Trunk as "Registration Not Required" - I am assuming that is because of the new X_RegisterEnable setting.

-Jason

drgeoff

1. The OBi syslogger does not seem to be giving much info.  Is its debug verbosity set very low?

2.  I use an OBi110 with FreePBX to give the PBX outbound access to a POTS line and the Obitalk network.  SP1 is for the phone on the 110 to register to the PBX.  SP2 is for a trunk from the PBX to the 110. OBi1x0 devices never had the ability to act as a SIP registrar for other devices.

The SP2 InboundCallRoute is

{>(<**9:>xxxxxxxxx):pp},{LI}

and X_RegisterEnable is ticked.

AuthUserName and AuthPassword match what is configured in FreePBX.


A trunk on FreePBX has as PEER details:

username=OBITRUNK1
secret=(redacted)
host=dynamic
type=friend
context=from-trunk
qualify=yes
dtmfmode=rfc2833
canreinvite=no
disallow=all
allow=ulaw&alaw

No USER details, no register string.

It is a while since I flirted with 3CX and don't remember how much of the above can be directly "mapped" to it

jholme004

OK, Thanks for all your help. I am able to now place calls externally via GV.  It took a bit, but I think this is what did it:
First I enabled call debugging for SP1 and SP4. Wow...alot more data. This one stuck out:
SIP/2.0 404 Not Found Call-ID: 6rqqX4GiWS-XcRw5y_Sezw

In peeking around, it looks like the obi will match the CallerIDName with information sent from 3CX Caller ID. Neither of those fields were configured previously. I undid the X_RegisterEnable and X_Proxy changes from earlier because prior to the changes both systems were showing as "registered", now neither one of them.

So I changed the following configs:

Obi202:
SP4/CallerIDName = 10001 (Trunk number)
SP4/X_RegisterEnable = yes (checked)
SP4/X_Proxy = no (unchecked)

3CX
SIPTrunks/10002/General/Authentication/Type of Authentication = Register/Account Based
SIPTrunks/10002/CallerID/Default Caller ID/Configure Outbound Caller ID=10002
SIPTrunks/10002/Options/Advanced/Supports Re-invites=No (Unchecked)

I've attached screen shots in case anyone else has similar issues and would love to hear any thoughts.
-Jason