The information contained in this document is confidential and proprietary to tekvizion PVS, Inc.

Transcription

1

2 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.

3 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

4

5 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.

6 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 The call flow and protocol path is as follows: POTS (dial ) 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 The call flow and protocol path is as follows: OpenText RightFax (2222) SIP > CUCM route pattern 2222-> Called Party Transform Mask >SIP POTS

7 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 caller-id enable The following allows the phone to be dialed out though the POTS lines: dial-peer voice pots description fax from opentext to pstn via cucm preference 1 service session destination-pattern no digit-strip port 0/0/0 The following allows reaching the Right Fax server: translation-rule 1111 Rule dial-peer voice voip description fax from pstn to opentext via cucm preference 1 destination-pattern translate-outgoing called 1111 session protocol sipv2 session target ipv4: :5060 session transport udp codec g711ulaw fax rate fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none 1 Ip address is the ip address of the call manager

8 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 3. The following screen appears:

9 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. 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: 4. Press Add New to add a new SIP Trunk.

10 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:

11 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: (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

12 10. Press Restart then press Close. 1. Using a web browser, log into the Cisco Unified CM Administration screen. 2. From the menu select Device Trunk. 3. Press Add New 4. The following screen appears:

13 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:

14 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: 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

15 3. Click on Add New to add a new Route Pattern 4. Route pattern 2222 is the format to send the fax via PSTN

16 5. In the Gateway/Route List, enter the IP address ( ) of the Voice Gateway sending out Fax calls. 1. From the Cisco Unified CM Administration screen, select Call Routing Route Hunt Route Pattern. 2. Click Add New

17 4. The following screen appears: 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.

18 To call OpenText RightFax from a POTS phone, dial The call flow and protocol path behaves as follows: POTS (dial ) 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 The call flow and protocol path behaves as follows: OpenText RightFax(2222) SIP > CUCM9 dial 2222 SIP > Cisco Gateway translates 2222 in to 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 caller-id enable The following allows the phone to be dialed out though the POTS lines: dial-peer voice pots description fax from opentext to pstn via cucm preference 1 service session destination-pattern no digit-strip port 0/0/0

19 The following allows reaching the Right Fax server : translation-rule 1111 Rule dial-peer voice voip description fax from pstn to opentext via cucm preference 1 destination-pattern translate-outgoing called 1111 session protocol sipv2 session target ipv4: :5060 session transport udp codec g711ulaw fax rate fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none Note-Ip address 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. 3. Press Add New to add a new H.323 Gateway

20 4. Select H.323 Gateway and press Next. 5. The following screen appears: 6. Set the following options: a. Device Name: (address of OpenText RightFax) b. Device Description: OpenText c. Device Pool: Default

21 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 4. Select H.323 Gateway for the Gateway Type and press Next.

22 5. The following screen appears: 6. Set the following options: a. Device Name: (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.

23 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. 3. Click on Add New to add a new Route 4. Route pattern 2222 is the format to send the fax via PSTN

24 5. In the Gateway/Route List, enter the IP address ( ) 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.

25 3. Click on Add New to add a new Route Pattern in Route Pattern is used to send faxes from PSTN to OpenText RightFax thru CUCM.

26 To call OpenText RightFax from a POTS phone, dial The call flow and protocol path behaves as follows: POTS (dial ) 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 The call flow and protocol path behaves as follows: OpenText RightFax(2222) SIP > CUCM route pattern 2222-> Called Party Transform Mask >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 dial-peer voice voip description fax from pstn to opentext via cucm preference 1 destination-pattern translate-outgoing called 1111 session protocol sipv2 session target ipv4: :5060

27 session transport udp codec g711ulaw fax rate fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none Note-Ip address 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 ! mgcp mgcp call-agent 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: 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 to be dialed out though the POTS lines: dial-peer voice pots description fax from opentext to pstn via cucm preference 1 service mgcp destination-pattern no digit-strip port 0/0/0:15

28 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.

29 3. The following screen appears: 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: 5. Change Outgoing Transport Type to UDP. Note: UDP is required by OpenText RightFax. 6. Press Save and Reset, then press Close.

30 1. Using a web browser, log into the Cisco Unified CM Administration screen. 2. From the menu select Device Trunk.

31 3. The following screen appears: 4. Press Add New to add a new SIP Trunk. 5. Select the following options and click Next: Trunk Type = SIP Trunk Device Protocol = SIP Trunk Service Type = None (Default)

32 6. The following screen appears: Set the following options: Device Name: CUCMSipTrunkToOpenTextFaxServer Device Description: Siptrunk_to_OpenText _Fax _Server Device Pool: Default Call Classification: OffNet Destination Address: (address of OpenText RightFax) SIP Trunk Security Profile: Non Secure SIP Trunk Profile SIP Profile: Standard SIP Profile 8. Press Save and Reset.

33 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 Gateway. 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.

34 7. The Gateway Configuration screen appears: 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.

35 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. 1. Using a web browser, log into the Cisco Unified CM Administration screen. 2. From the menu select Call Routing Route / Hunt Route Pattern.

36 3. Click Add New to add a new Route Pattern 4. The following screen appears: 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).

37 1. Using a web browser, log into the Cisco Unified CM Administration screen. 2. Select Call Routing Route Hunt Route Pattern. Click on Add New to add a new Route Pattern

38 4. The following screen appears: 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.

39 To call OpenText RightFax from a POTS phone, dial The call flow and protocol path behaves as follows: POTS (dial ) 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 The call flow and protocol path behaves as follows: OpenText RightFax(2222) SIP > CUCM9 dial 2222 SIP > Cisco Gateway translates 2222 in to 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 dial-peer voice voip description fax from pstn to opentext via cucm preference 1 destination-pattern

40 translate-outgoing called 1111 session protocol sipv2 session target ipv4: :5060 session transport udp codec g711ulaw fax rate fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none Note-Ip address 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 ! mgcp mgcp call-agent 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: 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 to be dialed out though the POTS lines: dial-peer voice pots description fax from opentext to pstn via cucm preference 1 service mgcp destination-pattern no digit-strip port 0/0/0:15

41 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 3.Press Add New to add a new H.323 Gateway.

42 4. Select H.323 Gateway and press Next. 5. The following screen appears: 6. Set the following options: a. Device Name: (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.

43 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. 4. The following screen appears:

44 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. 7. The Gateway Configuration screen appears: 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.

45 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. 1. Using a web browser, log into the Cisco Unified CM Administration screen. 2. From the menu select Call Routing Route / Hunt Route Pattern. 3. Click on Add New to add a new Route Pattern.

46 4. The following screen appears: 5. Set Route Pattern to 2222 to send faxes via the E1 (PSTN). 6. In this scenario, Gateway/Route List is (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.

47 9. Click on Add New to add a new Route Pattern 10. The following screen appears:

48 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

49 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. 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.

50 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.

51 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.

52 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 by Using Text to Speech (TTS)

53 1. Access a user s web inbox via the url : 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 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 with prefix [Fax Failure] (see below screenshot)

54

55 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 CUCM transforms 2222 to and send it to Cisco Cisco 3845 gateway forwards the same destination number( ) to 3825 gateway through the E1 connectivity. Cisco 3825 receives the requests and transforms the incoming number ( ) as 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 Rule interface Serial1/0:15 no ip address encapsulation hdlc isdn switch-type primary-qsig isdn timer T 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 voip description fax from pstn to opentext via cucm

56 preference 1 destination-pattern translate-outgoing called 1111 session protocol sipv2 session target ipv4: session transport udp codec g711ulaw fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw dial-peer voice pots description fax from opentext to pstn via cucm huntstop preference 1 service session destination-pattern ^ $ 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 translate-outgoing called 73 session protocol sipv2 session target ipv4: 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 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 / / / /!! 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 no digit-strip direct-inward-dial

57 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 CUCM transforms it to to Cisco Cisco 3845 gateway forwards the same destination number ( ) to 3825 gateway through the E1 connectivity. Cisco 3825 receives the requests and transforms the incoming number ( ) as 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 Rule interface Serial1/0:15 no ip address encapsulation hdlc isdn switch-type primary-qsig isdn timer T isdn not-end-to-end 64 isdn protocol-emulate network isdn incoming-voice voice isdn map address.* plan isdn type national no cdp enable!

58 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 voip description fax from pstn to opentext via cucm preference 1 destination-pattern translate-outgoing called 1111 session protocol sipv2 session target ipv4: session transport udp codec g711ulaw fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw dial-peer voice pots description fax from opentext to pstn via cucm huntstop preference 1 service session destination-pattern ^ $ 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 translate-outgoing called 73 session protocol sipv2 session target ipv4: 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 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 / / / /

59 !! 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 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 CUCM transforms it to to Cisco Cisco 3845 gateway will forward the same destination number( ) to 3825 gateway through the E1 connectivity. Cisco 3825 receives the requests and transforms the incoming number ( ) as 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 ! mgcp mgcp call-agent service-type mgcp version 0.1 mgcp dtmf-relay voip codec all mode out-of-band mgcp default-package fxr-package! mgcp profile default

60 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 Rule 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 voip description fax from pstn to opentext via cucm preference 1 destination-pattern translate-outgoing called 1111 session protocol sipv2 session target ipv4: session transport udp codec g711ulaw fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw dial-peer voice pots description fax from opentext to pstn via cucm huntstop preference 1 service session destination-pattern ^ $ 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 translate-outgoing called 73 session protocol sipv2 session target ipv4: session transport udp codec g711ulaw fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw

61 dial-peer voice 3334 pots description incoming dialpeer for call from 3825 to route to cucm service session incoming called-number 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 / / / /!! 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 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

62 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 CUCM transforms it to to Cisco Cisco 3845 gateway forwards the same destination number( ) to 3825 gateway through the E1 connectivity. Cisco 3825 receives the requests and transforms the incoming number ( ) as 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 ! mgcp mgcp call-agent service-type mgcp version 0.1 mgcp dtmf-relay voip codec all mode out-of-band mgcp default-package fxr-package

63 ! 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 Rule 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 voip description fax from pstn to opentext via cucm preference 1 destination-pattern translate-outgoing called 1111 session protocol sipv2 session target ipv4: session transport udp codec g711ulaw fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw dial-peer voice pots description fax from opentext to pstn via cucm huntstop preference 1 service session destination-pattern ^ $ 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 translate-outgoing called 73 session protocol sipv2 session target ipv4: session transport udp codec g711ulaw

64 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 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 / / / /!! 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 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