I believe the issue could be one of two problems or possibly both.
Firstly have you applied the outgoing cor list to the outgoing POTS dial-peer?
For example the corlist outgoing cointernationalcall should be applied to your International POTs dial-peer.
Secondly, as you are using variable length digit-strings, I suspect that these are overlaping and International will be using the National POTs dial-peer for the outbound call-leg.
Run a 'debug voice capi inout' when you attempt to make an outbound International call from an IP Phone which does not the permission.
The debug will indicate which outbound dial-peer was used. If this is the case then you will need to revise the destination-patterns to make them more explicit.
For example, is your local digit dialplan a fixed number of digits starting with a certain prefix. Here in the UK they start with 2-9 and can be 6,7 or 8 digits, at least this defines it from National calls which start 0 and internation which start 00.
As I have previously mentioned, if you are using variable length digit-strings then it is possible that these are overlaping.
Run a 'debug voice capi inout' when you attempt to make an outbound International call from an IP Phone which does not the appropriate cor list.
The debug will indicate which outbound dial-peer was used. For example if you dial an international number from an IP Phone which is not permitted, the debug will show which dial-peer was used to place the call.
Please capture the appropriate debug as I have mentioned, and post the results.
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...