Application Notes for Configuring the ESNA Telephony
Office-LinX v8.0 with Avaya Business Communications
Manager Release 6.0 - Issue 1.0
Abstract
These Application Notes describe the procedure for configuring the ESNA Telephony OfficeLinX v8.0 to interoperate with the Avaya Business Communications Manager Release 6.0.
The Telephony Office-LinX Enterprise Edition server connects to the Avaya Business
Communication Manager via SIP connectivity and provides unified communications features
such as greeting menu, user mailbox services, wake up services and transfer functionalities.
Information in these Application Notes has been obtained through DevConnect compliance
testing and additional technical discussions. Testing was conducted via the DevConnect
Program at the Avaya Solution and Interoperability Test Lab.
RS; Reviewed:
SPOC 11/8/2010
Solution & Interoperability Test Lab Application Notes
These Application Notes describe the procedure for configuring the ESNA Telephony OfficeLinX v8.0 (TOL) to interoperate with Avaya Communications Manager (BCM) Release 6.0.
The objective of this compliance testing is to verify that TOL can connect via SIP trunk to the
BCM and provide unified communication services like greetings, messaging and transfer
functionalities.
1.1. Interoperability Compliance Testing
The interoperability compliance test included features and serviceability that operate via SIP
connectivity. The focus of the compliance testing was primarily on verifying the interoperability
between ESNA TOL v8.0 and the Avaya BCM R6 so that the following features operate:
• BCM clients can access the TOL pilot number.
• TOL can access the BCM clients.
• TOL provides messaging services to the BCM clients.
• TOL can conduct transfer operations for the BCM clients.
1.2. Support
Technical support for the ESNA Telephony Office-LinX solution can be obtained by contacting
ESNA:
• URL – techsupp@esna.com
• Phone – (905) 707-1234
2. Reference Configuration
Figure 1 illustrates the configuration used in these Application Notes. The sample configuration
shows an enterprise with a BCM talking to the TOL via a SIP trunk. The BCM has an analog, a
digital and an IP Telephone connected as endpoints.
For interoperability, the TOL requires the use of the G.711MU codec, and transmission of
DTMF tones using RFC2833.
RS; Reviewed:
SPOC 11/8/2010
Solution & Interoperability Test Lab Application Notes
Configuration > Resources > IP Trunks > SIP Trunking
Select the tab Private > URI Map as shown in Figure 3 below.
Figure 3: URI Map
Do note here that some values need to be blank for the TOL to integrate correctly with the BCM.
Entering any values here will cause the integration to fail since TOL does not recognize these
values. For example if you populate Private/CDP field with cdp.udp, the BCM tags the phone
context in the SIP messages and TOL does not recognize these and therefore fails to integrate
with BCM.
RS; Reviewed:
SPOC 11/8/2010
Solution & Interoperability Test Lab Application Notes