1

Dialogic® Media Gateway Installation and Configuration Integration Note

1. Scope This document is intended to detail a typical installation and configuration of a Dialogic® Media Gateway when used to interface between a PBX and a unified messaging application. 2. Configuration Details Listed below are the specific details of the PBX and Dialogic® gateway used in the testing to construct the following documentation. 2.1 PBX PBX Vendor Astra\Intecom

Model(s) 6880

Software Version(s) 3.4K or later

Additional Notes N/A 2.2 Gateway Gateway Model Dialogic® DMG2xxxDTI (former TIMGxxxDTI)

Software Version(s) 5.1 SU3 (5.1.160)

Protocol T1 CAS SMDI Serial Integration 2.3 System Diagram The diagram below details the setup used in the testing and creation of the technical document.

Fax

PBX DMG2000

T1/E1 IP LAN

Messaging Server

Subscriber Stations

Serial IntegrationLink

2

3. Prerequisites 3.1 PBX Prerequisites 3.1.1 PBX Equipment Required To support the T1 CAS configuration as documented, you need the 300-0289-001 Line side T1 interface card. The serial integration interface requires access to a Programmable Data Interface (PDI) interface card numbered 520-1000-004. 3.1.2 PBX Cabling Requirements

• No special cabling was required. A standard T1 cable was used. It is recommended that a high quality cable be used for long loop lengths or loops that will be run through electronically noisy environments.

• Because the integration data is transmitted along a secondary serial data path between

the PBX and the gateway, it will be required to either purchase or construct a cable that connects the serial port of the Intecom PBX to the serial port of the gateway. The diagram below provides details on how this cable was constructed for the creation of this document.

Pin Description of pin on PBX

1 DCD (Carrier Detect)

2 Rx (Receive)

3 Tx (Transmit)

4 DTR (Data Terminal Ready)

5 GND (Ground)

6 DSR (Data Set Ready)

7 RTS

8 CTS

9 NC (No Connection) The industry rule of thumb for RS232 serial communications is to keep the length of the cable no longer than 50 feet. Lengths longer than the recommended standard may need additional equipment to ensure correct transmission levels are maintained. 3.2 Gateway Prerequisites The gateway needs to support a T1 CAS robbed bit interface. 4. Summary of Limitations No limitations noted as of the last update to this document.

3

5. Gateway Setup Notes During the initial setup of the Dialogic® gateway using the serial port, you must:

• Assign the gateway a Unique IP address, subnet mask, and network gateway address (if the latter is required).

• Configure the gateway to use the SIP VoIP protocol. • Set the Line Mode to T1. • Set the Protocol to CAS – Loop start.

During the solution-specific setup of the Dialogic® gateway using the web interface, you must:

• Configure the gateway with at least a single IP endpoint pointing to your voice messaging server.

• Set the Voice coder to be either G7.11 (default) or G.273 if required. • Set the Line Encoding and Line Framing as required by your T1 Interface. Typical

settings are Encoding = AMI and Framing = SF (D4). • Set the CAS Cpid type to TypeII_CPID. • Set the Serial Mode to Master for the single master gateway and to Slave for any of the

additional slave gateways (if you are using any slaves). • Ensure that the serial port settings (baud rate, parity and stop bits) match the port

settings on the PBX. 6. PBX Setup Notes The basic steps of setting up the PBX for use with this gateway and a voice messaging server are as follows:

• Checking the SPAR • Building the Trunk Group • Building the Route Guide/assigning the proper PDT • Building the SDG (Satellite Directory Group) • Populating the User Group • Programming the PDI (Programmable Data Interface)

All of the PBX programming is done via a serial terminal. Trunk Groups, Route Guides and Satellite Directory Groups are all independent of each other. However, it is convenient and logical to assign the same numbers for each specific group. This may seem confusing at first but becomes clear by examining the switch output below. Unassigned groups are discovered by interrogating the PBX. 6.1 Checking SPAR Before proceeding to the actual configuration of the Voicemail Interface, the SPAR (System Parameters) table should be checked. Generically, the Intecom comes pre-programmed with 2 voicemail Interfaces. The SPAR table shows how many voicemail interfaces are theoretically possible. Scrolling down to the Voicemail mnemonic reveals that the system may have 255 interfaces. The prompt in this list that we are interested in is the IIN that tells us what we need to know. spar SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES => d ENTER DISPLAY TYPE or ?.....................S => DRL...DATABASE RELEASE LEVEL.............RL41022A SRL...SOFTWARE RELEASE LEVEL.............RL40PS3.5.K.C MMT...MAN MACHINE TERMINALS..............0 TO 53 PRT...PORTS..............................1 TO 147456 FAC...FACILITIES.........................1 TO 442367

4

