Call Manager 5.x Route Filter Numbering Plan issue (AUNP)

Unanswered Question
Nov 4th, 2007

Hi,

We have had 2 instances on our deployments when the Numbering Plan has broken.

The following actions have occured which seem to trigger this, rename a single route filter and then broke all numbering and performing a restoration.

What happens is route filters do appear to be matched eg dial a mobile 0.04 (then bombs out as this will be the match). When bombing out added an explicit route pattern and worked ok.

The only way we have been able to fix this was to remove the route patterns, route filters, uninstall numbering plan, restart server, re-install numbering plan (perform this on both call managers).

Would like to know if any one has encountered this issue?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
rob.huffman Mon, 11/05/2007 - 06:06

Hi Heath,

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

Symptom:

Route filter clause in route filter configuration page for a particular filter show incorrect clauses not added by user.

Conditions:

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.

Workaround:

Don't click the main Save button in route filter configuration window.

1st Found-In

5.0(4.2000.1)

Fixed-In

5.1(0.9921.44)

5.1(1.1000.7)

5.1(1.2000.2)

6.0(0.9901.37)

6.0(1.1000.37)

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: 5.0.4.1000-1 , Administration version: 1.1.0.0-1

CSCsh95215 Bug Details

CCM: changing route filter clause causes like patterns to stop working

Symptom:

9.@ route patterns stops working.

Conditions:

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.

Workaround:

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.

1st Found-In

5.0

5.1

Fixed-In

5.1(1.3119.1)

5.1(1.9131.61)

5.1(3.1000.12)

5.1(2.3110.1)

Hope this helps!

Rob

heathrw Mon, 11/05/2007 - 13:09

Thanks Rob!

Will keep this in mind and let the team know..

Heath

Actions

This Discussion