I cannot get Voxbone outbound trunk to work with our 3CX PBX

[gcnltd]

This is this the error messages I get:

07/23/2019 12:38:13 PM - Endpoint Extn:xx has refreshed contact <sip:[email protected]:5063>
07/23/2019 12:37:19 PM - Endpoint Extn:xx has refreshed contact <sip:[email protected]:5063>
07/23/2019 12:37:12 PM - Endpoint Extn:xx has refreshed contact <sip:[email protected]:5060>
07/23/2019 12:36:24 PM - Endpoint Extn:xx has refreshed contact <sip:[email protected]:5063>
07/23/2019 12:35:30 PM - Endpoint Extn:xx has refreshed contact <sip:[email protected]:5063>
07/23/2019 12:35:16 PM - Endpoint Extn:xx has refreshed contact <sip:[email protected]:5060>
07/23/2019 12:35:12 PM - Stop call record for leg L:385.1[Extn:xx]
07/23/2019 12:35:12 PM - Removing leg L:385.1[Extn:xx]
07/23/2019 12:35:12 PM - L:385.1[Extn:00]: Terminating targets, reason: SIP ;cause=200 ;text="User hangup"
07/23/2019 12:35:12 PM - Leg L:385.1[Extn:xx] is terminated: Cause: BYE from 127.0.0.1:5080
07/23/2019 12:35:12 PM - Call(C:385), Extn:xx on entry: DlgInfo(385-4687/Terminated / I)
07/23/2019 12:35:12 PM - Notify dialog-info: Extn:xx: sip:[email protected]:5060;rinstance=1-2019a091258b4396b9c4232c71af0c72, Call(C:385)
07/23/2019 12:35:12 PM - L:385.1[Extn:xx] got Terminated Recv Req BYE from 127.0.0.1:5080 tid=Pj1fa1c1a850f64d40a3eb8785b95ea7f7 Call-ID=8d2fd2cd32104dfa80c895e1adfe608b:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---Pj1fa1c1a850f64d40a3eb8785b95ea7f7;rport=5080
Via: SIP/2.0/UDP [::ffff:xx.xx.xx.xx]:61627;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.1-2019a091258b4396b9c4232c71af0c72
Via: SIP/2.0/TCP 1xx.1xx.x.xxx:50195;rport;branch=z9hG4bKPj1fa1c1a850f64d40a3eb8785b95ea7f7;alias
Max-Forwards: 69
Record-Route: <sip:[email protected]:5080;user=proxy;uri=clnt.1-2019a091258b4396b9c4232c71af0c72>
To: <sip:[email protected];tag3cx=52e3277d0d47444c9df41aadf3a139bc>;tag=7c013a12
From: "User Name" <sip:[email protected]>;tag=e60365e1db5341a9b8be5a6d15d61d0e
Call-ID: 8d2fd2cd32104dfa80c895e1adfe608b
CSeq: 476 BYE
User-Agent: 3CXPhone for Windows 16.0.1.81
Content-Length: 0

 

[gcnltd]

May be this
View attachment 11574

Those are 2 separate trunks going to 2 different groups.

 

[AWS2P]

Those are 2 separate trunks going to 2 different groups.

Of course but rules are read from top to bottom, so when +32 prefix is dialed this is the highest first rule matching which is used so, if i was you and you have not already tested, try to move up BE outbound rule before DEN one and do a test call to check if it's fine.

move up your rule


here, between this two lines

 

[AWS2P]

IMO, if i understand well, after this rule


who blocks eveything concerning Conversion with no prefix dialed, no more conversion rule can match, so for now your BE rule is at the end of the list , perhaps I'm wrong but for me this is the reason why you got the 3cx message : The destination is not available, registered or there are no routes available.