Solved Bridge to trunk failed.

[Mal@Port]

Howdy all.
I have two sites joined with a bridge sharing a pair of trunks and in the last 48 hours the slave site can no longer accees the Masters trunk.
When calling out we get a voice messaged 'Cancelled' and the call is ended by 2 seconds.

From the Master call log when calling out via the slave.

02/12/2025 6:12:12 PM

Test (101)

EndCall

Answered

00:00:00

00:00:02

0.00

Not specified

Calls between extentions ( to and from ) accross the bridge is working.
Presence is working in both directions.
The trunk on the Master is accessable to the Master extentions and working on the Master PABX.
Calls from the Slave are logging on the Master
Both are on - Version 20.0 Update 4 (Build 487 Release) self hosted on Azure.

On the slave the Outbound rules are working, and tested. (I can call extentions accross the bridge, and I have varied the rules to check).
I can call out the local trunk on the slave.
Each other is whitelisted.
Bridge is connected and using the FQDN.
Both PBX have been restarted.
Both PBX is very a simple set up with a few users each, and some basic in/out rules.
The master has TWO trunks. One has a prefix to access (3) as it presents as a mobile number. Neither are accessable to the Slave.

These have recently been upgraded from v18 to v20 and calling was WORKING across the bridge.
I have DELETED the bridge and done over with the same end result.


I have a Verbose log captured.
its a 1079 lines for about 4 seconds of capture.

I have found the olny reference to the SIP Trunk with my call..
I have xxxxx the mobile and FQDN
This is looking like just a DNS event that got in the middle.

Contact: <sip:[email protected]:5483>
To: "Test"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=f5532765
From: "041XXXX08"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=c90d7148
Call-ID: LnZpoINRnW4fiWAYBZT76g..
CSeq: 2 BYE
User-Agent: 3CX EndCall helper
Reason: SIP;text=User Hung Up
Content-Length: 0

02/12/2025 5:52:36.688 PM Lsip{792/34.3/UAC*[Connected&Neutral]} is terminated, reason - RemoteBye
02/12/2025 5:52:36.688 PM Lsip{792/34.3/UAC*[Connected&Neutral]} sends: SendResp Send 200/BYE from 0.0.0.0:0 tid=3280c02492bda04e Call-ID=LnZpoINRnW4fiWAYBZT76g..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1:5483;branch=z9hG4bK-524287-1---3280c02492bda04e;rport=5483
Contact: <sip:[email protected]:5060>
To: "Test"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=f5532765
From: "041XXXX308"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=c90d7148
Call-ID: LnZpoINRnW4fiWAYBZT76g..
CSeq: 2 BYE
Content-Length: 0

02/12/2025 5:52:36.688 PM L:34.3[EndCall:EndCall{59eff002fdfb}] onReadyToSend: Send Send 200/BYE from 0.0.0.0:0 tid=3280c02492bda04e Call-ID=LnZpoINRnW4fiWAYBZT76g..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1:5483;branch=z9hG4bK-524287-1---3280c02492bda04e;rport=5483
Contact: <sip:[email protected]:5060>
To: "Test"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=f5532765
From: "041XXXXX08"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=c90d7148
Call-ID: LnZpoINRnW4fiWAYBZT76g..
CSeq: 2 BYE
Content-Length: 0

02/12/2025 5:52:36.189 PM DNS records cache for Lc:10002(@TPG SIP TRUNK[<sip:[email protected]:0/UDP>]) are still valid, refreshing current registration
02/12/2025 5:52:36.189 PM Lc:10002(@TPG SIP TRUNK[<sip:[email protected]:0/UDP>]) DNS cache expiration check for CorrectIP:5060/UDP fk=0 tgt=trunk-nsw.bizphone.tpgtelecom.com.au
02/12/2025 5:52:36.189 PM Reg. onRefreshRequired: h=36
02/12/2025 5:52:34.785 PM Lsip{788/34.1/UAS*[Connected&Neutral]}: confirmed:
InvIN Recv Req ACK from 127.0.0.1:5080 tid=5ac8581b402ae422 Call-ID=JON2SAPlSxmw4X5fL8PPQg..:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---5ac8581b402ae422;rport=5080
Via: SIP/2.0/UDP XXXX.3cx.com.au:5090;branch=z9hG4bK-524287-1---tunneltid;rport;bridgeid=10000
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-524287-1---5ac8581b402ae422;rport=5060
Max-Forwards: 68
Record-Route: <sip:[email protected]:5080;user=proxy;uri;bridgeid=10000>
Contact: <sip:[email protected]:5060>
To: "041xxx7308"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=3e028356
From: "Test"<sip:[email protected]:5060;rinstance=d988e2cca2d71f22>;tag=1914c312
Call-ID: JON2SAPlSxmw4X5fL8PPQg..
CSeq: 2 ACK
Content-Length: 0

Looking through the log there are lots of repeats of the same info.
It is looking like the bridge is NOT getting to the out bound rule set. I dont see why.

Any ideas??
Thanks
M

 

[NicholasP_3CX]

Do your outbound rules on the slave PBX have a department, or extension numbers defined? You would need rules that dont have these criteria.

As a test, create a rule that has a prefix of 04 and see if your call gets processed. If it works, then you would need to modify your existing rules to limit calls from extensions at the top, then anything else at the bottom, and limit the calls with the prefixes.

 

[Mal@Port]

Thanks for the info and assist.
Yep there was a department set on the rule as I was using this to control access.

M

 

[NicholasP_3CX]

Logical, the calls coming from the bridge are not part of that department.