Caller ID Block Problem

[sm21375]

We have 2 switches that are DCS'd together (Switch A and Switch B) Switch A has a full time operator and Switch B does not. ARS is setup for low cost routing, so that when an employee from Switch A needs to call a customer that is local to Switch B the call routes to Switch B and goes out a T-1 line that is marked PRIVATE by the phone company. The reason it is marked PRIVATE is that too many customers were calling back the caller ID number and hitting Switch B's operator (who isn't always there). The Problem now lies with 9 out of every 10 customers seem to have the caller Id Block setup on their lines, so we get a message that states "This line doesn't accept private calls, please hangup and dial *82" When we try this we get the Definity error tone. Is there any way around this? Thanks for any help

 

[4merAvaya]

Try putting the *82 as the inserted digits in the Route Pattern.

Kevin

 

[OhioTelecom]

I have not done this on a Definity, but ended up having to setup the T-1 so that a few channels would show caller ID, and put those lines in a different line group. So when the customer got this error, they would dial the code for the new line group and then go out just fine.

 

[NX01]

Have the LEC allow you to provide the Caller ID Number. Then go into switch B's pub-isdn numbering and set the switch A ext's to show switch A's main number. "cha isdn pub" is the command....Assuming you are on R12 or below and not CM2.X.

In the future everything will work...

 

[sm21375]

The problem with putting *82 in the route pattern, is that all calls will bypass the PRIVATE feature and I am stuck with too many calls coming back into the operator at Switch B.

 

[sm21375]

Unfortunately the T-1 in Switch B is not an isdn Pri.

 

[DAVIDPAYNE]

You may need to check and make sure that your or in compliance with the law. In many states it is illegal for a company to call an individual without sending some sort of caller ID.

But what you may want to look is to have your line mark with an 800 number, and then route that 800 number how ever makes the most sense. To one switch or the other based on time of day, etc.

 

[surplus]

You can assign a Feature Access Code for Caller ID blocking/unblocking, using any numbers or combination that you're dial plan will allow. Then on the trunk screen, you can enter the digits for the telco associated with that trunk, such as the *82 that you mentioned.

Then when you dial the "Per Call CPN Unblock" code, of let's say 123 is what you assign, on the trunk group that it goes out on, it would issue the *82 or whatever is populated in that field for that SPECIFIC trunk group. Meaning if you had different providers for different trunk groups, you could enter their different "*82 or *67 codes...

From the trunk page 2:

TRUNK FEATURES
ACA Assignment? n Measured: none
Maintenance Tests? y
Data Restriction? n

Abandoned Call Search? n
Suppress # Outpulsing? n

Charge Conversion: 1
Decimal Point: none
Currency Symbol:
Charge Type: units Receive Analog Incoming Call ID: Bellcore
Per Call CPN Blocking Code:
Per Call CPN Unblocking Code:

Outgoing ANI: Ds1 Echo Cancellation? n


FROM THE FEATURE ACCESS CODE PAGE:

Per Call CPN Blocking Code Access Code:
Per Call CPN Unblocking Code Access Code:
Print Messages Access Code:
Priority Calling Access Code: 115