I remember in CCM it used to be: if you create a route pattern 9.@ with no partition , no filter. IP phone can call anywhere as long as carrier no block.
but today i experienced unbelieved thing: I still create the same route pattern 9.@ with no partition no filter. But I only can make local call. That's it.
Then I tried to add 9.1416XXXXXXX, long distance works, same as 411.
CCM 3.33 . 3725 router MGCP. Has Cisco changed concept for the router pattern or I missed something? I think I am not wrong because I have so many current customer they don't need call restriction, I always use one 9.@ route pattern without router pattern and route filter.
This type of behavior (specifically with the @ dial plan macro) is usually the result of a picky switch that doesn't like you trying to boss it around.
Default CallManager configuration calls for CallManager to attempt to interpret the proper numbering plan on circuit types that support it (MGCP-controller PRI is the most common trouble spot). In the real world, it's common that telco switches have an issue with this and reject certain types of calls. In my experience, it varies if it's local vs LD.
Regardless, the fix is usually to modify two settings under your gateway:
Called party IE number type unknown*
Called Numbering Plan*
Set both of these to Unknown, reset your gateway, and try again with your 9.@.
Be aware there are some issues to using 9.@ with nothing else; the most common complaint will be delay after 7-digit local dialing (if applicable to your area).
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.