[cisco-voip] Saving route patterns

[Lelio Fulgenzi]

You wouldn't need double the number of route patterns. You would only need an extra *67 route pattern for each CSS you have. 


For example, you have two phones (or lines, whatever). The first has a CSS of local_access. In that CSS you have a partition 67_local in which is contained the simple *67.@ route pattern with a CSS of local_access. 

The next phone, with a CSS of ld_access. ld_access has a partition 67_ld in which is contained the *67.@ route pattern with a CSS of ld_access. 

When the user dials a *67 plus the number, they can only dial what their original CSS would have let them. 

It all depends on the number of CSS's you have, not the route patterns. 

I do something similar to this for a few functions, and it quite manageable. 

----- Original Message ----- 
From: "FrogOnDSCP46EF" <ciscoboy2006 at gmail.com> 
To: lelio at uoguelph.ca 
Cc: "Jason Aarons (US)" <jason.aarons at us.didata.com>, "cisco-voip voyp list" <cisco-voip at puck.nether.net> 
Sent: Monday, February 2, 2009 11:00:49 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Saving route patterns 

Hehe..... 
Thats what I don't want to do ... just think if your customer has already 400 route patterns and would u like to double that up to 800? 
Thanks for the thought though..... 

The other way could be : 
1. create a regular- routepattern - *67!, treat here the caller ID, set any= GHOST 
2. send all these calls (COR will be preserved, since its going out of CCM) to a H323 router, then route them back to CCM. 

long way but that will work for sure.... bit messy... and it needs additional hardware..the router 

I will keep thinking... 


On Tue, Feb 3, 2009 at 12:32 PM, < lelio at uoguelph.ca > wrote: 




Create a *67 partition for each CoS, then create a*67 route pattern in each of those partitions with the appropriate CoS applied. It's not scalable, but should do what you need. 

Lelio Fulgenzi, Senior Analyst 
Computing & Communications 
University of Guelph 
519-824-4120 x56354 


...sent from my iPod - please pardon my fat fingers ;) 


[XKJ2000] 




On Feb 2, 2009, at 7:59 PM, FrogOnDSCP46EF < ciscoboy2006 at gmail.com > wrote: 





Thanks Jason, TCL script only works on router. Here we've CCM6x. 
Can't find anything in the archieve. 

Found solution myself but, it has impact on CoS requirement. It voiding COS. 


- Create a xlation pattern - *67.! 
-calling party transformation - block caller id, blcok caller name 
- Called party transformation - Digit-discard = "PREDOT", prefix 9 (this will strip *.67 , remove callerID and send any pattern with prefix "9") to call manager. 

Now this will match the regular pattern 9[2-9]xxxxxxxxx 

The only draw back is it touches all CoS requirement. 

Any thought? 





On Tue, Feb 3, 2009 at 11:37 AM, Jason Aarons (US) <jason.aarons at u Gmail - Saving route patterns - ciscoboy2006 at gmail.com s.didata.com > wrote: 






Needs to be a way to send *67 to telco for calls you want blocked or a TCL script, etc. I've seen this request before for *67 but don't recall if it's something that can be done and why –jason 





http://www.wikihow.com/Block-Caller-ID 






From: cisco-voip-bounces at puck.nether.net [mailto: cisco-voip-bounces at puck.nether.net ] On Behalf Of FrogOnDSCP46EF 
Sent: Monday, February 02, 2009 7:33 PM 
To: cisco-voip at puck.nether.net 
Subject: [cisco-voip] Saving route patterns 






Hi, 


1. 400 route patterns in call manager 
2. User demands , I want to block caller ID on each patterns. 


Q1: What is the best way to do this apart from creating 2 patterns for each routes, hence 800 patterns - 400 simple and 400 with blocking caller ID. 

Alternate to above for same scenario: 

Q2: PSTN switch environment; 

If those 400 route patterns are dialed with 1777 prefixes (e.g. user dials 1777+[2-9]xxxxxxx). PSTN switch gets 1777[2-9]xxxxxxx and PSTN switch blocks calls 
Here again, the challenge is to achieve this with a single route-pattern. 

I looked through the option, like - Application dial-rule, Directory lookup rules but can't see any optino there. 

the logic i am after: 

Route-pattern1: 9.[2-9]xxxxxxxx <simple dial> 
route-pattern2: 9.1777[2-9]xxxxxxx , pstn switch sees 1777[2-9]xxxxxxx and blocks caller id 

Can this be done with just creating a route pattern (one) and then adding some sort of application rule or any other ccm features? 

I can't think of anything... 

-- 
Smile, you'll save someone else's day! 
Frog 





Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. 


-- 
Smile, you'll save someone else's day! 
Frog 



_______________________________________________ 
cisco-voip mailing list 

cisco-voip at puck.nether.net 

https://puck.nether.net/mailman/listinfo/cisco-voip 



-- 
Smile, you'll save someone else's day! 
Frog 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090202/b430aa6e/attachment.html>