Skip to end of metadata
Go to start of metadata

Not supported by SBC SWe Lite in this release.

 

Table of Contents

About this Page

  • This Interoperability Note describes how to configure a TDM port on a Avaya S8300/8400/8500/8700 PBX to integrate with the Sonus SBC Edge.  Also included is configuration information for integrating Exchange Unified Messaging to the Avaya PBX via the SBC Edge.

Related Articles

Prerequisites

Requires Sonus SBC Edge Version 3.0

Avaya S8x00 PBX, Version 3.1.x, T1, QSIG

Interoperation Notes

The following extension numbers are used within this document:

•  UMS Pilot Extension: 2562
•  Extensions enabled for Microsoft Exchange Server UM: 5100 - 5199

PBX Configuration

Use the following configurations to interconnect the Avaya to SBC Edge. 

  1. Change Uniform Dialplan 

    Destinations on the SBC must be identified in the Uniform Dial Plan.

    In this example extensions are individually identified but there is no reason a block of numbers could be used (matching 51 for 4 = 5100-5199).

    For all individual stations or groups:

    •  Length = 4 (number of digits in the number)
     Deleted = zero (No digits to be deleted)
     Inserted Digits = 110 (used to route calls in AAR)
     Net = AAR
     Conv = N
     Node Num = blank

    Figure : Change Uniform Dialplan

     

     

  2. Change AAR Digit Analysis

    All calls starting with 110 and 7 digits in length are forwarded to AAR for distribution

     Dialed String = 110 [digits inserted in uniform dial plan]
     Min = 7 [110xxxx]
     Max = 7 [110xxxx]
     Route Pattern = 110 [SBC 1k/2k Route Pattern]

    Figure : Change AAR Digit Analysis

     



  3. Change Route Pattern

    Calls directed to route pattern 110 from the AAR digit analysis are forwarded to trunk group 10 in this operation. The first three digits [110] are dropped from the number so the call hits the SBC Edge as a 4-digit extension.

     Grp No = 10 [trunk group 10]
     Del Dgts = 3 [deleted 110 from the number]

    Figure : Change Route Pattern

     


     

  4. Change Trunk Group

    Trunk group 10 is a standard 23 channel QSIG T1 trunk used in UM integrations.

    Figure : Trunk Group Tab 1

     

     

    Figure : Trunk Group Tab 2

     

     

    Figure : Trunk Group Tab 3

     

     

    Figure : Trunk Group Tab 4

     

     

    Figure : Trunk Group Tab 5

    Figure : Trunk Group Tab 6



     

  5. Change Coverage Path

    Coverage path is available for routing unanswered calls on PBX extensions to Unified Messaging over the SBC Edge. This configuration directs the unanswered call to hunt group 110.

    Figure : Change Coverage Path

     

     


     

  6. Change Hunt Group

    All calls forwarded to this hunt group are redirected to 7772562. The original called party and calling party are retained and sent in the data stream to voicemail so the call hits the correct mailbox.

    Figure : Hunt Group Tab 1

    Figure : Hunt Group Tab 2

     


     

  7. Change AAR Digit Analysis

    All calls for 7772562 are handled via dialed string 2562. The (forward calls) feature access code 777 is ignored and the 4 digits behind it are used to determine the path of the call.

    Figure : Change AAR Digit Analysis

     

     



  8. Change Route Pattern

    Calls directed to route pattern 110 from the AAR digit analysis are forwarded to trunk group 10 in this operation. The first three digits [777] are dropped from the number so the call hits the gateway as 2562.

     Grp No = 10 [trunk group 10]
     Del Dgts = 3 [deleted 777 from the number]

    Figure : Change Route Pattern

     

     

  9. Use the TDM document to configure SBC Edge.

    •  Configuring TDM ports on SBC Edge

  10. Use the EUM integration document to finished the voicemail integration.

      Configuring SBC 1000/2000 with Exchange 2013

     

 

  • No labels