AudioCodes Gateway to

Unified Messaging

Bill Devlin November 2005

© 2005 AudioCodes Ltd.

All rights reserved.
AudioCodes portfolio

Variety of Applications Enterprise 25,000/quarter

Mature, Shipping since 2002

1000/quarter

Technology Networking

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Supported Voice Mail Architecture

E1
Exchange UM

SMDI

• VoIP Gateway provides mediation between PBX and SIP

based Unified Messaging application
• Integration modes offered:
– In band integration - Analog, E1 or T1
– Serial (Simplified Message Desk Interface -SMDI) – Analog, E1 or T1
– Qsig* E1 or T1
* -AudioCodes'
Roadmap 5.0 June 2006 Information covered under Non-Disclosure Agreement
Confidential
Ordering Information

MediaPack™ Ordering Information

Analog 4 ports MP-104/FXO/AC/SIP-0
Analog 8 ports MP-108/FXO/AC/SIP-0
In the $100’s

Mediant™ Ordering Information

1 E1/T1 Trunks Mediant2000/1Spans/SIP/RS232
2 E1/T1 Trunks Mediant2000/2Spans/SIP/RS232
4 E1/T1 Trunks Mediant2000/4Spans/SIP/RS232
In the $1000’s
8 E1/T1 Trunks* Mediant2000/8Spans/SIP
16 E1/T1 Trunks* Mediant2000/16Spans/SIP

* -AudioCodes'
Don’t includeConfidential
serial connection
Information covered under Non-Disclosure Agreement
Fundamentals
• Highest Quality Voice over Packet (as noted by ETSI, ETSI 3rd Speech Quality Test
Event, Anonymized Test Report – “Gateways”. )
• Packet processing:
– Variety of Vocoders(over 20 currently supported): G.711, G.723, G.726, G.729, etc.
– Adaptive Jitter buffer (up to 300ms)
– RTP redundancy
– Packet interpolation
– Packet Loss Concealment
• Voice Processing (Universal ports - Not affecting GW density):
– DTMF (Inband, RFC2833, Signaling, Mute)
– Tones detection and generation, Digit Manipulation
– Modem/Fax detection
• Echo Cancellation
• Line Echo Cancellation ,G.168-2002 compliant, with tail of 30/64/128 msec
• Full Duplex Acoustic Echo Cancellation
• CNG - Comfort Noise Generation
• Silence Suppression & Comfort Noise Generation
• G.711 ITU-T G.711 Appendix 2
• G.723.1
• G.729a
• Voice Activity Detection
• Automatic Gain Control
AudioCodes' Confidential Information covered under Non-Disclosure Agreement
Fundamentals

• Telephony functions
– Supplementary Services:
• Hold
• Transfer
• Waiting
• Forward
• Privacy
• Pickup
– Call Progress Tones Generation & Detection
– Caller ID, Caller ID Restriction
– DID Variants
– Distinctive Call Waiting
– Integral Announcements
– Answering Machine Detection
– Answer & Energy Detection
– Channel Select Modes
• Provisioning
– BootP – For Remote Configuration and Firmware Bootup
– FTP/TFTP/HTTP – For Remote Configuration and Firmware Update
– DHCP – For Central Provisioning of IP Configuration
– .INI Files
– CAS and Tone files

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Voice Mail integration – Supported functionality

• Audio and Fax Message

– Redirect Number (Individual’s Greeting)
– Reason for Transfer (Specialized Greeting)
– Caller ID (Pending on PBX/PSTN support)
– Message Retrieval
– Message Waiting Indicator
• Auto-attendant
– Blind Transfer
• Security
– Control: SIP/TLS
– Media: SRTP
– Telnet: SSL for Remote Configuration
– Web: HTTPS (HTTP over SSL)
– Access Lists for Web and Telnet Management
– Web & Telnet User Authentication via RADIUS
• Scalability
– DNS support for load balancing

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Distributed Deployment

