CALLERID PRIORITY

[covarrubiasgg]

Im currently running a cluster with VERSION: 2.14-777a BUILD: 201113-0754

We have 5 cities that we call most, so we have 10 DID from that cities and I would like to have those cities rotating the caller id, doing this with AC-CID is super easy.

BUT we don't want all other calls to default into the campaign CID, we would like to have rotating CID for all numbers without an area-code entry, i know i can do this with CID GROUP

So this is my problem the call priority is as following

Code: Select all

If all of the CallerID options are enabled, this is the priority in which each type of CallerID will be used, 1 is top priority -
1 - List CallerID Override
2 - CID Group entry
3 - AC-CID AREACODE entry
4 - Custom CallerID, Security Phrase
5 - USER_CUSTOM CallerID
6 - Campaign CID

So if I enable CID Group on my campaign I lost the ability to do AC-CID, is there any way to achieve what I am looking for ?

So far my only idea is to create an AC-CID for my 3 main cities and add two digits area codes 11,12,13...22,23...50,51..97,98,99 , but that means that if want to rotate 10 CIDs i will have to ad 900 entries per campaign

Am I missing something? Is there anyway to change the priority. To be honest that priority doesn't make much sense to me

[carpenox]

well im not sure which php page has the code for that but im sure if you looked at the code you could just "rearrange" the order of the code.....should work in theory

[mflorell]

It's not just in one place in one PHP script, it's multiple places in more than one PHP and Perl script, and it took hours just to get them all into one uniform order when I reviewed the code a few years ago, making this operate in a configurable order would probably take days of programming and testing given the complexity of how it all works.

[carpenox]

well dayum, thats a mission and a half.....

[ccabrera]

@covarrubiasgg , if nothing of the available options suit you, just call a custom AGI which reads the destination number and switches CID accordingly by reading from the database, just before as you dial out.

As long as you only change the CALLERID(num) and not the CALLERID(name), the agi-VDAD_ALL_outbound.agi will still work, and calls will get routed properly to their respective agents.