If T.38 faxing does not work between the MultiVOIP and Avaya PBXs, try these suggestions.

For Avaya PBX platforms that do not use CLAN or Medpro such as S8300, S8500, S8700, etc:


1. Make sure the Avaya PBX is running VoIP DSP firmware 54 or higher. This firmware is on the Avaya web site.

2. ** New ** Make sure the Avaya PBX is running G700 gateway firmware 23.19 or higher. This is also available on the Avaya web site.

3. ACM version needs to be 2.1 or higher.

4. Make sure the MultiVoIP is running firmware 9.06.DE or 2.06.D3 or higher. This firmware has a fix for SuperG3 fax, a fix for a fax problem where the VoIP could lockup and stop responding to pings. It also fixes a problem where the voice channel could get stuck showing XMT, RCV, and RSG after a couple thousand fax calls.

Here is a link to the latest MultiVoIP firmware:
http://www.multitech.com/en_US/SUPPORT/Families/MultiVOIP/firmware

5. Make sure the MultiVoIP is configured for T.38 and the fax baud rate is set to 9600.

6. Make sure that the CODEC on the Avaya PBX is set for T.38 standard.



For Avaya platforms that use CLAN/Medpro:


1.Make sure the PBX is running Medpro version 104 or higher. This firmware is on the Avaya web site.

2. ACM needs to be 2.1.1 or higher.

3. Make sure the MultiVoIP is running firmware 9.06.DE or 2.06.D3 or higher. This firmware has a fix for SuperG3 fax, a fix for a fax problem where the VoIP could lockup and stop responding to pings. It also fixes a problem where the voice channel could get stuck showing XMT, RCV, and RSG after a couple thousand fax calls.

Here is a link to the latest MultiVoIP firmware:
http://www.multitech.com/en_US/SUPPORT/Families/MultiVOIP/firmware

4. Make sure the MultiVoIP is configured for T.38 and the fax baud rate is set to 9600

5. Make sure that the CODEC on the Avaya PBX is set for T.38 standard.