I'm trying to set it up so all calls coming from certain lines will have restricted outgoing caller ID information.
I've set up separate route patterns as follow:
9.[2-9]XXXXXX in the regular partition
with the Calling Line ID Presentation and Calling Name Presentation both set to Allowed.
9.[2-9]XXXXXX in the blocked partition with the Calling Line ID Presentation and Calling Name Presentation both set to Restricted.
I also have configured separate route lists and route groups to segregate these route patterns.
I have a test phone that is set up in the same restricted partition, but the regular caller id info is still going out.
What am I missing here?
I understand that I can create a more distinguished Route Pattern like *9.XXXXXXX (which is in production now,) or use another number to get an outside line, but I'm trying to keep it as simple for the user as possible.
It works just fine if I use a distinct route pattern. In production I'm currently using *9.XXXXXXX. I just changed my test to 6.XXXXXXX and the call did in fact show up as restricted with I made an off net call.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...