Interactive Intelligence Messaging Interaction Center 2.4

Interactive Intelligence Messaging Interaction Center 2.4

PBX Configuration Note:

Siemens HiPath 4000 with AudioCodes Mediant 1000/2000 using T1 Q.SIG

Technical Reference

By AudioCodes

READ THIS BEFORE YOU PROCEED

This document is for informational purposes only and is provided “AS IS.” Interactive Intelligence, its partners and vendors cannot verify the accuracy of this information and take no responsibility for the content of this document. INTERACTIVE INTELLIGENCE, ITS PARTNERS AND VENDORS MAKE NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Customer Interaction Center®
Vonexus Enterprise Interaction Center®

Document Version 1.0

Last updated: 05-19-2008

Content

This document describes the configuration required to setup Avaya S8300 and AudioCodes Mediant 2000 using T1 CAS In-band DTMF Tones as the telephony signaling protocol. It also contains the results of the interoperability testing of Interactive Intelligence Messaging Interaction Center 2.4 (MIC) based on this setup.

iii

Copyright ©1994 – 2008 Interactive Intelligence Inc. All rights reserved. Interactive Intelligence®, Vonexus®, Interaction Center Platform®, Communité®, Vonexus Enterprise Interaction Center®, Interactive Intelligence Customer Interaction Center®, e-FAQ®, e-FAQ Knowledge Manager, Interaction Dialer®, Interaction Director®, Interaction Gateway, Interaction Marquee, Interaction Mobile Office, Interaction Optimizer, Interaction Recorder®, Interaction Screen Recorder, Interaction SIP Proxy, Interaction Supervisor, Interaction Tracker®, Mobilité®, SIP Interaction Media Server, Vocalité®, Interaction Administrator®, Interaction Attendant®, Interaction Client®, Interaction Designer®, Interaction Fax Viewer, Interaction FAQ, Interaction Melder, Interaction Scripter®, Interaction EasyScripter, Interaction Server, Interaction Voice-mail Player, iRecord, Wireless Interaction Client, Interactive Intelligence Live Conference, Vonexus Live Conference, icNotify, InteractiveLease, the Vonexus logo design® and the Interactive Intelligence “Spirograph” logo design® are all trademarks or registered trademarks of Interactive Intelligence Inc.

NOTICE

This product contains Information and/or data of Telcordia Technologies, Inc. (Telcordia) licensed to be included herein. Recipient acknowledges and agrees that (1) TELCORDIA AND ITS AFFILIATES MAKE NO REPRESENTATIONS, EXTEND NO WARRANTIES OF ANY KIND, EXPRESSED OR IMPLIED, AND ASSUME NO RESPONSIBILITY OR LIABILITY WHATSOEVER WITH RESPECT TO THE USE, SUFFICIENCY OR ACCURACY OF THE PRODUCT, (2) RECIPIENT SHALL MAKE NO CLAIM AGAINST TELCORDIA OR ANY OF ITS AFFILIATES WITH RESPECT TO THE PRODUCT, AND WAIVES ALL CLAIMS AGAINST TELCORDIA OR ANY OF ITS AFFILIATES WITH RESPECT TO THE PRODUCT, (3) IN NO EVENT SHALL TELCORDIA OR ANY OF ITS AFFILIATES BE LIABLE FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES RELATING TO THE PRODUCT, AND, (4) THIS AGREEMENT SHALL BE ENFORCEABLE BY TELCORDIA.

DISCLAIMER

Interactive Intelligence (Interactive) has no responsibility under warranty, indemnification or otherwise, for modification or customization of any Interactive software by Interactive, Customer or any third party even if such customization and/or modification is done using Interactive tools, training or methods documented by Interactive.

Interactive Intelligence Inc.
7601 Interactive Way
Indianapolis, Indiana 46278
Telephone/Fax (317) 872-3000
www.ININ.com

Interaction Center Platform Statement

This document describes Interaction Center (IC) features that may not be available in your IC product. Several products are based on the IC platform, and some features are disabled in some products.

These products are based on the IC platform:

· Customer Interaction Center (CIC)

· Vonexus Enterprise Interaction Center (Vonexus EIC, or EIC)

· Message Interaction Center (MIC)

While all of these products share a common feature set, this document is intended for use with all IC products, and some of the described features may not be available in your product.

Table of Contents

Who should read this document 1

Technical Support 1

Chapter 1: General Information 2

Components 2

PBX or IP-PBX 2

