Multiple SIP trunks for outgoing call

[Nobi0987]

Hello Again, Community!

We are hitting a roadblock getting Telnyx and 3CX to allow for multi-number support. We believe it might be because 3CX does not support Telnyx as a SIP provider out of the box. It looks like Twilio is natively supported, but we thought we would get feedback here before we migrate to another SIP provider.

We would love to hear who your favored SIP providers are that play nicely with 3CX and allow for:

- Multiple SIP trunks
- Our users to select which outgoing number to use on their 3CX clients

 

[SnakeRiverWebDevelopment]

Your provider make no difference, I have some SIP trunks with Telnyx as well as others, but you can't have
"Multiple SIP trunks for outgoing call" While 3cx does not support Telnyx, you can still use Telnyx. If you have multiple DID's with any provider you can choose within the outbound rules how to rout the calls, but you can't go out more than 1 SIP trunk at a time. What you can do is have a backup SIP trunk if the first one is busy or unreachable,

 

[leejor]

Some providers do have alternative URL's for registration, (individual city "locations" in some case) as to whether you can use the same account information on both, at the same time...you'd have to ask. Some do allow the creation of a sub account, to register on the alternative server address.

 

[YiannisH_3CX]

Hi @Nobi0987

What do you mean by multiple SIP trunks exactly? You mean multiple accounts, multiple DIDs or perhaps multiple channels so you can have multiple outbound calls simultaneously?

- Our users to select which outgoing number to use on their 3CX clients

You can do this via outbound rules where you can set different caller IDs based on what which outbound rule is matched.

Regardless of what you mean however it's always best to go with a 3CX supported provider.

 

[rayfield]

I'll add to the questions:

Do you mean multiple trunks, where each trunk has it's own unique Outbound DID number, where the 3CX client can select which outbound trunk/DID number is going to be used for an outbound call?

John Rayfield, Jr.
Rayfield Communications

 

[STI-David]

I have a similar request, using Dedicated Hosted.
One company, two divisions, each division has it's own main number.
Incoming calls are easy to route, however, outgoing calls from desk sets proving difficult, as some users need ability to use one or both numbers and to show the respective outgoing number call ID showing.
I was hoping there was a way to program a button that would allow the user to decide which outgoing number to use.

Thank you,
David

 

[leejor]

You could simply use a different prefix, depending on the number you wish to send. this would allow calls to use different outbound rules, each with a unique caller ID set in the rule. If one number was used for most calls, and those cals didn't require a prefix for outbound calls, then they could use one route, by default. Then the other outbound number was required to be sent, then a prefix could be added, thereby using the second outbound rule, sending the other CID number.

 

[STI-David]

Thanks Leejor,
I have tried this and one outbound rule uses an '8' with strip '1' works. The other I have tried 7 or 77 (strip 2) gets fast busy.

 

[STI-David]

OK, I got outbound calling to work for both accounts, using a 7 and 8.
On voip.ms wiki, they recommended "you MUST enable option "Use both "Call Source Identification" rules and "Caller Number/Name->CalledNum" field mappings""
and that works.
Now I have to figure out how to get the respective company name CNAME to show and not the users extension name.

David

 

[leejor]

Now I have to figure out how to get the respective company name CNAME to show and not the users extension name.

You may be able to get what you want by changing the outbound parameters on the trunk. Settings dealing with name display. Be careful, and make note of the original settings, before you change anything, as "playing around" with those can stop all outbound calls.

 

[YiannisH_3CX]

OK, I got outbound calling to work for both accounts, using a 7 and 8.
On voip.ms wiki, they recommended "you MUST enable option "Use both "Call Source Identification" rules and "Caller Number/Name->CalledNum" field mappings""
and that works.

That has nothing to do with outbound rules. This only affects inbound calls and VoIP.MS is currently rolling an update to make this not needed. You might already have the change depending on what VoIP.MS server you are using.

 

[STI-David]

Right now, the system is working as designed, users have option to dial out with either company name and number, using a 7 0r 9.

Thank you all for your input.
David