Solved Calling SIP from bridge

[PaulEmous]

I have 2 PBX systems up and running.

PBX A, facilitating local calls
PBX B, (different location), facilitating local calls

I made a bridge with all outbound rules and confirmed its working for local extentions.

Now when I try to make an outbound call from PBX A > over over the bridge > to PBX B > SIP line; I get either a not allowed or not found error message.

We have been testing, wiresharking and what not, and came to the conclusion that it will only work if the extensions from PBX A are also present on PBX B. So it works. The weird thing however is that when I initially made a test setup this wasn't needed? I can say this quite confidently because the extensions on PBX B where not setup.

The only thing that changed is that we had a trial-license installed on PBX B that expired (the bridge function got lost) and I replace the expired key with a new Pro license last week when it all became dodgy and not working.

Super confusing. Anyone any idea what might be the issue?

Thanks,
P

 

[PaulEmous]

PBX A has v15.5 installed
PBX B has v16 installed.

 

[leejor]

Now when I try to make an outbound call from PBX A > over over the bridge > to PBX B > SIP line; I get either a not allowed or not found error message.

We have been testing, wiresharking and what not, and came to the conclusion that it will only work if the extensions from PBX A are also present on PBX B. So it works. The weird thing however is that when I initially made a test setup this wasn't needed? I can say this quite confidently because the extensions on PBX B where not setup.

You haven't said if you are using a prefix, to route the calls in the outbound rules. I have to assume that you are, as you mention the same extension number(s) exist in both PBXs. Check the 3CX Activity Log, in the PBX receiving the calls. Do the incoming digits match an extension , did you strip off the prefix, in the originating PBX?

Do the calls even make it that far, If not, then check the Activity Log in the originating PBX to see why they are failing. I also have to assume that, at this point, you are only trying to get extension to extension calls working , and not extension to outbound call via the other PBX.

 

[PaulEmous]

Okay let me try to explain how I initially had it setup.

PBX A -> 20 odd extensions
PBX B -> SIP 2 Lines installed (more about this below)

Bridge A -> B with outbound rule 5 to call PBX B
Bridge B -> A with outbound rule 3 to call PBX A

Outbound using PBX B, SIP 1
So when a call from PBX A gets initiated; It looked like the following: 5 (route to PBX B, strip 1 digit), followed by a phone number. -> This would work and all good.

Outbound using PBX B, SIP 2
So when a call from PBX A gets initiated; It looked like the following: 5 (route to PBX B, strip 1 digit & add 6), followed by a phone number. -> This would activate call route outbound rule use SIP 2. It worked as well until the license expired. Now some voodoo reason I have to add all the extensions in order to make outbound calls...

 

[YiannisH_3CX]

Hello @PaulEmous

You probably need a new outbound rule that does not filter extensions or groups of extensions to accommodate calls coming from the bridge A.
Test it using a generic outbound rule like only using the "Calls to numbers starting with prefix" option and use "+,0-9" as a value. Also select your SIP trunk as your route and see if that works. You can then further lock down the outbound call as per your requirements.

 

[PaulEmous]

Hello @PaulEmous

You probably need a new outbound rule that does not filter extensions or groups of extensions to accommodate calls coming from the bridge A.
Test it using a generic outbound rule like only using the "Calls to numbers starting with prefix" option and use "+,0-9" as a value. Also select your SIP trunk as your route and see if that works. You can then further lock down the outbound call as per your requirements.

Do I add a call group?

 

[PaulEmous]

Ok I noticed the rule was broken. I redid it and now its working.

 

[YiannisH_3CX]

Glad to see the issue has been resolved