Config please? COR should definitely respect whatever configuration has been made in the originating ephone-dn. If you are in doubt what is the ephone-dn being used, please enable "term mon" and "debug dialpeer".
My understanding of this feature is that what you have discovered is working as designed. The Cor parameter is applied per unique ephone-DN. So that means that you cannot have two diffent Restriction levels on the same number (in this case 8001). Have a look at these good docs;
I think that what Ken is saying, he has two separate ephone-dn (buttons in his terminology) with the same number (8001), and these are configured with different corlist. That is why I've asked for the configuration to clarify.
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...