Block caller id on a pri (outbound) 2

[micford]

Verizon's telling me that you can't block caller id outbound on a pri line. Has anyone been able to do this?

 

[circuitorderingguy]

I'd like to know too. If any knows, please help us out!

 

[Naperguy1]

The reason you can't block OB caller ID on a PRI is for a couple of reasons that I can think of:

LD -
Most companies have your BTN determining if you can make a LD call. I have experienced (when sending individual DIDs) that a person making a LD call gets the message that they are not authorized to use such and such network. In that case, we had to change it to send the BTN only. I have had work the other way where the LD company needed everyone's DID on record to allow the LD call to go through. I think that was a ploy to get more money because they said it cost them about $2/number to the customer to have it in the database. And I have also had it where the provider overrode anything passed and jsut sent the main BTN. CLECs are an odd group!

911 -

Enough said. When dialing 911, the call goes to athe PSAP which maintains the ANI and ALI information associated with the number being sent. Third party software (RedSky) can do this on site if the customer wants to manage the ANI/ALI info themselves. Not cost-efficient for small to medium business customers. I have also experienced when sending individual DIDs, the CLEC overrides the number sent (b/c it is going to 911) and sends the BTN. And, conversely, the DID got sent through on another occasion and the PSAP did not have any information and said to have it corrected immediately which led to the database issues (Addl cost for maintaining individual DID database for such and such customer).

You can try putting in a FAKE number to send, but you may run into problems with the above issues. That would be the only way I can think of blocking OB caller ID.

Hope this information helps everyone!

Naperguy1

 

[jgideon]

The Legend cannot do selective caller ID blocking, any blocking has to be done by the carrier. The carrier should be able to configure the whole trunk group in the CO to block Calling Party Number. With ISDN calls, the BTN (or ANI) adn the CPN (Calling Party Number) are two separate information elements. Both are always sent to the far end with the call setup message, along with a 'privacy' indicator. If the call is marked 'private' then the far end is supposed to respect that and not display the number. Since both the BTN/ANI and the CPN are transmitted, and the privacy is done by a 'flag' there shouldn't be any problems with LD carriers. That having been said, there are some local carriers out there who don't know how to correctly program their own trunk groups. (For example, the 'usual' way to configure PRI is for the CO to transmit one billing number/ani for the group, but multiple CPN's, as provided by the PBX for each call. Some carriers send the CPN as the billing number also, rather than the single billing number for the group.)

 

[Pepperz]

If you want to get sneaky, and most of us do, at one time or another, you can try this: IF TELCO PERMITS IT, you can change the outbound number in the PRI Programming to show a ficticious number, or an 800 number. That may serve your purpose.

Pepperz@charter.net

 

[Furball8675309]

Cant you change the number sent to say 555-5555?

 

[jgideon]

That will be telco dependant--many 'screen' the CPN you transmit. Also, I think it's illegal in the US to provide false calling part number information.