SPA112, Cloud PBX, can receive calls, but "call rejected" when initiating calls to extensions/outside numbers

[Nicolai]

So I realize the Cisco SPA112 is not officially supported but appreciate any recommendations / help

IP and Names changed, but you get the picture and critical information

I have a CLOUD hosted PBX (trial) at this point. (Standard Annual 15.5.15502.6)
REF > [email protected].156
This is working with a SIP trunk provider with a local DID, which is working properly (can receive calls to IVR/Extensions/Queue)

I have a number of extensions able to both

• received (incoming from a DID as well as internal extensions) and
• make calls internally and externally, using on Windows Client as well as iPhone 3CX app.

REF> Extension 104 is registered, contact: sip:[email protected]:5483;rinstance=de2a5a4dde304d04

At a remote site I have a specific extension (103) setup to a Cisco SPA112 adapter which is registering properly.

Extension 103 is registered, contact: sip:[email protected].115:5060

REF> Remote Site:96.XYZ.XYZ.115
REF> spa112 : 192.168.0.109

I am able to receive calls on the extension, the phone will ring and things seems normal, I can answer and hear voice from both internal calls/extensions as well as when connecting through the DID.

HOWEVER, I don't seem to be able to initiate, make an outgoing call from this physical phone, either to a PBX extensions or to any public phone number.

From the same remote office, the soft-phones work fine, but the hard phone fails due to the way it identifies itself w/ the Cloud PBX.
Here is the LOG file with the error message I am getting about being unable to initiate an outgoing call as the system does not recognize the extension for the hard phone through the spa112.

03/01/2019 8:26:30 PM - [CM503013]: Call(C:46): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 96.XYZ.XYZ.115:5060 tid=-1526bba1 [email protected]: INVITE sip:[email protected].156 SIP/2.0 Via: SIP/2.0/UDP 96.XYZ.XYZ.115:5060;branch=z9hG4bK-1526bba1 Max-Forwards: 70 Contact: "103" <sip:[email protected].115:5060;ref=103> To: <sip:[email protected].156> From: "103"<sip:[email protected].156>;tag=ea7f67eb7bba7abeo0 Call-ID: [email protected] CSeq: 102 INVITE Expires: 240 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Content-Type: application/sdp Proxy-Authorization: Digest username="XXXXXXX",realm="3CXPhoneSystem",nonce="XXXXXXXX",uri="sip:[email protected].156",algorithm=MD5,response="30246cb5028de16dd3310e0160db6a6a" Supported: replaces User-Agent: Cisco/SPA112-1.4.1SR1(002) Remote-Party-ID: "103" <[email protected].156>;screen=yes;party=calling Content-Length: 329

I'm at a loss as to where to change this behavior in order to let the SPA112 register itself, and then be able to initiate outbound calls.
Somehow when the SPA112 tries to initiate the call it uses the PUBLIC IP (96.XYZ.XYZ.115) of the remote office when connecting to the 3CX PBX (35.XYZ.XYZ.156) which then is rejects the ability to make the call.

Is this a spa112 specific configuration field (firmware Version 1.4.1SR1 (002) ), or something in the 3CX configuration one can adjust.

Any suggestions/assistance would be greatly appreciated.

N

 

[leejor]

Somehow when the SPA112 tries to initiate the call it uses the PUBLIC IP (96.XYZ.XYZ.115) of the remote office when connecting to the 3CX PBX (35.XYZ.XYZ.156) which then is rejects the ability to make the call.

Which is normal when using STUN, which I assume the device is set to use. In fact, 3CX should not be referring to the private IP of the 112 at all, as it has no way of contacting it, using that information. It must use the publc IP plus the unique (at that site), local port. You might check to be certain that all STUN settings on the 112 are correct. There should be some examples, on the web, to compare your settings to, or someone may post some.

 

[Nicolai]

Thanks for the answer, sorry on late reply, was on break.

So I've tried a number of different options and still can't get this to work.