TGP...TRUNK GROUPS.......................1 TO 4094 TKA...TRUNK ACCUMULATORS.................8 TO 00000 UGN...USER GROUPS........................1 TO 1000 DIR...DIRECTORY NUMBER DESCRIPTORS.......1 TO 100 FDD...FIRST DIGIT DISPOSITION ENTRIES....1 TO 300 TDD...TWO DIGIT DISPOSITION ENTRIES......1 TO 300 CHD...CALL HANDLING DESCRIPTORS..........1 TO 300 SNP...SPECIAL NPA DESCRIPTORS............1 TO 300 LOC...LOCAL CALL DESCRIPTORS.............1 TO 300 CTR...CALL TYPE ROUTING DESCRIPTORS......1 TO 300 AC1...1 DIG ACCESS CODE ROUTING ENTRIES..1 TO 300 AC2...2 DIG ACCESS CODE ROUTING ENTRIES..1 TO 300 NPA...NPA DESCRIPTORS....................0 TO 299 Q00...NPA CORE/DISK ENTRIES..............CORE NNP...NETWORK NUMBER PLAN DESCRIPTORS....1 TO 100 4DS...FOUR DIGIT SPEED DESCRIPTORS.......1 TO 100 3DS...THREE DIGIT SPEED DESCRIPTORS......1 TO 100 IDD...INTL COUNTRY CODE DESCRIPTORS......1 TO 1000 CCR...CITY CODE ROUTING GROUPS...........1 TO 2046 BNP...FIRST DIGIT BLOCKS FOR NNP.........0 TO 799 B4D...FIRST DIGIT BLOCKS FOR 4DS.........0 TO 799 B3D...FIRST DIGIT BLOCKS FOR 3DS.........0 TO 799 NNX...NNX EXCLUSION GROUPS...............1 TO 2047 Q01...NNX CORE/DISK ENTRIES..............CORE ORG...ORIGINATION RESTRICTION GROUPS.....1 TO 127 Q06...ORES CORE/DISK ENTRIES.............CORE RTG...ROUTE GUIDES.......................1 TO 4000 PDT...PREFIX DIGIT TABLES................1 TO 2600 CDT...COLLECT DIGIT TABLES...............1 TO 64 AMG...ANNUNCIATOR MESSAGES...............1 TO 47 ICI...INCOMING CALL MESSAGES.............1 TO 1000 DCP...DATA CALL PROGRESS MESSAGES........1 TO 31 THR...THRESHOLD CFG GROUP IN/OUT.........30 DLY...DELAY TIME FOR SENDING PORTS TO CP.2 SEC CLS...CLASSES OF SERVICE.................1 TO 255 TTP...TERMINAL TYPES.....................1 TO 126 BTM...BUTTON TEMPLATES...................1 TO 255 SKA...SOFTKEY APPLICATION NAME NUMBER....1 TO 25 ADY...DAY OF YEAR RESTRICTION ENTRIES....1 TO 14 ADW...DAY OF WEEK RESTRICTION ENTRIES....1 TO 9 ATA...TIME OF DAY RESTRICTION ENTRIES....1 TO 24 ICM...MAX. INTERCOM GROUPS...............1 TO 4090 CPG...CALL PICKUP GROUPS.................1 TO 4089 SDG...SATELLITE DIR. GROUPS..............1 TO 999 ABD...ABBREVIATED DIAL(100) GROUPS.......1 TO 2000 ABV...NUMBER OF 100 ABBV. DIALS USED.....0 ACD...AUTOMATIC CALL DISTRIBUTION PILOTS.1 TO 4001 CGS...ACD CALL GUIDES....................1 TO 12003 ACS...ACD CALL STEPS PER CALL GUIDE......1 TO 256 NPS...NUMBER OF ACD PILOT SOURCES........1 TO 100 AGP...ATDC GROUPS........................0 TO 249 ATD...ATTENDANT CONSOLES.................0 TO 249 ITK...INTEMAIL TRUNK IDENTIFICATION......1 TO 1000 IIN...INTEMAIL INTERFACE NUMBER..........1 TO 255 NRS...NUMBER OF CRS ENTRIES USED.........15 CRS...MAXIMUM NUMBER OF CRS ENTRIES......2047 MNL...MAX MAN-MACHINE NESTING LEVELS.....3 HUN...NUMBER OF HUNT GROUPS..............1 TO 250 HUL...LINES PER HUNT GROUP...............1 TO 250 IIG...ISDN PRI GROUPS....................0 TO 2001 IPS...ISDN PRI SPANS.....................0 TO 2301 MPG...MAX NUMBER OF PRI SPANS/GROUP......22

5

