[cisco-voip] enabling "ring down to 9" in existing dial-plan

[Lelio Fulgenzi]

Correct. And that's the part I want to avoid. Having to duplicate any of the dialplan work I've done just to allow for off-campus only without the access code. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Nate VanMaren" <VanMarenNP at ldschurch.org> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "cisco-voip voyp list" <cisco-voip at puck.nether.net> 
Sent: Friday, January 29, 2010 12:35:21 PM GMT -05:00 US/Canada Eastern 
Subject: RE: [cisco-voip] enabling "ring down to 9" in existing dial-plan 




Don’t think about it as a ring down, think about making route patterns without the 9. This basically disables internal dialing. So your new CSSs can’t see the partition that the extensions are in. 



If you don’t need LD, you’d have a route pattern that is [2-9]XX[2-9]XXXXXX for 10 digit dialing. That would be about the only think in the partition and the only partition in the CSS. I guess you’d probably need one for X11 too. 



Problem with translation pattern, is it doesn’t look for more digits. Unless maybe you have overlap sending enabled? 





From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi 
Sent: Friday, January 29, 2010 8:02 AM 
To: cisco-voip voyp list 
Subject: [cisco-voip] enabling "ring down to 9" in existing dial-plan 




We have a need to deploy some phones with an immediate ringdown to 9, so they don't have to dial 9 to get an outside line, i.e. for fax machines, pay terminals, etc. that are brought from an outside vendor temporarily on campus. For those that are permanently on campus, we will require them to program the appropriate off-net access code, i.e. 9. 

We are currently using the device/line approach, which means we give the device access to everything and use the line to prevent LD, etc. What I don't want to do is have to do a complete redesign or start building new filters, etc. 

What I had thought of doing was using a combination of partitions and search spaces and route patterns to mimic each pair of device/line classes of service I have, and then use translations to put in the 9. 

So, say I have: device-business-CSS (for the phone) & line-local-CSS (for the line). 
These each have device-business-PT (permit patterns) & line-local-PT (deny patterns). 

    • create ringdown-outbound-CSS and add device-business-PT and line-local-PT to it 
    • create ringdown-inbound-CSS and add ringdown-inbound-PT to it 
    • create RP: @ in ringdown-inbound-PT w/ ringdown-outbound-CSS w/ 9 prefix 
    • assign ringdown-inbound-CSS to the analog device CSS and leave line CSS blank 


This should give me what I want, with minimal work. 



--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 




NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100129/81b3ac83/attachment.html>