Mailing List Archive

Urgent bypasses normal Digit Analysis and forces the call out the gateway the moment all digits are matched.

This means that for 9.911, the moment it sees the last 1, its sent to the gateway, rather than going through the dial plan.

________________________________

From: cisco-voip-bounces@puck.nether.net on behalf of Peter Mauro
Sent: Sat 4/3/2004 10:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Re: cisco-voip Digest, Vol 14, Issue 3


How does "marking these routes as Urgent routes" effect the handling of the call within CallMgr?

I was hoping to find a Cisco-eze description, but can you believe I didn't find one explanation on their website? Almost every match said something like 'check this box if appropriate'. Well, geeez, duh! I didn't even find a good explanation in the forums. Oh well, maybe I just wasn't search hard enough.

Essentially, and urgent route patterns are mainly used for overlapping dial plans so that they do not wait the interdigit timeout delay before they place a call. It's an exact match immediate route. Granted, you should never have another route pattern that matches 911 or 9.911, but it's set to urgent anyways, just in case.

For example, say you have 5 and 4 digit extensions, and 4 digit extensions starting with 41 are routed to another system across tie lines of some sort. If you did not have an urgent priority set, and you had a 5 digit extension starting with 41, which matches the first four digits, the system would wait the ten seconds before your call was routed. With the urgent priority, it would immediately route the call after the fourth digit, even if there was a five digit extension which matched the first four digits.



--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)

"This signature may contain traces of nuts"
--------------------------------------------------------------------------------


----- Original Message -----
From: Peter Mauro
To: cisco-voip@puck.nether.net
Sent: Saturday, April 03, 2004 12:54 PM
Subject: [cisco-voip] Re: cisco-voip Digest, Vol 14, Issue 3


How does "marking these routes as Urgent routes" effect the handling of the call within CallMgr?

--

*************************************************

Peter J. Mauro Peterj@ufl.edu

Network Engineer, CCNP-VA Phone: (352) 392-2061

OIT-Network Services IPhone:(352) 273-1052

University of Florida Gainesville, Fl 32611

*************************************************



Message: 2
Date: Fri, 2 Apr 2004 16:15:21 -0500
From: "Lelio Fulgenzi" <lelio@uoguelph.ca>
Subject: Re: [cisco-voip] 911
To: <cisco-voip@puck.nether.net>
Message-ID: <009201c418f7$9f442ad0$25196883@delliscious>
Content-Type: text/plain; charset="iso-8859-1"

Cisco recommends using a more specific pattern for 9.911 and 911 calls and marking these routes as Urgent routes. This will prevent any overlapping dial plan from interfering with emergency calls. By using more specific patterns you can treat them differently, i.e. different external calling masks, different route lists (perhaps some copper after PRIs), etc. From what I understandy, CER (Cisco Emergency Responder) will want to use these seperate route patterns as well.






------------------------------------------------------------------------------


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