I too would also like to block the caller id on some outbound calls. I tried setting up the route pattern *67 but keep getting busy signals, call cannot be completed as dialed, or in one case transfered over to Unity errors. Can someone who has gotten this to wok please be a little more detailed on the setup?
You cannot send the *67 out a PRI or at least I have never been able to do so. This whole issue depends on where the CLID comes from. If it's an analog port, the CLID comes from the serving providers switch and sending the *67 route pattern probably will work since that is a code given to all analog lines to block CLID. However, if the gateway is a PRI, the CLID can be affected many places, at the DN, at the RP, on the Gateway, at the service provider, etc.
So assuming that you can affect the final CLID from a Translation Pattern, that is where I would block it. Make it like *67.XXXXXXXXXX then inside for the Calling Line ID Presentation option put it to Restricted. Then do the rest of the Translations as what ever you need for your dialing pattern, discard PreDot, prefix '9', etc.
What I meant by the "The best way is to set up a separate Route Pattern which blocks CLI such as 9 for allow CLI and *9 to block " is to configure a new route pattern with a different prefix can be *9, *67 etc any number which is different to the route pattern which is normaly used to route your calls out. Configure to route in thE nomral way i.e use predot to delete the new prefix and set up CLI restriction on either the CCM GW page or in the H323 GW
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.