DNIS and Night Ring

[randall5]

We have a customer with a Legend R6 with a T1. Currently, the T1 is programmed with 7 loop-start emulated lines which correspond to 7 keys on the MLX-20 reception phone (simulating analog trunks). The reception desk is not manned full time and is often covered with Night Service to a group of phones to provide for call answering, with the Auto Attendant as backup. The problem is that this limits the efficient use of the T1 trunks. Is there a way to:
1. Use DNIS digits for incoming calls with the trunks setup as TIE 2-way
2. Cover the calls with Night Service to a group
3. Still use AA as a backup

Any insight is appreciated.

P.S. The T1 is currently a partial T running through an Adtran TSU120 to split the data. If they go to a full T1, can it terminate directly into the card and avoid using the Adtran?

Randy S

 

[Pepperz]

Yep, set the DNIS to the same extension as the operator. Set the class of service of the Operator mailbox to be an autoattendant. Set the Voice Mail system to run Day/Night on it's own schedule, and use a do not disturb key, rather than a Night Service Key as the Night Service button. You should keep the Adtran between the T-1 and the Legend. TipHelp@charter.net

 

[Ghostin]

Why do you say it limits efficient use of the T-1. You don't get any advantage with 7 TIE trunks vs with 7 analog trunks. In fact, using TIE trunks in your scenario is more of a limitation than use analog. Is you T-1 split half for voice and half for data? if so, make sure you have the additional 5 trunks programmed in your switch so you can have 12.

 

[randall5]

Perhaps I was somewhat incomplete in my description. Currently, the T1 is 20 channels for voice and 4 for data. The customer is purchasing a second T1 to dedicate for data and make the first one exclusive for voice. The full setup is as follows: 7 channels-loop start hunt group; 3 channels-separate loop start hunt group; 10 channels TIE 2-way for outbound/inbound DID (which is minimal). The site is a seasonal hospitality operation. The fisrst hunt group is for their inbound calls to the main line. The second group is for a separate department which does not need to go through the operator/main line. I think the idea is to have all 24 channels available at all times to all users for maximum flexibility. So, the thought is to bring calls in with DNIS, have them ring on SA buttons (?) and have all channels in the outgoing Pool, enabling full 2-way usage on all channels. I hope that clears it up.

Pepperz-why keep the Adtran? Can't the DS1 card handle the T straight up?

Randy

 

[Ghostin]

The Adtran give you a good test point, so unless you need to unload it, keep it. When you go to a straight voice t-1, keep your current setup and just add the additional 4 trunks as the two-way tie. Using DNIS or DID number as main numbers just doesn't work as well on a Legend, especially if you have to have multiple lines apperances on multiple phones. Having 14 two ways plus those main hunt groups should handle it just fine.

 

[Pepperz]

Randy, the Adtran CSU or any for that matter is recommended as a sort of isolation point between the T-1 circuit, and the Legend. Avaya "requires" it for support, and the T-1 provider can use it to test the circuit. It helps a lot in troubleshooting. Telco can "loop up" to the network interface unit, the adtran, and based on their results can isolate a problem later on. It's OK to test without the Adtran, but ought to keep it while in use. You are right in your assessment of efficient channel use. Providing DNIS directly to various phones, calling groups, etc., and then having those same channels used for outbound is fine. This way you don't have to worry about allocating enough channels for this group, and that, and so on. TipHelp@charter.net