I'm assuming you are attempting block outgoing called party numbers starting ^7 from ?
If this is the case then you should apply the call-block translation-profile incoming block_india on the incoming call-leg specifically the VoIP dial-peer from CallManager not on the pots as this will be the outbound call-leg:-
Can you clarify a little further please, it is not clear what telephony system the calling party 906821 is connected to. I don't belive it is CME as the diagram would show it connect to the gateway, so is it a PBX or CUCM?
Ideally it would be practical to block the calls nearer to the source, rather allowing the call to transverse the WAN using value bandwidth before being dropped.
If the calling party is connected to CUCM then you can implement calling restrictions using route-patterns in partitions assigned specifically to this DN's CSS.
Alternatively if the gateway is connected to a PBX, then you should configure the block translation profile on the incoming trunk call-leg. Is port 1/0:15 the PBX trunk port?
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...