VoIP Gateway 2

Interactive Intelligence Messaging Interaction Center 2

Prerequisites 2

PBX Prerequisites 2

Cabling Requirements 2

Summary and Limitations 3

Chapter 2: Gateway Setup 4

Step 1: SIP Environment Setup 4

Step 2: Routing Setup 5

Step 3: Coder Setup 6

Step 4: Message Waiting Indication Setup 7

Step 5: Supplementary Services Setting 8

Step 6: Trunk Group Setup 9

Step 7: TDM Bus Setting 10

Step 8: Trunk Setting Setup 11

Step 9: Fax Setup 12

Step 10: General Setup 13

Step 11: General Setup (Cont.) 14

Step 12: Reset Mediant 2000 15

Configuration Files 15

Chapter 3: PBX Setup 16

Fail-Over Configuration 24

Tested Phones 25

Other Comments 25

Chapter 4: Messaging Interaction Center 2.4 Validation Test Matrix 26

Testing the Core Feature Set 26

Detailed Description of Limitations 27

Chapter 5: Troubleshooting 28

Appendix 30

Dial Pilot Number and Mailbox Login 30

Navigate Mailbox using Mobile Office 30

Navigate Mailbox using Telephony User Interface (TUI) 30

Dial User Extension and Leave Voicemail 30

From an Internal Extension 30

From an External Phone 30

Dial Auto Attendant (AA) 31

Call Transfer by Dial By Name 31

Called Party is Busy 31

Called Party does not Answer 31

Voicemail Button 31

Testing Fax Features 31

Message Waiting Indicator (MWI) 32

Appendix A: Change Log 33

Appendix B: Acronyms Used in This Document 34

iii

Who should read this document

This document is intended for Systems Integrators with significant telephony knowledge.

Technical Support

The information contained within this document has been provided by Interactive Intelligence, its partners or equipment manufacturers and is provided AS IS. This document contains information about how to modify the configuration of your PBX or VoIP gateway. Improper configuration may result in the loss of service of the PBX or gateway. Interactive Intelligence is unable to provide support or assistance with the configuration or troubleshooting of components described within. Interactive Intelligence recommends readers to engage the service of an Interactive Intelligence MIC Certified Engineer or the manufacturers of the equipment(s) described within to assist with the planning and deployment of Messaging Interaction Center.

Chapter 1: General Information

Components

PBX or IP-PBX

PBX Vendor / Siemens
Model / HiPath 4000
Software Version / Ver 3.0 SMR5 SMP4
Telephony Signaling / T1 Q.SIG
Additional Notes / None

VoIP Gateway

Gateway Vendor / AudioCodes
Model / Mediant 2000
Software Version / 5.0A.023.001
VoIP Protocol / SIP
Additional Notes / Tests were conducted with Mediant 2000. However, these tests are also applicable to Mediant 1000.

Interactive Intelligence Messaging Interaction Center

Version / 2.4 SU 25 + MIC SU 6

Prerequisites

PBX Prerequisites

· Verify that PSS1V2 QSIG protocol is available by typing this command: dis-prode:db,vartab.

· The PBX is installed with Trunk card module Q2216-X DIU2U-M T1.

Cabling Requirements

· This integration uses a standard RJ-48c cable to connect a digital trunk (T1/E1) between the Q2216-X DIU2U-M T1 card and Mediant 2000 trunk interface.

Summary and Limitations

A check in this box indicates the UM feature set is fully functional when using the PBX/gateway in question.

Chapter 2: Gateway Setup

Step 1: SIP Environment Setup

Step 2: Routing Setup

Note: The Proxy IP Address must be one that corresponds to the network environment in which the MIC server is installed (For example, 10.15.3.207 or the FQDN of the MIC host).

Step 3: Coder Setup

Step 4: Message Waiting Indication Setup

Step 5: Supplementary Services Setting

Note: Choose any 4-digit number that is not used in the PBX for Transfer Prefix (e.g., 9989).

Step 6: Trunk Group Setup

Step 7: TDM Bus Setting

Step 8: Trunk Setting Setup

Step 9: Fax Setup

Step 10: General Setup

Step 11: General Setup (Cont.)

