Toggle sidebar Toggle sidebar

External Call Over the Bridge

Status
Not open for further replies.

amanjuman

Trial User
Joined
Oct 3, 2020
Messages
36
Reaction score
1
So I have two 3CX Servers both are hosted in two different countries.
Master Server extension range - 1XXX
Slave Server extension range - 2XXX

Master Server Outbound Pattern - (9)2XXX - Length (5) > Stripe (1) - 2XXX
Slave Server Outbound Pattern - (9)1XXX - Length (5) > Stripe (1) - 1XXX

1. So both internal extension calling works. Master server got two numbers +1 (XXX)-XXX-XXXX which uses Master Server IVR and the other number are +1 (YYY)-YYY-YYYY. I like to set up rules so that when someone calls to +1 (YYY)-YYY-YYYY that call will be Routed to Slave Server IVR via Bridge.

2. I like to set up Outbound rules that whenever someone from the Slave server tries to call +1 (US) number that will use Bridge and use +1 (YYY)-YYY-YYYY as outbound caller id.

How do I achieve that?
 
For incoming, you will have to send callers to a destination that will "forward" the number to the second PBX. Something that adds the required prefix, for routing, to an IVR. This could be an IVR, on the first PBX, or a dummy extension.

As far as the outbound calls...use a different outbound prefix from what is used for outbound calls locally. If 9 is used locally, hen consider 7, or 8, for example. It would appear that you want to use 9 as a routing prefix for extensions, but if the range, on each PBX does not conflict, then you should be able to set it up to simply dial the extension number. I also assume you don't normally make use of a prefix for outbound calls. For calls to use the other PBX you'd have to have have a unique prefix for 3CX to know you want the call to use the other PBX outbound trunks.
Route the external call over the Bridge and use the new prefix to route the call to a new outbound rule, that will include the desired outbound caller ID. That provider must allow that caller ID to be used. Just be certain that there is no conflict with local outbound calls, if you don't want local users to make use of that rule.
 
For the Inbound call on Master Server, I created the same rules that you mentioned but it's not working and giving these errors.

Code: 
03/27/2022 11:51:14 PM - SendMsg from <sip:+1YYY YYY YYYY@master-server>;tag=fbe4ed37 to <sip:[email protected]>;tag=safasfas
03/27/2022 11:51:14 PM - Call(C:462) is terminated
03/27/2022 11:51:14 PM - [CM503020]: Call(C:462): Normal call termination. Call originator: Line:10002<<+1XYZXYZXYZZ. Reason: Not found
03/27/2022 11:51:14 PM - [CM503016]: Call(C:462): Attempt to reach <sip:[email protected]:5060> from Line:10002<<+1XYZXYZXYZZ has failed. Reason: Not Found
03/27/2022 11:51:14 PM - [CM503014]: Call(C:462): No known route from Line:10002<<+1XYZXYZXYZZ to target: <sip:[email protected]:5060/UDP>
03/27/2022 11:51:14 PM - Call(C:462): from Line:10002<<+1XYZXYZXYZZ to 91009 doesn't match any outbound rule. No outbound rule could be selected.
03/27/2022 11:51:14 PM - [Flow] Target endpoint for 91009 can not be built!
03/27/2022 11:51:14 PM - Selected prefix: 9
03/27/2022 11:51:14 PM - Selected prefix: 9
03/27/2022 11:51:14 PM - Looking for outbound rule: dialed = [91009], processed: [91009]; from-ext:
03/27/2022 11:51:14 PM - [Flow] Building target endpoint to 91009 from "+1XYZXYZXYZZ" <sip:+1XYZXYZXYZZ@master-server:5060>
03/27/2022 11:51:14 PM - [CM503010]: Call(C:462): Making route(s) from Line:10002<<+1XYZXYZXYZZ to <sip:[email protected]:5060/UDP>
03/27/2022 11:51:14 PM - Remote SDP is set for leg L:462.1[Line:10002<<+1XYZXYZXYZZ]
03/27/2022 11:51:14 PM - [CM505003]: Provider:[Twilo SIP] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060;transport=TCP]
03/27/2022 11:51:14 PM - Inbound DID: '+1YYY YYY YYYY'; Phonebook Name: ''
 
It says you don't have an outbound rule that matches 91009. Did you create one but limit who can access, perhaps?
 
Can you share a screenshot of your outbound rule so we can see the configuration?
 
From the looks of the rule, the call should use it. Do you have any other rules beginning with 9, perhaps above this one in the list? Could you try changing the prefix digits, in the rule to 91, making a bit more specific.
 
leejor said:
From the looks of the rule, the call should use it. Do you have any other rules beginning with 9, perhaps above this one in the list? Could you try changing the prefix digits, in the rule to 91, making a bit more specific.
Click to expand...
Tried 91 prefixes, same issue. In fact, removed all other rules just to be sure. No luck.
 
leejor said:
So...this is routing from a trunk (10002)...a Bridge trunk? Can an extension dial 91009, and reach the destination ?
Click to expand...
Master Bridge ID 10001 and Slave Bridge ID 10002
And Master and Slave can talk each other using 9 Prefix
 
So, I'm still unclear. Do calls from an extension, using the access digit 9, work, at each end?

amanjuman said:
from Line:10002<<+1XYZXYZXYZZ to 91009 doesn't match any outbound rule.
Click to expand...
Am I wrong, or is a call, coming in on a Bridge trunk, trying to route back out to the originating PBX?
 
leejor said:
So, I'm still unclear. Do calls from an extension, using the access digit 9, work, at each end?


Am I wrong, or is a call, coming in on a Bridge trunk, trying to route back out to the originating PBX?
Click to expand...
I'm trying to route a call for specific Phone Number calls to Slave 3CX using the bridge. 1009 is the extension on Slave 3CX so the rule is 91009 on Master 3CX.
 
...and where is the call originating from...a trunk?
 
Yes Twilio SIP
 
As it originates from a trunk, you may have to route the call to an extension, which is then forwarded to the other PBX, to make use of the outbound rules
 
Your outbound rule contains group of extensions. If the system is doing the forward then the rule will not work as the system does not belong to any group. Remove the groups from your outbound rule and try again.
 
Also if you are dialing normal numbers that are longer than 5 digits long then that will no match either.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,190
Messages
591,172
Members
165,244
Latest member
MentisAlliance
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom