Assigning Specific Extension to Seperate Outbound Routes

Status
Not open for further replies.
E

Eric Bester

New Member
Jul 17, 2023
7
0
1
28
Hi guys.

I am new to fusion and am not getting the guidance I need through the FusionPBX Documents nor threads being similar to this issue, and was hoping to get assistance here.

I want to have a set of extensions dial out using their own seperate Outbound routes.

I have five extensions, grouped to ring when specific number are dialed, inbound and outbound.

The ring groups are set up as follows:

4220 = Extension 101
4693 = Extension 102/105
4697 = Extension 100/103
6950 = Extension 104

Now I have tried setting the caller ID on each extension and ring group to reflect the number we wish to show as the caller ID when calling. But even with the caller ID and outbound Caller ID set per extension, FusionPBX still uses the main Outbound route, which on this case was set as Rosettenville 3 at first, and later updated so that each gateway is added as an outbound route.

See the setup below:

Gateway information:
1693804923013.png

Destinations:

1693804969196.png
Outbound route:
1693805159780.png

Example of outbound route data:
1693805140840.png


With all the above taken into account, my question is this: Is there code or data I can set up on the outbound routes, to take the extension and force it to use that specified outbound route?

or if it has to do with the caller ID, is my setup incorrect? Please see my caller ID settings below for one of the extensions:

1693806158321.png
 
What are you trying to achieve her by using specific outbound routes, is it just to get a different caller id or is there another purpose?
 
It is basically just to get the caller ID's on each extension to show as the same number that was dialed to get through to that destination.

I.E Destination 27114344693 rings at ring group 4693, which is extensions 102 and 105. Now Extensions 102 and 105 must then have the caller ID of its Destination.

Caller ID settings for 102:
1693814841160.png

Caller ID settings for extension 105:
1693814868904.png

The caller ID was still showing as the Outbound Route ID after the caller ID settings were updated per extension. I am not sure how the outbound route manages the caller ID (hence the mention of the additional outbound routes)
 
Have you set a specific caller ID in the outbound route? If not, this should just work.

Check the outgoing invite to the carrier with SNGREP to see if it is being sent to the cariier correctly and maybe the carrier is overriding it.
 
We are the ISP that is doing the VoIP hosting for this client. I can confirm that the outgoing invite is received as the outbound route caller ID. If there is only one outbound route set, all the outbound calls show as the gateway number used for that outbound route. This client has been calling out using one number the entire time, and it worked perfectly on one outbound number. They now requested this change where they want these extensions connected to an inbound number, to be linked to that number doing outbound calls as well.

if I understand this correctly, if I want to set specific caller ID's in the outbound route, I will have to set to which extensions that caller ID has to be applied, being a condition rule?

when that condition is met, the caller ID has to be set to the according caller ID.

See below the current and only caller ID rules:

1693822330808.png

I dont know the xml code for setting up these conditions and rules. But, I believe the setup of this would be something like this:

Condition > Caller_id_name > extension_102=${outbound_caller_id_name}
1693823191147.png

the condition will then be that if the outbound call is made from extension 102, then the outbound caller ID must be that of the outbound route? The idea of putting this into xml code is confusing me as I dont know which terms to use.
 
Apologies for making this sound so complicated. I am struggle to get the wording correct :).

We want to set up multiple gateways, and multiple outbound routes, and then specify which extension has to use a specific outbound route
 
My point is, if you just are trying to present a different caller id, you do not need multiple trunks if you are using a standard carrier.

I use one carrier with hundreds of caller IDs.

If you do really need a trunk per extension then just add a condition to the outbound route that matches the extension number.

so something like condition caller_id_number=300 etc
 
Sorry, not to user, here is an example off a live box put it just under the user exists conditionselectiveroute.png....
 
DigitalDaz said:
My point is, if you just are trying to present a different caller id, you do not need multiple trunks if you are using a standard carrier.

I use one carrier with hundreds of caller IDs.

If you do really need a trunk per extension then just add a condition to the outbound route that matches the extension number.

so something like condition caller_id_number=300 etc
Click to expand...
Thank you.

I will test and let you know what I find
 
@DigitalDaz, Thank you for your assistance on this matter. You have been great help. It works.

The "condition" "caller_id_number" "^(350)$" (specifying which extensions to make use of this outbound route), works!
 
Status
Not open for further replies.
Top Bottom