RightFax with CCM 4.2 (MGCP) help?

SBCdd7343 · ‎12-17-2007

Can someone led some guidance. We are trying to impliment a Rightfax server. Per Captaris direction, we have our existing MGCP gateway controled by CCM (with mgcp package-capability fxr-package added, mgcp stopped and restarted). no mgcp fax t.38 inhibit added, ECM disabled.

We added the rightfax server to CCM (as an h.323 gateway). We can get to the rightfax server (and hear fax tones) but shortly there after it cuts off).

Is the setup the correct way (with both gateway and rightfax registered to CCM)?

Any help would be appreciated. Our IOS is 12.4(3g) SPServices

thanks

bmoorman78 · ‎12-27-2007

When you say you added the Rightfax server to CCM as an H323 gateway, what do you mean specifically? Is is a T-1/PRI between the Fax card on the Rightfax server and a MGCP-controlled gateway? Is it SIP? When we setup Rightfax it ended up being a T1 CAS between the Fax board in the Rightfax server to a VWIC-1MFT card in a 2811 Voice gateway.

eloy.chio · ‎12-27-2007

I ran into the same issue. Had to convert the GWY to H323. Create VoIP Dial-Peers and point the session target to the RightFax IP. From what I understand RighFax should work with an existing MGCP GWY, but I had no luck and finally converted to H323.

cevala · ‎12-28-2007

T.38 with MGCP is only supported from CCM version 4.2(3).

T.38 with H.323 and SIP will work for sure, that's how we always do it.

bmoorman78 · ‎12-28-2007

I've attached parts of the config of our 2811 voice gateway. I was able to get it working with MGCP, by doing the following:

1. Added a T-1 CAS in Call Manager to one of the T-1 ports on the VWIC-2MFT Card. Due to Rightfax only being licensed for 2 channels, I only added two channels to the T-1 CAS. (See T-1 CAS CCM Config)

NOTE: Call Classification is OnNet.

NOTE 2: Make you set this interface to use the internal clock on the 2811 or you will have clock slipping on the T-1.

2. To route from Call Manager to RightFax (Fax DIDs), I created route patterns that pointed to this interface. The Route Patterns need to be in the same partition as your DID Translations.

We are running CCM 4.2(3)

tman701jperez · ‎01-04-2008

Maybe you guys can help me out here.

I have a similar setup as bmmorman78.

Inbound faxes work fine. Rightfax answers and faxes come thru to our email boxes using Exchange connector.

My issue is outbound faxes. They all fail. I run debugs and I see the call seize a channel on the PRi between the Rightfax and my 2851, but then it fails.

My current setup is as follows. CUCM 5.1

2851 running C2800NM-SPSERVICESK9-M), Version 12.4(3g. RightFax9.3 with a tr1034 card with a PRI between the RF card and the 2851. Then I have 2 more PRI's going to my carrier.

Thanks,

bmoorman78 · ‎01-04-2008

If you have to dial a digit, i.e. 8 or a 9 to get an outside trunk, are you doing that in RightFax? Is the PRI that ties the Brooktrout card to your 2851, in Call Manager, part of a Calling Search Space that can call out?

tman701jperez · ‎01-04-2008

Hey bmoorman78,

We dial 9 and i tried both ways to have RightFax add the 9 prefix and also tried doing it manually.

Also the CSS for the pri is able to dial out. I tried different CSS's that i get the same results. Below is some of the debug when i place a call:

*Jan 4 19:51:41.232: ISDN Se0/1/1:23 Q931: RX <- SETUP pd = 8 callref = 0x001

Bearer Capability i = 0x9090A2

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98386

Exclusive, Channel 6

Called Party Number i = 0x80, '9546439082'

Plan:Unknown, Type:Unknown

*Jan 4 19:51:41.236: ISDN Se0/1/1:23 Q931: RX <- SETUP pd = 8 callref = 0x001

Bearer Capability i = 0x9090A2

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98388

Exclusive, Channel 8

Called Party Number i = 0x80, '9546439082'

Plan:Unknown, Type:Unknown

*Jan 4 19:51:41.240: ISDN Se0/1/1:23 Q931: TX -> RELEASE_COMP pd = 8 callref

0x8018

Cause i = 0x8081 - Unallocated/unassigned number

*Jan 4 19:51:41.240: ISDN Se0/1/1:23 Q931: TX -> RELEASE_COMP pd = 8 callref

0x8019

Cause i = 0x8081 - Unallocated/unassigned number

Thanks for your help with this.

tman701jperez · ‎01-07-2008

Update:

I basically overlooked the inbound digits on the PRI between the RF server and my 2851.

I had it set to only accept 4 digits when in reality it should have been set to "All" in my case. Found out by doing a ccm trace since it wasnt the GW giving me the error but CCM. I also checked the CSS just in case but that was correct, changed the digits accordingly and now all fax calls go out fine.

Tman

Googi1974 · ‎07-09-2008

Hi Tman-

I am new to our telephony team & voip and I see these words PRI, T1, trunk, and others used all the time. Would you be able to clarify for me what you mean by "...PRI between the RF card and the 2851?" and "2 more PRIs going to carrier?" I assume these are hardware, how r they represented or defined in Call Manager?

I ask bcuz we are trying to implement ffax 9.3 w an H.323 gateway using the boardless sr140 solution and we have not been successful. Any help is greatly appreciated.

Thanks,

Kelly

kadambari.beelwar · ‎07-24-2008

Hello,

I have a rightfax server which disconnects the call after 30 secs. The rel_complete comes from rightfax boaord after connect message.

Is there anything I need to check

11:18:36.509 H.225 0x8007 RELEASE_COMP RX <-- 172.26.6.197

RELEASE_COMP pd = 8 callref = 0x8007

Cause i = 0x8080 - Unknown Cause value

User-User i = 0x052580060008914A0004111811000072B5DAAF77E11D07005902AC1A1E100100014010800100