[cisco-voip] CallManager Route Pattern/Filter Problem...

Sat Dec 17 08:42:23 EST 2005

The problem lies with the fact that some carriers do not want to see a 1 and
the Number Plan/Type ISDN/National - same goes with International calls -
some switches just puke if you send them both, however send them one or the
other and they are just fine.

Basically it is a programming problem in your local 5ESS - But the carrier
would never admit that ;)

  _____  

From: Cisco [mailto:subs-cisco at cbvcollections.com] 
Sent: Saturday, December 17, 2005 1:58 AM
To: Lelio Fulgenzi; Mark Snow; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CallManager Route Pattern/Filter Problem...

Yes, I'm with Bell (West) in Vancouver.  We have another CM cluster in the
east (Toronto) who is also with Bell.  The cluster in Toronto is using a
different PRI protocol (DMS-100) then the Vancouver is using (NI2).

Well it is late at night so I've been playing with the gateway configs and
trying your suggestion.  After changing them to unknown - it worked!  Can
you tell me why?  Also what should the setting for "Called party IE number
type unknown*" be?

P.S.  I will definitely look into your site/course offering!

  _____  

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
Sent: Friday, December 16, 2005 9:35 PM
To: Mark Snow; Cisco; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CallManager Route Pattern/Filter Problem...

You cannot do a debug isdn, but you can import the CCM trace files into the
q931 debug tool and read the output that way. It's a pretty good tool and
I've used it a few times. That's the standalone tool, not the one that is
built into CallManager.

And our numbering plans are set to CallManager.

Frank - are you in Canada? What is your provider? Bell? I can provide with
all of our 6608 parameters if that would help.

----- Original Message ----- 

From: Mark Snow <mailto:highspeedsnow at gmail.com>  

To: 'Cisco' <mailto:subs-cisco at cbvcollections.com>  ;
cisco-voip at puck.nether.net 

Sent: Friday, December 16, 2005 11:41 PM

Subject: RE: [cisco-voip] CallManager Route Pattern/Filter Problem...

Lelio is correct, make sure that digit manipulation is not occurring at the
Route Pattern, OR within the Route Groups inside the Route Lists.

If those are not stripping anything but PreDot then try this:

Try changing:

*	Called Numbering Plan*: unknown 
*	Calling Numbering Plan*: unknown 

Then test your calls - see if they work - you will have to do a reset on the
6608 gateway first, so make sure that there are no calls going on at the
time.

Also, since you are running a 6608 blade on a 6500 Cat, you cannot do the
'debug isdn q931' command I asked about previously.

LMK if that helps .

And hey, if you do want to become a Voice Expert soon, check out my class
sometime:

http://www.ipexpert.com/products_services/product.asp?sku=ip0012

-Mark Snow

CCIE Voice # 14073

  _____  

From: Cisco [mailto:subs-cisco at cbvcollections.com] 
Sent: Friday, December 16, 2005 8:17 PM
To: Mark Snow; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CallManager Route Pattern/Filter Problem...

Well I'm far from the telephony expert I want to be (at this point - give me
a few months) but it would appear that you may be on to something.  I took a
look at the gateway configurations within CallManager.  Each of the gateways
within the PSTN group (Product : Cisco Catalyst 6000 T1 VoIP Gateway -
Device Protocol: Digital Access PRI) have the same configuration.  The
following settings are currently used from the Call Routing Information
(Outbound):

*	Calling Line ID Presentation*: Restricted 
*	Calling Party Selection*: Originator 
*	Called party IE number type unknown*: Cisco CallManager 
*	Calling party IE number type unknown*: National 
*	Called Numbering Plan*: Cisco CallManager 
*	Calling Numbering Plan*: ISDN 
*	Number of digits to strip*: 0 
*	Caller ID DN: 
*	SMDI Base Port*: 

Do you think the underlined (above) is causing the issue?  Is this something
I can change (to "Cisco CallManager") or do I need to involve our provider?

  _____  

From: Mark Snow [mailto:highspeedsnow at gmail.com] 
Sent: December 16, 2005 4:59 PM
To: Cisco; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CallManager Route Pattern/Filter Problem...

Is it a PRI that the call is going out of on an IOS GW?

If so, have you done a 'debug isdn q931' to ensure that in fact the CCM is
dropping the 1?

-Mark Snow

CCIE Voice # 14073

  _____  

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Cisco
Sent: Friday, December 16, 2005 7:24 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CallManager Route Pattern/Filter Problem...

I'm trying to use route filters (area code == 204 OR etc.) with a "9.@"
pattern instead of the more difficult to manage 9.1204XXXXXXX to route long
distance calls.  

The pattern/filter work fine, the problem is that when the number is matched
using 9.@ pattern (verified with the Cisco the dialled number analyser), by
the time it reaches the local provider somehow the "1" is dropped and the
caller is presented with a message "you must dial 1 to access a long
distance number" from the local provider.  If I change the pattern back to
9.1XXXXXXXXXX then the number is dialled as expected.

I've used the dialled number analyser to ensure that no transformations are
taking place at any point along the route to the PEST gateway.  According to
the analyser the dialled number that is sent to the PEST gateway in either
case is the same.  However, one works and the other does not.

I should also note that the 9.@ pattern with a filter of (local area code ==
604 OR etc.) for local 10 digit dialling works just fine as either 9.@ or
9.XXXXXXXXXX.  Both are routed as expected.

Ideas?

  _____  

  <http://www.cbvcollections.com/cbvImages/ecardlogo.jpg> 

Frank Wakelin
Senior Network/Security Analyst

100 - 814 Richards St.
Vancouver, BC
V6B 3A7

Telephone: (604) 661-7906
fwakelin at cbvcollections.com

Confidentiality Warning:
This message and any attachments are intended only for the use of the
intended recipients (cisco-voip at puck.nether.net), are confidential, and may
be privileged. If you are not the intended recipient, you are hereby
notified that any review, retransmission, conversion to hard copy, copying,
circulation or other use of this message and any attachments is strictly
prohibited. If you are not the intended recipient, please notify the sender
(Cisco <mailto:subs-cisco at cbvcollections.com> ) immediately by return
e-mail, and delete this message and any attachments from your system. Thank
you. 

Information Confidentielle:
Le present message, ainsi que tout fichier qui y est joint, est envoye a
l'intention exclusive de son ou de ses destinataires
(cisco-voip at puck.nether.net); il est de nature confidentielle et peut
constituer une information privilegiee. Nous avertissons toute personne
autre que le destinataire prevu que tout examen, reacheminement, impression,
copie, distribution ou autre utilisation de ce message et de tout fichier
qui y est joint est strictement interdit. Si vous n'etes pas le destinataire
prevu, veuillez en aviser immediatement l'expediteur (Cisco
<mailto:subs-cisco at cbvcollections.com> ) par retour de courriel et supprimer
ce message et tout document joint de votre systeme. Merci

  _____  

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20051217/2afb5041/attachment-0001.html