Internal 3cx to 3cx routing
Page 1 of 1
Internal 3cx to 3cx routing
Hi,
Does ProSBC support internal to internal dialling.
Theory below;
PBX 1 -> internal IP 10.200.201.5
PBX 2 -> internal IP 10.200.202.5
If PBX 1 wants to dial PBX 2 (ie CT group is PBX 1 and Client A is PBX2) can the SBC have a route that supports “internal dialling” for lack of a better phrase.
Essentially if we can keep the voice call completely inside our DC we can reduce call costs as well as improve the quality of the phone call as it won’t need to goto the upstream provider at all.
Does ProSBC support internal to internal dialling.
Theory below;
PBX 1 -> internal IP 10.200.201.5
PBX 2 -> internal IP 10.200.202.5
If PBX 1 wants to dial PBX 2 (ie CT group is PBX 1 and Client A is PBX2) can the SBC have a route that supports “internal dialling” for lack of a better phrase.
Essentially if we can keep the voice call completely inside our DC we can reduce call costs as well as improve the quality of the phone call as it won’t need to goto the upstream provider at all.
Guest- Guest
Re: Internal 3cx to 3cx routing
Hi,
At the moment, calls from PBXs will always go to Vocox, like below, no matter to external numbers or PBX1 calling PBX2, as recall from last time,
PBX -> SBC -> Vocus
We can try to, if needed, do a static route from PBX1 NAP to PBX2 NAP, for example, based on a unique matching called number from PBX1 to PBX2, that will distinguish that from PBX1 to Vocus (if not “ANY” for called number from PBX1 to Vocus). We can see the existing configuration and see how this can be achieved for the requirement.
If the route from PBX to Vocus is with no specification or “ANY” on called number, then we can also consider to use priority for routing, say, if going to Vocus doesn’t setup a call, it can always route retry to PBX 2, for example.
At the moment, calls from PBXs will always go to Vocox, like below, no matter to external numbers or PBX1 calling PBX2, as recall from last time,
PBX -> SBC -> Vocus
We can try to, if needed, do a static route from PBX1 NAP to PBX2 NAP, for example, based on a unique matching called number from PBX1 to PBX2, that will distinguish that from PBX1 to Vocus (if not “ANY” for called number from PBX1 to Vocus). We can see the existing configuration and see how this can be achieved for the requirement.
If the route from PBX to Vocus is with no specification or “ANY” on called number, then we can also consider to use priority for routing, say, if going to Vocus doesn’t setup a call, it can always route retry to PBX 2, for example.
Guest- Guest
Similar topics
» IP routing question
» FreeSBC How To - SIP Routing
» MS Teams Routing
» SIP - Domain Routing
» LCR Priority Routing
» FreeSBC How To - SIP Routing
» MS Teams Routing
» SIP - Domain Routing
» LCR Priority Routing
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|