Avaya 1000E Supplement

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
1 of 103
DLG1010MXSM62CS
Avaya Solution & Interoperability Test Lab
Application Notes for Dialogic IMG 1010 Media Gateway
with Avaya® Communication Server 1000E 7.5 and Avaya
®Meeting Exchange® Enterprise Edition 6.2 using SIP
Trunking with Avaya Aura® Session Manager R6.2 - Issue
1.0
Abstract
These Application Notes present a sample configuration for connectivity between Avaya ®
Communications Server 1000E (CS1000E) using E1/PSTN to connect to the Dialogic IMG 1010
Media Gateway. The Dialogic IMG 1010 Media Gateway provides E1 to SIP and SIP to E1
protocol translation to interoperate with Avaya Aura ®Session Manager R6.2 which in turn is
connected via SIP Trunking to Avaya® Meeting Exchange Enterprise Edition 6.2.
Testing was conducted via the Internal Interoperability Program at the Avaya Solution and
Interoperability Test Lab.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
2 of 103
DLG1010MXSM62CS
Table of Contents
1. Introduction............................................................................................................................. 5
2. Interoperability Testing........................................................................................................... 5
2.1. Test Description and Coverage....................................................................................... 6
2.2. Test Results and Observations........................................................................................ 6
2.2.1. G729 Codec Issue..................................................................................................... 6
2.2.2. UBlast (Blast Dial) - Manual & Auto....................................................................... 7
2.2.3. Bridge Talk Reports.................................................................................................. 7
2.2.4. Network Outage / Recovery...................................................................................... 8
2.2.5. Line Transfer / Conference Transfer......................................................................... 8
3. Reference Configuration......................................................................................................... 8
4. Equipment and Software Validated...................................................................................... 10
4.1. Configuration Tools...................................................................................................... 11
5. Configure Avaya Communication Server............................................................................. 12
5.1. Login to Unified Communication Management GUI................................................... 12
5.2. Verify Equipped Feature Packages............................................................................... 14
5.3. Administer E1 Card ...................................................................................................... 15
5.4. Administer D-Channel.................................................................................................. 16
5.5. Administer Routes and Trunks ..................................................................................... 19
5.6. Administer Route List Block........................................................................................ 24
5.7. Administer Distant Steering Code ................................................................................ 26
5.8. Enable the E1 Card ....................................................................................................... 27
5.9. Enable D-channel Automatic Establishment................................................................ 28
5.10. Backing up the changes to CS1000E............................................................................ 28
6. Configure Dialogic IMG 1010 Media Gateway ................................................................... 29
6.1. Connecting with Client View........................................................................................ 29
6.2. Dialogic IMG Configuration Name.............................................................................. 31
6.3. Profiles.......................................................................................................................... 32
6.3.1. Create SIP Profile ................................................................................................... 32
6.3.2. Create DS1 Profile.................................................................................................. 33
6.3.3. IP Bearer Profiles.................................................................................................... 34
6.3.3.1 New IP Codec in Bearer Profile ...................................................................... 35
6.4. Logical IMG.................................................................................................................. 36
6.4.1. Physical IMG .......................................................................................................... 37
6.5. Network Interfaces........................................................................................................ 38
6.5.1. Network Interface VoIP Module ............................................................................ 39
6.5.2. Network Interface CPU - Signaling........................................................................ 40
6.6. Facilities for DS1 and VoIP.......................................................................................... 41

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
3 of 103
DLG1010MXSM62CS
6.6.1. DS1 Facilities.......................................................................................................... 42
6.6.2. VoIP Facilities ........................................................................................................ 43
6.7. IMG Signaling (ISDN, SS7, SIP, H.323) ..................................................................... 44
6.7.1. SIP Signaling .......................................................................................................... 45
6.7.2. ISDN Signaling....................................................................................................... 46
6.7.2.1 ISDN D Channel............................................................................................ 47
6.8. External Network Elements.......................................................................................... 48
6.8.1. External Gateways .................................................................................................. 48
6.8.1.1 External Gateway ............................................................................................ 49
6.9. Routing Configurations................................................................................................. 50
6.9.1. Channel groups ....................................................................................................... 50
6.9.1.1 Channel Group (ISDN).................................................................................... 51
6.9.1.1.1 Assign ISDN D Channel to Channel Group (ISDN)................................... 53
6.9.1.1.2 Assign ISDN B-Channels to the ISDN Group............................................ 54
6.9.1.2 Channel Group (SIP)....................................................................................... 55
6.9.1.2.1 Channel Group with SIP Gateway.............................................................. 56
6.9.2. Routing.................................................................................................................... 57
6.9.2.1 Route Entry...................................................................................................... 57
7. Configure Avaya Aura Session Manager ............................................................................. 60
7.1. Log in to Avaya Aura® Session Manager.................................................................... 60
7.2. Administer SIP Domain................................................................................................ 61
7.3. Administer Locations.................................................................................................... 61
7.4. Administer Adaptations................................................................................................ 62
7.5. Administer SIP Entities................................................................................................. 63
7.6. Administer SIP Entity Links......................................................................................... 66
7.7. Administer Time Ranges .............................................................................................. 68
7.8. Administer Routing Policy ........................................................................................... 68
7.9. Administer Dial Pattern ................................................................................................ 72
7.10. Confirm Entity Link Status........................................................................................... 74
8. Configure Avaya Meeting Exchange Enterprise Application .............................................. 76
8.1. Configure System Manager for Meeting Exchange...................................................... 76
8.2. Configure SIP Listener ................................................................................................. 80
8.3. Configure Dial Out ....................................................................................................... 81
8.4. Configure DNIS Mappings........................................................................................... 83
8.5. Creating a Sign In User for Bridge Talk....................................................................... 85
8.6. Bridge Talk Configuration............................................................................................ 87
8.6.1. Create a SCAN Conference .................................................................................... 87
9. Verification Steps.................................................................................................................. 90
9.1. Verify Call Flows.......................................................................................................... 90

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
4 of 103
DLG1010MXSM62CS
9.2. Verification Avaya Communication Server 1000E...................................................... 91
9.2.1. Troubleshooting Call tracing .................................................................................. 92
9.3. Verify Dialogic IMG 1010............................................................................................ 93
9.3.1. Verify ISDN Trunk Status ...................................................................................... 93
9.3.2. Verify ISDN D-Channel Status .............................................................................. 94
9.4. SIP trunk Status............................................................................................................. 94
9.5. Call Tracing in IMG 10101........................................................................................... 95
9.6. Verify Session Manager................................................................................................ 97
10. Conclusion ........................................................................................................................ 98
11. Additional References....................................................................................................... 99
Appendix A –Meeting Exchange Configuration via SSH ................................................ 100

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
5 of 103
DLG1010MXSM62CS
1. Introduction
There are installation instances of Avaya Communication Server 1000E which are not SIP or IP
capable, or where the software release may not have been SIP interoperability tested, but the
customer wishes to deploy Avaya Meeting Exchange Enterprise Edition. In this case an effective
solution is to front end the Avaya Communication Server 1000E with an E1-PSTN to SIP
gateway, which signals via SIP trunks to Avaya Aura ® Session Manager R6.2, which in turn
has a SIP trunk to Avaya ®Meeting Exchange Enterprise Edition. This configuration supports
basic and advanced conference features.
2. Interoperability Testing
The solution in this document uses the following configuration:
Avaya® Communication Server 1000E (CS1K) is configured with an E1/PSTN link to Dialogic
IMG 1010 Media Gateway (IMG_1010). In turn, the Dialogic IMG 1010 Media Gateway is
configured with a SIP trunk to Avaya Aura ® Session Manager R6.2. Session Manager is also
configured with a SIP trunk to Avaya® Meeting Exchange Enterprise Edition R6.2.
The incoming call from the Avaya ® Communication Server 1000E is presented as E1 to the
Dialogic IMG 1010 Media Gateway. The E1 signal is converted to SIP by the IMG_1010 and
signaled to the Avaya Aura® Session Manager R6.2 using TCP, with DTMF being transmitted
within the RTP stream using RFC2833 compliant messages. Avaya Aura® Session Manager is
configured with SIP Entities for Dialogic IMG 1010 Media Gateway and Avaya ® Meeting
Exchange. Entity links have also been created between Session Manager and Dialogic IMG 1010
Media Gateway and Session Manager and Meeting Exchange dictating the protocol and ports to
be used, i.e. TCP/5060.Additionally, a routing plan and dial pattern has been created on Session
Manager to route calls to Meeting Exchange when the relevant conference number has been
dialed.
Additionally a SIP trunk and relevant digit patterns were also added to Avaya Aura ®
Communication Manager R6.2 for the purposes of managing the Avaya H.323 endpoint that
comprised part of the test phones.However testing did not focus on this side of the Avaya PBX
environment.
The Avaya Meeting Exchange Enterprise Edition R 6.2 is a new release of software, and can
now be managed via the Avaya Aura® System Manager as a Managed Element. The initial
configuration of Meeting Exchange as a Managed Element is not covered in this document. For
more details, see Section 11 Reference [6].
Note: A third party PBX was connected to the solution to represent an ―external PSTN‖ caller
dialing to the Meeting Exchange conference service via Avaya Communication Server 1000E.
The configuration of the E1 trunk between Avaya Communication Server and the third party
PBX is not covered in this document.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
6 of 103
DLG1010MXSM62CS
2.1. Test Description and Coverage
Testing focused on the following:
SCAN/FLEX/DIRECT Conference connectivity / two way audio
Use of CODECS –G711MU /A and G729
DTMF –In-Band / Out of Band
Blast Dial - a predefined list of attendees that can rung by use of a feature code by the
moderator
Moderator Features / Conferee features
Moderator initiated Out Dial
Conference Recording / Playback
Operator Audio Path
Operator activities i.e. Help / Blast Dial / Conference Room transfers
2.2. Test Results and Observations
Testing was generally successful; however at the time of testing, the release of software for
Meeting Exchange was a pre GA (General Availability) release. As such, some problems were
experienced during testing which have been reported. The following issues were discovered
during the testing phase:
2.2.1. G729 Codec Issue
Under tests codecs G711MU and G711A functioned correctly. However when the codec was
defined as G729 only, the call initially failed. On observation, the SIP Invite to MX contained
G729 in the SDP. The MX responded with SIP 488 Not Acceptable here and traces from MX
indicated ―No matching media found‖. On further investigation, it was discovered that
insufficient capacity had been made available to the system under test which was configured
with 8000 revenue ports. Alteration of the processTable.cfg was needed to increase the softms
(soft media server) processes from default 8 softms processes to a required 12 softms processes.
Under recommendation from the support team, this was increased to 12 by configuring the
processTable.cfg file manually, incrementing the ipcKeyNumber and ProcessArgs value by one
each time.
The screen shot on the next page shows the four additional media Server entries to the
processTable.cfg file within Meeting Exchange to increase the number of ports from 8 to 12 to
accommodate the use of the G729 codec.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
7 of 103
DLG1010MXSM62CS
[sroot@mx62 config]# cat processTable.cfg
# processes file, enumerates the number of processes in the network.
# will have the name of the process Key ID and the IP address
proccessName ipcKeyNumber autoStart ProcessExe ipAddress
route ProcessArgs
initipcb 110 0 noexecute 0.0.0.0
bridget700 100 0 noexecute 0.0.0.0
dspEvents/msDispatcher,netEvents/sipAgent
commsProcess 111 1 /usr/dcb/bin/serverComms 0.0.0.0
sipAgent 101 1 /usr/dcb/bin/sipagent 0.0.0.0
dspEvents/msDispatcher,appEvents/bridget700
msDispatcher 102 1 /usr/dcb/bin/msdispatcher 0.0.0.0
netEvents/sipAgent,appEvents/bridget700,dspEvents/mediaServer
mediaServer 141 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 1
mediaServer 142 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 2
mediaServer 143 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 3
mediaServer 144 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 4
mediaServer 145 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 5
mediaServer 146 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 6
mediaServer 147 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 7
mediaServer 148 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 8
mediaServer 149 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 9
mediaServer 150 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 10
mediaServer 151 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 11
mediaServer 152 1 /usr/dcb/bin/softms 0.0.0.0
appEvents/msDispatcher,netEvents/msDispatcher 12
notifyService 113 1 noexecute 127.0.0.1:10235
snmpAgent 120 1 noexecute 0.0.0.0
logServer 191 1 /usr/dcb/bin/logServer 0.0.0.0 none
/usr/ipcb/config/logServerConfig.xml
#mxmonitor 200 1 noexecute <aps1-ip>
appEvents/msDispatcher,netEvents/msDispatcher aps1
#mxmonitor 201 1 noexecute <aps2-ip>
appEvents/msDispatcher,netEvents/msDispatcher aps2
#mxmonitor 202 1 noexecute <aps3-ip>
appEvents/msDispatcher,netEvents/msDispatcher aps3
#mxmonitor 203 1 /usr/dcb/bin/mxmonitor <stdby-ip>
appEvents/msDispatcher,netEvents/msDispatcher standby
2.2.2. UBlast (Blast Dial) - Manual & Auto
On attempting to test uBlast (Blast Dial-Automatic and manual), the feature was found not be
working. On further investigation, it was recommended that when entering the participants into a
blast dial list, the Name field should not be populated with an extension number. Instead use
Alpha characters.
2.2.3. Bridge Talk Reports
Bridge Talk is the software management tool used for creating conferences. On using the Bridge
Talk tool ―Reports‖ to view the conference details for the long period, it was not possible to open
the reports for the previous day. A message would be received that the ―pages were blank‖, else

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
8 of 103
DLG1010MXSM62CS
the Bridge Talk would crash completely. Only reports for ―today‖ would load to the report
viewer. The Meeting Exchange was checked and confirmed that the files used for reporting
(*.COD and *.CODR) do exist and have a reasonable size.
This issue was resolved by applying patch mx-bridge-patch-6.2.0.2.1-1.
2.2.4. Network Outage / Recovery
When the NIC was pulled the endpoints were disconnected. On reapplying the NIC to bring MX
on line, there was no attempt to reconnect the callers. Observations in Bridge Talk showed a
conference with 5 users, however these were not dialable from an Operator in Bridge Talk.
However a moderator or conferee could recall into the Conference and be joined to the original
conference. The phantom endpoints in the conference had to be disconnected via Bridge Talk
before the conference room was cleared completely. The Avaya SIP and H.323 endpoints were
rejoined to the conference.
2.2.5. Line Transfer / Conference Transfer
It is possible via Bridge Talk to move participants by selecting their line number and performing
a transfer to a different conference room. It is also possible to move the participants in one
conference room to another. However, this is intermittently not working. On the occasion the
transfer does not complete a message is displayed in Bridge Talk “Problems with the statusTCP
socket –you are not receiving messages. Your display may not be accurate”. However the
Operator can perform a transfer from one conference room to another of a participant. This issue
was resolved by applying patch mx-bridge-patch-6.2.0.2.1-1.
3. Reference Configuration
The configuration in Figure 1 was used to compliance test Avaya Communication Server 1000E
(CS1000E) interoperability with Avaya Meeting Exchange Enterprise Editionvia E1/PSTN and
SIP trunks using Dialogic IMG 1010 Media Gateway with a SIP trunk to Session Manager R6.2.
E1 trunk is used to connect Avaya Communication Server 1000E to the Dialogic IMG 1010
Media Gateway. The gateway’s role is to translate E1 messages to SIP and vice versa between
Avaya Aura Session Manager R6.2. In turn, a SIP trunk between Avaya Aura Session Manager
and Avaya Meeting Exchange will deliver calls to conferencing numbers to Meeting Exchange.
Avaya Communication Server 1000E supports an Avaya 1140 IP Phone (Unistim) , Avaya 1220
IP Phone (Unistim), and an Avaya M3904 Digital Phone.
The Avaya Aura environment also consisted of System Manager which was used for
management programming of the Session Manager and Meeting Exchange. Session Manager
was used for management of SIP endpoint used in testing, but is not focused on as part of this
document. The Communication Manager was part of the test environment for its support of the
H323 endpoint used in testing, as well as processing calls from Session Manager but is not
focused on as part of this document. An additional third-party PBX was connected to the
CS1000E with an E1 trunk to simulate an external caller. The configuration of this is outside the
scope of this document.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
9 of 103
DLG1010MXSM62CS
Avaya Meeting Exchange Enterprise Edition has been installed and configured on Avaya S8800
Media Server.
Figure 1 Network configuration of Avaya® Communication Server 1000E, Dialogic IMG 1010 Media
Gateway, with Avaya Aura® Session Manager, Avaya Aura® Communications Server R6.2 and Avaya Aura
® System Manager R6.2

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
10 of 103
DLG1010MXSM62CS
4. Equipment and Software Validated
The following equipment and software were used for the sample configuration provided:
Equipment
Software
Avaya S8800 Media Server
Avaya Aura® Meeting Exchange Enterprise
Edition R 6.2
Version 6.2.0.0.24
mx-bridge-patch-6.2.0.2.1-1
mx-bridge-patch-6.2.0.0.27-1
mx-bridge-patch-6.2.0.0.25-1
Avaya Bridge Talk
Version 6.2.0.0.7
Avaya S8800 Media Server
Avaya Aura® Communication Manager R6.2
Software Level:02.0.823.0-19926
Avaya G650 Media Gateway
TN2312BP HW15 FW054
TN799DP HW16 FW040
TN2602AP HW08 FW063
Avaya S8800 Media Server
Avaya Aura ® Session Manager R6.2
Release 6.2.2.0.623006 (Service Pack 3)
Linux : 5.6 5.6.0.3
Avaya S8800 Media Server
Avaya Aura® System Manager R6.2
Release: smgr 6.2.12.0 (Service Pack 3)
Build 6.2.0.0.15669 –6.2.12.307
VSP: smgr 6.2.1.0.9
Avaya Handset 9621 (SIP)
SIP –S96x1_SALBR6_0_3_v470.tar
Avaya Handset 9650 (H323)
H.323 - ha96xxua3_1_04_S.bin
Avaya Communication Manager
1000E
Release 7.5 Q Version 4121
Avaya Handset 1140E (IP) Phone
UniStim 0625C8A
Avaya Handset 1220 (IP) Phone
UniStim 062AC8A
Avaya Handset M3904 (Digital)
Digital Endpoint
Dialogic
Dialogic Gate Control Element
Management System (GCEMS) Server
IMG 1010 Media Gateway
RedHat Enterprise Linux Server Release 5.1
(Tikanga)
Dialogic ClientView Version 10.5.3.242
Software Version 10.5.3.360

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
11 of 103
DLG1010MXSM62CS
4.1. Configuration Tools
Avaya Communication Server 1000E (CS1K) was configured via UCM Element Manager –
which can be accessed via Avaya Aura System Manager if using Single Sign On. Alternatively,
the Element Manager GUI can be accessed directly via the ELAN IP Address. Additional
configuration was carried out using PuTTY to access the relevant ―Overlays‖ via the CLI
console screen.
Dialogic IMG 1010 Media Gateway was configured via IMG Client View software. This was
accessed by using VNC Viewer to connect to the GCEMS server and running the IMG Client
software installed on the Linux server. For later versions, a Windows based IMG ClientView
software package is available.
Avaya Aura Session Manager and Avaya Meeting Exchange were configured via Avaya Aura
System Manager. Configuration of Meeting Exchange is also possible via a PuTTY session.
Avaya Bridge Talk was used to configure the conference settings for SCAN, FLEX and
DIRECT.
This document has assumed the following:
All relevant IP equipment has been installed and licensed and introduced to the IP LAN
Endpoints on CS1000E have been configured and are capable of dialing one another.
Endpoints on the Avaya Aura Communication Manager and Avaya Aura Session
Manager have been configured and can dial each other.
Users have a basic familiarity with PuTTY and the web GUI interfaces for both Avaya
Communication Server 1000E (CS1000E), Avaya Aura System Manager and Avaya
Aura Meeting Exchange.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
12 of 103
DLG1010MXSM62CS
5. Configure Avaya Communication Server
This section focuses on configuring the E1 trunks on Avaya Communication Server 1000E to
connect with Dialogic IMG 1010 Media Gateway. The NTBK50AAE5 E1 2Mbps ISDN trunk
card is installed in slot 3 of the Avaya MG1000 Media gateway. These Application Notes
assume that the telephones are installed and configured and the ISDN PRI is not being
configured for the first time, so error detection thresholds and clock synchronization control are
assumed to be in place. If not, refer to the ISDN Primary Rate Interface Document in Section 11
Reference [4] for detailed descriptions. Furthermore these Applications Notes used the Co-
ordinated Dial Plan (CDP) feature to route calls from the Avaya Communication Server 1000E
over the E1 to Dialogic IMG 1010 Media Gateway. The CDP feature is assumed to be already
enabled on Avaya Communication Server 1000E, and therefore will not be described in detail.
The procedures below describe the details of configuring Avaya Communication Server 1000E:
Log in to the Unified Communications Management GUI
Launch Element Manager
Verify Equipped Feature Packages
Administer E1 card
Administer D-Channel
Administer Routes and Trunks
Administer Route List Block
Administer Distant Steering Code
Enable E1 card
Enable D-channel automatic establishment.
5.1. Login to Unified Communication Management GUI.
In these application notes, access was made via Avaya Aura System Manager using Single Sign
On. Open an instance of a web browser and connect to the web GUI for Avaya Aura System
Manager and login in with appropriate credentials.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
13 of 103
DLG1010MXSM62CS
Once connected to System Manager, select UCM Services from the System Manager Home
screen in the Services section.
Once the Elements screen has opened, select the Element Manager system to be opened.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
14 of 103
DLG1010MXSM62CS
If prompted to, accept the web security certificate.
A successful connection will show the System Overview Screen. Menu choices on the left are
expandable where indicated with a +symbol. Once selected, the details will be displayed on the
right hand side.
5.2. Verify Equipped Feature Packages
To verify the features available within CS1000E which are necessary for this configuration select
Tools Logs and Reports Equipped Feature Packages. Using the column labeled
Package Number on the right, scroll down and ensure the following packages are equipped.
19 Digit Display (DDSP)
59 Coordinated Dialing Plan (CDP)
95 Calling Party Name Display (CPND)
145 Integrated Services Digital Network (ISDN)
146 Primary Rate Access (CO) (PRA)
154 2.0 Mb/s Primary Rate Interface (PRI2)
184 Overlap Signaling (M1 to M1 and M1 to 1TR6 CO) (OVLP)
202 International Primary Rate Access (CO) (IPRA)
263 QSIG Interface (QSIG)
305 QSIG Generic Functional Protocol (QSIGGF)
316 QSIG Supplementary Service (QSIG-SS)

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
15 of 103
DLG1010MXSM62CS
5.3. Administer E1 Card
Select System Core Equipment Loops. To add a new Loop, click on the drop down
arrow, select 2.0 Mb/s Primary Rate Interface and click on the Add button.
In the new screen that opens enter the following:
PRI Loop Number Enter the loop number i.e. 043 to represent where the
Media Gateway Card will be inserted in the relevant Shelf
and Slot. Alternatively enter a number between 0-255.
Media Gateway Card Enter the Shelf-Cabinet-Slot where the NTBK50AAE5 E1
2Mbps ISDN trunk card has been inserted into the Avaya
MG1000 Media Gateway. In this example the trunk card
has been inserted in slot 3.
Click Save to save the changes.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
16 of 103
DLG1010MXSM62CS
At this stage, the screen may look similar to the one below, however the status of the loop may
show as disabled. At this stage, the status of disabled is normal as further configuration is
required before the trunk card can be enabled for service.
5.4. Administer D-Channel
The next step is to administer a D-Channel. Navigate to Routes and Trunks D-Channels.
From the drop down for Choose a D-Channel Number selecting an appropriate number from
the list and set type to DCH. In the example below, the D-Channel number chosen matches the
loop number created in Step 5.3 for programming purposes. Click on the Add button to begin the
creation of the D-Channel.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
17 of 103
DLG1010MXSM62CS
The D-Channel 43 Property screen is displayed. Enter the following values for the specified
fields and leave other fields at default.
D channel Card Type Set to MSDL
Media Gateway Card Set to 004 0 03
Port Number Set to 1
Designator Set to a desired name for the D-Channel
User Set to Primary Rate Interface
Interface Type for D-Channel Set to Euro ISDN Interface (EURO)
Country Set to ETS 300=102 basic protocol (ETSI)
D channel PRI loop Set to 43
Scroll down the screen and expand Basic Options (BSCOPT)
Configuring D-channel Basic Options
Configure the following settings:
PINX customer number Set to 0
Output request Buffers Set to 128
D-channel transmission rate Set to 64kb/s clear (64KC)
Channel Negotiation option Set to No Alternative acceptable, exclusive(1)
Then click on Edit button to configure Remote Capabilities

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
18 of 103
DLG1010MXSM62CS
Configure Remote Capabilities:
Scroll down the screen and check the following capabilities:
Connected line identification presentation (COLP)
Diversion info. Sent, rerouting requests processed (DV3I)
Message waiting indication using integer values (QMWI)
Once these fields have been checked, click on Return –Remote Capabilities button.
Please note: screen show has been condensed.
Once the changes have been made, scroll down the screen and select Submit button.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
19 of 103
DLG1010MXSM62CS
The D-channel should then be displayed.
5.5. Administer Routes and Trunks
The next step is to create a route and trunks to route calls to Dialogic IMG 1010 Media Gateway.
From the menu on the left select Routes and Trunks Routes and Trunks. Next to the
applicable Customer click on the Add Route button.
The Customer 0, New Route Property Configuration screen is displayed. Enter the following
values and leave the remaining fields at default.

BD; Reviewed:
SPOC 02/26/2013
Solution & Interoperability Test Lab Application Notes
©2013 Avaya Inc. All Rights Reserved.
20 of 103
DLG1010MXSM62CS
Route Number (ROUT) Set to 43
Designator field for Trunk (DES) Set to a descriptive name
Trunk Type (TKTP) Set to TIE
Incoming & Outgoing Trunk (ICOG) Set to IAO
Access Code for trunk route (ACOD) Set to 143
Digital Trunk Route (DTRK) Enable
Digital Trunk Type (DGTP) Set to PRI2
Integrated services digital network option (ISDN) Enable
Mode of operation (MODE) Set to ISDN/PRA route,
DTRK must be Yes (PRA)
Interface type for Route (IFC) Set to EuroISDN Interface
(EURO)
Private Network Identifier (PNI) Set to 00001
Call Type for outgoing direct dialed TIE route (CTYP) Set to Coordinated Dial
Plan (CDP)
Calling Number Dial Plan (CNDP) Set to Unknown (UKWN)