The following configuration items must be set in the INI file, or via the AdminPage web interface (http://gateway/AdminPage). You will see these in the attached INI example.

VoiceMailInterface = 3 (for QSIG)

ISDNIBehavior = 1073741824

EnableMWI = 1

SubscriptionMode = 1

EnableDetectRemoteMACChange = 2

ECNLPMode = 1

TrunkTransferMode_X = 0

Note: "X" refers to the Trunk number, for example: for the first trunk
TrunkTransferMode_0 = 0

Step 12: Reset Mediant 2000

Click Reset to reset the gateway.

Configuration Files

Chapter 3: PBX Setup

Information used for this test case:

Our test configuration uses extensions 5000 to 5050 that are configured as off-premises extensions and are reachable through Trunk Group 3 configured for T1 QSIG. Calls to Siemens Optiset phone ext. 2417 are forwarded under busy/no answer conditions to ext. 5000.

Step 1: T1 QSIG Trunk Group Setup

disp-buend

TGRP = 3

FORMAT = l;

DISP-BUEND:3,L;

H500: AMO BUEND STARTED

+------FORMAT = L ------+

| TGRP NUMBER : 3 TGRP NAME : T1 QSIG MAXIMUM NO. : 23 |

| CHARCON : NEUTRAL |

| SUBGROUP NO.: 4 DEVICE TYPE : S1CONN TRACENO : 0 |

| SEARCH MODE : CIRCULAR ACD THRESHOLD : * |

| NUMBER OF ASSOCIATED ROUTES : 1 PRIORITY : 2 |

| TDDRFLAG : ON TDDRTHRESHOLD: 2 SOURCEGROUPIDX : 1 |

| GDTRRULE : 0 ACDPMGRP : 0 |

| THE FOLLOWING TRUNKS (LTG-LTU-SLOT-CCT) HAVE BEEN ALLOCATED: |

+------+

| 1- 1- 14-0 1 | 1- 1- 14-0 2 | 1- 1- 14-0 3 |

| 1- 1- 14-0 4 | 1- 1- 14-0 5 | 1- 1- 14-0 6 |

| 1- 1- 14-0 7 | 1- 1- 14-0 8 | 1- 1- 14-0 9 |

| 1- 1- 14-0 10 | 1- 1- 14-0 11 | 1- 1- 14-0 12 |

| 1- 1- 14-0 13 | 1- 1- 14-0 14 | 1- 1- 14-0 15 |

| 1- 1- 14-0 16 | 1- 1- 14-0 17 | 1- 1- 14-0 18 |

| 1- 1- 14-0 19 | 1- 1- 14-0 20 | 1- 1- 14-0 21 |

| 1- 1- 14-0 22 | 1- 1- 14-0 23 | |

+------+

AMO-BUEND-111 TRUNK GROUP

DISPLAY COMPLETED;

Step 2: Trunks Setup

Verify that the trunks are configured with DEVICE TYPE: S1CONN and using the PSS1V2 protocol.

disp-tdcsu

PEN1 = 1-1-14-0;

DISP-TDCSU:1-1-14-0;

H500: AMO TDCSU STARTED

+------DIGITAL TRUNK (FORMAT=L) ------+

| DEV = S1CONN PEN = 1-01-014-0 TGRP = 3 |

|------|

| PROTVAR = PSS1V2 INS = Y SRCHMODE = CIR |

| COTNO = 3 COPNO = 3 DPLN = 0 |

| ITR = 0 COS = 3 LCOSV = 25 |

| LCOSD = 1 CCT = DESTNO = 0 |

| SEGMENT = 1 DEDSCC = DEDSVC = NONE |

| FACILITY = DITIDX = SRTIDX = |

| TRTBL = GDTR SIDANI = N ATNTYP = TIE |

| CBMATTR = NONE NWMUXTIM = 10 TCHARG = N |

| SUPPRESS = 0 DGTPR = CHIMAP = N |

| ISDNIP = ISDNNP = |

| PNPL2P = PNPL1P = PNPAC = |

| TRACOUNT = 31 SATCOUNT = MANY NNO = 3 |

| ALARMNO = 0 FIDX = 1 CARRIER = 1 |

| ZONE = EMPTY COTX = 3 FWDX = 1 |

| DOMTYPE = UNKNOWN DOMAINNO = 0 TPROFNO = |

| INIGHT = CCHDL = |

| UUSCCX = 16 UUSCCY = 8 FNIDX = 1 |

| CLASSMRK = EC & G711 & G729OPT SRCGRP = |

| TCCID = |

|------|

| BCNEG = N BCGR = 1 LWPAR = 1 |

| LWPP = LWLT = LWPS = |

| LWR1 = LWR2 = |

| DMCALLWD = DMCSEC = |

| SVCDOM = |

| BCHAN = 1 & 23 |

| |

+------+

AMOUNT OF B-CHANNELS IN THIS DISPLAY-OUTPUT: 23

AMO-TDCSU-111 DIGITAL TRUNKS

DISPLAY COMPLETED;

Step 3: Trunk’s COP & COT Parameters

<disp-cop

COPNO = 3;

DISP-COP:3;

H500: AMO COP STARTED

COP: 3 INFO:

DEVICE: INDEP SOURCE: DB

PARAMETER:

LINE WITH START-DIAL-SIGNAL SDL

SPECIAL MODE SFRM

REGISTRATION OF LAYER 3 ADVISORIES L3AR

START-DIALING-SIGNAL TIMER 1 (AMO DTIM2: PARAMETER STADIAL1) TIM1

AMO-COP -111 CLASS OF PARAMETER FOR DEVICE HANDLER

DISPLAY COMPLETED;

<disp-cot

COTNO = 3;

DISP-COT:3;

H500: AMO COT STARTED

COT: 3 INFO:

DEVICE: INDEP SOURCE: DB

PARAMETER:

RECALL IF USER HANGS UP IN CONSULTATION CALL RCL

UNRESTRICTED SUFFIX DIALING USD

KNOCKING OVERRIDE POSSIBLE KNOR

CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC

NETWORKWIDE AUTOMATIC CALLBACK ON BUSY CBBN

NETWORKWIDE AUTOMATIC CALLBACK ON FREE CBFN

NETWORKWIDE CALL FORWARDING PERMITTED FWDN

NETWORKWIDE FORWARDING NO-ANSWER FNAN

REGISTRATION OF IMPLAUSIBLE EVENTS IEVT

END-OF-DIAL FOR BLOCK IS SET BLOC

SEND NO NODE NUMBER TO PARTNER LWNC

CONNECTION TO ROUTE OPTIMIZATION NODE ROPT

INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR NLCR

TSC-SIGNALING FOR NETWORKWIDE FEATURES (MANDATORY) TSCS

USE DEFAULT NODE NUMBER OF LINE DFNN

INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR (DATA) NLRD

LINE WITH IMPLICIT NUMBERS LINO

LAST REDIRECTING NUMBER IS SEND TO PHONEMAIL LRPM

NO SIMPLE DIALOG AVAILABLE NOSD

NO TONE NTON

AMO-COT -111 CLASS OF TRUNK FOR CALL PROCESSING

DISPLAY COMPLETED;

Step 4: Trunk Route's Information

<disp-richt

MODE = ?

MODE : ADDRESS-MODE OF THE ROUTE

CHARACTERISTIC : REQUIRED CONDITIONAL

POSS. VALUES : ALL ALL

PM PHONE MAIL

INFO SERVICE INFORMATIONS

LRTE LCR ROUTE NUMBER

CD CODE

MODE = all;

DISP-RICHT:ALL;

H500: AMO RICHT STARTED

+------+

| ROUTES FOR ALL DPLN SVC = VCE |

| |

+------+------+----+-+------+-----+----+--+

| |DESTNO AND CPS |CCNO|L+---+---+------+-----+ | | W|

| | 1 111112| |B|CNV|DSP| TEXT |PULS | | | D|

| |12345 67890 123452| | | | | |PAUSE| | | B|

+------+------+----+-+---+---+------+-----+----+--+

|30 |...... | 3| | W | W | | | 3| | |

|NEUTRAL|VM | | | | | | | | | |

+------+------+----+-+---+---+------+-----+-----+----+--+

Step 5: Out-Dial Rule (ODR) Routing Setup

<disp-lodr;

DISP-LODR;

H500: AMO LODR STARTED

+------+

| ODR POSITION CMD PARAMETER |

+------+------+

| 3 | 1 ECHO 3 |

| | 2 ECHOALL |

| | 3 END |

+------+------+
Step 6: Route for Trunk Group 3 Setup

<disp-ldat;

DISP-LDAT;

H500: AMO LDAT STARTED

| LROUTE = 3 NAME = VM SERVICE = VCE |

| TYPE = NWLCR DNNO OF ROUTE = 30 |

| SERVICE INFO = |

+------+-----+-----+----+-----+------+------+------+------+------+

+------+-----+-----+----+-----+------+------+------+------+------+

| 1| 1| 3| 1| 1 | ******** | 1 EMPTY| NONE | | 0 |