[cisco-voip] Blocking number when calling?

[Sullivan, Gary, GREENWICH, Information Services]

The issue we had with not sending the CLID  on a PRI. If Telco didn't
see the out going CLID they would send the BTN. 
When one of are sale's people would call the competition to get there
pricing they didn't want any CLID to show up on the other end.

  _____  

From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Monday, July 07, 2008 11:27 AM
To: Sullivan,Gary,GREENWICH,Information Services
Cc: Madziarczyk, Jonathan; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Blocking number when calling?


Specifically you either have a route pattern like Gary mentions (though
I would make it *679.@) or a translation pattern set to drop the *67 and
let your existing route patterns route the call.  In both cases you
simply set the calling party number to Restricted to block calling
number. 


-Ryan


On Jul 7, 2008, at 11:02 AM, Sullivan, Gary, GREENWICH, Information
Services wrote:

We've been using this in our route patterns. 9.*67@ and has been working

  _____  

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Madziarczyk,
Jonathan
Sent: Monday, July 07, 2008 10:56 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Blocking number when calling?



I've got a weird request from a user.  Apparently on their old NEC
system they were able to block their number from being sent when they
made specific calls (through a series of key sequences).  Is such a
thing possible either with the Call Manager or through the regular POTS
lines (like *69 for redial of last call)?

Thanks

_______________________________________________
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/20080707/228137fb/attachment.html>