TOL Cisco CM5 1 Integration

8/2/2019 TOL Cisco CM5 1 Integration

1/18

Telephony Office-LinX 7.1+ Integration with

Cisco CallManager 5.1

doc v. 7.0.2.0

April 2009


2/18

TelephonyOffice-LinX

Title 2

TOL integration with Cisco CallManage

Copyright 2008 Esna Technologies Inc

Introduction

This document describes the configuration required to setup Cisco CallManager 5.1 with Telephony Office-LinX

Unified Messaging System using SIP connection. It also contains the results of the interoperability testing based on

this setup.

Copyright

ESNA Technologies Inc.

30 West Beaver Creek Rd., Suite 101

Richmond Hill, ON L4B 3K1

Copyright 2007 by ESNA Technologies. All rights reserved.

Telephony Office-LinX enterprise edition Unified Communications Server is made available under the terms of the

ESNA Technologies Inc. (E.T.I.) License Agreement without express or implied warranties of any sort, including,

specifically, any warranties relating to the performance or maintenance of the program.

While every effort has been made to ensure accuracy, ESNA Technologies Inc. will not be liable for technical or

editorial errors or omissions contained within the System documentation. The information contained in this

documentation is subject to change without notice.

ESNA software and related documentation may be used only in accordance with the terms of the ESNA Technologies

Inc. License Agreement and copied only to provide adequate backup protection.

Trademarks

Other brands and their products are trademarks or registered trademarks of their respective holders and should be

noted as such.

Contacting ESNA Technologies

Contact us by mail at:

ESNA Technologies Inc.

30 West Beaver Creek Rd., Suite 101

Richmond Hill, ON L4B 3K1

Contact us by phone:

Tel: 905-707-9700

Fax: 905-707-9170

Find us on the web at:

www.esnatech.com

For hardware and software support, call:

Tel: 905-707-1234

Email: [email protected]


3/18

Telephony Office-LinX integration with Cisco CallManager



3

ATelephony Office-LinX integration

with Cisco CallManager 5.1

Chapter Listings:

1. Components Information........................................................................... 4

2. Prerequisites ........................................................................................... 53. Summary and Limitations.......................................................................... 6

4. Gateway Setup Notes ............................................................................... 7

5. PBX Setup Notes...................................................................................... 8

5.1. Check Licensing..................................................................................................8

5.2. Configuring Cisco Unified CallManager, CallManager Groups, Region and Device Pool....8

5.3. Create a New SIP Trunk..................................................................................... 11

5.4. Create a New Route Pattern ............................................................................... 13

5.5. Configure Voicemail Profile................................................................................. 14

5.6. Check the Phone Configuration ........................................................................... 16

5.7. Optional: Configuring MRG & MRGL ..................................................................... 18

5.8. Configuring MWI............................................................................................... 18

5.9. TLS Setup........................................................................................................ 18


4/18


integration

with

CiscoC

allManager

Telephony Office-LinX integration with Cisco CallManager 4



A1. Components Information

Warning: These integration notes are created through internal testing and cannot be guaranteed for outsidedeployment due to the variance of settings in the different sites. Some integration may not work even if you

follow the documentation as shown here due to the variables that we cannot foresee. It is recommended that

you use this guide as a reference to customize your own configuration rather than to literally following through

the document.

1.1. PBX or IP-PBX

1.2 VoIP Gateway

1.3 Telephony Office-LinX Unified Messaging

PBX Vendor Cisco

Model CallManager 5.1

Software Version 5.1.0.9921-12

Telephony Signaling Direct SIP integration

Gateway Vendor N.A.

Model N.A.

Software Version N.A.

VoIP Protocol N.A.

Version 7.1+


5/18


6/18


integration

with

CiscoC

allManager




A3. Summary and Limitations

Telephony Office-LinX Unified Messaging (UM) has the following functional limitations when operate with Cisco

CallManager (CCM) 5.1:

CCM 5.1 and Telephony Office-LinX UM support G.723.1 codec. However, we were unable to perform interop

testing using this codec as the Cisco IP phones available during testing do not natively support G.723.1. Whilehardware-based transcoders can be used to perform the necessary transcoding between G.723.1 and a codec

supported by the phones, none of these transcoders were unavailable at the time of testing.

CCM 5.1 and Telephony Office-LinX UM support TLS over SIP trunk. However, there are some differences in the

protocol implementation, which are causing interop to fail. We are working to resolve these differences.


7/18


integration

with

CiscoC

allManager




A4. Gateway Setup Notes

N/A.

4.1. Configuration Files N/A.

4.2. TLS Setup

N/A.


8/18


integration

with

CiscoC

allManager




A5. PBX Setup Notes

In general, the steps required to configure Cisco CallManager to work with Telephony Office-LinX UM can be

summarized as:

Create A SIP trunk.

Define route pattern for Telephony Office-LinX UM.

Configure appropriate coverage paths for UM-enabled users.

In this section, we show how the configuration can be done via the CallManager web-based administration interface.

We shall use the convention x ? y to indicate click on x followed by click on y.