Headquarters

Branches
E1
Exchange UM
SMDI

• Voice Quality
• Allowing Traversal over NAT ISP Networks for:
– Signaling Protocols
– Voice Streams
– Network Management
• Packet Loss Concealment
AudioCodes' Confidential Information covered under Non-Disclosure Agreement
PBX support

Alcatel OmniPCX 4400

Avaya Partner, Merlin, •Documentation
Definity •.INI file specifics
•CAS and Tone files
Intecom EADS2001
Mitel SX-200, SX-2000
NEC Electra, elite, IPX,
NEAX2000,
NEAX2400
Nortel Succession,
Meridian*
Panasonic KX-TD
Siemens 9005, HiCom300,
HiPath 3000/4000
Toshiba DK * - available 5.0, June 2006

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Reseller’s program

• 3 Tiers program (Gold, Certified,

Authorized)
– Pricing
– training (schedules)
– support
• Channels portal, Tools for
scalability:
– Marketing material and collateral
– Success stories
– Technical information
– eLearning
• Sign up as an AudioCodes
certified Reseller.

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Why AudioCodes

• Cost Effective
• Covers Low-end spectrum: 4 ports
• Covers Hi-end spectrum: 16 E1/T1
• Top voice quality
– Distributed Deployment
– Speech Recognition
• Supports Distributed deployment
• Versatile Gateways: Added business value to
Resellers

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Technical Overview
Configuration
Trouble shooting

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Cabling

Power
Supply RS-232
10/100 8 RJ-11 Port
Socket Base-T FXS or
RJ-45 Port FXO Ports

Grounding Screw Label ‘FXS’ or ‘FXO’

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Assigning IP Address

 HTTP using switch / hub or using direct PC connection

 BootP Application

 Serial communication software (e.g., HyperTerminal)

connected to the MP-1xx via the RS-232 port.
SCP IP [ip_address] [subnet_mask] [default_gateway] &SAR

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Embedded Web Server

• Point browser at IP address of the gateway

• User: Admin; Password Admin (case sensitive)
• Default IP Config:
• M2k (& MP/FXS): 10.1.10.10/255.255.255.0
• MP/FXO: 10.1.10.11/255.255.255.0
(& M2k trunks8-16)
AudioCodes' Confidential Information covered under Non-Disclosure Agreement
BootP: configuration

BOOTP Definition:
The Bootstrap Protocol allows a host to configure itself
dynamically at boot time. This protocol provides 3 services:

IP address assignment.

Detection of the IP address for a serving machine.
A file to be loaded and executed by the client machine.
.
Relevant parameters & tables (ini file)*
1. AudioCodes' BootP/TFTP Application
2. Device Mac address
3. Configuration, Firmware, CAS & Tones Files

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Gateway Configurations Options

 The Embedded Web Server

 A configuration file referred to as the ini file

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Basic Configuration

Protocol Management  Protocol Definition  Coders

Protocol Mgmt  Protocol Definition  DTMF and Dialing

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Recommended Files to Load

• MediaPack-10x FXO:
– Call Progress Tones (CPT) file: usa_tones.dat
– FXO coefficient file: MP1xx12-1-xxkhz-fxo.dat (for working with PBX)
• Mediant 2000
– Call Progress Tones (CPT) file: M2k_usa_tones.dat
– CAS File for Voice Mail: LoopStartTable_FXO.dat

• All Auxiliary files can be found on CD shipped with

gateway or on AudioCodes support site in the software
packages available for download.

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Mediant 2000 Specific Configurations

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Trunk Group setup (for SMDI)

Protocol Management  Trunk Group

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Digital Trunk Configuration

• Advanced Configuration  Trunk Settings

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Make some choices before beginning

• Choice of line type (E1/T1) should be made at software

