atcomsystems.ca/forum Forums Other TDM Phone Systems VoiceMail Systems and Programming Interpreting Altered CLID

With some of our voicemail system's you have to program what are vaild digits to be received fron internal calls and external calls so the voicemail can route them to the proper destination . We are coming across more and more issues where the incoming caller id has been altered by the sender . This is frequent occurence with our Government Intities . We will receive an ID that looks like this .

209-000-0000 or
510-656

Since these are not valid NANP our voicemail sends them to the "thank you for calling hang up bucket" Is any one else having an issue like this . We keep having to alter our external dial plan to reconcile these altered ID'S .

Sorry for the long post .

Keyvoice just has a wildcard for CID (example: B@#103#=103,*,*:caller=@, where the traced string would show up as B5595551212#103#). I wonder if you have a wildcard option you could use on the ones you're having this trouble with.

See if you have the ability to route invalid or unknown CIds to a mailbox with the greeting.."Your caller ID cannot be matched to records in our database. Please wait while your call is routed to a customer service representative." Calls would then be routed to an attendant console. They can wait in queue like everyone else if they choose to mask their caller id.

Yes the systems that are causing us extra programming have incoming X & Y wildcards .

X = x&x
Y = x-x
or you can programm per incoming digits received .

The software will not allow digit conflicts in the wildcard table .

We also do a lot of CLID routing so the area code gets directed to the correct Message Box .

RBF

That is a good idea ! I will take a second look at our options . Thank You for your suggestion . At the very least they will not be disconnected but will be routed to a live body.

RBF
I tried your idea on 1 system today , though some what modified and it works great . Thanks again