3CX Connecting to FreePBX

[mikegillespie]

Hi,

I followed the 3cx guide to setup a bridge between 3CX and Asterisk (https://www.3cx.com/docs/ )
Calls placed frm the 3CX to the Asterisk give a "403 forbidden" from the Asterisk IP address and the Asterisk reports;
"sip rtp tos bits 184
sip rtp cos mark 5"

Calls placed from the Asterisk to 3CX establish and function correctly.

Thanks

Mike

 

[mikegillespie]

here are the logs from 3CX;

10/28/2019 12:06:06 PM - L:49.2[Line:10000>>2000]: Terminating targets, reason: SIP ;cause=403 ;text="Forbidden"

10/28/2019 12:06:06 PM - Leg L:49.2[Line:10000>>2000] is terminated: Cause: 403 Forbidden/INVITE from 172.17.0.225:5060

10/28/2019 12:06:06 PM - L:49.2[Line:10000>>2000] got Terminated Recv 403/INVITE from 172.17.0.225:5060 tid=8058f3345e70df2b Call-ID=boF7tobgg0SbylDsEz9_oQ..: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 192.168.5.170:5060;branch=z9hG4bK-524287-1---8058f3345e70df2b;received=192.168.5.170;rport=5060 To: <sip:[email protected]:5060>;tag=as56490df7 From: "Mike Cabco"<sip:[email protected]:5060>;tag=604ff91f Call-ID: boF7tobgg0SbylDsEz9_oQ.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Server: FPBX-2.8.1(1.6.2.19) Supported: replaces, timer Content-Length: 0

10/28/2019 12:06:06 PM - L:49.1[Extn:1053] failed to reach Line:10000>>2000, reason Forbidden

10/28/2019 12:06:06 PM - Call to T:Line:10000>>2000@[Dev:sip:[email protected]:5060] from L:49.1[Extn:1053] failed, cause: Cause: 403 Forbidden/INVITE from 172.17.0.225:5060

10/28/2019 12:06:06 PM - L:49.2[Line:10000>>2000] got Failure: Failure Recv 403/INVITE from 172.17.0.225:5060 tid=8058f3345e70df2b Call-ID=boF7tobgg0SbylDsEz9_oQ..: SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 192.168.5.170:5060;branch=z9hG4bK-524287-1---8058f3345e70df2b;received=192.168.5.170;rport=5060 To: <sip:[email protected]:5060>;tag=as56490df7 From: "Mike Cabco"<sip:[email protected]:5060>;tag=604ff91f Call-ID: boF7tobgg0SbylDsEz9_oQ.. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Server: FPBX-2.8.1(1.6.2.19) Supported: replaces, timer Content-Length: 0

10/28/2019 12:06:06 PM - Session 3382 has failed in leg L:49.2[Line:10000>>2000] ; Cause: 403 Forbidden/INVITE from 172.17.0.225:5060

10/28/2019 12:06:06 PM - [CM503025]: Call(C:49): Calling T:Line:10000>>2000@[Dev:sip:[email protected]:5060] for L:49.1[Extn:1053]

10/28/2019 12:06:06 PM - Route to L:49.2[Line:10000>>2000] sends Invite-OUT Send Req INVITE from 0.0.0.0:0 tid=8a70a243e35efa0e Call-ID=boF7tobgg0SbylDsEz9_oQ..: INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---8a70a243e35efa0e;rport Max-Forwards: 70 Contact: <sip:[email protected]:5060> To: <sip:[email protected]:5060> From: "Mike Cabco"<sip:[email protected]:5060>;tag=604ff91f Call-ID: boF7tobgg0SbylDsEz9_oQ.. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE Content-Type: application/sdp Supported: replaces, timer Remote-Party-ID: "Mike Cabco"<sip:[email protected]3cx.ca:5060>;party=calling Content-Length: 255

 

[eddv123]

Why don't you just convert to 3CX fully ? https://www.3cx.com/docs/online-freepbx-elastix-askozia-converter/

Bridging 2 x 3CX systems would be far easier than separate vendors.

 

[mikegillespie]

Thanks for your feedback. Unfortunately, that is not the situation I am in currently.

 

[leejor]

Which PBX is the master? Does the Asterisk show any logs for the failed call attempts? A reason for the 403?

 

[YiannisH_3CX]

If the 3CX PBX is sending the call and the forbidden error comes from the Asterisk side then you should be searching for the solution in the Asterisk PBX. Perhaps there is something it does not like in the format of the call sent from 3CX but before you make any changes to the 3CX side you need to find out what needs changing.

 

[mikegillespie]

Yes, it appears to be the asterisk refusing the connection. TBH, i dont know where to look any deeper into the asterisk other than what is in the guide. https://www.3cx.com/docs/

 

[leejor]

If the asterisk has any sort of logging/troubleshooting system incorporated (like the Activity Log in 3CX), then that would show why the call is being rejected. If you don't get a helplfull reply here, you might try the an Asterisk forum, once you have narrowed down a reason for the 403 message as without that, you're just guessing.