installation time.
• Load default ini file for E1/T1 along with software
• Cannot change between E1/T1 on the fly once a system
has been loaded with software
• To switch from E1 to T1 / T1 to E1, reload the system
with a new ini file
• Back up current running configuration (Advanced Configuration 
Get ini File)
• Modify appropriate ini file parameters to reflect change to be made
• Load CAS files prior to trunk provisioning (if using CAS)

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

CAS Files

• Contain State machines for CAS protocol variants

• Available in software download packages and product
CD (shipped with product)
• Voice Mail requires FXO Loopstart CAS file to work
• Can store up to 8 CAS files (one per span) per board
• All loaded CAS files must be of same line type (E1/T1)
• Each CAS file can be associated with one or more spans
• Loading
– BootP through ini file
– ‘Software Upgrade’  ‘Software Upgrade Wizard’
– ‘Software Upgrade’  ‘Load Auxiliary Files’  Browse for CAS File and
then ‘Send’ it to the board

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Digital Trunk Configuration Steps

• Place mouse over a trunk status indicator and single

click to select it
• Scroll down in the right pane and click ‘Stop Trunk’
(changes can only be made to trunk settings with the
trunk stopped)
• Once the trunk is stopped, select a protocol type from
the drop-down menu to display the configuration
parameters associated with the protocol variant selected
• Configure pertinent parameters
• Click ‘Apply Trunk Settings’ button
• Select ‘Save Configuration’ in left pane

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Auxiliary File Download

Software Update  Load Auxiliary Files

ALWAYS RESET GATEWAY AFTER LOADING FILES!

AudioCodes' Confidential Information covered under Non-Disclosure Agreement
 FXO Configurations

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

FXO Endpoint Configuration

Protocol Management  Endpoint Phone Numbers

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

MediaPack-10x FXO Specific Configurations

Protocol Management  FXO Settings  FXO Settings

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Voice Mail integration Settings

MP: Protocol Management  FXO Settings  Voice Mail

M2k: Protocol Management  Advanced Applications  Voice Mail

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 DTMF based Integration
Mediant 2000 E1/T1, or
MediaPack 4 or 8 analog FXO ports

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

DTMF: Calls from PBX to Voice Mail

• When the gateway detects a ringing signal it seizes the line

and collects the received DTMF digits.
• The collected digits are compared against pre-configured
patterns to extract the Redirect Number (usually identifies the
VM box number), Redirect Reason (forward reason) and, if
available, the Source Number.
• The patterns are configured per PBX according to its
specifications.
• The gateway sends an INVITE message to the IP VM.
• The headers in the SIP message are the same as in the SMDI
Operation mode

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Pattern Syntax

• The digit patterns generated by the PBX are composed of the

following notations:
• 0-9, A-D, #, * ‑ Specific DTMF digits
• R – A single Redirect Number digit
• S ‑ A single Source Number digit
• X – Any digit
• ‘.d’ (single dot followed by a digit) – Repeat the last rule until digit ‘d’
is received (digit ‘d‘ is ignored)
• For example:
– #03RRR#S.# ‑ Collects a three-digit Redirect number, and
Source number of variable size, until a ‘#’ sign is received.
– #01#R.# ‑ Collects digits to Redirect Number until the digit ‘#’ is
received
– X.*RRR ‑ Ignores all digits until the digit ‘*’ is received (‘*’ is also
ignored), and collects a three-digit Redirect number.

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Pattern examples

• Avaya
– DigitPatternForwardOnNoAnswer = #03##R.#
– DigitPatternInternalCall = #00#X.#S.#
• NEC, Nortel – Don’t have separate reasons for Call
Forward. They always dial the Redirect number only.
– DigitPatternForwardNoReason = R.

• Default patterns will be provided with AudioCodes default

files for certified PBX
• Granted, installer needs to verify matching to PBX
specific install

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 DTMF Web Configuration

MP: Protocol Management  FXO Settings  Voice Mail

M2K: Protocol Management  Advanced Applications  Voice Mail

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Message Waiting Indication (Optional)

