I have a customer with CM 3.3. There does not appear to have the "canned" 7 digit dial filter that CM used to come with. I can work around this with spelling out all the individual route patterns (ie 9.XXXXXXX) but this customer of mine has 20 sites and a centralized model will mean I need need like a half-dozen route patterns for each site...that comes out to like 120 route patterns. That is crazy. I can use the 9.@ with route filters. But, I try copying a 7 digit dial filter on a current CM (3.1) and applying the rules to CM 3.3... it just doesn't work! Any ideas? I'm going to go over the CM 3.3 design guide again....
Yes! It's not brain surgery. So you're saying this should be working right? I'll have to check the trace files next...I'm making sure the design guide doesn't say something like..."in 3.3, you need to" blah blah blah
Interesting you should complain about having to build 120 route patterns,
Outside the USA the NANP file and subsequently the @ pattern do not work at all. I have a customer with 48 sites and was going to have to build a Route Pattern table with 1300 entries, however i have re-written the NANP file to cope with the UK dial plan and am now down to 6/7 entries per site including all their call barring requirements.
If you are having problems building a route filter you need to have a look at how the calls are matched in the NANP file (c:\program files\cisco\dial plan\) and then build the relevant 7 digit filter. I can't tell you the specific details because I don't work in the USA and am not familiar with the use of this filter, but once you study the file you should get the idea.
Interstingly All my CM builds so far (including 3.3) seem to have the 7 digit filter even though it's no good to me.
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.