[grendon]

We have 8 Sipura 2000s (16 lines) connected to our Nortel Meridian One PBX via 2 Universal Truck Cards.

If we dial a programmed access code (in our case 71) the PBX puts us straight out on the Sipura 2000. We then proceed to dial out as normal. Evrything works fine.

But if we try to program the PBX to use these lines first if someone dials 9 instead of our AT&T T-1s, the PBX is having difficulties sending the number dialed info to the Sipura. It's almost as if the Sipura receives no info from the Meridian System, yet we know the PBX is sending the data.

I am sure it's something in the setting of the Sipura or maybe even the Nortel system.

ANYONE HAVE ANY IDEAS? :?:

Thanks
Gus Rendon
American Traveler

[mberlant]

Gus,

Your problem is almost certainly in your Meridian. You're going to have to do a little testing in order to pinpoint what's going on. Grab up a butt set and come with me to the switch room.

First, a question. Have you put these 8 trunks (trunk access code 71) into a trunk group or are they separate trunks? If they are not yet in a group, create a trunk group and contribute only one trunk to the group. Assign the group access code 71 and test it. Then, add the trunk group to the head of the LCR table for access code 9.

Next, connect the butt set to the one trunk that is "alive" in 71 and make sure that you can manually call out through the SPA. Then, while monitoring on the butt set, try making a call using 71 and then 9. See what the two calls sound like in the monitor.

Let us know what you find during this testing. We'll be able to figure out next steps after that.

Michael

[grendon]

When we use the access code 71 it works great because we don't go thru the Meridian system. it just release the line to the Sipura and then you are dialing out straight from the Sipura. But when we go thru the Meridian programming (dial 9 only) the Meridian is sending the tones about 1 second after the Sipura has gone from dial toine to fast busy. If someone can tell me what setting will extend the time the Sipura waits for digits before going busy, we think this will solve the problem.

Michael,
Thanks for your advise on troubleshooting the problem, this is how we have come to this point. Any futher help will be greatly appreciated.

[grendon]

***UPDATE****

After many changes to the Meridian programming we were unable to speed up the transfer of digits between it and the Sipura.
We managed to solve the problem going into the Sipura 2000 under the "REGIONAL TAB" - "InterDigit Short Times" from default "3" to "5" and that did the trick. We had changed it to "10" but that caused a long lag time after the last digit was dialed and the connection.....

Gus Rendon

[mberlant]

Try lengthening the Interdigit Long Time, instead. That timer is meant to control the amount of Dial Tone before the first digit. The Short Timer is meant to figure out when you have finished dialing a number of indeterminant length, like international.