• After being informed by the VM of MWI, the gateway notifies the PBX.
• It allocates an endpoint according to the Source IP (MWIServerIP), Destination
Number (Message-Account) and ChannelSelectMode.
• The endpoint allocation procedure is similar to the mechanism used to allocate
incoming IP to Tel calls.
• The gateway dials a number to the PBX that is composed of a digit code and an
extension number. The extension number is the number received from the VM in
the NOTIFY message .
• The digit code is a configurable pattern that indicates if there are / or aren’t any
waiting messages.
• Relevant parameters (in addition to the parameters described before)
– MWIOffCode
Determines a digit code used by the gateway to notify the PBX that there
aren’t any messages waiting for a specific extension. This code is added as
prefix to the dialed number. The valid range is a 25-character string.
– MWIOnCode
Determines a digit code used by the gateway to notify the PBX of messages
waiting for a specific extension. This code is added as prefix to the dialed
number. The valid range is a 25-character string.

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 SMDI based Integration
Mediant 2000 E1/T1 , or
MediaPack 4 or 8 analog FXO ports

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 SMDI Operation

• SMDI provides the gateway with data, enabling it to intelligently

process incoming voice-messaging calls
• When routing a call (to the VM), the PBX sends an SMDI message
to the gateway (through an RS-232 connection)
• The message informs it as to the line it is using, the type of call it is
forwarding, and information about the source and destination of the
call
• In this message, the PBX may include the Redirect Number (usually
identifies the VM box number), Redirect Reason (forward reason),
Source Number, Source Number Presentation (Allowed / Restricted)
and Source Name. Not all information is always available
• The SMDI Message Line Identifier must match the gateway’s local
endpoint number

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 SMDI Format

• Required fields:
– Message Desk Number
– Position Number
– Type of Call Indicator
A = all calls forwarded to VM
B = forward on busy
D = direct dial to VM
N = forward no answer
U = call forwarded to VM, reason unknown
• Other fields may or may not be present

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Message Line Identifier

• Must match endpoint/trunk phone numbers on the

gateway
• Analog:
• Message Desk Indicator and Position Number are equivalent to the
entire phone number assigned to each port
• Digital:
• Message Desk Indicator is the span/trunk number
• Position Number is b-channel allocated for call

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Type of Call Indicator

• Indicates the redirect reason:

– A = all calls forwarded to VM
– B = forward on busy
– D = direct dial to VM
– N = forward no answer
– U = call forwarded to VM, reason unknown

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Message Line Identifier matches Trunk Group
setup (Digital)

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Message Line Identifier to Endpoint Phone
Number (Analog)

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

MediaPack FXO SMDI Web Configuration

MP: Protocol Management  FXO Settings  Voice Mail

M2k: Protocol Management  Advanced Applications  Voice Mail

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Relevant parameters

• VoiceMailInterface = 2
– Enables VM on the gateway and determines the communication method
used between the PBX and the gateway:
0 = None (default)
1 = DTMF
2 = SMDI
• SMDI = 1
– Enables SMDI on the gateway.
0 = Normal serial (default).
1 = Enable RS-232 SMDI interface.
• SMDITimeOut
– Determines the time (in msec) that the gateway waits for an SMDI Call
Status message before or after a Setup message is received. This
parameter is used to synchronize the SMDI and Tel interfaces. If the
timeout expires and only an SMDI message was received, the SMDI
message is dropped. If the timeout expires and only a Setup message
was received, the call is established.
– Valid range is 0 to 10000 (10 seconds). The default value is 2000

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Additional mandatory Call Scenarios configuration
Call Transfer
Call termination

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Call Transfer - Relevant parameters

• Same configuration for both SMDI and DTMF configuration

