’‡‡š–‹‰Š– ƒš‹–‡‰”ƒ–‹‘™‹–Š
‹• ‘‹ˆ‹‡†ƒŽŽƒƒ‰‡”ƒ†‹• ‘
‹–›‘‡ –‹‘Ǥ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
Copyright © 2012 by tekVizion PVS, Inc.
All Rights Reserved.
Confidential Information
The information contained in this document is confidential and proprietary to tekVizion PVS, Inc.
This document is the property of, and is proprietary to tekVizion. It is not to be disclosed in
whole or in part without the express written authorization of tekVizion, shall not be duplicated or
used, in whole or in part, for any purpose other than to evaluate the proposed scope of testing
under contemplation.
TEKVIZION, TEKVIZION PVS, AND TEKVIZION LABS ARE TRADEMARKS OF TEKVIZION
PVS, INC. FAST FORWARD IS A SERVICE MARK OF TEKVIZION.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
DOCUMENT REVISION HISTORY
Version
Reason for Change
Date
Created/Updated by
1.0
Initial Draft
3/11/2013
Satheesh Kumar
1.1
Review Comments and addition of Cisco Unity
Connection Integration notes.
3/11/2013
Ameeta Thukral
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
ƒ„Ž‡ˆ‘–‡–•
WƌĞĨĂĐĞ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱ
KǀĞƌǀŝĞǁ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϲ
ŽŶĨŝŐƵƌĂƚŝŽŶ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϲ
KƵƚůŝŶĞŽĨ^ĐĞŶĂƌŝŽƐ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϲ
^ĐĞŶĂƌŝŽϭ͗^/WͲƚŽͲ^/WŽŶĨŝŐƵƌĂƚŝŽŶ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϲ
^ĐĞŶĂƌŝŽϮ͗,͘ϯϮϯͲƚŽͲ,͘ϯϮϯŽŶĨŝŐƵƌĂƚŝŽŶ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϭϴ
^ĐĞŶĂƌŝŽϯ͗^/WͲƚŽͲD'WŽŶĨŝŐƵƌĂƚŝŽŶ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘Ϯϲ
^ĐĞŶĂƌŝŽϰ͗,͘ϯϮϯͲƚŽͲD'WŽŶĨŝŐƵƌĂƚŝŽŶ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϯϵ
ŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶŽŶĨŝŐƵƌĂƚŝŽŶͬ/ŶƚĞŐƌĂƚŝŽŶǁŝƚŚ&Ădž͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϰϵ
ůůŽǁŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶƚŽĐĐĞƐƐƚŚĞ/WĚĚƌĞƐƐĐĐĞƐƐŽĨƚŚĞŝƐĐŽ&Ădž^ĞƌǀĞƌ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϰϵ
ŶĂďůĞƚŚĞŝƐĐŽ&Ădž^ĞƌǀĞƌ/ŶƚĞŐƌĂƚŝŽŶŽŶŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϰϵ
ƵƐƚŽŵŝnjĞƚŚĞŝƐĐŽ&Ădž^ĞƌǀĞƌ/ŶƚĞŐƌĂƚŝŽŶŽŶŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱϬ
ŽŶĨŝŐƵƌŝŶŐŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶhƐĞƌƐĨŽƌƚŚĞŝƐĐŽ&Ădž^ĞƌǀĞƌ/ŶƚĞŐƌĂƚŝŽŶ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱϭ
ĐĐĞƐƐŝŶŐƚŚĞǁĞďŝŶďŽdžĂŶĚǀŝĞǁŝŶŐŵĞƐƐĂŐĞƐ͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱϯ
>ŽĂĚdĞƐƚŽŶĨŝŐƵƌĂƚŝŽŶ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱϱ
^ĐĞŶĂƌŝŽϭʹ^/WƚŽ^/WŽŶĨŝŐƵƌĂƚŝŽŶ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱϱ
^ĐĞŶĂƌŝŽϮʹ,͘ϯϮϯƚŽ,͘ϯϮϯŽŶĨŝŐƵƌĂƚŝŽŶ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱϳ
^ĐĞŶĂƌŝŽϯʹ^/WƚŽD'WŽŶĨŝŐƵƌĂƚŝŽŶ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϱϵ
^ĐĞŶĂƌŝŽϰʹ,ϯϮϯƚŽD'WŽŶĨŝŐƵƌĂƚŝŽŶ͗͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘͘ϲϮ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
”‡ˆƒ ‡ǣ
This supplementary guide to Open Text Right Fax describes deployment models and procedures for using
Open Text Right Fax in a Fax-over-IP (FoIP) deployment with Cisco Voice and Unified Communications
products - Cisco Unified Communications Manager (CUCM) version 9.0 and Cisco Unity Connection
9.0.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
˜‡”˜‹‡™ǣ
OpenText RightFax connects to telephony environments using Cisco Voice and Unified
Communications Products through Plain Old Telephone Service (POTS) technology and using Faxover-IP (FoIP) technologies. In a FoIP solution, OpenText RightFax can connect to Cisco Unified
Communications Manager, Cisco IOS Voice Gateways, and Cisco Universal Gateways over IP
networks. This integration to send and receive fax documents utilizes either Session Initiation
Protocol (SIP) or H.323 and T.38 real-time Fax-over-IP.
Common document delivery solutions using OpenText RightFax and Cisco Voice and Unified
Communications products consist of the following components:
• OpenText RightFax version 9.4 FP1 SR2 or later, containing either Dialogic® Brooktrout®
SR140 software-only FoIP, or TR1034-series IP-enabled fax boards.
• Cisco Unified Communications Manager (CUCM)
• Cisco IOS Voice Gateways
Cisco Unity Connection can integrate with the Cisco Fax Server so that users can do the following
while on the phone or while using the Connection Web Inbox (Connection 9) or Messaging Inbox
• Receive faxes that are sent to the fax extension for the user. Depending on the system
configuration, faxes will be available in the user mailboxes or in the user IMAP clients.
• Forward the faxes that they receive to a fax machine for printing.
• Forward the faxes that they receive to another user.
‘ˆ‹‰—”ƒ–‹‘ǣ
—–Ž‹‡‘ˆ ‡ƒ”‹‘•
1. Scenario 1: SIP-to-SIP Configuration
a. RightFax <-SIP-> CUCM 9 <-SIP-> Gateway
2. Scenario 2: H.323-to-H.323 Configuration
a. RightFax <-H.323-> CUCM 9<-H.323-> Gateway
3. Scenario 3: SIP-to-MGCP Configuration
a. RightFax <-SIP-> CUCM 9 <-MGCP-> Gateway
4. Scenario 4: H.323-to-MGCP Configuration
a. RightFax <-H.323-> CUCM 9 <-MGCP-> Gateway
The configuration below includes the following for each scenario under test:
1. Dialing Plan overview
2. Cisco Voice Gateway Configuration
3. Cisco Unified Communications Manager Configuration
‡ƒ”‹‘ͳǣ Ǧ–‘Ǧ ‘ˆ‹‰—”ƒ–‹‘
‹ƒŽŽƒ˜‡”˜‹‡™
To call OpenText RightFax from a POTS phone, dial 99728522627. The call flow and protocol path is as
follows:
• POTS (dial 99728522627)
• Cisco Gateway translates the incoming number as 1111—SIP—>
• CUCM 9.0 dial 1111—SIP—> OpenText RightFax.
To call the POTS lines of the Gateway, dial 2222. The call flow and protocol path is as follows:
• OpenText RightFax (2222) —SIP—>
• CUCM route pattern 2222-> Called Party Transform Mask- 9728522626->SIP
• POTS
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‹• ‘͵ͺͶͷ ƒ–‡™ƒ›‡–—’‘–‡•
For the sample test configuration, the Cisco 3845 Gateway was configured the Cisco IOS command-line
interface. The specific items configured include:
• Enable T.38 support
• Configure line card interface
• Configure IP Protocol
• Configure Dial-Peers – POTS
• Configure Dial-Peers – VoIP
ƒ„Ž‡Ǥ͵ͺ•—’’‘”–
The following lines allow SIP calls and T.38 fax calls
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
SIP
‘ˆ‹‰—”‡˜‘‹ ‡Ǧ’‘”–
voice-port 0/0/0
station-id name fax test
station-id number 9728522626
caller-id enable
‘ˆ‹‰—”‡‹ƒŽǦ‡‡”•Ȃ
The following allows the phone “9728522626” to be dialed out though the POTS
lines:
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
preference 1
service session
destination-pattern 9728522626
no digit-strip
port 0/0/0
‘ˆ‹‰—”‡‹ƒŽ‡‡”•Ȃ‘ ǣ
The following allows reaching the Right Fax server:
translation-rule 1111
Rule 1 9728522627
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
preference 1
destination-pattern 9728522627
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.21:5060
session transport udp
codec g711ulaw
fax rate 14400
fax protocol t38 ls-redundancy 2 hs-redundancy
fallback none
1
Ip address 10.70.1.2 is the ip address of the call manager
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
0
ͻ‡–—’‘–‡•Ȃ Ȁ ‘ˆ‹‰—”ƒ–‹‘
The following areas of CUCM 9.0 are modified in this scenario:
• Configure SIP Trunk Security Profile
• Configure Sip Trunk from CUCM to OpenText RightFax
• Configure Sip Trunk from CUCM to Gateway
• Configure Call Routing
‘ˆ‹‰—”‡ ”—‡ —”‹–›”‘ˆ‹Ž‡
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select System | Security Profile | SIP Trunk Security Profile
&ŝŐƵƌĞϭ^ĞůĞĐƚŝŶŐ^/WdƌƵŶŬ^ĞĐƵƌŝƚLJWƌŽĨŝůĞ
3. The following screen appears:
&ŝŐƵƌĞϮĚĚŝŶŐĂ^/WdƌƵŶŬ^ĞĐƵƌŝƚLJWƌŽĨŝůĞ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
4. Click Find to edit an existing Sip Trunk Profile or click Add New to add a new Sip Trunk
Profile. Note: By default the Outgoing Transport Type is set to TCP. OpenText RightFax
requires UDP.
&ŝŐƵƌĞϯĚŝƚŝŶŐŽƌĚĚŝŶŐĂEĞǁ^/WdƌƵŶŬ^ĞĐƵƌŝƚLJWƌŽĨŝůĞ
5. Change Outgoing Transport Type to UDP.
6. Press Save.
‘ˆ‹‰—”‡ ”—ˆ”‘–‘’‡‡š–‹‰Š– ƒš
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Device | Trunk.
3. The following screen appears:
&ŝŐƵƌĞϰ^ĞůĞĐƚŝŶŐĂĞǀŝĐĞŽƌdƌƵŶŬ
4. Press Add New to add a new SIP Trunk.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϱĚĚŝŶŐĂŶĞǁ^/WdƌƵŶŬ
5. Select the following options and click Next:
a) Trunk Type = SIP Trunk
b) Device Protocol = SIP
c) Trunk Service Type = None (Default)
6. The following screen appears:
&ŝŐƵƌĞϲ^ĞůĞĐƚŝŶŐƚŚĞKƉƚŝŽŶƐĨŽƌ^/WdƌƵŶŬ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϳ^/WdƌƵŶŬ/ŶĨŽƌŵĂƚŝŽŶ
7. Set the following options:
a. Device Name: CUCMSipTrunkToOpenTextFaxServer
b. Device Description: Siptrunk_to_OpenText _Fax _Server
c. Device Pool: Default
d. Call Classification: OffNet
e. Destination Address: 10.64.3.2 (address of OpenText RightFax)
f. SIP Trunk Security Profile: Non Secure SIP Trunk Profile
g. SIP Profile: Standard SIP Profile
8. Click Save.
9. On the next screen, click Reset
&ŝŐƵƌĞϴdƌƵŶŬŽŶĨŝŐƵƌĂƚŝŽŶ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
10. Press Restart then press Close.
&ŝŐƵƌĞϵZĞƐĞƚtŝŶĚŽǁ
‘ˆ‹‰—”‡‹’”—ˆ”‘–‘ ƒ–‡™ƒ›
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Device | Trunk.
3. Press Add New
&ŝŐƵƌĞϭϬĚĚŝŶŐŶĞǁ^/WdƌƵŶŬ
4. The following screen appears:
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϭϭ^/WdƌƵŶŬŽŶĨŝŐƵƌĂƚŝŽŶ
5. Select the following options:
• Trunk Type = SIP Trunk
• Device Protocol = SIP
• Trunk Service Type = None (Default)
6. Click Next.
7. The following screen appears:
&ŝŐƵƌĞϭϮ^/WdƌƵŶŬŽŶĨŝŐƵƌĂƚŝŽŶKƉƚŝŽŶƐ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϭϯ^/WdƌƵŶŬŽŶĨŝŐƵƌĂƚŝŽŶKƉƚŝŽŶƐ
8. Set the following options:
a. Device Name: cucm-gw
b. Device Description: Trunk between CUCM and GW
c. Device Pool: Default
d. Call Classification: OffNet
e. Destination Address: 10.64.1.72
f. SIP Trunk Security Profile: Non Secure SIP Trunk Profile
g. SIP Profile: Standard SIP Profile
Note: Destination Address is the IP address of the Gateway.
9. Save and reset.
Configure Call Routing (From OpenText RightFax to PSTN)
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu, select Call Routing | Route / Hunt | Route Pattern
&ŝŐƵƌĞϭϰ^ĞůĞĐƚŝŶŐZŽƵƚĞWĂƚƚĞƌŶ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
3. Click on Add New to add a new Route Pattern
&ŝŐƵƌĞϭϱĚĚŝŶŐEĞǁZŽƵƚĞWĂƚƚĞƌŶ
4. Route pattern “2222” is the format to send the fax via PSTN
&ŝŐƵƌĞϭϲWĂƚƚĞƌŶĞĨŝŶŝƚŝŽŶƐĨŽƌƚŚĞEĞǁZŽƵƚĞWĂƚƚĞƌŶ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
5. In the Gateway/Route List, enter the IP address (10.64.1.72) of the Voice Gateway sending out Fax
calls.
‘ˆ‹‰—”‡ƒŽŽ‘—–‹‰ȋ ”‘–‘’‡‡š–‹‰Š– ƒšȌ
1. From the Cisco Unified CM Administration screen, select Call Routing | Route Hunt | Route
Pattern.
&ŝŐƵƌĞϭϳ^ĞůĞĐƚŝŶŐZŽƵƚĞWĂƚƚĞƌŶ
2. Click Add New
&ŝŐƵƌĞϭϴĚĚŝŶŐEĞǁZŽƵƚĞWĂƚƚĞƌŶ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
4. The following screen appears:
&ŝŐƵƌĞϭϵĚĚŝŶŐWĂƚƚĞƌŶĞĨŝŶŝƚŝŽŶƐĨŽƌƚŚĞEĞǁZŽƵƚĞWĂƚƚĞƌŶ
Set options as follows:
• Route Pattern: 1111
• Description: CUCM to OpenText RightFax
• Gateway/Route List: Open Text
• Call Classification: OffNet
“1111” in the Route Pattern field will send a fax from PSTN to OpenText RightFax thru CUCM.
4. Click Save and reset.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‡ƒ”‹‘ʹǣ Ǥ͵ʹ͵Ǧ–‘Ǧ Ǥ͵ʹ͵‘ˆ‹‰—”ƒ–‹‘
‹ƒŽŽƒ˜‡”˜‹‡™
To call OpenText RightFax from a POTS phone, dial 99728522627. The call flow and protocol path
behaves as follows:
• POTS (dial 99728522627)
• Cisco Gateway translates the incoming number as 1111—SIP—>
• CUCM 9 dial 1111—SIP—>
• OpenText RightFax.
To call the POTS lines of the Gateway, dial 2222. The call flow and protocol path behaves as follows:
• OpenText RightFax(2222) —SIP—>
• CUCM9 dial 2222—SIP—>
• Cisco Gateway translates 2222 in to 9728522626
• POTS
‹• ‘͵ͺͶͷ ƒ–‡™ƒ›‡–—’‘–‡•
For the sample test configuration, the Cisco 3845 Gateway was configured the Cisco IOS command-line
interface. The specific items configured include:
• Enable T.38 support
• Configure line card interface
• Configure IP Protocol
• Configure Dial-Peers – POTS
• Configure Dial-Peers – VoIP
ƒ„Ž‡Ǥ͵ͺ•—’’‘”–
The following lines allow SIP calls and T.38 fax calls
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
H323
session transport udp
h245 tunnel disable
‘ˆ‹‰—”‡˜‘‹ ‡Ǧ’‘”–
voice-port 0/0/0
station-id name fax test
station-id number 9728522626
caller-id enable
‘ˆ‹‰—”‡‹ƒŽǦ‡‡”•Ȃ
The following allows the phone “9728522626” to be dialed out though the POTS
lines:
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
preference 1
service session
destination-pattern 9728522626
no digit-strip
port 0/0/0
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‘ˆ‹‰—”‡‹ƒŽ‡‡”•Ȃ‘ ǣ
The following allows reaching the Right Fax server :
translation-rule 1111
Rule 1 9728522627
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
preference 1
destination-pattern 9728522627
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.2:5060
session transport udp
codec g711ulaw
fax rate 14400
fax protocol t38 ls-redundancy 2 hs-redundancy
fallback none
Note-Ip address 10.70.1.2 is the ip address of the call manager.
ͻ‡–—’‘–‡•Ȃ Ǥ͵ʹ͵Ȁ Ǥ͵ʹ͵‘ˆ‹‰—”ƒ–‹‘
The following areas of CUCM 9 are modified in this scenario:
• Configure OpenText RightFax Gateway
• Configure Gateway
• Configure Call Routing
Configure H.323 Gateway to OpenText RightFax
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Device | Gateway.
&ŝŐƵƌĞϮϬĚĚŝŶŐĂ,͘ϯϮϯ'ĂƚĞǁĂLJ
3. Press Add New to add a new H.323 Gateway
&ŝŐƵƌĞϮϭĚĚŝŶŐĂEĞǁ,͘ϯϮϯ'ĂƚĞǁĂLJ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
0
4. Select H.323 Gateway and press Next.
&ŝŐƵƌĞϮϮ^ĞůĞĐƚŝŶŐĂEĞǁ,͘ϯϮϯ'ĂƚĞǁĂLJ
5. The following screen appears:
&ŝŐƵƌĞϮϯĚĚŝŶŐĞǀŝĐĞ/ŶĨŽƌŵĂƚŝŽŶ
6. Set the following options:
a. Device Name: 10.64.3.2 (address of OpenText RightFax)
b. Device Description: OpenText
c. Device Pool: Default
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
d. Call Classification: OffNet
7. Save and Reset.
‘ˆ‹‰—”‡ Ǥ͵ʹ͵ ƒ–‡™ƒ›–‘–Š‡‹• ‘‘‹ ‡ ƒ–‡™ƒ›
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Device | Gateway.
3. Press Add New to add a new H.323 gateway
&ŝŐƵƌĞϮϰĚĚŝŶŐĂEĞǁ,͘ϯϮϯ'ĂƚĞǁĂLJ
4. Select H.323 Gateway for the Gateway Type and press Next.
&ŝŐƵƌĞϮϱ^ĞůĞĐƚŝŶŐ,͘ϯϮϯ'ĂƚĞǁĂLJ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
5. The following screen appears:
&ŝŐƵƌĞϮϲĚĚŝŶŐĞǀŝĐĞ/ŶĨŽƌŵĂƚŝŽŶĨŽƌƚŚĞEĞǁ,͘ϯϮϯ'ĂƚĞǁĂLJ
6. Set the following options:
a. Device Name: 10.64.1.72 (address of the Cisco Voice Gateway)
b. Device Description: CUCM 9.0—H323---Gateway 3845
c. Device Pool: Default
d. Call Classification: OffNet
7. Press Save and click on Apply Config.
7. Click OK to close the window and select Reset.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
Configure Call Routing (From OpenText RightFax to PSTN)
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Call Routing | Route / Hunt | Route Pattern.
&ŝŐƵƌĞϮϳ^ĞůĞĐƚŝŶŐZŽƵƚĞWĂƚƚĞƌŶ
3. Click on Add New to add a new Route
&ŝŐƵƌĞϮϴĚĚŝŶŐĂEĞǁZŽƵƚĞWĂƚƚĞƌŶ
4. Route pattern “2222” is the format to send the fax via PSTN
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϮϵĚĚŝŶŐWĂƚƚĞƌŶĞĨŝŶŝƚŝŽŶƐĨŽƌƚŚĞEĞǁZŽƵƚĞWĂƚƚĞƌŶ
5. In the Gateway/Route List, enter the IP address (10.64.1.72) of the Voice Gateway that sends out the
Fax call.
Configure Call Routing (From PSTN to OpenText RightFax)
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. Select Call Routing | Route Hunt | Route Pattern.
&ŝŐƵƌĞϯϬ^ĞůĞĐƚŝŶŐZŽƵƚĞWĂƚƚĞƌŶ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
3. Click on Add New to add a new Route Pattern.
&ŝŐƵƌĞϯϭĚĚŝŶŐĂEĞǁZŽƵƚĞWĂƚƚĞƌŶ
4. “2222” in Route Pattern is used to send faxes from PSTN to OpenText RightFax thru CUCM.
ϱ͘/ŶƚŚĞ'ĂƚĞǁĂLJͬZŽƵƚĞ>ŝƐƚ͕ĞŶƚĞƌƚŚĞ/WĂĚĚƌĞƐƐ;ϭϬ͘ϲϰ͘ϯ͘ϮͿŽĨKƉĞŶdĞdžƚZŝŐŚƚ&Ădž͘
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‡ƒ”‹‘͵ǣ Ǧ–‘Ǧ ‘ˆ‹‰—”ƒ–‹‘
‹ƒŽŽƒ˜‡”˜‹‡™
To call OpenText RightFax from a POTS phone, dial 99728522627. The call flow and protocol path
behaves as follows:
• POTS (dial 99728522627)
• Cisco Gateway translates the incoming number as 1111—SIP—>
• CUCM 9 dial 1111—SIP—>
• OpenText RightFax.
To call the POTS lines of the Gateway, dial 2222. The call flow and protocol path behaves as follows:
• OpenText RightFax(2222) —SIP—>
CUCM route pattern 2222-> Called Party Transform Mask- 9728522626->SIP
• POTS
‹• ‘͵ͺͶͷ ƒ–‡™ƒ›‡–—’‘–‡•
For the sample test configuration, the Cisco 3845 Gateway was configured the Cisco IOS command-line
interface. The specific items configured include:
• Enable T.38 support
• Configure line card interface
• Configure IP Protocol
• Configure Dial-Peers – POTS
• Configure Dial-Peers – VoIP
Enable T.38 support
The following lines allow SIP calls and T.38 fax calls
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
SIP
‘ˆ‹‰—”‡Ž‹‡ ƒ”†‹–‡”ˆƒ ‡
controller E1 0/0/0
clock source internal
pri-group timeslots 1-31 service mgcp
‘ˆ‹‰—”‡‹ƒŽ‡‡”•Ȃ‘ ǣ
The following allows reaching the Right Fax server:
translation-rule 1111
Rule 1 9728522627
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
preference 1
destination-pattern 9728522627
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.2:5060
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
session transport udp
codec g711ulaw
fax rate 14400
fax protocol t38 ls-redundancy
fallback none
2
hs-redundancy
0
Note-Ip address 10.70.1.2 is the ip address of the call
manager.
Configure MGCP
When enabling MGCP, first configure the following basic router information:
• Hostname
•
IP addressing
•
Routing information
The next steps to configure MGCP are
• Enable MGCP
•
Specify how to reach the call agent
•
Specify that the call agent is a Cisco Communications Manager.
Enter the following commands in Global Configuration Mode to allow MGCP calls:
ccm-manager mgcp
!Note: The following command enables music on hold so off-net callers
receive streaming music as multicast, rather than unicast:
ccm-manager music-on-hold
ccm-manager config server 10.70.1.2
!
mgcp
mgcp call-agent 10.70.1.2 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp default-package fxr-package
!
mgcp profile default
Notes:
• 10.70.1.2 is the IP address of the CUCM.
• Verify that mgcp fax t38 inhibit does not exist, as it disables T.38
‘ˆ‹‰—”‡‹ƒŽǦ‡‡”•Ȃ
Next, you must bind MGCP to the voice ports:
• Configure a dial peer for each voice port
•
Binding MGCP to it using the application MGCPAPP command. Note: This command is case
sensitive in some IOS releases. If you are unsure, use all capital letters.
‘ˆ‹‰—”‡‹ƒŽǦ‡‡”•Ȃ
The following allows the phone “9728522626” to be dialed out though the POTS
lines:
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
preference 1
service mgcp
destination-pattern 9728522626
no digit-strip
port 0/0/0:15
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
ͻ‡–—’‘–‡•Ȃ Ȁ ‘ˆ‹‰—”ƒ–‹‘
Configuration of CUCM 9 consists of the following steps:
•
•
•
Configure SIP Trunk Security Profile
Configure Sip Trunk from CUCM to OpenText RightFax
Configure MGCP Gateway
‘ˆ‹‰—”‡ ”—‡ —”‹–›”‘ˆ‹Ž‡
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select System | Security Profile | SIP Trunk Security Profile.
&ŝŐƵƌĞϯϮ^ĞůĞĐƚŝŶŐĂ^/WdƌƵŶŬ^ĞĐƵƌŝƚLJWƌŽĨŝůĞ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
3. The following screen appears:
&ŝŐƵƌĞϯϯĚĚŝŶŐĂ^/WdƌƵŶŬ^ĞĐƵƌŝƚLJWƌŽĨŝůĞ
4. Click Find to edit an existing Sip Trunk Profile or click on Add New to add a new Sip Trunk Profile.
The following screen appears:
&ŝŐƵƌĞϯϰĚĚŝŶŐĂEĞǁ^/WdƌƵŶŬ^ĞĐƵƌŝƚLJWƌŽĨŝůĞ
5. Change Outgoing Transport Type to UDP. Note: UDP is required by OpenText RightFax.
6. Press Save and Reset, then press Close.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‘ˆ‹‰—”‡–Š‡ ”—ˆ”‘–‘’‡‡š–‹‰Š– ƒš
1. Using a web browser, log into the Cisco Unified CM Administration screen.
&ŝŐƵƌĞϯϱDĂŝŶ^ĐƌĞĞŶĂĨƚĞƌ>ŽŐŝŶ
2. From the menu select Device | Trunk.
&ŝŐƵƌĞϯϲ^ĞůĞĐƚŝŶŐĞǀŝĐĞŽƌdƌƵŶŬ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
3. The following screen appears:
&ŝŐƵƌĞϯϳĚĚŝŶŐĂEĞǁĞǀŝĐĞŽƌdƌƵŶŬ
4. Press Add New to add a new SIP Trunk.
&ŝŐƵƌĞϯϴĚĚŝŶŐĂEĞǁ^/WdƌƵŶŬ
5. Select the following options and click Next:
• Trunk Type = SIP Trunk
• Device Protocol = SIP
• Trunk Service Type = None (Default)
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
6. The following screen appears:
&ŝŐƵƌĞϯϵĞǀŝĐĞ/ŶĨŽƌŵĂƚŝŽŶĨŽƌdƌƵŶŬŽŶĨŝŐƵƌĂƚŝŽŶ
&ŝŐƵƌĞϰϬ/ŶĨŽƌŵĂƚŝŽŶĨŽƌdƌƵŶŬŽŶĨŝŐƵƌĂƚŝŽŶ
Set the following options:
• Device Name: CUCMSipTrunkToOpenTextFaxServer
• Device Description: Siptrunk_to_OpenText _Fax _Server
• Device Pool: Default
• Call Classification: OffNet
• Destination Address: 10.64.3.2 (address of OpenText RightFax)
• SIP Trunk Security Profile: Non Secure SIP Trunk Profile
• SIP Profile: Standard SIP Profile
8. Press Save and Reset.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‘ˆ‹‰—”‡ ƒ–‡™ƒ›
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Device | Gateway
&ŝŐƵƌĞϰϭĚĚŝŶŐĂĞǀŝĐĞŽƌ'ĂƚĞǁĂLJ
3. Press Add New to add a new Gateway.
&ŝŐƵƌĞϰϮĚĚŝŶŐĂEĞǁ'ĂƚĞǁĂLJ
5. Select the Gateway Type. For MGCP gateways, choose the device type (router model or voice
gateway). In this example, a Cisco 3845 router was selected. Note: You cannot configure
Communication Manager to recognize the same device as both an MGCP and an H.323 gateway.
6. Next, set Protocol to MGCP and click Next. &ŝŐƵƌĞϰϯ^ĞƚƚŝŶŐƚŚĞWƌŽƚŽĐŽů
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
7. The Gateway Configuration screen appears: &ŝŐƵƌĞϰϰ'ĂƚĞǁĂLJŽŶĨŝŐƵƌĂƚŝŽŶƐ
8. Under Gateway Details, enter the following information:
a. Domain Name: Enter hostname of the router. Important information:
i. MGCP gateways are identified by hostname, not IP address.
ii. If the router is configured with a domain name, append it to the hostname, such as router1.lab.
tekvizion.com
iii. The name is case sensitive.
b. Description (optional): Enter optional description string.
c. Cisco Unified Communications Manager Group (required): Choose a group, or set as Default.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
9. On the next screen, reset the gateway by clicking Reset then click Close. Note: Resetting the MGCP
gateway drops all in-process calls on the gateway.
&ŝŐƵƌĞϰϱĞǀŝĐĞZĞƐĞƚ
‘ˆ‹‰—”‡ƒŽŽ‘—–‹‰ȋ’‡‡š–‹‰Š– ƒš–‘Ȍ
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2.
From the menu select Call Routing | Route / Hunt | Route Pattern.
&ŝŐƵƌĞϰϲ^ĞůĞĐƚŝŶŐZŽƵƚĞWĂƚƚĞƌŶ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
3. Click Add New to add a new Route Pattern
&ŝŐƵƌĞϰϳĚĚŝŶŐEĞǁZŽƵƚĞWĂƚƚĞƌŶ
4. The following screen appears:
&ŝŐƵƌĞϰϴWĂƚƚĞƌŶĞĨŝŶŝƚŝŽŶƐ
5. Set Route Pattern to “2222” to send faxes via the E1 (PSTN).
6. In this scenario, Gateway/Route List is S0/SUO/DS1-0@router1.lab.tekvizion.com (the MGCP Trunk
of the Gateway).
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‘ˆ‹‰—”‡ƒŽŽ‘—–‹‰ȋ–‘’‡‡š–‹‰Š– ƒšȌ
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. Select Call Routing | Route Hunt | Route Pattern.
&ŝŐƵƌĞϰϵ^ĞůĞĐƚŝŶŐZŽƵƚĞWĂƚƚĞƌŶ
ϯ͘Click on Add New to add a new Route Pattern
&ŝŐƵƌĞϱϬĚĚŝŶŐEĞǁZŽƵƚĞWĂƚƚĞƌŶ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
4. The following screen appears:
&ŝŐƵƌĞϱϭWĂƚƚĞƌŶĞĨŝŶŝƚŝŽŶƐ
5. Set the following options:
a. Route Pattern: “1111” (where faxes can be sent from the PSTN to OpenText RightFax via the
CUCM).
b. Gateway/Route List: Enter the Sip trunk created to OpenText RightFax
6. Click Save to save the configuration changes.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‡ƒ”‹‘Ͷǣ Ǥ͵ʹ͵Ǧ–‘Ǧ ‘ˆ‹‰—”ƒ–‹‘
‹ƒŽŽƒ˜‡”˜‹‡™
To call OpenText RightFax from a POTS phone, dial 99728522627. The call flow and protocol path
behaves as follows:
• POTS (dial 99728522627)
• Cisco Gateway translates the incoming number as 1111—SIP—>
• CUCM 9 dial 1111—SIP—>
• OpenText RightFax.
•
•
•
•
•
To call the POTS lines of the Gateway, dial 2222. The call flow and protocol path behaves as
follows:
OpenText RightFax(2222) —SIP—>
CUCM9 dial 2222—SIP—>
Cisco Gateway translates 2222 in to 9728522626
POTS
‹• ‘͵ͺͶͷ ƒ–‡™ƒ›‡–—’‘–‡•
For the sample test configuration, the Cisco 3845 Gateway was configured the Cisco IOS command-line
interface. The specific items configured include:
• Enable T.38 support
• Configure line card interface
• Configure IP Protocol
• Configure Dial-Peers – POTS
• Configure Dial-Peers – VoIP
ƒ„Ž‡Ǥ͵ͺ•—’’‘”–
The following lines allow SIP calls and T.38 fax calls
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
H323
session transport udp
h245 tunnel disable
‘ˆ‹‰—”‡Ž‹‡ ƒ”†‹–‡”ˆƒ ‡
controller E1 0/0/0
clock source internal
pri-group timeslots 1-31 service mgcp
‘ˆ‹‰—”‡‹ƒŽ‡‡”•Ȃ‘ ǣ
The following allows reaching the Right Fax server :
translation-rule 1111
Rule 1 9728522627
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
preference 1
destination-pattern 9728522627
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.2:5060
session transport udp
codec g711ulaw
fax rate 14400
fax protocol t38 ls-redundancy 2
fallback none
hs-redundancy
0
Note-Ip address 10.70.1.2 is the ip address of the call manager.
‘ˆ‹‰—”‡ When enabling MGCP, first configure the following basic router information:
• Hostname
•
IP addressing
•
Routing information
The next steps to configure MGCP are
• Enable MGCP
•
Specify how to reach the call agent
•
Specify that the call agent is a Cisco Communications Manager.
Enter the following commands in Global Configuration Mode to allow MGCP calls:
ccm-manager mgcp
!Note: The following command enables music on hold so off-net callers
receive streaming music as multicast, rather than unicast:
ccm-manager music-on-hold
ccm-manager config server 10.70.1.2
!
mgcp
mgcp call-agent 10.70.1.2 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp default-package fxr-package
!
mgcp profile default
Notes:
• 10.70.1.2 is the IP address of the CUCM.
• Verify that mgcp fax t38 inhibit does not exist, as it disables T.38
‘ˆ‹‰—”‡‹ƒŽǦ‡‡”•Ȃ
Next, you must bind MGCP to the voice ports:
• Configure a dial peer for each voice port
•
Binding MGCP to it using the application MGCPAPP command. Note: This command is case
sensitive in some IOS releases. If you are unsure, use all capital letters.
‘ˆ‹‰—”‡‹ƒŽǦ‡‡”•Ȃ
The following allows the phone “9728522626” to be dialed out though the POTS
lines:
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
preference 1
service mgcp
destination-pattern 9728522626
no digit-strip
port 0/0/0:15
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
ͻ‡–—’‘–‡•Ȃ Ȁ ͵ʹ͵‘ˆ‹‰—”ƒ–‹‘
Configuration of CUCM 9 consists of the following steps:
• Configure H323 Gateway from CUCM to OpenText RightFax
• Configure MGCP Gateway
‘ˆ‹‰—”‡’‡‡š–‹‰Š– ƒš ƒ–‡™ƒ›
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Device | Gateway
&ŝŐƵƌĞϱϮ^ĞůĞĐƚŝŶŐĞǀŝĐĞŽƌ'ĂƚĞǁĂLJ
3.Press Add New to add a new H.323 Gateway.
&ŝŐƵƌĞϱϯĚĚŝŶŐĂEĞǁ,͘ϯϮϯ'ĂƚĞǁĂLJ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
4. Select H.323 Gateway and press Next.
&ŝŐƵƌĞϱϰ^ĞůĞĐƚŝŶŐ,͘ϯϮϯ'ĂƚĞǁĂLJ
5. The following screen appears:
&ŝŐƵƌĞϱϱĞǀŝĐĞ/ŶĨŽƌŵĂƚŝŽŶ
6. Set the following options:
a. Device Name: 10.64.3.2 (address of OpenText RightFax)
b. Device Description: H323 Gateway to OpenText RightFax
c. Device Pool: Default
d. Call Classification: OffNet
7. Save and apply the configuration.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‘ˆ‹‰—”‡ ƒ–‡™ƒ›
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Device | Gateway.
&ŝŐƵƌĞϱϲĚĚŝŶŐĂĞǀŝĐĞŽƌ'ĂƚĞǁĂLJ
3. Press Add New to add a new H.323 Gateway.
4. The following screen appears: &ŝŐƵƌĞϱϳĚĚŝŶŐĂEĞǁ,͘ϯϮϯ'ĂƚĞǁĂLJ
&ŝŐƵƌĞϱϴ^ĞůĞĐƚƚŚĞƚLJƉĞŽĨ,͘ϯϮϯ'ĂƚĞǁĂLJ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
5. Select the Gateway Type. For MGCP gateways, choose the device type (router model or voice
gateway). In this example, a Cisco 3845 router was selected. Note: You cannot configure
Communication Manager to recognize the same device as both an MGCP and an H.323 gateway.
6. Next, set Protocol to MGCP and click Next.
&ŝŐƵƌĞϱϵ^ĞůĞĐƚƚŚĞWƌŽƚŽĐŽů
7. The Gateway Configuration screen appears: &ŝŐƵƌĞϲϬ'ĂƚĞǁĂLJŽŶĨŝŐƵƌĂƚŝŽŶƐ
8. Under Gateway Details, enter the following information:
a. Domain Name: Enter hostname of the router. Important information:
i. MGCP gateways are identified by hostname, not IP address.
ii. If the router is configured with a domain name, append it to the hostname, such as
router1.lab.tekvizion.com
iii. The name is case sensitive.
b. Description (optional): Enter optional description string.
c. Cisco Unified Communications Manager Group (required): Choose a group, or set as Default.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
9. On the next screen, reset the gateway by clicking Reset then click Close. Note: Resetting the MGCP
gateway drops all in-process calls on the gateway.
&ŝŐƵƌĞϲϭĞǀŝĐĞZĞƐĞƚ
‘ˆ‹‰—”‡ƒŽŽ‘—–‹‰’‡‡š–‹‰Š– ƒš–‘
1. Using a web browser, log into the Cisco Unified CM Administration screen.
2. From the menu select Call Routing | Route / Hunt | Route Pattern.
&ŝŐƵƌĞϲϮĚĚĂZŽƵƚĞWĂƚƚĞƌŶ
3. Click on Add New to add a new Route Pattern.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϲϯĚĚĂEĞǁZŽƵƚĞWĂƚƚĞƌŶ
4. The following screen appears: &ŝŐƵƌĞϲϰWĂƚƚĞƌŶĞĨŝŶŝƚŝŽŶ
5. Set Route Pattern to “2222” to send faxes via the E1 (PSTN).
6. In this scenario, Gateway/Route List is S0/SUO/DS1-0@router1.lab.tekvizion.com (the MGCP Trunk
of the Gateway).
‘ˆ‹‰—”‡ƒŽŽ‘—–‹‰ȋ–‘’‡‡š–‹‰Š– ƒšȌ
7. Using a web browser, log into the Cisco Unified CM Administration screen.
8. Select CallRouting | Route Hunt | Route Pattern.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϲϱ^ĞůĞĐƚŝŶŐZŽƵƚĞWĂƚƚĞƌŶ
9. Click on Add New to add a new Route Pattern
&ŝŐƵƌĞϲϲĚĚŝŶŐEĞǁZŽƵƚĞWĂƚƚĞƌŶ
10. The following screen appears:
&ŝŐƵƌĞϲϳĚĚŝŶŐWĂƚƚĞƌŶĞĨŝŶŝƚŝŽŶƐ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
11. Set the following options:
a. Route Pattern: “1111” (where faxes can be sent from the PSTN to OpenText RightFax via the
CUCM).
b. Gateway/Route List: Enter the IP address of OpenText RightFax.
12. Click Save to save the configuration changes
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‹• ‘‹–›‘‡ –‹‘‘ˆ‹‰—”ƒ–‹‘Ȁ –‡‰”ƒ–‹‘™‹–Š ƒš
ŽŽ‘™‹• ‘‹–›‘‡ –‹‘–‘ ‡••–Š‡ ††”‡•• ‡••‘ˆ–Š‡‹• ‘ ƒš‡”˜‡”
1. In Cisco Unity Connection Administration, expand System Settings, then select SMTP
2. Configuration > Server.
3. On the SMTP Server Configuration page, in the Edit menu, select Search IP Address Access
List.
4. On the Search IP Address Access List page, select Add New.
5. On the New Access IP Address page, in the IP Address field, enter the IP address of the Cisco
Fax Server.
6. Select Save.
ϳ͘ Check the Allow Connection check box and select Save.
&ŝŐƵƌĞϲϴ&Ădž^ĞƌǀĞƌ/WĚĚƌĞƐƐĐĐĞƐƐ
ƒ„Ž‡–Š‡‹• ‘ ƒš‡”˜‡” –‡‰”ƒ–‹‘‘‹• ‘‹–›‘‡ –‹‘
1. In Cisco Unity Connection Administration, expand System Settings, then select Fax Server.
2. On the Edit Fax Server page, check the Enabled check box.
3. In the Fax Server Name field, enter a descriptive name for the Cisco Fax Server.
4. In the SMTP Address field, enter the fully qualified SMTP address of the SMTP server on the
Cisco Fax Server.[ This fully qualified SMTP address must match the server address and domain
that are configured for the POP3 mailbox on the Cisco Fax Server. Otherwise, the integration will
not function correctly.]
5. In the IP Address field, enter the IP address of the Cisco Fax Server.
6. Select Save.
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϲϵ&Ădž^ĞƌǀĞƌŽŶĨŝŐƵƌĂƚŝŽŶ͗ŶĂďůŝŶŐ
—•–‘‹œ‡–Š‡‹• ‘ ƒš‡”˜‡” –‡‰”ƒ–‹‘‘‹• ‘‹–›‘‡ –‹‘
1. In Cisco Unity Connection Administration, expand System Settings, then select Advanced >
Fax.
2. In the Fax Configuration page, in the Faxable File Types field, enter the file extensions
(separated by a comma) that Connection keeps in messages that are delivered to the Cisco Fax
Server. Connection removes all files with other file extensions before delivering the message to
the Cisco Fax Server.
3. In the Subject Prefix for Notification of a Successful Fax field, enter the prefix that the Cisco Fax
Server adds to the Subject field of fax reports. When Connection detects this prefix, it generates a
delivery receipt and places it in the user mailbox.
4. In the Subject Prefix for Notification of a Failed Fax field, enter the prefix that the Cisco Fax
Server adds to the Subject field of fax reports. When Connection detects this prefix, it generates a
non-delivery receipt and places it in the user mailbox.
5. Select Save.
&ŝŐƵƌĞϳϬ&ĂdžŽŶĨŝŐƵƌĂƚŝŽŶ͗&ŝůĞdžƚĞŶƐŝŽŶƐ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‘ˆ‹‰—”‹‰‹• ‘‹–›‘‡ –‹‘•‡”•ˆ‘”–Š‡‹• ‘ ƒš‡”˜‡” –‡‰”ƒ–‹‘
Note: The Cisco Fax Server must have a subscriber for each Connection user that you are configuring.
While on the phone, users can add or change the number for the fax machine that they send faxes to for
printing.
‘‘ˆ‹‰—”‡•‡”•
1. In Cisco Unity Connection Administration, expand Users, then select Users.
2. On the Search Users page, select the alias of a user.
3. On the Edit User Basics page, in the Outgoing Fax Number field, enter the number for the fax
machine that users send faxes to for printing.
4. In the Outgoing Fax Server field, select the name of the Cisco Fax Server.
5. In the Phone System, select the name of the Phone System configured to integrate with CUCM.
6. In the Class of Service, select the Class of Service that the user intends to be part of .The “Voice
Mail User COS” was used for testing.
7. Select Save.
&ŝŐƵƌĞϳϭŽŶĨŝŐƵƌŝŶŐŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶhƐĞƌƐ;ϭͬϮͿ
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϳϮŽŶĨŝŐƵƌŝŶŐŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶhƐĞƌƐ;ϮͬϮͿ
‘ˆ‹‰—”‹‰Žƒ••‘ˆ‡”˜‹ ‡ǣ
ϭ͘ In Cisco Unity Connection Administration, expand Class of Service, then select Class of Service.
Ϯ͘ Select Voice Mail User COS(assuming it was already created, else add/configure one) 3. Apart from the default settings, check the following checkboxes:
a. Allow Users to Access Voice Mail Using an IMAP Client and/or Single Inbox
i. Allow IMAP Users to Access Message Bodies
b. Allow Users to Use the Web Inbox and RSS Feeds
c. Allow Access to Advanced Features
i. Allow Access to Exchange Email by Using Text to Speech (TTS)
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϳϯŽŶĨŝŐƵƌŝŶŐŝƐĐŽhŶŝƚLJŽŶŶĞĐƚŝŽŶhƐĞƌ͛ƐůĂƐƐŽĨ^ĞƌǀŝĐĞ
‡••‹‰–Š‡™‡„‹„‘šƒ†˜‹‡™‹‰‡••ƒ‰‡•
1. Access a user’s web inbox via the url : https://<CUC IP>/inbox
2. Provide access credentials as configured for the user (web application password)
3. The voice messages and fax messages sent to the user can now be accessed as seen in the
screenshot below:
a. A successful fax received by the user is shown as “A Fax arrived from remote id “<>””
4. The user can browse through his voice mail on the phone and choose to forward a received fax
for printing. The user is prompted to confirm the fax number configured earlier or forward to a
new fax number. On initiating a forward request, the request is queued. The Right Fax server
then forwards this fax for printing.
a. If it was successfully printed, the user receives an email with prefix [Fax Success] (see
below screenshot)
b. If there was an error in printing the fax, the user receives the notification in the form of
an email with prefix [Fax Failure] (see below screenshot)
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
&ŝŐƵƌĞϳϰhƐĞƌ͛ƐǁĞďŝŶďŽdž
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‘ƒ†‡•–‘ˆ‹‰—”ƒ–‹‘ǣ
‡ƒ”‹‘ͳȂ –‘ ‘ˆ‹‰—”ƒ–‹‘ǣ
CUCM’s SIP trunk, Routing configuration remains the same as shown earlier under the SIP to SIP
section.
Load test was performed using the loop back scenario between two cisco voice gateways, where we used
two e1 line’s to utilize 30 channels for transmission(sending fax) and remaining 30 channel’s for
receiving fax purpose.
‡ƒ”‹‘ǣ
•
•
•
•
•
•
•
Cisco gateways, 3845 and 3825 configured in a loop back mode as described above,
Open Text fax Server sends a batch of faxes to the destination 2222.
CUCM transforms 2222 to 9728522626 and send it to Cisco 3845.
Cisco 3845 gateway forwards the same destination number(9728522626) to 3825 gateway
through the E1 connectivity.
Cisco 3825 receives the requests and transforms the incoming number (9728522626) as
19728522626 and sends back to C3845.
Cisco 3845 gateway receives the request and transforms the number to 1111 and sends to CUCM.
CUCM sends the request to the Open Text Right Fax Server.
ƒ–‡™ƒ›ͳǣ‹• ‘͵ͺͶͷ
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
SIP
controller E1 1/0
pri-group timeslots 1-31
controller E1 1/1
pri-group timeslots 1-31
translation-rule 73
Rule 1 9728522621 2621
Rule 2 19728522626 1111
interface Serial1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn timer T310 120000
isdn not-end-to-end 64
isdn protocol-emulate network
isdn incoming-voice voice
isdn map address .* plan isdn type national no cdp enable !
interface Serial1/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
isdn map address .* plan isdn type national
isdn bind-l3 ccm-manager
no cdp enable
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
preference 1
destination-pattern 9728522627
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
huntstop
preference 1
service session
destination-pattern ^9728522626$
no digit-strip
direct-inward-dial port 1/0:15
dial-peer voice 3335 voip
description outgoing dialpeer for call to cucm for opentext-load
huntstop
destination-pattern 19728522626
translate-outgoing called 73
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
dial-peer voice 3334 pots
description incoming dialpeer for call from 3825 to route to cucm
service session
incoming called-number 19728522626
no digit-strip
direct-inward-dial
port 1/1:15
ƒ–‡™ƒ›ʹȂ‹• ‘͵ͺʹͷ
controller E1 1/0
clock source internal
pri-group timeslots 1-31
controller E1 1/1
clock source internal
pri-group timeslots 1-31
voice translation-rule 13
rule 1 /^\(..........\)/ /1\1/
rule 2 /9728522626/ /19728522626/
!
!
voice translation-profile addone
translate called 13
!
dial-peer voice 3333 pots
description Opentext dial peer for incoming fax from 3845
translation-profile incoming addone
service session
incoming called-number 9728522626
no digit-strip
direct-inward-dial
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
port 1/0:15
dial-peer voice 3334 pots
description outgoing dialpeer to loop back to cucm via 3845 service
session destination-pattern 1..........
no digit-strip
direct-inward-dial
port 1/1:15
‡ƒ”‹‘ʹȂ Ǥ͵ʹ͵–‘ Ǥ͵ʹ͵‘ˆ‹‰—”ƒ–‹‘ǣ
CUCM’s Gateway, Routing configuration remains the same as shown earlier under the H.323 to H.323
section.
Load test was performed using the loop back scenario between two cisco voice gateways, where we used
two e1 line’s to utilize 30 channels for transmission(sending fax) and remaining 30 channel’s for
receiving fax purpose.
‡ƒ”‹‘ǣ
•
•
•
•
•
•
•
Cisco gateways, 3845 and 3825 configured in a loop back mode as described above,
Open Text fax Server sends a batch of faxes to the destination 2222.
CUCM transforms it to 9728522626 to Cisco 3845.
Cisco 3845 gateway forwards the same destination number (9728522626) to 3825 gateway
through the E1 connectivity.
Cisco 3825 receives the requests and transforms the incoming number (9728522626) as
19728522626 and sends back to C3845.
Cisco 3845 gateway receives the request and transforms the number to 1111 and sends to CUCM.
CUCM sends the request to the Open Text Right Fax Server.
ƒ–‡™ƒ›ͳǣ‹• ‘͵ͺͶͷ
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
H323
controller E1 1/0
pri-group timeslots 1-31
controller E1 1/1
pri-group timeslots 1-31
translation-rule 73
Rule 1 9728522621 2621
Rule 2 19728522626 1111
interface Serial1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn timer T310 120000
isdn not-end-to-end 64
isdn protocol-emulate network
isdn incoming-voice voice
isdn map address .* plan isdn type national no cdp enable !
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
interface Serial1/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
isdn map address .* plan isdn type national
isdn bind-l3 ccm-manager
no cdp enable
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
preference 1
destination-pattern 9728522627
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
huntstop
preference 1
service session
destination-pattern ^9728522626$
no digit-strip
direct-inward-dial
port 1/0:15
dial-peer voice 3335 voip
description outgoing dialpeer for call to cucm for opentext-load
huntstop
destination-pattern 19728522626
translate-outgoing called 73
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
dial-peer voice 3334 pots
description incoming dialpeer for call from 3825 to route to cucm
service session
incoming called-number 19728522626
no digit-strip
direct-inward-dial
port 1/1:15
ƒ–‡™ƒ›ʹȂ‹• ‘͵ͺʹͷ
controller E1 1/0
clock source internal
pri-group timeslots 1-31
controller E1 1/1
clock source internal
pri-group timeslots 1-31
voice translation-rule 13
rule 1 /^\(..........\)/ /1\1/
rule 2 /9728522626/ /19728522626/
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
!
!
voice translation-profile addone
translate called 13
!
dial-peer voice 3333 pots
description Opentext dial peer for incoming fax from 3845
translation-profile incoming addone
service session
incoming called-number 9728522626
no digit-strip
direct-inward-dial
port 1/0:15
dial-peer voice 3334 pots
description outgoing dialpeer to loop back to cucm via 3845 service
session destination-pattern 1..........
no digit-strip
direct-inward-dial
port 1/1:15
‡ƒ”‹‘͵Ȃ –‘ ‘ˆ‹‰—”ƒ–‹‘ǣ
CUCM’s SIP trunk with Open Text ,MGCP Gateway connectivity with Cisco Voice gateway 3845and
Routing configuration remains the same as shown earlier under the SIP to MGCP section.
Load test was performed using the loop back scenario between two cisco voice gateways, where we used
two e1 line’s to utilize 30 channels for transmission(sending fax) and remaining 30 channel’s for
receiving fax purpose.
‡ƒ”‹‘ǣ
•
•
•
•
•
•
•
Cisco gateways, 3845 and 3825 configured in a loop back mode as described above,
Open Text fax Server sends a batch of faxes to the destination 2222.
CUCM transforms it to 9728522626 to Cisco 3845.
Cisco 3845 gateway will forward the same destination number(9728522626) to 3825 gateway
through the E1 connectivity.
Cisco 3825 receives the requests and transforms the incoming number (9728522626) as
19728522626 and sends back to C3845.
Cisco 3845 gateway receives the request and transforms the number to 1111 and sends to CUCM.
CUCM sends the request to the Open Text Right Fax Server.
ƒ–‡™ƒ›ͳǣ‹• ‘͵ͺͶͷ
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
SIP
ccm-manager music-on-hold
ccm-manager config server 10.70.1.2
!
mgcp
mgcp call-agent 10.70.1.2 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp default-package fxr-package
!
mgcp profile default
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
controller E1 1/0
pri-group timeslots 1-31 service mgcapp
controller E1 1/1
pri-group timeslots 1-31 service mgcapp
translation-rule 73
Rule 1 9728522621 2621
Rule 2 19728522626 1111
interface Serial1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
isdn map address .* plan isdn type national
isdn bind-l3 ccm-manager
no cdp enable
interface Serial1/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
isdn map address .* plan isdn type national
isdn bind-l3 ccm-manager
no cdp enable
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
preference 1
destination-pattern 9728522627
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
huntstop
preference 1
service session
destination-pattern ^9728522626$
no digit-strip
direct-inward-dial
port 1/0:15
dial-peer voice 3335 voip
description outgoing dialpeer for call to cucm for opentext-load
huntstop
destination-pattern 19728522626
translate-outgoing called 73
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
dial-peer voice 3334 pots
description incoming dialpeer for call from 3825 to route to cucm
service session
incoming called-number 19728522626
no digit-strip
direct-inward-dial
port 1/1:15
ƒ–‡™ƒ›ʹȂ‹• ‘͵ͺʹͷ
controller E1 1/0
clock source internal
pri-group timeslots 1-31 service mgcapp
controller E1 1/1
clock source internal
pri-group timeslots 1-31 service mgcapp
voice translation-rule 13
rule 1 /^\(..........\)/ /1\1/
rule 2 /9728522626/ /19728522626/
!
!
voice translation-profile addone
translate called 13
!
dial-peer voice 3333 pots
description Opentext dial peer for incoming fax from 3845
translation-profile incoming addone
service session
incoming called-number 9728522626
no digit-strip
direct-inward-dial
port 1/0:15
dial-peer voice 3334 pots
description outgoing dialpeer to loop back to cucm via 3845 service session
destination-pattern 1..........
no digit-strip
direct-inward-dial
port 1/1:15
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
‡ƒ”‹‘ͶȂ ͵ʹ͵–‘ ‘ˆ‹‰—”ƒ–‹‘ǣ
Call Manager H323 Gateway with Open Text ,MGCP Gateway connectivity with Cisco Voice gateway
3845and Routing configuration remains the same as shown earlier under the H323 to MGCP section.
Load test was performed using the loop back scenario between two cisco voice gateways, where we used
two e1 line’s to utilize 30 channels for transmission(sending fax) and remaining 30 channel’s for
receiving fax purpose.
‡ƒ”‹‘ǣ
•
•
•
•
•
•
•
Cisco gateways, 3845 and 3825 configured in a loop back mode as described above,
Open Text fax Server sends a batch of faxes to the destination 2222.
CUCM transforms it to 9728522626 to Cisco 3845.
Cisco 3845 gateway forwards the same destination number(9728522626) to 3825 gateway
through the E1 connectivity.
Cisco 3825 receives the requests and transforms the incoming number (9728522626) as
19728522626 and sends back to C3845.
Cisco 3845 gateway receives the request and transforms the number to 1111 and sends to CUCM.
CUCM sends the request to the Open Text Right Fax Server.
ƒ–‡™ƒ›ͳǣ‹• ‘͵ͺͶͷ
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none
H323
ccm-manager music-on-hold
ccm-manager config server 10.70.1.2
!
mgcp
mgcp call-agent 10.70.1.2 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp default-package fxr-package
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
!
mgcp profile default
controller E1 1/0
pri-group timeslots 1-31 service mgcapp
controller E1 1/1
pri-group timeslots 1-31 service mgcapp
translation-rule 73
Rule 1 9728522621 2621
Rule 2 19728522626 1111
interface Serial1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
isdn map address .* plan isdn type national
isdn bind-l3 ccm-manager
no cdp enable
interface Serial1/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
isdn map address .* plan isdn type national
isdn bind-l3 ccm-manager
no cdp enable
dial-peer voice 8522627 voip
description fax from pstn to opentext via cucm
preference 1
destination-pattern 9728522627
translate-outgoing called 1111
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
dial-peer voice 9722626 pots
description fax from opentext to pstn via cucm
huntstop
preference 1
service session
destination-pattern ^9728522626$
no digit-strip
direct-inward-dial
port 1/0:15
dial-peer voice 3335 voip
description outgoing dialpeer for call to cucm for opentext-load
huntstop
destination-pattern 19728522626
translate-outgoing called 73
session protocol sipv2
session target ipv4:10.70.1.2
session transport udp
codec g711ulaw
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through
g711ulaw
dial-peer voice 3334 pots
description incoming dialpeer for call from 3825 to route to cucm
service session
incoming called-number 19728522626
no digit-strip
direct-inward-dial
port 1/1:15
ƒ–‡™ƒ›ʹȂ‹• ‘͵ͺʹͷ
controller E1 1/0
clock source internal
pri-group timeslots 1-31 service mgcapp
controller E1 1/1
clock source internal
pri-group timeslots 1-31 service mgcapp
voice translation-rule 13
rule 1 /^\(..........\)/ /1\1/
rule 2 /9728522626/ /19728522626/
!
!
voice translation-profile addone
translate called 13
!
dial-peer voice 3333 pots
description Opentext dial peer for incoming fax from 3845
translation-profile incoming addone
service session
incoming called-number 9728522626
no digit-strip
direct-inward-dial
port 1/0:15
dial-peer voice 3334 pots
description outgoing dialpeer to loop back to cucm via 3845 service
session destination-pattern 1..........
no digit-strip
direct-inward-dial
port 1/1:15
ƚĞŬsŝnjŝŽŶWs^͕/ŶĐ͘ŽŶĨŝĚĞŶƚŝĂů