IST...ISDN PRI SPAN STATISTICS TABLES....1 TO 2301 IPT...ISDN PARAMETER TABLES..............1 TO 30 INT...ISDN SERVICE SELECTION TABLES......1 TO 100 ITA...ISDN PRI TRUNK GRP ASSIGN TABLES...1 TO 32 IF1...CALLING PARTY NUMBER - 1 INFORMATION DIGIT CALLING NUMBER IDENTIFIED..........0 MULTI-PARTY LINE...................1 IDENTIFICATION FAILURE.............2 IF2...CALLING PARTY NUMBER - 2 INFORMATION DIGITS CALLING NUMBER IDENTIFIED..........00 MULTI-PARTY LINE...................01 IDENTIFICATION FAILURE.............02 DLG...LONG PERIOD ( 1000 MS) OAI DIALS.600 DST...SHORT PERIOD ( 250 MS) OAI DIALS.150 ALG...LONG PERIOD ( 1000 MS) ARC MSGS..600 AST...SHORT PERIOD ( 250 MS) ARC MSGS..150 WHS...WORK AT HOME STATIONS CONFIGURED...12000 WORK AT HOME STATIONS EQUIPPED.....12000 WHL...WORK AT HOME LOCATORS (NUMBERS)....1 TO 12000 IPG...IVS SERVICES - # IVS GROUPS........500 IPZ...IVS SERVICES - # IVS PHRASES.......65535 URT...IPI USER ROUTE TABLES..............1000 SRT...IPI SYSTEM ROUTE TABLES............1000 NMC...# OAI MIRROR CHANNELS LICENSED.....16 NTC...# OAI TRANSPORT CHANNELS LICENSED..15 NOC...# ETHERNET OAI CHANNELS LICENSED...36 EVT...# OAI EVENT CHANNELS LICENSED......2 6.2 Looking for Unused Trunk Groups This screen shows the process of searching the PBX for an unused trunk group number for use latter in the programming. The programming shown below will be using an already assigned number (25) so it does not show on this list. If configuring a new trunk, you will want to use an unassigned number. grps SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES, SEARCH => d SPECIFY GROUP NUMBER or - ................... => - A=Assigned; U=Unassigned GROUPS.............A => u GROUP NUMBER ASSIGNMENT REPORT *** 09/10/07 10:40:32 UNASSIGNED GROUPS: 10 12-13 17-19 29 46-47 49-51 59 63 65-70 72-79 81-87 91-95 97 99-107 109-140 142-149 158-159 161-198 202-207 209 211-246 248-249 251 258-259 261-298 300-349 351 358-359 361-398 400 402-409 411-419 421-439 445-449 451 458-459 461-529 533-910 912-924 926-999 1001-1299 1305 1326 1343 2084 2416 2874-2882 3957-3960 3974-3999 4008-4075 4078

6

6.3 Looking for Unused Satellite Directory Groups SELECT COMMAND => sdgp SELECT MODE: PRINT, DISPLAY, UPDATE, SEARCH => d SPECIFY GROUP NUMBER or -.................... => - A=Assigned; U=Unassigned SATELLITE GROUPS...A => u *** UNASSIGNED SATELLITE GROUP REPORT 09/10/07 10:40:43 1-3 5-13 17-21 26-27 29 31 33-34 38-40 43 45 47 49-70 72-95 97-99 102-124 126-140 144-214 216-221 224-233 236-246 248-249 252-439 441-530 532-924 926-999 6.4 Looking for Unused Route Guides SELECT COMMAND => rout SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES, SEARCH => d ROUTE GUIDE # or ?........................... => - ** ALLOCATED ROUTE GUIDE NUMBERS: 1 - 5 , 13 , 15 - 16 , 22 - 25 , 28 , 30 , 32 , 35 - 37 , 41 - 42 , 44 , 46 , 48 , 61 , 71 , 96 , 100 - 101 , 125 , 138 , 141 , 215 , 222 - 223 , 235 , 247 , 250 , 300 , 440 , 511 , 531 , 911 , 925 , 1234 , 2314 6.5 Configuring Trunk Group Once the group number has been determined, the trunk group in programmed with the attributes described below. Several of the important prompts are listed here: ITY – This specifies the format for the SMDI data. SMDI – Fixed 10 Digit is the setting that should be used. IST – This allows the PBX to perform supervised transfers. If this prompt is set to NO then ONLY blind transfers are allowed. To use supervised transfers then this setting needs to be set to YES. SLC – This allows you to set the hunting pattern of the trunk members in the group. UMS T1 OPX GRP ** TRUNK GROUP DEFINITION 08/17/07 13:15:29 ***...TRUNK GROUP........................25 ***...TRUNK GROUP TYPE...................UNIVERSAL TCI...TRUNK CLASS IDENTIFICATION.........LOCAL CO UGP...USER GROUP NUMBER..................1 VTT...VOICE TRUNK TRANSFER ENABLED.......YES CDT...TRANSFER COLLECT DIGIT TABLE #.....NONE DCS...DEFAULT CLASS OF SERVICE...........0 CNC...NATIONAL CALLING PARTY # CONTENTS..NONE DCP...DISPLAY CALLING PARTY NUMBER.......NO PND...PRIVATE NETWORK....................NO ***...LANmark PRI TRUNK GROUP............NO ITY...INTEMAIL TYPE......................SMDI - FIXED 10 DIGIT IST...DOES InteMail SUPERVISE TRANSFERS?.NO

