[cisco-voip] CallManager Route Pattern/Filter Problem...
Cisco
subs-cisco at cbvcollections.com
Wed Dec 21 02:59:15 EST 2005
I forgot to write and thank the two of you (and the list) for your help.
All gateways in each site are now routing calls using the 9.@ route
patterns/filters. The satellite problem was due to a lack of calling
party ID, not called. Setting plan types to unknown for all gateways
worked just fine.
P.S. Mark - I'll definitely look into your course offerings...
________________________________
From: Mark Snow [mailto:highspeedsnow at gmail.com]
Sent: Saturday, December 17, 2005 5:44 AM
To: Cisco; 'Lelio Fulgenzi'; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CallManager Route Pattern/Filter Problem...
That sattelilte most likely uses a different telco POP and the telly's
switch wants to see both - switch the Plan/Type back to ISDN/National or
CallManager/CallManager but for that GW only and you should be fine.
HTH
-Mark Snow
________________________________
From: Cisco [mailto:subs-cisco at cbvcollections.com]
Sent: Saturday, December 17, 2005 3:23 AM
To: Lelio Fulgenzi; Mark Snow; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CallManager Route Pattern/Filter Problem...
Argh - one more thing. We have a satellite office that uses the same CM
cluster which experienced the same problem - with called numbering plan
on CallManager all calls matching route pattern 9.@ that included 1
played the carrier message (you must dial 1 first...).
I tried adjusting the called/calling party numbering plans to unknown as
I did the local 6608 gateways. Once the gateway was adjusted all
dialled numbers called that are matched 9.@ that include the "1" were
routed to the gateway, but then dropped. The main different there is
that the gateway is a 2691.
Thoughts - ideas?
________________________________
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 10:58 PM
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/20051221/cde60718/attachment-0001.html
More information about the cisco-voip
mailing list