Obi110 with IncrediblePBX2022B2 on Debian 11 and pjsip

[dbayer]

Hello,
I have an existing FreePBX 14 that I'm moving over to IncrediblePBX. On FreePBX I have an Obi110 FXO trunk using chansip that works just fine. I've tried moving over the same chansip trunk settings and when I make a call it can't find the proper codec (alaw). So I tried setting it up with pjsip. But the incoming calls, keep saying they are anonymous. I cannot figure out what setting I need to change so these incoming calls do not appear to be anonymous. Below is the asterisk log output from an incoming call.

63607SIP/2.0 100 Trying
63608Via: SIP/2.0/UDP 10.x.x.160:5061;rport=5061;received=10.x.x.160;branch=z9hG4bK-6b50db7d
63609Call-ID: [email protected]
63610From: "NUMBERALL STAMP" <sip:[email protected]>;tag=SP2714cc30a291cf17d
63611To: <sip:[email protected]>
63612CSeq: 8001 INVITE
63613Server: IncrediblePBX-16.0.26(18.0)
63614Content-Length: 0
63615
63616
63617[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [2078xxxx11@from-sip-external:1] NoOp("PJSIP/anonymous-00000022", "Received incoming SIP connection from unknown peer to 2078xxxx11") in new stack
63618[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [2078xxxx11@from-sip-external:2] Set("PJSIP/anonymous-00000022", "DID=2078xxxx11") in new stack
63619[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [2078xxxx11@from-sip-external:3] Goto("PJSIP/anonymous-00000022", "s,1") in new stack
63620[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx_builtins.c: Goto (from-sip-external,s,1)
63621[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [s@from-sip-external:1] GotoIf("PJSIP/anonymous-00000022", "1?setlanguage:checkanon") in new stack
63622[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx_builtins.c: Goto (from-sip-external,s,2)
63623[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [s@from-sip-external:2] Set("PJSIP/anonymous-00000022", "CHANNEL(language)=en") in new stack
63624[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [s@from-sip-external:3] GotoIf("PJSIP/anonymous-00000022", "1?noanonymous") in new stack
63625[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx_builtins.c: Goto (from-sip-external,s,5)
63626[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [s@from-sip-external:5] Set("PJSIP/anonymous-00000022", "TIMEOUT(absolute)=15") in new stack
63627[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] func_timeout.c: Channel will hangup at 2022-12-05 18:20:07.972 EST.
63628[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [s@from-sip-external:6] Set("PJSIP/anonymous-00000022", "receveip=pjsip,remote_addr") in new stack
63629[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [s@from-sip-external:7] Log("PJSIP/anonymous-00000022", "WARNING,"Rejecting unknown SIP connection from 10.x.x.160:5061"") in new stack
63630[2022-12-05 18:19:52] WARNING[908842][C-00000017] Ext. s: "Rejecting unknown SIP connection from 10.x.x.160:5061"
63631[2022-12-05 18:19:52] VERBOSE[908842][C-00000017] pbx.c: Executing [s@from-sip-external:8] Answer("PJSIP/anonymous-00000022", "") in new stack
63632[2022-12-05 18:19:52] VERBOSE[896998] res_pjsip_logger.c: <--- Transmitting SIP response (911 bytes) to UDP:10.x.x.160:5061 --->
63633SIP/2.0 200 OK

 

[kenn10]

Did you place the IP address of the OBI in the "match" field on the PJSIP trunk in the PBX? Is the new PBX in the cloud or on a local server?

 

[dbayer]

Thank you for the help.

It is on a local server.
I have tried putting it in the match field, no change in the issue.
I've also tried changing the context, didn't seem to make any difference.

 

[kenn10]

OK. I don't have or know much about the OBI devices so maybe someone else will speak up here. Most of us have abandoned the physical land line and gone with a SIP provider.

My only other advice is to look at the OBI and make sure you have it registering to your PJSIP port (5061 or whatever) instead of the chan_sip port. The other thing seems to point to that number not being known to the PBX. Is that DID added as an inboud route?

 

[dbayer]

We probably won't be using the OBI much longer, but I wanted to move everything over as is for now.

I have logged into the OBI and configured it to use the right ports and address. I can make outgoing calls, It just doesn't seem to recognize it as an internal device for incoming calls.

For now, I just have an inbound route for Any DID/CID to my extension for testing.

I can see in the Asterisk log that it is registering with the PBX on bootup.

 

[dbayer]

Just wanted to post a follow up to this. I ended up deleting this trunk and the chansip trunk I was working on. I recreated from scratch the chansip trunk and it works perfectly. I must have messed something up while troubleshooting this.