7

IML...InteMail USER ID LENGTH............5 IIN...INTEMAIL INTERFACE NUMBER..........1 VNP...InteMail NUMBER FORMAT.............DIRN VNN...InteMail SYSTEM NODE NUMBER........1 OAM...OAI ASSOCIATED MEMBER..............NO BTG...BROADCAST TRUNK GROUP..............NO FTH...FAILURE THRESHOLD..................3 RDT...RESEIZE DELAY TIME............MSEC:250 CHT...TRUNK MONITOR MINIMUM HOLD TIME....0 DET...DISTANT END RELEASE TIME.......SEC:60 DCT...DATA CALLS ALLOWED.................NO SWM...SEIZE WHEN MOS.....................YES TCH...TRUNK CALL HANDLING................EXTERNAL NDS...DISCONNECT SUPERVISION.............NO IGG...IGNORE GLARE.......................NO GDT...GLARE DETECT TIME.............MSEC:100 XFT...DISTANT IBX ALLOWS FEATURE TRANSP..NO DPT...DTMF PASSTHROUGH TIMING INDEX......NONE CRO...CPN/ANI ROUTING....................NO ......TRUNK DIRECTION....................BOTH WAYS *** INCOMING PARAMETERS STY...INCOMING CALL ORIGINATION TYPE.....T1 OFF PREM.....OPX (OFF PREMISE) TYP...INCOMING TRUNK TYPE................DIALED ICM...INCOMING CALL MESSAGE #............NONE DCC...ROUTING TYPE.......................NORMAL ROUTING ONLY IDS...INCOMING DIGIT SEQUENCE............DESTINATION NUMBER ONLY IRD...RESPONSE TO DESTINATION NUMBER.....NONE IRC...RESPONSE TO CALLING PARTY NUMBER...NONE IIT...INCOMING INFO DIGIT TYPE/LENGTH....NONE WPR...WHISPER MESSAGE SOURCE GROUP.......NONE APA...TRUNK GROUP AUTHORIZATION TYPE.....NONE PVA...PRE-VALIDATE AUTHORIZATION CODE....NO RSC...RESET COUNT........................1 LVL...PREDEFINED LEVEL CODE..............NONE TNE...TONE TABLE ENTRY NUMBER............NONE MOD...INCOMING DIAL MODE.................DTMF RGF...DTMF RECEIVER GROUP................52 TOO...TIMEOUT TO ATTENDANT...............NO MCL...MULTIPLE CALLING ALLOWED...........NO RAC...REUSE AUTH FOR MULT. CALLS.........NO GAC...GROUP AUTH REQUIRED FOR TRUNKS.....NO SAC...SYSTEM ACCESS CODE.................NONE CWR...CALLWAIT RINGBACK..................NO UCT...TRUNK UPDATE CDR ON TRANSFER.......ALL CPT...CALL PROGRESSING TONES:............IBX PROVIDED RIO...RESPONSE TO INCOMING ORIGINATION...NONE IUG...InteMail LAMP MESSAGE USER GROUPS..OWN NUG...INTER-USER GROUP NNP USER GROUPS...OWN TCT...STATION CALL RESTRICTION ENABLED...NO 8NC...800 TO 4D SPEED NUMBER CONVERSION..NO *** OUTGOING PARAMETERS MSG...MODEM SIGNALLING...................YES TXA...DIRECT TGRP SELECT ALLOWED.........YES ATG...ANNOUNCEMENT TRUNK GROUP...........NO SLC...TRUNK SELECTION....................TOP DOWN ICA...INTER-LATA CARRIER.................10XXX CPN...CALLING PARTY NUMBER...............DO NOT SEND DIAGNOSTIC PARAMETERS: Y or N............N => PORT ASSIGNMENT REPORT 1.3.07.01 1.3.07.02 1.3.07.03 1.3.07.04 1.3.07.05 1.3.07.06 1.3.07.07 1.3.07.08 1.3.07.09 1.3.07.10 1.3.07.11 1.3.07.12 1.3.07.13 1.3.07.14 1.3.07.15 1.3.07.16 1.3.07.17 1.3.07.18 1.3.07.19 1.3.07.20 1.3.07.21 1.3.07.22 1.3.07.23 1.3.07.24

