Tech Note Cisco CallManager Fax Integration TN093 March 08 1 Objectworld Communications Corp. • 308 Legget Drive • Ottawa, ON • Canada • K2K 1Y6 • T: 613‐599‐9698 • F: 613‐599‐7457 • www.objectworld.
Copyright Copyright © 2008 Objectworld Communications Corporation. All rights reserved. Trademarks Objectworld Unified Communications Server, Objectworld UC Server, Objectworld UC Client, IT Telephony, the IT Telephony Company and UC Server are trademarks of Objectworld Communications Corporation. Published March 27, 2008 2 Objectworld Communications Corp. • 308 Legget Drive • Ottawa, ON • Canada • K2K 1Y6 • T: 613‐599‐9698 • F: 613‐599‐7457 • www.objectworld.
Table of Contents 1 2 3 Introduction ................................................................................................................................................ 4 1.1 Required Components............................................................................................................................................. 5 1.2 Additional References .................................................................................................................................
1 Introduction This technical note describes the fax integration between Objectworld UC Server and Cisco CallManager. UC Server integrates with Cisco CallManager using SIP Interoperability and T.38 Fax Relay. UC Server can support the following applications of fax in a Cisco CallManager environment: • • • Separate incoming voice and fax numbers (DID Fax) Shared incoming voice and fax application Outgoing faxing Summary of fax deployment models: • • • • Direct SIP Integration using T.
1.1 Required Components The following are minimum requirements. 1. Objectworld UC Server – SIP Edition Release 4.3 or higher. UC Server SIP Edition is required to take advantage of advanced routing rules to support fax integration with Cisco CallManager. 2. Users that require pre‐answering to determine if a call is a voice call or a fax call must be configured as a Personal Business Assistant (PBA) call answering mode. 3. Cisco CallManager 5.1 or higher (Cisco CallManager 6.
2 Deployment Models Objectworld UC Server can integrate with Cisco CallManager in a variety of ways, depending on the desired capabilities and the current voice and data environment. 2.1 Direct SIP Integration using T.38 Relay Direct SIP Integration using T.38 relay provides direct T.38 fax integration with dedicated DID numbers routed via SIP to Objectworld UC Server. Cisco IOS Gateways do not provide CNG Detection in their default configurations.
5. exit 2.1.1.2 Configuring Cisco IOS outbound VoIP dial peer for voice calls Perform the following steps on the Cisco gateway to route calls to the UC Server pre‐answering behavior. 1. 2. Log onto the Cisco Gateway destination pattern …. The configured voice routing prefix must match the parameter defined in the previously configured application service. The voice routing prefix will also be configured in UC Server. 3. 4. 5. 6. 7. 8.
session protocol sipv2 session target ipv4:192.168.8.129 codec g711ulaw ! dial-peer voice 2852 voip description Incoming Fax Calls to UC Server destination-pattern 71.. session protocol sipv2 session target ipv4:192.168.8.54 codec g711ulaw fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none ! sip-ua ! 2.2 Direct SIP Integration using T.38 Relay with CNG Detection Direct SIP Integration using T.38 relay with CNG detection allows a single incoming telephone number to receive voice and fax calls.
2.2.1 Configuration The high level configuration steps are: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.
6. application service CNG‐detect param mode connect‐first 2.2.1.2 Configuring Cisco IOS inbound POTS dial peer Perform the following steps on the Cisco gateway: 1. 2. 3. 4. 5. Log onto the Cisco IOS Gateway dial‐peer voice tag pots service cng‐detect direct‐inward‐dial incoming called‐number string Where string is a Cisco routing character that specifically identifies either a single number or multiple numbers that are pre‐answered. 6. exit 2.2.1.
The fax routing prefix configured here must match the parameter defined in the previously configured application service. The fax routing prefix will also be configured in UC Server. 3. 4. 5. 6. 7. 2.2.2 session protocol sipv2 session target ipv4: dtmf‐relay rtp‐nte fax protocol t38 ls‐redundancy 0 hs‐redundancy 0 fallback none exit Example This example uses the following information: • • • • Incoming DID called number pattern: 28xx (2800 to 2899) UC Server IP Address: 192.168.8.
2.3 Direct T1/E1 PRI Integration to Central Office Direct T1/E1 PRI integration to a central office leverages dedicated facilities terminating on an Objectworld interoperable SIP PSTN Gateway. This integration can provide both dedicated fax integration (DID fax) as well as combined voice and fax services. It is also possible to route voice calls through Objectworld UC Server SIP PBX using SIP trunks between Objectworld UC Server and Cisco CallManager.
CallManager are used to avoid hair‐pinning (using two channels on the PRI for a single call) calls being redirected through the SIP PRI gateway. 2.4.1 Configuration The high level configuration steps are: 1. 2. Configure the SIP PRI Gateway in accordance to Objectworld guidelines. Technical notes are available on Objectworld’s Web site Resource Center or on the media that is shipped with the product.
3 Configuring Cisco CallManager This section highlights specific Cisco configuration to provide transparent dialing between CallManager and UC Server. 3.1 Creating a SIP Trunk to Route Calls from Cisco CallManager to Objectworld UC Server To create a SIP Trunk in Cisco CallManager to route calls to Objectworld UC Server 1. 2. 3. 4. Log into Cisco Unified CM Administration. Navigate to Device > Trunk. Click on Add New. Select SIP Trunk from the Trunk Type drop down list. 5.
4 Configuring Objectworld UC Server This section highlights the configuration steps that can be performed on UC Server. Some of the detailed steps may be optional. 4.1 Creating SIP Routing Rule to Cisco CallManager 4.1.1 Adding a gateway To add a gateway 1. 2. 3. 4.1.2 From the Administration Navigation pane, select Gateways. Right‐click in the Content pane and select New Gateway. Follow the wizard instructions and include the following information: a. Select SIP Peer b.
4.2 Creating a Database – Mapping Pre‐answer Numbers to Target Extensions Follow the instructions below to create a new data source that allows an incoming DID number to be mapped to extension numbers. This table will define a mapping between the incoming called number and the associated extension. If the call is not a fax – no CNG tone is detected – then the call will be transferred to the associated extension using the SIP trunk. 4.2.
Note: The ODBC Data source cannot be used while the Microsoft Excel spreadsheet is open. To create an ODBC Data source in UC Server 1. 2. 3. 4. 5. 6. 7. From the Administration Navigation pane, select Data Sources. Right‐click in the Content pane and select New > ODBC Source… Create a name. ODBC DSN: Select the data source that was created in a previous step. Click Connect Include the Called Number and Transfer Extension Click OK 8. Change the access settings for this database to Everyone a.
4.3 Creating a Fax Pre‐answer Service The fax pre‐answer service is only required if you want to provide voice and fax on the same incoming called number. You can skip this step if you have separate incoming numbers for voice and fax. The fax pre‐answer service performs a database ‘fetch data’ that matches the original called number (represented as Caller‐ID Number) to an associated extension.
2. Right‐click the user in the Content pane that you want to create the pre‐answer service and select Create Identity… 3. Select the UC Server communications system. 4. Select Attendant Service and click Next. 5. Configure a Name and Address. The address that you enter is the . 6. Check the Run Service radio button, and navigate to the shared service that was created in the previous step. 7. Click Finish. 4.
