Hello - I had a question that I was hoping someone could help me with. I recently had an issue on CallManager 4.1.3sr6a. I have 10 sites, each using their own set of 6 9.@ route patterns for outgoing calls. Although the patterns are distinct, they all use the same route filters. Today, all of the sites began matching on the route pattern with the seven digit filter rather than matching on the long distance filter when a 91XXXXXXXXXX number was dialed (we tested with a number of numbers in different area codes). I wasn't able to input more digits after the 7th and DNA confirmed that it matched on the seven digit filter. The filters are as follows:
Long Distance =(AREA-CODE EXISTS AND LONG-DISTANCE-DIRECT-DIAL EXISTS)
SevenDigit = (LOCAL-AREA-CODE DOES-NOT-EXIST AND INTERNATIONAL-DIRECT-DIAL DOES-NOT-EXIST AND AREA-CODE DOES-NOT-EXIST AND SERVICE DOES-NOT-EXIST).
I was able to resolve the issue by going to each site, removing the long distance 9.@ pattern and simply readding it (no changes were made to configuration).
It was like it just stopped seeing all patterns using the long distance filter.
I'm wondering if anyone is aware of a bug that may have caused this.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...