Block Outgoing Caller ID

[wcntech]

Hi all!

I am new to this forum and relatively new to VoIP. We are using CUCM v. 6.1 and have a few users (law enforcement) who need to be able to block their outgoing caller ID. TAC has worked on this issue for about 3-4 weeks now to no avail as well as the vendor who installed the system. We have created a new route pattern and route list for callers to dial a different number (8 instead of 9) for these calls. We have succesfully got the system to not send the calling number, but the phone company (Verizon) goes ahead and lists the billing number of the PRI and these calls. Verizon is stating that the q.931 needs to have the presentation restricted to not allow presentation of caller ID. Here is the example they sent.

INFORMATION_ELEMENT:
QIE_INFO_ELEMENT: QIE_CALLING_PARTY_NUMBER
SINGLE_OCTET: FALSE
QIE_LENGTH: 5
CALLING_NUMB_PLAN:
CALLING_NPID: NATIONAL_NUMBER_ISDN_NUMBERING_PLAN
CALLING_NPID_EXT: FALSE
CALLING_ONPS:
NUMB_AVAIL: PRESENTATION_ALLOWED <====== they need to chg to an option in the CPE that doesn't allow presentation of the # such as PRESENTATION_RESTRICTED"

One Cisco rep suggested sending *67 in front of the call but I don't think that POTS codes work on a PRI. Also, the Cisco engineer with TAC said this might not be possible with MGCP and that all of his documentation has fixes for H.323 and he hasn't been able to find any info on MGCP.

If anyone of you have ran into this before and know how get the equipment to send the phone company the PRESENTATION_RESTRICTED message, please let me know. I've been trying for over 2 months now to get this fixed.

Thanks!

 

[trvlr1]

Have you tried simply putting in a generic number (main desk) in the External Phone Number Mask on the Directory Number Configuration Page of the phone?

 

[wcntech]

Since it is law enforcement, they need the caller id to say unknown and be totally blocked/restricted. Also, Verizon doesn't allow the external number mask to say something that isn't on that PRI. If you set it to something else or bogus, it still displays the billing number of the PRI regardless.

Thanks for your reply!

 

[Iwontremember]

http://www.tek-tips.com/viewthread.cfm?qid=1556803&page=1

Hope this helps.

 

[wcntech]

Iwontremember,

Thanks for that info, but I have already tried that. I can get it to not send the caller id, but Verizon goes ahead and tags the call with the btn of the pri. Frustrating. Here is a couple sample q.931 logs of how a call looks when it goes out with caller id, and one without caller id (set to restricted in the route pattern/list.) (I changed the NXX to 555 for privacy.)

with caller id:
.Jul 9 15:45:40.831: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x19D8
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98395
Exclusive, Channel 21
Calling Party Number i = 0x2181, '3255554439'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '5553579'
Plan:Unknown, Type:Unknown
.Jul 9 15:45:40.907: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x99D8
Channel ID i = 0xA98395
Exclusive, Channel 21

and without caller id:
VG-CommCenter#
.May 6 00:12:29.136: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0003
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Called Party Number i = 0x80, '5553579'
Plan:Unknown, Type:Unknown
.May 6 00:12:29.212: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8003
Channel ID i = 0xA98397
Exclusive, Channel 23


You will notice that the Calling Party Number is totally missing from the log where caller id is restricted. My question is there a way to include in the q.931 message for what Verizon techs say it needs? (NumbAvail: PRESENTATION_RESTRICTED)

 

[whykap]

In your gateway configuration in call manager, if you select that PRI, there is an option:
Calling party presentation.

If you change that to restricted what happens? That should be the setting you need as far as I know.
If that does not work then you need to get a definite answer from TAC and if h323 is what you need then you need to change it to h323.
If the TAC engineer is not sure then escalate it to someone who does.

Let us know if you have tried the calling party presentation setting.

Also Verizon is full of crap. They should be able to set their switch to send no caller ID at all (unknown) unless you send a caller ID out of the gateway.
If the tech you are working with, does not know how to do it escalate with someone who will.

I have dealt with Verizon on several occasions and they are the biggest pain to work with.

 

[Iwontremember]

if you do it on the gateway you will block all calls. do he need to block on a per call basis?

Hope this helps.

 

[wcntech]

Whykap,

Thanks for your response! And I totally agree with you that Verizon is the biggest pain of all the vendors I have ever dealt with.

I have set the Calling Party Presentation to Restricted and somehow Verizon still tags the call with the BTN of the PRI.

So, I may try my dangedest to get in touch with someone at Verizon to get their switch set right. I know that I can't be the only one to run into this problem.

Thanks for all of your help!

 

[wcntech]

Iwont,

I have even set all calls at the gateway level to see if that solved the problem just as a test. Darn Verizon still sends out the BTN of the PRI. I set it back to default as there most outgoing calls want their number to show up. It's just the calls when the cops are wanting to call their informants or set up a sting or something of that nature that they want to block caller id.

Thanks!

 

[whykap]

when you change the option to restricted, does the q931 debug change the field to show the presentation as restricted or does it still show allowed?

What type of gateway is it and what is the IOS version it's running?

 

[BustedVoIP]

I have temporarily resolved this issue for my department by using Calling Party Transformation to send a DID associated with my PRI group but that is not in use out as the CP-Number, then a route plan that takes that DID and slams it with a re-order tone if someone calls it back.

It is crude and the called party is still being presented with a number but at least people aren't calling back and reaching an attendant at the station like they where before.

I'll work on this issue further when I have time but I have to much on my plate as it :-/.

Let us know if you come up with anything new.

 

[wcntech]

The MGCP gateway is a Cisco 3825. The last thing I heard from Cisco:
"If you are using a MGCP gateway, there isn't much configuration we can try on the gateway itself. You can try to block it using route patterns or on the GW config itself, enter a 'Caller-ID DN'. From previous engineer's notes see that you have already tried this but Telco is adding your company's number as the caller id. If you want to send Telco a PI-Restrict, it is possible only if you use a H.323 Gateway. These option are not available on MGCP gateway."

So, I guess the only way is to switch from MGCP to H.323. Anyone done this? How involved is it? We have 5 PRI's, one CUCM 6.1.2.1134.1 publisher, two subscribers, and approximately 590 phones.

Thanks for all of your help!

 

[1A2K]

I second this that Verizon is full of Bull, we have done this with our Nortel CS1k and it works very well.
You just add a Calling Party Privicy activate code.
It works perfectly, BTN will not go out. It shows up as Private to the called party.
It works well with Verizon, have yet to try this on our Call Manager