8

This trunk group is then applied to the T1 card you have selected to be used in the PBX. Because this is a line side T1 interface, you will notice that each bearer channel of the T1 is specified with a circuit type of OPX STE (Off Premise Extension) SELECT COMMAND => card SELECT MODE: PRINT, DISPLAY, UPDATE, MOVE => d ENTER LOCATION or ?.......................... => 1.3.7 FRAMING....D4 TRANSMIT LENGTH....4000-6000 LINE CODE..AMI MESSAGE TYPE....AT&T YELLOW ALARM TYPE...."0" IN BIT 2 CARRIER GROUP ALARM: SIGNAL LOSS....NO RED ALARM....NO YELLOW ALARM....NO BLUE ALARM....NO TRUNK LOSS NIGHT SAT TRAN REC CIRCUIT CKT GROUP DIR. CLOS PLAN DIRN CKT GAIN GAIN TYPE VTN --- ----- ---- ---- ---- ------- --- ---- ---- ------------- ---- CABINET 1 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 1 1 2 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 2 SHELF 3 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 3 3 4 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 4 SLOT 5 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 5 7 6 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 6 7 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 7 8 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 8 9 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 9 10 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 10 11 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 11 12 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 12 13 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 13 CABINET 14 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 14 1 15 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 15 SHELF 16 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 16 3 17 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 17 SLOT 18 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 18 7 19 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 19 20 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 20 21 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 21 22 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 22 23 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 23 24 25 BOTH 21 DTT NONE NO 0.0 0.0 OPX STE 24 6.6 Define the Route Guide and PDT At this point, we can define the route guide and the PDT. SELECT COMMAND => rout SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES, SEARCH => d ROUTE GUIDE # or ?........................... => 25 UM Voicemail *** ROUTE GUIDE # 25 08/17/07 13:18:09 1 TRUNK GROUP 25 -- PREFIX DIGIT STRING # 2 2 BUSYOUT

9

The PDT defines how integration digits will be out pulsed to the VM system. Since we are using serial style integration, we will turn this off. SELECT COMMAND => pdt SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES, SEARCH => d PREFIX DIGIT TABLE NUMBER or ?............... => 2 Empty PDT No Digits sent *** OFF-NET PREFIX DIGIT TABLE # 2 08/17/07 13:18:52 1) DESTINATION NUMBER: PLAN: UNKNOWN TYPE: UNKNOWN OUTPULSE NUMBER TYPE: UNKNOWN NUMBER: NO PREFIX DIGITS PLUS SAME DIGITS RECEIVED 6.7 Define the Satellite Directory Group Now that the trunk group and route guide have been created, the Satellite Directory Group may now be assigned. This will later be populated into the User Group settings. It is important to understand that the Satellite Directory Group is just a routing mechanism. A directory number is assigned to the SDG. This becomes the Voicemail number that users dial to retrieve messages. In this case, the number is 66250. It can now be seen that 66250 points to a Route Guide, this in turn points at a Trunk Group within the route guide. UM 66250 ** SATELLITE DIRECTORY GROUP 25 08/17/07 13:17:40 ***...SATELLITE DIRECTORY GROUP TYPE.....InteMail-Direct ***...USER GROUP.........................1 RCF...REMOTE CALL FORWARD................YES DDD...DEFAULT DESTINATION DIRN...........66250 COS...CLASS OF SERVICE...................0 ** MMP WARNING: THE ORIGINATOR"S COS WILL BE USED RGN...ROUTE GUIDE NUMBER.................25 MDL...MINIMUM DIRECTORY NUMBER LENGTH....1 66250 6.8 Define the User Group The Satellite Directory Number is now populated into the User Group setting. When a user depresses the Voicemail button on the Intecom telephone set, this determines which Voicemail system is the target of the button push. All directory numbers must have a User Group assigned to them.

10

