BCM400 4.0 T.38 to Rightfax

[conkyd]

Hi guys,
Having a few issues with H323 trunks into a Rightfax server using T.38.

Public network connections is ISDN E1.

When the rightfax dials out to a local or public fax - all ok.

When a local BCM fax extension (GASM) or a public fax dials in - the rightfax answers but then timesout.

Any ideas would be appreciated.

 

[suckamucka]

I have the same setup, but having an issue finding a T.38 gateway to sit between my BCM400 and Rightfax. Do you mind sharing what you are using to get T.38 to Rightfax? Thanks

 

[conkyd]

the BCM is producing t.38

 

[suckamucka]

Do you mind sharing where this configuration is set in the BCM manager? Thanks for your quick reply.

 

[conkyd]

in release 4.0 - where you program your IP trunks (configuration/telephony resources/ip trunks) - there is a checkbox called t.38 under the h.323/sip (as applicable to the trunk) parameters tab

 

[suckamucka]

Thanks for the clarification. On to investigate.

 

[suckamucka]

We also have the call being routed to rightfax. Rightfax is not able to complete the call. Using wireshark it seems as if the t38:t30 negotiating fails. What update is your BCM running? We are at 4.0.2.03A

 

[gberger]

Also make sure you're up to date with the DSP patches.Those have the latest T.38 fixes.The last one released is BCM.R400.149-DSPFIRMWARE included in SU17.

 

[suckamucka]

I verified that BCM.R400.149-DSPFIRMWARE is installed.

 

[SlateHadi]

I was wondering if anyone got anywhere with this issue. I am having a similar issue with SIP trunks and Rightfax.

thanks

 

[suckamucka]

We spent several weeks with RightFax and Brooktrout. We tried SIP as well as H323 and got nowhere. We were able to fax out but at only 4800bps. Using H323 we could get the inbound fax call to answer but it would never negotiate handshake.
With SIP the BCM passes an OPTIONS request and the SR140 app doesn't know that command.
Our fix will be to get a new phone system.