From you message, it seems to stem from the fact that the SPA112 is having issues with the 3CX cloud server.
To be clear, the adapter is able to register with the server, I can receive incoming calls, both from local extensions and DID. The issue is with attempting an OUTGOING call from the spa112 (as from 3cx client on same LAN has no problems making calls).
Does anyone have any of the specifics on STUN settings for SPA112 to connect from a private LAN to a cloud based 3CX install. I'm played with different options, but does not seem to change the message from the 3CX activity logs.

03/14/2019 7:05:14 PM - [CM503013]: Call(C:26): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 96.AAA.BBB.115:5070 tid=-b35b0073 [email protected]:
INVITE sip:[email protected].156 SIP/2.0
Via: SIP/2.0/UDP 96.AAA.BBB.115:5070;branch=z9hG4bK-b35b0073
Max-Forwards: 70
Contact: "103" <sip:[email protected].115:5070;ref=103>
To: <sip:[email protected].156>
From: "103"<sip:[email protected].156>;tag=d9a3f791f20aeeb6o0
Call-ID: [email protected]
CSeq: 102 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Content-Type: application/sdp

So seems to be an issue w/ how the 3CX server is NOT recognizing the public IP from the Office, when trying to connect to other extensions or dialing out.
I actually get the dial tone, can attempt the call, however after about 10 seconds, the call fails and I get the above message.

Does anyone have this working ? Is it maybe a firmware specific setting for the Cisco/SPA112-1.4.1SR1(002). Any details on what to configure on the spa112 would be appreciated.

I've tested with port forwarding with 5060 and 5070 on the local router, but somehow I'm not sure where / what I need to setup on the spa112. Are any changes required on the 3cx server side (V15.5) to let it use the remote extension.

Suggestion welcome,

 

[eddv123]

Why not save yourself the headaches and simply hook up a VPN, most reputable platform providers support software firewalls now so it's a very easy deployment.

 

[leejor]

03/14/2019 7:05:14 PM - [CM503013]: Call(C:26): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 96.AAA.BBB.115:5070 tid=-b35b0073 Call-ID=4a5930ed-3759a50a@192.168.0.109:
INVITE sip:[email protected].156 SIP/2.0
Via: SIP/2.0/UDP 96.AAA.BBB.115:5070;branch=z9hG4bK-b35b0073
Max-Forwards: 70
Contact: "103" <sip:[email protected].115:5070;ref=103>
To: <sip:[email protected].156>
From: "103"<sip:[email protected].156>;tag=d9a3f791f20aeeb6o0
Call-ID: 4a5930ed-3759a50a@192.168.0.109
CSeq: 102 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Content-Type: application/sdp

It is very dd that hte IP of the 112 is being referenced in the Invite. let me do some digging, it may be a STUN setting. I don't think it will be a firmware issue.

 

[Nicolai]

Why not save yourself the headaches and simply hook up a VPN, most reputable platform providers support software firewalls now so it's a very easy deployment.

Definitively looking at this as an option, but right now still have to migrate by PBXExpress to a static IP, as well as see if I can configure local office router to support a VPN tunnel. Install is for a single spa112 phone, used for continuity of business for non technical staff members.
Everything except making outgoing calls works at this point, which is why I'm just looking for help/assistance on the spa112 / 3cx configuration. As far as I understand having a single sip device behind nat should work with stun, but as leejor indicated, not sure why the local IP is mentionned in the invite.

 

[eddv123]

OK so I get your point - for a single SPA this seems a major over-kill. I think you would be best buying a cheap "preferred" phone model (like a Yealink T19-E2) or just move them across to softphone with USB headset.

FYI if you I interested I have found using a platform provider with VPN a great option mostly because you have direct access into each endpoints web GUI from the platform itself - this is very useful when the need for troubleshooting arises - obviously I am talking about sites with multiple phones at a single location.

 

[bkreeger]

I agree, the time and effort is not worth wasting. Buy an inexpensive SIP phone like T19, Htek 924, etc.

 

[leejor]

Post a shot of the STUN settings on the 112.