• EnableTransfer = 1
Must be set to 1 to enable transfer.
• LineTransferMode = 1
To activate Blind Transfer into PBX (FXO gateways only).
• TrunkTransferMode_x = 1 (CAS NFA) or 3 (CAS Normal) (digital
gateways only)
When a SIP REFER message is received, the gateway performs a
Blind Transfer by executing a CAS Wink, dialing the Refer-to
number and then releasing the call.
Note: A specific CAS table is required.
• WaitForDialTime
Determines the delay between the time the line is seized and dialing
is begun, during the establishment of an IP2Tel call.
The valid range (in milliseconds) is 0 to 20000 (20 seconds). The
default value is 1000 (1 second).

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Call Termination: PBX Disconnect Code

• A DTMF code sent by the PBX to the gateway notifying it that

the VM call is terminated.
• When the gateway identifies that a call is terminated by the
PBX, it closes the IP session and releases the line towards
the PBX.
• A digit pattern that, when received from the Tel side, indicates
the gateway to disconnect the call.
– Relevant parameter: TelDisconnectCode.
– For example:
• Panasonic: #9; TelDisconnectCode = #9 (for Panasonic PBX)
• Toshiba: D; TelDisconnectCode = D (for Toshiba PBX)

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Supplementary Services
MWI additional parameters
(MWI is optional)

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Message Waiting Indication

• The IP VM uses SIP NOTIFY messages to inform the gateway of

Message Waiting Indications (MWI).
• The gateway must first subscribe to an MWI server (a single
subscription per gateway) using the SIP MWI package – (simple-
message-summary).
• After a successful subscription, the MWI server can start sending
NOTIFY messages to the gateway with message waiting
indications. The extension number sent to the PBX is provided in
the Message‑Account header in a NOTIFY message
• After being informed by the VM of MWI, the gateway sends an
Operate MWI (Turn On) message over the serial connection to the
PBX. In this message, the gateway includes the extension number
received in the NOTIFY message.
• A Remove MWI (Turn Off) message is used to remove the MWI.

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 MWI Web Configuration

Protocol Management  Advanced Configuration  Supplementary Services

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 MWI: Relevant parameters

• VoiceMailInterface = 2 (for SMDI)

• SubscriptionMode = 1 (subscription per gateway)
Determines the method the gateway uses to subscribe to an
MWI server.
• Username= Gateway
Account name used for subscription to the MWI server.
• EnableMWISubscription = 1
• MWIExpirationTime = 7200 (seconds)
• SubscribeRetryTime = 120 (seconds)
• MWIServerIP = xxx.xxx.xxx.xxx
IP address of the MWI server.
• SMDI = 1

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

 Basic Troubleshooting on AudioCodes Gateways

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

INI File Save/Load

Advanced Configuration  Configuration File

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Debugging Configurations with Syslog

SYSLOG Definition:

The SYSLOG is a collection of error messages,

warning messages, and/or other system messages
that are sent to a central server using UDP port 514

Relevant parameters & tables (ini file)*

1. Enable SYSLOG
2. SysLog Server IP address
3. Debug Level
Should ONLY be set while debugging;
not during normal operations
AudioCodes' Confidential Information covered under Non-Disclosure Agreement
SYSLOG Server :configuration

Syslog messages may increase the network traffic.

Logs can also be sent to the RS-232 serial port

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

SYSLOG :setting debug level

Protocol Management  Advanced Parameters  General

Parameters

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Online SYSLOG

AudioCodes' Confidential Information covered under Non-Disclosure Agreement

Status & Diagnostics

Status & Diagnostics

View and monitor the gateway’s channels, Syslog messages,
hardware / software product information, and to assess the
gateway’s statistics and IP connectivity information.

Gateway Statistics
Monitor real-time activity such as IP Connectivity information, call
details and call statistics, including the number of call attempts,
failed calls, fax calls, etc.
AudioCodes' Confidential Information covered under Non-Disclosure Agreement
 Thank you for your time !

AudioCodes' Confidential Information covered under Non-Disclosure Agreement