shoretel to avayacustomers.btxchange.com/manuals/shoretel/kb16148_t1_qsig...shoretel to avaya...

ShoreTel to Avaya ShoreTel to Avaya

Version 3: 04-22-2011

T-1 QSIG Voice Mail Integration

Wayne [email protected]

408-962-2722

Systems Engineer - North Star Region

Overview

TOPIC: T-1 QSIG integration between a ShoreTel PBX and an Avaya system

Customer: Anderson WIndowsPartner: SDN, MinnesotaShoreTel SE: Wayne Cochrane

Functionality:• Calls between the two systems

© 2011 ShoreTel, Inc. All rights reserved worldwide. 1

• Leave messages for the Avaya phones using the ShoreTel Voice Mail system• Message waiting lights (MWI) on the Avaya phones

Time Estimate:• About 10 minutes on the ShoreTel PBX• About 4 hours on the Avaya PBX

Requirements:• Basic Supplementary Services• Supplementary Service with Rerouting

Wayne CochraneSystems EngineerNorth Central [email protected]+1 (408) 962-2722

ShoreTel to Avaya QSIG/T1 integration

T-1 Crossover

ShoreTel HQ Server

G450220T1K

16.22.9109AvayaS8500CM5.1


SG-90

System 1ShoreTel as Voice Mail

System 2Avaya as PBX

EXT XXXX EXT 85000

ShoreTel Configuration


Create a User Group for your Avaya-based VM only users. While not specifically necessary, it will allow you to set COS parameters specific to these users down the road if necessary. The key parameter is to set Voice Mail Interface Mode to None.



Create a Mailbox Only user. The ‘Number’ will match an Off-System Extension (OSE) which will be created later. Set the User Group to the group created in the previous step. If you have multiple DVS servers or V-Switches make sure you choose the appropriate Mailbox Server.



Identify your ShoreTel system’s voice mail extension under “System Parameters | System Extensions.” Ours is x1101. On the Avaya system you will need to specify the ShoreTel Voice Mail extension as the destination of a “cover path.”



Create a Digit Translation Table (if necessary) to route the incoming Avaya-created Voice Mail call to the correct ShoreTel Voice Mail number. We named our Translation Table “Inbound”. In this case when a call is received from the Avaya for the ShoreTel voice mail the Avaya will dial 11101. We translate those digits to 1101.



In our case we have a 4 digit dial plan on the ShoreTel system and a 5-digit dial plan on the Avaya. To enable inter-system dialing from the 4-digit ShoreTel system to the 5-digit Avaya users we can create a Digit Translation Table to route outbound ShoreTel calls to the correct Avaya extension. Our outbound Translation Table is called “Test.” In our system we wanted the ShoreTel users to dial 5xxx to reach any Avaya user with the extension of 85xxx.This Translation Table will translate any 5xxx dialed number to 85xxx. This also required an OSE to be set (see next slide)



Create a new trunk group. Make sure you have the number of digits from CO set correctly. This should be set to match what the Avaya is configured to send.Also check the box next to “Extension” and select the translation table (“Inbound”) created earlier.



Create an Off System Extension for those extensions that will be routed across this trunk group towards the Avaya PBX. In our case the Avaya user exists on the Avaya PBX as user x85000 but exists on the ShoreTel system as user x5000. For any ShoreTel users to dial the Avaya users they will dial the 4-digit number and the OSE table will route that call over the TIE line which will be expanded to 5-digits by the Translation Table “Test”.We only tested one user so our range was 5000-5000. You can create a larger range such as 5000-5999 for a larger set of Avaya users.



Create the channels for the trunk group on the appropriate switch that is your T-1 interface. Set the Layer 3 and Layer 1 protocols are set to match the far end (one side Slave, one side Master). The Layer 3 Protocol Type should be ISO QSIG.



Check to make sure your channels populated appropriately in the Individual Trunks screen.

Avaya Required Features

Refer to separate output .TXT file of the “display system-parameters customer-options” of our test system. It was a lab system with most all Avaya features turned on.

The key features that need to be turned on in the Avaya system relate to QSIG:

QSIG Optional Features:Basic Call Setup – YBasic Supplementary Services – YSupplementary Service with Rerouting – Y


Supplementary Service with Rerouting – Y