The IMD prompt is where you specify the Satellite Directory group number defined above. SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES => d USER GROUP NUMBER (1-1000) OR ?..... => 1 SELECT SUBCOMMAND or ? => ugp ** USER GROUP PARAMETERS FOR USER GROUP #1 08/17/07 13:15:14 PPN...PHYSICAL PARTITION NUMBER...................0 MOH...MUSIC ON HOLD PORT NUMBER...................NONE HUG...HOME USER GROUP NUMBER......................NONE CNO...CALL CENTER NUMBER..........................1 IMD...InteMail DIRECT CALL SDGP NUMBER............25 IMC...InteMail MESSAGE CENTER SDGP NUMBER.........NONE IUG...InteMail LAMP MESSAGE USER GROUPS...........ALL OCC...OAI NUMBER FOR OAI ASSOCIATED MEMBER........20 OAP...OAI APPLICATION ID..........................1 AGN...ATTENDANT GROUP ............................NONE IAG...INTERCEPT ATTENDANT GROUP...................NONE PCG...PARK CHANNEL GROUP .........................90 COG...CALL ORIGINATION GROUP .....................20 UTG...UTILITY TRUNK GROUP.........................NONE HNP...HOME NPA ...................................425 HN1...HOME NNP NUMBER #1..........................NONE HN2...HOME NNP NUMBER #2..........................NONE HN3...HOME NNP NUMBER #3..........................NONE HN4...HOME NNP NUMBER #4..........................NONE NUG...INTER-USER GROUP NNP USER GROUPS............ALL RETURN CONTINUES DISPLAY..... => TLT...RECLASSIFY TOLL W/HOME NPA AS LOCAL TOLL....NO LOC...LOCAL/LOCAL-TOLL ROUTING....................NORMAL ILC...INTER-LATA CARRIER CODE.....................NONE CRD...CALL RECORDING DIRECTORY NUMBER.............NONE GRP...WORK AT HOME IDLE MESSAGE SOURCE GROUP......NONE CN1...NATIONAL CALLING PARTY NUMBER 1.............425-70X-XXXX NAME.................DIRN LOOKUP CN2...NATIONAL CALLING PARTY NUMBER 2.............425-722-XXXX NAME.................NONE CN3...NATIONAL CALLING PARTY NUMBER 3.............300-30X-XXXX NAME.................NONE CN4...NATIONAL CALLING PARTY NUMBER 4.............425-306-XXXX NAME.................TESTMICRO SPA...SMART PHONE ISDN/TELEPHONY # ACCESS CODE....0 AC1...1 DIGIT ACCESS CODE ROUTING.................UNASSIGNED AC2...2 DIGIT ACCESS CODE ROUTING.................UNASSIGNED CHP...CALL HANDLING PARAMETERS....................ASSIGNED CTR...CALL TYPE ROUTING...........................UNASSIGNED DNA...DIRECTORY NUMBER ALLOCATION.................ASSIGNED DNS...DNIS ROUTING................................ASSIGNED FDD...FIRST DIGIT DISPOSITION.....................ASSIGNED TDD...TWO DIGIT DISPOSITION.......................UNASSIGNED IDD...INTL DIRECT DIALING.........................ASSIGNED RETURN CONTINUES DISPLAY..... => LCR...LOCAL CALL ROUTING..........................ASSIGNED LTR...LOCAL TOLL ROUTING..........................UNASSIGNED NNP...NNP ROUTING.................................2 3 4 5 6 7 8 9 NPA...NPA ROUTING.................................ASSIGNED SNP...SPECIAL NPA ROUTING.........................ASSIGNED 3DS...THREE DIGIT SPEED NUMBERS...................UNASSIGNED 4DS...FOUR DIGIT SPEED NUMBERS....................UNASSIGNED FRT...10 DIGIT DIALED FOREIGN NPA TABLE...........ASSIGNED XRT...EXCHANGE RECLASSIFICATION TABLE.............UNASSIGNED END OF DISPLAY

11

6.9 Programming the PDI The last step is to actually program the PDI (Programmable Data Interface). The PDI is essentially a modem emulator but can take on many roles. In this case, it is assigned as a VMP (Voicemail Program). The physical RS232 cable is attached to the PDI. This provides the SMDI output. It is necessary to know the baud rate, parity and stop bits of the interface. The appropriate Terminal Type must be configured and assigned to the PDI. First you will set the terminal type using the ttyp command. SELECT COMMAND => ttyp SELECT MODE: PRINT, DISPLAY, UPDATE, SEARCH, TITLES => d SPECIFY DATA TERMINAL TYPE BY NUMBER: n; or nn,mm (from,to); or -................ => 90 2400 7 1 and E ** DATA TERMINAL TYPE DEFINITION NUMBER 90 08/17/07 13:33:04 TYP...LINE TYPE..........................ASYNCHRONOUS PTC...PROTOCOL...........................BISYNC MDM...MODEM..............................NO TUI...TYPE OF USER INFORMATION...........UNKNOWN SPD...TERMINAL SPEED.....................2400 MGF...MODEM GROUP........................0 MG2...MODEM GROUP, SECOND CHOICE.........0 MG3...MODEM GROUP, THIRD CHOICE..........0 DRG...ISDN DATA RATE ADAPTION GROUP......NONE CDE...ENCODING...........................ASCII DTE...DATA TERMINAL EQUIPMENT............NO PAR...PARITY.............................EVEN STB...STOP BITS..........................1 DLG...DATA LENGTH........................7 DATA BITS In this example we are using the standard serial settings for SMDI as 7 Data Bits, 1 Stop Bit, Even parity and a speed (Baud rate) of 2400. You now build the PDI interface using the VMP command as follows: VMP 1.2.3.6 ***...INFORMATION LINK DEVICE TYPE.......VMP1 ***...INFORMATION LINK ENTRY NUMBER......76 ***...INFORMATION LINK PORT..............001.1.01.20 ***...PDI-1000 PORT......................001.2.03.06 ***...APPLICATION NAME...................VMP IUG...INFORMATION LINK USER GROUP........1 ITT...INFORMATION TERMINAL TYPE..........90 BRT...BAUD RATE....................2400 NDB...NUMBER OF DATA BITS..........7 STB...NUMBER OF STOPS BITS.........1 PAR...PARITY.......................EVEN PUG...PDI-1000 USER GROUP................1 PTT...PDI-1000 TERMINAL TYPE.............90 RTY...INFORMATION LINK RETRY COUNTER.....10 SUG...SERVED USER GROUPS.................ALL

