Showing results for 
Search instead for 
Did you mean: 

Cisco CUBE and RightFax configuration help required


I need a help to configure Cisco CUBE to get this working with RightFax. We recently installed SIP trunk in our  organization and using CUB(H323) with CUCM 8.6. We also have RightFax which is  working fine with H323 gateways.

Can someone help me to configure Cisco CUBE to get this working with RightFax system

Call Flow


Codec G711alaw

8 Replies 8

Chris Deren
Hall of Fame Master Hall of Fame Master
Hall of Fame Master

Simply configure routing to direct calls to the right fax and ensure you use supported fax protocol on all sides ie protocol based T.38.

Sent from Cisco Technical Support iPhone App

Hi Chris,

Thanks for your reply, can you please give any sample config. I am using following config, please correct if I need any changes. CUBE will be used for incoming faxes only

voice class codec 1

codec preference 1 g711alaw

dial-peer voice 101 voip

description **** Outbound calls to Primary CUCM ***

translation-profile outgoing CLI

destination-pattern 6...

session target ipv4:CUCM-192.168.X.X

voice-class codec 1

dtmf-relay h245-alphanumeric

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none

ip qos dscp cs4 media

ip qos dscp cs3 signaling

no vad

We are using the same method of routing as chris mentioned.

dial-peer voice 2000 voip


incoming called-number .T

voice-class codec 1

dtmf-relay rtp-nte

fax protocol pass-through g711alaw

dial-peer voice 2844 voip

description "TO FAX"

destination-pattern 2948677

session protocol sipv2

session target ipv4: (FAX IP)

codec g711alaw

fax protocol pass-through g711alaw

Hope it helps.

Hi Zekeria

Thanks for your reply. basically we have Cisco Voice Gateways in CUCM Integration Scenario. I mean call routing is not directly through RightFax, it is basically through call manager.

This scenario is working fine with the H323 gateways now we setup Cisco CUBE router and wanted this to work with RightFax. Please note Call Flow is


In your dial-peer you routed call to Rightfax but we are doing this through CUCM. Also, you used fax protocol pass-through g711alaw in dial-peer but the in the document I found on internet is recomending the

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none

Can you please explain whats the difference between these two?

I have also attached this document.

Can someone please help me how can this work in our scenario

Here are my suggestions.

1. create a dial-peer to CUCM on your CUBE gateway
dial-peer voice 1234 voip
description inbound calls to rightfax via CUCM
destination-pattern 5555
session target ipv4: x.x.x.x (ip add of cucm)
session transport udp
codec g711ulaw

2. configure T.38 support
voice service voip
fax protocol t38 ls-redundancy 2 hs-redundancy 0 fallback none

3. Configure h323 gateway in cucm with ip address of rightfax server as device name. Assign it to a RG and the RG to a RL. Ensure you add the correct CSS for inbound calls on the gateway.

4. Create a RP on cucm for the rightfax number eg 5555 and send it to the RL of right fax

5. Ensure that for all outbound calls to CUBE for fax, you use G711...

6. Ensure that the region between the rightfax h323 gateway and CUBE is set to G711

NB: Use the rightfax guide to setup right fax as required

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Please rate all useful posts

Hi Aok

Many thanks for your suggestions. As these are production system so I have to arrange out of hours time to apply this config. Thanks once again


Configuration for Inbound / Outbound VoIP dial-peer on both leg of the calls:

dial-peer voice 1 voip

   fax protocol t38 nse ls-redundancy 0 hs-redundancy 0

   fax-relay ecm disable

   fax nsf 000000

   fax-relay sg3-to-g3

Rate the post accordinly.



We initally used the fax protocol t38

But we faced some problems with the codec negotiation between the GW and FAX Server and we switched to g711alaw passthrough everything seemed to work flawlessly.

I agree with Chris, its just easier to maintain and troubelshoot if you send fax directly from the Gateway.

Good Luck

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers