This is the first edition of the Ericsson MD110 CAS EL7 TCP/IP VM Integration Technical Note.
Information in this document applies to CallXpress software Version 5.31 or later, or CallXpress Enterprise
software Version 5.31 or later.
This document was produced by the CTI Software Group Technical Communications Department.
AVT Corporation reserves the right to revise this publication and to make changes from time to time in the
content hereof without obligation of AVT Corporation to notify any person of such revisions or changes.
AVT Corporation exercises care in researching other manufacturers’ specifications but disclaims all
responsibility for their accuracy. All specifications shown here are subject to change without notice.
Trademarks
AVT, the AVT logo, CallServer, CallXpress, and PhoneXpress are registered trademarks of
AVT Corporation.
All other products, brand names, or companies mentioned in this document may be trademarks or registered
trademarks of their respective companies.
AVT Corporation
CTI Software Group
P.O. Box 97025
Kirkland, Washington 98083
(425) 820-6000
http://www.avtc.com
This Integration Technical Note (ITN) is written for dealers who are experienced
with CallXpress
®
and who are familiar with CallXpress procedures and terminology.
It also assumes that you are familiar with the features and programming of the
Ericsson MD110 telephone system.
This document describes how to integrate CallXpress with an Ericsson MD110
telephone system, using an E1 CAS EL7 interface in conjunction with the MD110
Voice Mail TCP/IP integration. This integration is an outband integration. The E1
CAS EL7 interface is a digital 2.048Mb 32-channel interface that can provide up to
30 CAS (channel associated signaling) voice mail ports to CallXpress per E1 link.
The MD110 E1 CAS connection is established at the CallXpress telephony server by
means of an Aculabäplc High Capacity Digital Access card. The Aculab card is the
E1 interface between the MD110 and the Dialogic card(s) in the CallXpress
telephony server. DTMF signaling and voice communications are performed over
the established E1 link between CallXpress and the MD110. The MD110 Voice
Mail interface is an Ethernet network connection that uses the TCP/IP protocol to
communicate between the MD110 and CallXpress. Calling and called party
information is sent to CallXpress via TCP/IP over the network connection at the
same time that a call is sent to a CAS channel. The data is matched with the ringing
channel and CallXpress answers with the appropriate dialog. Message Waiting
Indicator (MWI) operation is also performed via TCP/IP over the
network connection.
Refer to the Ericsson Extra Facility Voice Mail, VM description and the
Interworking Description, CAS extension, EL7 Interface to Voice Mail system for
complete details.
Use this document in conjunction with CallXpress installation guides, administration
guides and online help.
Known limitations or conditions within the telephone system and CallXpress that
affect the integration performance are listed here. General recommendations are
provided when ways to avoid these limitations exist.
•The MD110 voice mail port number of each CAS EL7 extension must be assigned
correctly to each integrated CallXpress port. The integration will not function if
these entries are incorrect. The voice mail port numbers and format (POFMT)
are programmable parameters and are defined during the initiation of the voice
mail port of the MD110.
•Program the instrument category (ICAT) of the CAS EL7 extensions that will
serve CallXpress for enhanced global tones and assign them as voice mail ports.
•The MD110 requires a static TCP/IP address. It cannot be assigned a lease
through a DHCP server. If the customer site is using a DHCP server, a
reservation must be made for the MD110.
•Set the traffic matrix (TCMAP) and TRAF parameter of the extension category
to restrict voice mail ports from calling other voice mail ports. This allows a Ttype supervised transfer to take place for call screening applications without
having to remove diversion programming from the subscriber telephone.
•The use of traffic restricted voice mail ports is not compatible with blind
transfers. We recommend that you use the monitor transfer type unless the
application requires a t-type supervised transfer..
•If the malicious call trace feature of the MD110 is enabled on the voice mail
ports, no disconnect packet will be sent to CallXpress from the NIU port of the
MD110.
•When using reason code diversions from subscriber telephones, diverted calls
will always go to the common diversion position. If CallXpress is chosen as the
common diversion position (CDCOI), calls will always be diverted there, even if
individual diversions (CDINI) have been programmed to divert calls elsewhere.
•Station numbers cannot have a 0 as the leading digit. Non-numeric
DTMF tones cannot be used as any character in a station number. The
maximum length of a station number is six digits.
•Aculab does not provide BNC connectors on their PCI type boards. These boards
are supplied with RJ45 connectors only.
•Mixing like kinds of ISA and PCI cards in the same telephony server platform
requires a separate system interrupt (IRQ) for each type board used. This practice
is not recommended or supported.
•Mixing unlike kinds of ISA and PCI type Aculab or Dialogic boards in the same
telephony server platform require an SCbus to H.100 bus (CTbus) cable adapter.
ISA boards have SCbus connectors and use SCbus ribbon cables for connection;
PCI boards have CTbus connectors and use CTbus or H.100 bus ribbon cables
for connection. SCbus signaling is done over the H.100/CTbus interface.
Review the following information before performing any of the procedures in this
document. To successfully install this integration, you must meet the installation
requirements for both the telephone system and CallXpress.
Telephone System Requirements
These are the software and hardware requirements for the MD110:
•Ericsson MD110 PABX with system software Version BC10 or later. The
following Version BC10 patches are required for TCP/IP integration: 87804,
87997, 87998, 88383 and 88407. The following Version BC10 patches are
required for ANI/CLI information to the GICI port: 86363, 86376, 86377, 86444
and 88445.
•NIU port to provide the TCP/IP network connection. The TCP/IP address of this
network interface port must be a static network address.
•TSR 902 0240/XXXX cable for the network connection between the NIU board
and the Ethernet network.
•One TLU76/3 E1 CAS card will provide up to 30 CAS EL7 voice ports
•TSR 902 0267/XXXX cable for the RJ45 high impedance connection between
the TLU76/3 card and the E1 Aculab card, or a TSR 901 0301/XXXX cable for
the BNC low impedance connection between the TLU76/3 board on the MD110
and the E1 Aculab card.
•Properly configured Windows NT Server 4.0 telephony server platform with an
Ethernet network adapter card
•CallXpress software Version 5.31 or later. Consult the AVT BBS, OTIS, or the
AVT web site for current service packs and software levels. (See “References”
earlier in this document)
•Ericsson MD110 E1 CAS TCP/IP VM Switch Integration Module (SIM 34)
enabled on the AVT software key diskette
•Aculab Rev.5 ISA single port cards will support 30 CallXpress ports
•Aculab Rev.5 PCI single port cards will support 30 CallXpress ports
•Aculab Rev.5 PCI dual port cards will support 60 CallXpress ports
•One digital Dialogic port for each CallXpress voice port to be integrated. Use
Follow the recommendations and programming examples in this section to program
the MD110 for integration with CallXpress. Programming examples show
commands and parameters of Version BC10 that are necessary for integration, but
they do not represent PBX programming in its entirety.
The installing technician should be familiar with programming the telephone system.
For detailed programming information on this software version or other MD110
software versions, refer to the appropriate ASB Basic Exchange and Extra Facility
documentation and the Ericsson MD110 OEM country-specific documentation.
Initiating the Number Series for the CAS Extensions
Initiate extension numbers in Number Analysis for the CallXpress extensions. Use
EX as the NUMTYP. Choose directory numbers that are appropriate for your
numbering plan.
For example:
NANSI:NUMSE=4001&&4030,NUMTYP=EX;
Verify your work with the command: NADAP;
Programming the Category for CAS Extensions
Set the Extension Category code for the CallXpress ports and configure the traffic
matrix to restrict one voice mail port from calling another voice mail port. Use a
separate category for the CallXpress ports.
1. Set the CAT for CallXpress ports with the TRAF parameter that uses the defined
TCMAP table.
2. Configure the Traffic Matrix (TCMAP) to restrict voice mail ports from
connecting to other voice mail ports. Allow all other extensions to connect to
voice mail ports and allow voice mail ports to connect to all other extensions.
Table 3 is an example of the restricted traffic matrix.
1. Initiate the CAS EL7 extensions, assign the equipment, the category, and the
instrument category. ICAT=0086 assigns enhanced global tones for call progress
and enables the CAS ports as voice mail ports.
1. Initiate a hunt group and assign the CallXpress extensions to the group. Specify
the type as LONGEST FREE HUNTING and set Queuing to 10. Define the SEL
parameter to allow overflow diversion when all ports are busy, if desired.
Verify your work with the command: GHDAP:GRP=4000;
2. Assign the CallXpress Directory numbers to the hunt group.
For example:
GHGMI:GRP=4000,DIR=4001&&4030;
Verify your work with the command: GHDAP:GRP=4000;
3. You may want to program the CallXpress ports to divert when they are
unavailable. For instance, the following programming example would divert calls
intended for CallXpress, to the attendant, if all ports were busy or RNA.
For example:
CDINI:GRP=4000,DIV=00; (00=operator)
Verify your work with the command: CDIDP:GRP=4000;
3. Initiate the I/O Network Connection. Assign the USER as GICI-1, the RPORT as
2555, and the TCP/IP address that was pre-determined by the
network system administrator.
Initiate the Information Computer Function for the Voice Mail Port. Name the I/O
Device “CallXpress” and specify the USER as GICI-1. Set the directory format
length (DFMT) to match the directory number length of the extensions, set the
update function (UPDFCN) to YES, and set the FILLER to 32 (space).
Initiate the Message Waiting data for the voice mail port. Define the system ID
(SID) of the PBX, the DTXT, and group number (DIG) to be called when
subscribers press the message-waiting button (MWC) to retrieve messages.
For example:
ICMWC:SID=01,DTXT=4000,DIG=4000,KFCN=MWC;
Verify With ICMWP:SID=01;
Initiating the Voice Mail Function
Initiate the Voice Mail Function for the NIU port. Set the port format (POFMT) to 3.
Set the Voice Mail Functionality (VMF) to EXTN3 if ANI/CLI services will be used.
If ANI/CLI services are not required, set VMF to EXTN2.
For example:
VMFUI:IFCIND=1,VMF=EXTN3,POFMT=3;
Verify your work with the command: VMFUP;
Initiate the Voice Mail Port and identify the starting PORT number. Add the
CallXpress directory numbers and the hunt group number to the Voice Mail Port.
Programming Message Waiting and Call Diversion for
Subscriber Telephones
Digital subscriber telephones can have an MWI key assigned in addition to the
“Message Waiting” display on their LCD telephones. Subscribers can press the lit
MWI key to retrieve messages from CallXpress. Use the Key System Function Key
Change command to assign an MWI key appearance on each subscriber telephone.
For example:
KSFKC:DIR=2001&&2299,KEY=2,FCN=MEW;
Verify your work with the command: KSFKP:DIR=2001&&2299;
Analog subscriber telephones can receive a pling ring for MWI or a special dial
tone. Use the ASPAC command to set either pling ring or special dial tone.
For example:
ASPAC:PARNUM=88,PARVAL=1;
(PARVAL=1 sets special dial tone and PARVAL=0 sets pling ring.)
NOTE When PARVAL=0 the “Message Waiting” text message on digital set
displays is not available.
Program the time interval between pling rings when pling is used for message
notification. The following example sets the pling interval to fifteen minutes.
Assign the CallXpress hunt group as the diversion point for subscribers. Use the
CDCOI command to create a common diversion to voice mail for subscribers or use
the CDINI command to create individual diversions.
For example:
CDINI: DIR=2001&&2299, DIV=4000;
Verify your work with the command: CDIDP:DIR=2001&&2299;
If Call Diversion is not programmed, subscribers must use the FOLLOW ME feature
to divert calls to CallXpress.
NOTE If CallXpress is chosen as the common diversion position (CDCOI), then
ICS calls will always be diverted to this position, even if CDINI has been
programmed to divert calls elsewhere. In other words, reason code diversion will
always go to the common diversion position. Refer to the VIM online book for more
information on programming reason code diversions.
Completing the MD110 Programming
Verify your work and that the programming is correct by using the print command
related to each executable command.
Make sure that the following program units have been installed in the MD110 in
accordance with the Line Interface Module (LIM) disposition table, as follows:
The Integration Configuration field values are shown in Table 7 for your
information. Some of the values are preset for the Ericsson MD110 E1 CAS TCP/IP
VM integration when you choose the correct telephone system. The field values left
unspecified require modification to suit the specific site and application. Consult the
PBX installation manual or the third-party documentation for specifics on the
network port configuration. Consult the PBX installation manual for information on
the network port configuration.
Table 7. Integration configuration parameters for the MD110 E1 CAS TCP/IP VM
integration
FieldComments
PBX switch codeEnter the PABX name code.
The default is 1 (MD110).
PBX IP address or Computer
name
TCP/IP port number to useEnter the RPORT number defined on the
Parser filename
MWI initialization mode
Enter the TCP/IP address or name
of the PBX.
MD110. The default is 2555.
MDCASTCP is the default. Do not
change this filename unless advised by
AVT technical staff.
Enter a parameter to determine how
CallXpress initializes all message waiting
indicators when the system is started or
restarted.
3 causes CallXpress to synchronize all
MWIs by issuing an MWI set or clear
command for each subscriber mailbox
that the Set MWI box checked to Yes and
the telephone Primary Type set to Real.
2 causes CallXpress to clear MWIs only
on startup.
Table 7 (continued). Integration configuration parameters for the
MD110 E1 CAS TCP/IP VM integration
FieldComments
Pause between MWIEnter the number of milliseconds to wait
between MWI packets. Default is 500.
Voice message system number
Enter the VMS number. Default is 01.
This number is the system ID (SID)
number of the voice mail system of
the MD110.
T-extension lengthEnter the length of the MD110 directory
(TLEN) number. Default is 4.
D-extension lengthEnter the length of the MD110 directory
(DLEN) number. Default is 4.
V-extension lengthEnter the length of the MD110 voice
message port number (VLEN). Default is
3. The number of digits here matches the
number of digits in the parameter
POFMT of the VMFUI command. (See
“Programming the Telephone System”
earlier in this document.)
Optional MWI filler digitEnter the filler digit to be used for short
DNs when setting/clearing MWIs on
mixed DN systems. The default is a blank
space.