Below you'll find the simplest form I can come up with for representing my Calling Search Space & Route/Translation Patterns. My thought process for this is as follows. If a call comes in to a phone registered to CUCM, we want to match that (All-IP-Phones). We're transitioning from 7 digit numbers to 10-digit numbers, so there's a translation pattern that takes a call placed to 7 digit number and tries it w/ the area code pre-pended ...and check for that number registered to CUCM (10-digit-864-translate-864-SIP). We check for int'l calls (SIP864-Intl), and 911 (SIP864-911)*. I have partitions in place I'm not using (SIP864-1803 & SIP864-1864) ...and probably should remove. Our voicemail (currently Asterisk) pilot number begins with 555 so we funnel all those calls down the appropriate SIP trunk (SIP864-555). For Long distance calls (1.@) they're matched in SIP864-LD.
The problem comes in here. I've specified a route pattern that should match 10 digit calls w/ XXXXXXXXXX in the SIP864-10-Digits** partition. (These last two partitions/route patterns direct calls out our sip trunk un-molested.)
The final route patterns are in the SIP864 partition. We allow per-call caller-id blocking with the *67 route patterns. I also have a pattern that should match 7 digits (XXXXXXX) and @ ...which should match anything else, though I've tried to build the CSS so that the @ won't be used. On these last two patterns, we prepend the area code (864) so that we can direct calls out our SIP trunk (which requires 10 digits).
What is happening is a user calls a number w/ 10 digits, it hits the @ pattern in SIP864 (instead of the XXXXXXXXXX in SIP864-10-Digits) and strips off the intended area code and replaces it with 864 ...and the call fails.
I get that @ is a list of patterns, ...and apparently one of them is more specific than my 10 xes pattern above. How can I make it so that users are able to dial 10 digits or 11 digits for long distance, while maintaining the ability to dial 7 digits in-area-code?
Route Partitions in order, with route patterns (except the translation pattern specified):
Just for giggles, I wanted to see if removing the @ would make it work as expected (since I DO have a 7xes route pattern ...which is all I'd intended to use the @ for anyway). I also tweaked the 7 & 10 digit patterns to [2-9]XXXXXX and [2-9]XX[2-9]XXXXXX.
It works like I want it to. I'm a bit nervous to remove the @ permanently from my CSS, but I've set up a copy of this CSS for testing to see if I run into problems without it.
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...