Setting Outbound Caller ID on Outbound Route

[kriley87]

Hi there-

We we have multiple phone numbers in different cities/area codes. When we call customers in different cities, we want our local number to show up as the outbound caller ID.

In FreePBX we have the ability to create outbound routes like this that would match the dialed route and set the caller ID to whatever the caller ID of the route is configured for.

713NXXNXXXX >> Caller ID: 7134444444
972NXXNXXXX >> Caller ID: 9724444444
817NXXNXXXX >> Caller ID: 8174444444

However, I don't see an option to configure an outbound caller ID for a particular outbound route in 3CX.

How can this be accomplished?

 

[AWS2P]

you can set it directly on each extension

 

[AWS2P]

in trunk sip do not set Global caller id if you want each extension send his proper number

 

[kriley87]

Thanks for the reply but I'm afraid that's not what I'm asking for.

I am asking if it's possible to set the outbound caller ID based upon the number being dialed.

For example, if I dial a 972 area code, it would show our 972 number as the outbound caller ID.
If I dialed an 817 area code, it would show our 817 area code as the outbound caller ID.

We are currently accomplishing this in FreePBX by setting the outbound caller ID on the outbound route itself. So for example:

713NXXNXXXX >> Caller ID: 7134444444
972NXXNXXXX >> Caller ID: 9724444444
817NXXNXXXX >> Caller ID: 8174444444

 

[leejor]

The feature you seek is still "In Progress"..
.
https://www.3cx.com/community/threads/ability-to-set-a-caller-id-for-outbound-calls.42840/

 

[kriley87]

In progress for 3 and a half years? That's reassuring... guess we'll be sticking with FreePBX as there's no way I would ever be able to convince my customer to pay for something that doesn't have the ability to do what their current platform does that they pay no licensing costs for.

Shame. I really want to like 3CX because the potential is there, but the lack of customization is a dealbreaker.

We moved a customer over to 3CX from FreePBX about 6 months ago and found out the hard way that you can't add external numbers to ring groups so we had to create a bunch of "virtual extensions" that forwarded to those external numbers and add them to the ring groups, which just made things messy from a management perspective.

shrug

You'd think with all of the monetization of 3CX that their feature set would blow everything else out of the water. Not so.

EDIT: I just thought of a workaround for this which was mentioned in the thread you posted... seems like the norm with 3CX, a ton of work arounds. I guess I could create multiple trunks with a dedicated outbound caller ID for each one and then create outbound routes for those dial patterns to route through the dedicated trunk to show the correct caller ID. Again, just makes things very messy from a management perspective.

 

[cobaltit]

So there are a couple ways to accomplish this in 3cx and they are both a bit of an administrative headache. You'd want to get a SIP trunking provider that does IP authentication (we can). Then you'd setup as many trunks as you need differing caller-ids and then outbound rules to use those trunks. You can also get creative with loopback trunks and caller-id manipulation but no only is that an administrative headache it also eats simultaneous calls.

@voiptoys Has a caller-id plugin that can handle this request as well, but it's an additional cost for something you can already do for free in FreePBX.

 

[cobaltit]

Oops, I see you amended your post with one of the two options I mentioned.