Any system that is at CM 2.0 or higher should have all the ISDN features needed as well as the QSIG Basic Call Setup turned on. Before 2.0 they were features that were paid for individually . After that they were included. However, Basic Supplementary Services and Supplementary Service with Rerouting was generally never turned on. Typically the only way you got those features in the past was to have a 3rd party voice mail QSIG attached or you were using Avaya Modular Messaging.

If those 2 additional features are not turned on and the Avaya system is old enough they likely will not be able to purchase those features anymore. Such customers would need do standard SMDI integration with ShoreTel using a VTG unit. See other AppNotes for those instructions.


First we will define the circuit pack that will be out T-1 interface on the Avaya system. On the next few pages the output of the “display DS1” command on the system. It is important to match Line Coding and Framing Mode with the ShoreTel side. Signaling Mode, Interface, Peer Protocol and Side also need to be set appropriately.


Next, we will set up the Trunk Group associated with our connection. This and the subsequent screen shots show the completed Trunk Group 1. Note that you will have to start the Trunk Group configuration, then configure the Signaling Group, then come back to the Trunk Group forms.


Next, we will set up the Signaling Group associated with our Trunk Group. This screen shot shows the completed Signaling Group 1. The TSC Supplementary Service Protocol parameter must be set to “b” to indicate QSIG.


Next, we will set up a Route Pattern that utilizes Trunk Group 1.


The pilot number on the ShoreTel side for voice mail is 1101. Because the Avaya system in this case has a 5 digit dial plan, we will append a 1 and strip it out on the ShoreTel side. Thus we need to route to 11101 to cover to voice mail. To do this we create an entry in the ARS table that routes 11101 to Route Pattern 11 of type “pubu” (public unknown).


The public unknown numbering table can do many things. In this case we are using the table to output the correct extension number in the QSIG message to the ShoreTel system when a call covers to voice mail. Any time the system sees and extension that is 5 digits starting with 85 across trunk group 1 it will only send the last 4 digits, or in our case instead of 85000 it only sends 5000 in the QSIG message.


Next, we set up a Hunt Group, 11, to route to as a coverage point for voice mail.


Next, we set up a Coverage Path, 11, to route to our Hunt Group.


Finally, we modify our user extension, 85000, to use Coverage Path 11 for the “forward no answer” condition.

Avaya Call Flows

Call flow internal to Avaya (Avaya Ext. – to – Avaya Ext. – Redirected to ShoreTel Voice Mail box):Avaya extension dials 85000On no answer it covers to Coverage Point 11Coverage Point 11 points to Hunt Group 11Hunt Group 11 utilizes ARS and dials 11101ARS 11101 routes to Route Pattern 11 utilizing the public unknown numbering tableRoute Pattern 11 routes to Trunk Group 1, which is the T-1 to the ShoreTel systemThe leading digit on the Inbound call is stripped on the ShoreTel side in the inbound translation table and 1101 is what we see and the QSIG message from the Avaya side tells it is destined for extension 5000Message is left, QSIG message from ShoreTel to Avaya says to light MWI for extension 85000


Message is left, QSIG message from ShoreTel to Avaya says to light MWI for extension 85000

Call flow external to Avaya (ShoreTel Ext. – to – Avaya Ext. – Redirected to ShoreTel Voice Mail box):ShoreTel extension dials 50005000 is an OSE using the T-1 to Avaya to routeThe 5 is converted in the outbound translation table to 85 so 85000 is passed to the Avaya systemOn no answer it covers to Coverage Point 11Coverage Point 11 points to Hunt Group 11Hunt Group 11 utilizes ARS and dials 11101ARS 11101 routes to Route Pattern 11 utilizing the public unknown numbering tableRoute Pattern 11 routes to Trunk Group 1, which is the T-1 to the ShoreTel systemThe leading digit on the Inbound call is stripped on the ShoreTel side in the inbound translation table and 1101 is what we see and the QSIG message from the Avaya side tells it is destined for extension 5000Message is left, QSIG message from ShoreTel to Avaya says to light MWI for extension 85000

Success & Conclusion

There are potentially other ways that this could have been configured/set-up and accomplished on the Avaya side.


Avaya has very good troubleshooting tools via the “list trace” commands that can track a call and show exactly what is being sent, what tables are being referenced, and what QSIG messages are being exchanged.

Avaya MWI is lit after Voice Mail is left on ShoreTel system

shoretel to avayacustomers.btxchange.com/manuals/shoretel/kb16148_t1_qsig...shoretel to avaya...

Documents