12

6.10 Subscriber Setup All voice system subscribers need to be configured to use the user group as their voice mail destination when they press their voice mail button to retrieve messages. The subscriber sets should also be forwarded to use the extension number defined in the satellite directory group for busy and ring no answer conditions. 6.11 Additional Comments N/A 7. Testing Validation Matrix The table below shows various test scenarios that are run as typical validation scenarios when the gateway is used in a voice messaging situation. The notes column specifies any notable parts of the test. The test scenarios below assume that all gateway configuration parameters are at their default values. For a complete sample showing call flows and states, please consult the Gateway SIP Compatibility Guide. Test Number

Call Scenario Description Notes

Inbound call scenarios

1 Direct call to hunt group. The calling party number is expected to be contained in the From header of the Invite.

2 Internal ring-no-answer forward. The called party will be shown in the Diversion header of the invite The calling party number is expected to be contained in the From header of the Invite. The reason of the diversion header is shown as no-answer.

3 External ring-no-answer forward. The called party will be shown in the Diversion header of the invite. The calling party number is expected to be contained in the From header of the Invite. The reason of the diversion header is shown as no-answer.

4 Internal busy forward from a subscriber’s station set.

The called party will be shown in the Diversion header of the invite. The calling party number is expected to be contained in the From header of the Invite. The reason of the diversion header is shown as busy.

5 External busy forward from a subscriber’s station set.

The called party will be shown in the Diversion header of the invite The calling party number is expected to be contained in the From header of the Invite. The reason of the diversion header is shown as busy.

13

6 Internal all call forward from a subscribers station set.

The called party will be shown in the Diversion header of the invite. The calling party number is expected to be contained in the From header of the Invite. The reason of the diversion header is shown as fwd-all.

7 External all call forward from a subscriber’s station set.

The called party will be shown in the Diversion header of the invite. The calling party number is expected to be contained in the From header of the Invite. The reason of the diversion header is shown as fwd-all.

Transfer Scenarios

8 Blind transfer to a station from messaging server where the destination answers the call.

The transfer is completed once the destination is judged as connected. Depending upon the speed that the destination is answered the caller and called parties may be connected together with a slight bit of the called parties voice clipped.

9 Blind transfer to a station from messaging server where the destination does not answer the call.

If the station is configured to forward back to the gateway then the call will arrive looking as a forwarded call with the called party being the transfer destination.

10 Blind transfer to a subscriber’s station from messaging server where the destination is busy.

The transfer should fail.

11 Blind transfer to an invalid number. The transfer should fail.

12 Supervised transfer to a subscriber’s station from messaging server where the user does not answer the call.

The transfer completion speed and timing is up to the application. The application should decide to either complete the transfer and let the stations forwarding carry it back to the gateway or abort it before the forwarding happens.

13 Supervised transfer to a subscriber’s station from messaging server where the user answers the call.

The transfer completion speed and timing is up to the application.

13 Supervised transfer to a subscriber’s station from messaging server where the destination is busy.

The transfer completion speed and timing is up to the application. The application should decide to either complete the transfer and let the stations forwarding carry it back to the gateway or abort it before the forwarding happens.

14 Supervised transfer to an Invalid number.

The transfer completion speed and timing is up to the application.

14

Outbound Call Scenarios

15 Outbound call to subscriber station that answers.

The call is flagged to the application as completed when the gateway can determine that the call has been connected through. The application should take this into account when making decision when to start the audio stream.

16 Outbound call to subscriber station that does not answer.

The application needs to take into account if the destination has been set to forward back to the gateway for a ring no answer condition and judge accordingly when to either stop waiting for an answer and cancel the call or know that it will end up arriving back to the gateway as a forwarded call.

