Can't dial *82 or any other Pac Bell codes

[Peach66]

We have a t1 and POTS lines connected to our PBX, but we can't seem to dial *82 to remove a caller ID blocking. Does anyone have any idea how to configure this type of dialing?

 

[gregarican]

If I'm not mistaken I would think you would need the POTS lines to be business lines that subscribe to these Pac Bell calling features. Otherwise dialing those Pac Bell feature codes won't do anything.

Once the services subscription is confirmed you should hit the 9 button to get out to the PSTN trunks so that the *82 isn't be interpreted by the Merlin PBX first. Otherwise you would just hear the reorder tone since Merlin wouldn't accept the *82.

Let me know how it goes.

 

[Peach66]

the PBX was already setup when I got here. Apparantly they configured port 890 for all outbound calling, except for 411 that routes to the POTS lines. Is there a way to force the route of *82 to go to the POTS lines that are configured to port 70?

 

[Peach66]

To clarify my previous posting. We have a T1 configured on pool 890 for all in/out calling. We recently added two POTS lines on pool 70 (main pool). They didn't use the main pool for the T1. I believe this causing some problems. I need to figure out how I can force certain calls to the POTS lines, especially calls that start with a "*" Any idea?

 

[gregarican]

In addition to the N11 Output Table that by default looks to Pool 70 you could try checking the Dial 0 Output Table. By looking at the Absorb (i.e. - digits truncated) and Other Digits (i.e. - digits added) values you should be able to directly hit Pool 70 for your subscriber calling features.

The Dial 0 Output Table is by default Table 27 I believe. Hope this helps!

 

[TelNetSystems]

I recently had this problem in a Merlin Legend I installed. Two things were causing the problem:

1. I had to remove * from the disallow list, thought I am not sure how it got there.

2. PacBell was "dropping" the first digit dialed after the feature code. For example *82 555-1212 was being received as *82 551-121 by PacBell. Dialing *82 X555-1212 where X was a random digit was odd but it resulted in the call being completed properly. There is a setting for "second dial tone delay" or something similar which I had to increase to correct this problem. If this is the source of your problem, email me and I will find the instructions on how to increase this setting for you.

 

[Pepperz]

Just ran accross the identical problem, and EVEN THOUGH you are on an outside line, *82 is denied because of the disallowed table. Remove the entry, & life goes on.

Pepperz@charter.net

 

[SYQUEST]

The * is defaulted in the disallow list. Lucent/Avaya have a whole bunch of things setup as default for security reasons to prevent toll fraud under a variety of conditions. This is discussed in the manuals in various places.

The T1 ckt you have on your system, is it setup as 24 2-way trunks(SUPERTRUNK) or is it PRI ISDN? In the case of SUPERTRUNK on a 5ESS switch there is no caller ID info sent on outgoing calls. It shows as 'unavailable'. That is my experience in the Pacific Bell areas on 5ESS switches. I do not know what the DMS100 switch shows for caller ID info with SUPERTRUNK. With the SUPERTRUNK offering the trunks are from the "trunk side" of the switch and so certain features are not available because of this.

So in this case the *82 to unblock caller ID doesn't do anything useful for any calls placed thru your T1 if it is a SUPERTRUNK because there is no ID to unblock!. In fact the calls may not even complete.

....JIM....

 

[kristiandg]

I've had issues with Definitys that dial *82 and *67 and the 1'st digit of the number is being dropped. Its because that stutter dialtone interferes with the CO's ability to receive more digits. I had to put a pause in to get rid of the dropped digit problem.

Hope this helps...

Kris

 

[jlshelton]

I never figured out how to put a "*" into an autodial entry, so I used the old-fashioned work-around: "11" instead of "*". Most of the PacBell * dial codes have a comparable "rotary" version beginning with "11." Hope this helps.

=John=

 

[SYQUEST]

On the 5ESS and DMS100 switches "stutter dialtone" has NO effect on call processing for digit reception with the DTMF receivers. But a bad cable pair can affect "twist" and cause a digit not to be recognized or distorted.

....Just a point of information.....

....JIM....