outbound rules with CID

[Zvjer]

Hello,

We have a dialer in place for a sort of outbound calling campaign. We have customers in the database that need to be reminded for a doctors appointment etc, and we have agents that are logged in to queue. How this works: 3rd party dialer tells 3CX via API to make a call and if the called party answers the phone it transfers the call to the agent who already has everything he needs to say on his screen. Up to this point we already have everything working, but

Company grew and now we have a need for two different dialers for two different sets of agents and outgoing calls that dialer makes must send a corresponding caller ID, so in case of a missed call from the called party side - the end customer can get back to the right agent group. We haven't found a way for the dialer to tell 3CX which caller ID to use (via API) so we just forced all outbound calls from the SIP trunk to have the same number. Otherwise - the dialer sends a "makecall" identification to the SIP provider who in turn drops the call.

Do you guys have any idea how to solve this? One idea would be that outbound rules have different prefixes and different caller id, but 3CX hasn't got this implemented.
Other idea is to tell SIP provider to authorize us via IP address instead of username/password so we can duplicate SIP trunks and put different caller ID to each one, but that means we'll have to split the amount of paid/available voice channels.

I'm out of ideas how best to handle this.

 

[YiannisH_3CX]

Hello @Zvjer

Currently to send a different caller ID you need to call from a different extension which has a different caller ID configured or call from a different trunk. With a second trunk you can add a prefix and select the correct outbound caller ID that way.

Other idea is to tell SIP provider to authorize us via IP address instead of username/password so we can duplicate SIP trunks and put different caller ID to each one, but that means we'll have to split the amount of paid/available voice channels.

IP based trunks do not authenticate to the provider so the provider only sees one system. So even if you have 2 trunks the channels would be the same. The limitation is at the providers side not the PBX so even if you have 2 trunks you can still have all calls go through one trunk.

 

[leejor]

I think this is what you're waiting for (It's long, just go to the last page)....

https://www.3cx.com/community/threads/ability-to-set-a-caller-id-for-outbound-calls.42840/