17 Outbound call to subscriber station that is busy.

The application needs to take into account if the destination has been set to forward back to the gateway for a ring no answer condition and judge accordingly when to either cancel the call or know that it will end up arriving back to the gateway as a forwarded call.

18 Outbound call to an external number. Depending on the state of the destination the call will either be judged as connected or failed due to busy or error tone conditions.

MWI Scenarios

19 Turn a subscriber’s light on that is currently off.

This should return success.

20 Turn a subscriber’s light on that is currently on.

This should return success.

21 Turn a subscriber’s light off that is currently on.

This should return success.

22 Turn a subscriber’s light off that is currently off.

This should return success.

15

8. Troubleshooting 8.1 Important Debugging Tools

• Ethereal/Wireshark – Used to view and analyze the network captures provided by the Dialogic® gateway diagnostic firmware.

• Adobe Audition – Used to review and analyze the audio extracted from the network captures to troubleshoot any audio-related issues.

• Microsoft HyperTerminal – Used to test the output of the PBXs serial port to determine if data is being sent by the PBX. This helps in the validation of the cabling and all connects on the serial interface between the PBX and the gateway.

• RS232 breakout box – This tool can be very valuable in doing serial cabling work. It helps you determine what signals are available and if data is being either transmitted or received.

8.2 Important Gateway Trace Masks These keys are helpful during all troubleshooting scenarios and should be considered keys to activate by default for all troubleshooting cases.

• voip prot and voip code – this allows the capture of all SIP-related messages as they are sent from and received by the gateway. This data is important in cases where you feel that the gateway is not able to communicate properly with the server.

• tel event and tel code – This allows the capture of all circuit-side activity of the emulated station set such as display updates, key presses, light transitions and hook state changes. This data is very important in the following scenarios:

o Call control problems (dropped calls, failing transfers, etc…) o Integration problems (incorrect mailbox placement, missed auto-attendant

greetings etc…)

These keys are helpful during specific issues and can be enabled for targeted troubleshooting of very specific cases. Activation of these keys may generate large amounts of data on busy systems and increase the size of the collected log files, but will not harm system performance.

• dspcpi (all keys) – This allows the capture of tone-related audio data. This data is very helpful in cases where you think you have problems detecting specific tones that should be, should not be, or are expected to be present at specific times during the call. If you do not suspect a tone-related issues this key may be left disabled. This data is very important in the following scenarios:

o Failing transfers o Failing outbound calls (play to phone) o Dropped calls (callers cut off while leaving messages, etc…)

• si – This allows the collection of all inbound and outbound serial data on the serial master gateway. This data is required in the troubleshooting of all integration-related issues seen on the gateway designated as the serial master.

• siip – This allows the collection of all inbound and outbound serial data on any of the serial slave gateways. This data is required in the troubleshooting of all integration-related issues seen on the gateway designated as a serial slave.

• simwi – This allows the collection of all activity reacted to the processing of MWIs using the serial port. This data is required for any MWI-related issues while using the serial interface.

16

9. Appendix 9.1 Abbreviations LBRC Low Bit Rate Coder

MWI Message Waiting Indication

LWC Leave Word Calling

PBX Private Branch Exchange

17

Copyright and Legal Notice Copyright © 2007 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation at the address provided below.

All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation or its subsidiaries (“Dialogic”). Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document.

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY.

Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.

Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the countries where such use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on the web at www.dialogic.com.

It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with Dialogic. More detailed information about such intellectual property is available from Dialogic’s legal department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9.

Dialogic encourages all users of its products to procure all necessary intellectual property licenses required to implement any concepts or applications and does not condone or encourage any intellectual property infringement and disclaims any responsibility related thereto. These intellectual property licenses may differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with different national license requirements.

Dialogic, Dialogic Pro, Brooktrout, Cantata, SnowShore, Eicon, Eicon Networks, Eiconcard, Diva, SIPcontrol, Diva ISDN, TruFax, Realblocs, Realcomm 100, NetAccess, Instant ISDN, TRXStream, Exnet, Exnet Connect, EXS, ExchangePlus VSE, Switchkit, N20, Powering The Service-Ready Network, Vantage, Making Innovation Thrive, Connecting People to Information, Connecting to Growth and Shiva, among others as well as related logos, are either registered trademarks or trademarks of Dialogic. Dialogic's trademarks may be used publicly only with permission from Dialogic. Such permission may only be granted by Dialogic’s legal department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9. Any authorized use of Dialogic's trademarks will be subject to full respect of the trademark guidelines published by Dialogic from time to time and any use of Dialogic’s trademarks requires proper acknowledgement.

Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other countries. Other names of actual companies and products mentioned herein are the trademarks of their respective owners.

This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property rights.

05-2672-001 November 2008