how i can determine outbound fxo line for each extension

[Network Emad]

how i can determine outbound fxo line for each extension through 3cx

i tried to find any way to determine the trunk for each extension
ex: the outbound call for theses extensions

this FXO-0 00000 fro extensions: 124. 114. 117

FXO-1 000001 for extensions: 110, 125, 178
FXO-2 000002 for extensions: 127, 247, 205
FXO-3 000003 for extensions: 635, 576, 332


each extension will forwarded through determined line.

how to apply this in 3cx and patton ???


thak you

 

[eddv123]

Hi Network Emad,

One way you could do this would be to dial a prefix and have the Patton select a specific FXO port based on that.

The prefix would be a way to avoid breaking into four trunks.
All outgoing calls would have a prefix.

e.g. 71<number>..74<number>

The Patton would need some modifications for the routing table + mapping function.
e.g. 71(.%) -> send to FXO1, strip the first two digits.

 

[NickD_3CX]

The config file generated by 3CX and the tested/supported way of configuring FXO Patton devices involves 1 registration/connection between 3CX and the Patton device.
That means that 3CX only "sees" 1 device, not 4, so there is no way to configure 3CX to send to 4 lines depending on who is initiating the call with this setup.

If however you were to do a custom/manual setup of the Patton device (not supported by 3CX), you theoretically have 2 options:

• You could have the Patton device register against 3CX 4 times, so 3CX would perceive this single device as 4 as well, then you could adjust the Outbound Rules to send the call to each one as you want. Of course you would also have to manually configure the routing of each account in the Patton device as to which FXO port it would use accordingly.

or

• Leave the registration as is so that it registers only once, but for each "group" of extensions, you set a Outbound Caller ID which is the same among extensions of the same "group". Then on the Patton device, you would read the "From" number and route and the corresponding FXO port.