You need to specify in Route pattern more specific ranges, so once the call comes back to cucm it gets rejected.
In route pattern we have the block this pattern option.
From an architecture point of view when u place a call to PBX, for cucm we have 2 call ids, ip phone and gw call id.
When the call is route back to cucm via vg from pbx , for cucm thats a new call and we cannot keep track of that call since H.225 GUId changes, if you are having this problem you need to review carefully your dial plan, since this problem is normally related to a bad dial plan design.
You could make use of Path Replacement and PINX number so that CCM and PABX knows where the call orginated from and drops the link if it is a tromboned call- or deny trunk to trunk - PABX will most certainly have this option if CCM does not.
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...