Re: Call Manager 5.x Route Filter Numbering Plan issue (AUNP)
It sure sounds like one of these 5.x Bugs. The first one listed does affect the AUNP;
CSCsg43265 Bug Details
Route filter main save button incorrectly modified filter in database
Route filter clause in route filter configuration page for a particular filter show incorrect clauses not added by user.
There are 20 existing clauses, and a 21st has just been added. Save button on upper right of configuration screen is clicked.
This may also occur under other conditions when Save button is pressed. Currently unable to reproduce this part, but saw multiple clauses get deleted after removing a clause and clicking Save, although only one clause should be removed.
Don't click the main Save button in route filter configuration window.
Router filter clause information becomes corrupt after clicking save
- Open CCMAdmin on Cisco CallManager 5.0.4 - Go to Call Routing --> Route Filter - Click "Add New" - Select Numbering Plan - Enter route filter name (e.g. "test") - Within the clause information area, select AREA-CODE exists, and click "Save" - Click "Add Clause" to add another clause - Select COUNTRY-CODE exists, and click "Save" - Click "Add Clause" to add another clause - Select SERVICE exists, and click "Save" Up to this point, if you leave things as they are, everything works perfectly. Route filter functions as it should, and it also looks fine, where Clause = (AREA-CODE EXISTS) OR (COUNTRY-CODE EXISTS) OR (SERVICE EXISTS) To recreate the problem, just click on the "Save" button again, while looking at the route filter. Once done, the clause information will change dramatically, breaking the way the route filter works, where it becomes: (AREA-CODE EXISTS AND COUNTRY-CODE EXISTS AND SERVICE EXISTS) OR (SERVICE EXISTS) OR (SERVICE EXISTS) This has been tested on both the North American Numbering Plan and the Australian Numbering Plan on System version: 126.96.36.1990-1 , Administration version: 188.8.131.52-1
CSCsh95215 Bug Details
CCM: changing route filter clause causes like patterns to stop working
9.@ route patterns stops working.
If you have more than one 9.@ route pattern and at least one of the 9.@ patterns has a route filter.
If you change the clause on the route filter the other 9.@ patterns will stop working.
To get the 9.@ patterns with out the filter to start working again go and make a change on them update them then change it back and update again.
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...