5.1. Check Licensing

On the administration UI, go to System > Licensing > License Unit Report. Confirm that the license file is uploaded

and the status indicates Ready.

5.2. Configuring Cisco Unified CallManager, CallManager Groups, Regionand Device Pool

Go to System > Cisco Unified CallManager. Use the default configuration for the Cisco Unified CallManager (Figure

2).

Go to System > Cisco Unified CallManager Groups. Use default configuration for the Cisco CallManager Group

Figure 1

Figure 2


9/18


10/18


integration

with

CiscoC

allManager




AGo to System > Device Pool. Use default configuration for the device pool (Figure 5).

Figure 5


11/18


integration

with

CiscoC

allManager




A5.3. Create a New SIP Trunk

Go to Device > Trunk > Add New to create a new SIP trunk with the following parameter settings (Figure 6):

Trunk Type = SIP Trunk

Device Protocol = SIP

Configure the following parameters for the SIP trunk (Figure 7):

Device Pool = Default

Media Resource Group List = None

Media Termination Point = Unchecked (default). When this field is unchecked, the CCM sends SIP INVITEs to the

UM server with no SDP in the offer. When checked, the SIP INVITEs contain SDP in the offer. The UM server

supports both, but the default configuration is recommended.

Continue: Configure the following parameters for the SIP trunk (Figure 8):

Redirecting Diversion Header Delivery Inbound = Checked

Calling Party Selection = Originator

Redirecting Diversion Header Delivery Outbound = Checked

Destination Address = IP Address of the UM Server

Figure 6

Figure 7


12/18


integration

with

CiscoC

allManager




A Destination Port = 5060 when TLS is not used, or 5061 when TLS is used.

Preferred Originating Codec = 711uLaw (default)

SIP Profile = Standard SIP Profile (default)

DTMF Signaling Method: No Preference (default). Using RFC2833 for this field should also work.

Figure 8


13/18


integration

with

CiscoC

allManager




AThe standard SIP Profile is shown in Figure 9 and 10:

5.4. Create a New Route Pattern

Go to Call Routing > route/hunt > route pattern > Add New to create a new route pattern for the Telephony Office-

LinX UM pilot number. Configure the following parameters (Figure 11 and 12):

Route Pattern = Pilot number for Telephony Office-LinX UM.

Figure 9

Figure 10


14/18


15/18


integration

with

CiscoC

allManager




Acorrespond to the pilot number configured on the Telephony Office-LinX UM server (Figure 13).

Go to Voice Mail > Voice Mail Profile. Configure the Voice Mail Pilot field under the Default Voice Mail profile to be

the Voice Mail Pilot configured earlier (Figure 14 and 15).

Figure 13

Figure 14

Figure 15


16/18


integration

with

CiscoC

allManager




A5.6. Check the Phone Configuration

Go to Device > Phone and select the phone you want to configure (Figure 16).

Select the line you want to configure its voice mail settings (Figure 17).

Confirm the Voice Mail Profile is set to the profile configured in Step 5, which contains the pilot number of

Figure 16

Figure 17


17/18


integration

with

CiscoC

allManager




ATelephony Office-LinX UM (Figure 18).

Ensure the following are enabled (Figure 19):

Forward Busy Internal

Forward Busy External

Forward No Answer Internal

Forward No Answer External

Figure 18

Figure 19


18/18


integration

with

CiscoC

allManager


A

5.7. Optional: Configuring MRG & MRGL

Depending on actual deployment, you may observe that Telephony Office-LinX UM drops every call from Cisco

CallManager. In addition, you may find Event ID 1079 in the system event log of the UM server with the following

description:

The VoIP platform encountered an exception Esnatech.SpeechServer.SpeechApplicationException: The requested

DTMF payload type (101) has been refused by the remote end. ---> System.ArgumentException: The requested

DTMF payload type (101) has been refused by the remote end

First, you need to make sure that the Default MTP Telephony Event Payload Type property under your SIP Profile

Configuration has been correctly set to 101 (Figure 9).

If the problem continues to persist, you may be required to use the following configuration on the CallManager:

Create a Media Termination Point (MTP).

Create a Media Resource Group (MRG) and add the above MTP to this MRG.

Create a Media Resource Group List (MRGL) and add the MRG to this MRGL.

Go to your existing Device Pool configuration page and update the Media Resource Group List entry to

reflect the new MRGL you have created.

Go to your existing SIP Trunk configuration page and update the Media Resource Group List entry to

reflect the new MRGL you have created.

5.8. Configuring MWI

The SIP trunk should support the TCP transport and should support unsolicited SIP NOTIFY. These options can be

enabled in the SIP Trunk Security Profile assigned to the trunk. The supported transport protocols can be specifiedby using the Incoming Transport Type and Outgoing Transport Type profile parameters. Specify the TCP parameters.

To enable unsolicited SIP notification, set the Accept Unsolicited Notification parameter to true.

5.9. TLS Setup

Null

Figure 20

Documents

TOL Cisco CM5 1 Integration