[cisco-voip] Saving route patterns

[Jason Aarons (US)]

Begging with 7.0(1) you can remove the Translation Pattern Urgent
Priority so it pays attention to Calling Search Spaces, which is what I
think you mean when you say voiding CoS.  The only other option with
5x/6x is to test your trick with CTI Route Point, which I don't think
will work but would have to test -jason

 

From: FrogOnDSCP46EF [mailto:ciscoboy2006 at gmail.com] 
Sent: Monday, February 02, 2009 8:00 PM
To: Jason Aarons (US)
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Saving route patterns

 

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 uGmail
- Saving route patterns - ciscoboy2006 at gmail.coms.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




-----------------------------------------
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090202/09ddae09/attachment.html>