Page 1 of 1

INTIP Board problem with t.38 fax

Posted: 23 Dec 2011 07:53
by nubi
Hi ,

i am having troubles with T38 and our IntIP-Boards.

Situation :

Our (New-)Faxserver is connected via Sip-trunk with our Alcatel PBX(R9.1-i1.605-33-ge-c0).
We have 3 IntIp Boards, 2 INTIP3B and 1 INTIPA Board.
Most of the received faxes reached our Faxserver without any problems, only some did not.
A deeper wireshark analysis shows that EVERY Fax that comes over the INTIPA Board does
not work, the other faxes over the INTIP3B Boards allways work.
If i take a look into an "working fax" wireshark protocol, both sides (faxserver and PBX) are
talking t.38. In case of the "not working fax" only the faxserver is talking t.38, the PBX never.
All Boards are in same VLAN without special configuration.

Do the INTIPA Boards know the t38 protocol ?
If yes, what is to configure so that faxes via the INTIPA Board reach the faxserver ?

Is it possible to switch off t.38 , so that all Boards talk only g711 ?

Merry Christmas and thanks for help

Nubi

Re: INTIP Board problem with t.38 fax

Posted: 28 Dec 2011 06:05
by OXE_4400
You need upgrade to patch 35 or ask ALU support for hotfix.

Diagnosis:
Regression in INTIP/GD binary, starting from OXE R9.1 i1.605.30 and OXE R10. When sending a FAX from a SIP/T.38 Fax server
(various brands, like OFS, Cycos, XMedius) to OXE gateway, the fax call is established, but speed negotiation fails.
This exchange is repeated for all speeds 9600, 7200, 4800, 2400. Thus fax call is disconnected again. .

Solution:
Correction will be available in i1.605.35 and j1.410.42 patches

Re: INTIP Board problem with t.38 fax

Posted: 29 Dec 2011 09:23
by nubi
Thanks OXE_4400,

we will make an update in mid of January !

Regards
Nubi

Re: INTIP Board problem with t.38 fax

Posted: 09 Jan 2012 06:59
by tot3nkopf
nubi wrote: Is it possible to switch off t.38 , so that all Boards talk only g711 ?
Nubi
OXE doesn't support fax over g.711, only T.38.

Re: INTIP Board problem with t.38 fax

Posted: 18 Jan 2012 07:42
by nubi
Hi!

We installed R9.1-i1.605-33-c-ge-c0
and we don t have this problem anymore !