I want to send fax using MIcrosoft Fax between T38modem and sip gateway. MIcrosoft Fax can send fax to gateway, but cannot receive fax from gateway. After MIcrosoft Fax answer and T38 negotiating is completed, no T30 negotiating, T38modem doesn't send any T38 packet(such as DIS).
The test topolgy is: MIcrosoft Fax --com0com---T38modem---sip-->gateway---fax
T38modem version is 1.2.0 with opal 3.67, ptlib 2.6.6
The command is : t38modem -n -tttt -o trace.log -p \\.\CNCB0 -route "sip:.*=modem:<dn>;OPAL-Force-Fax-Mode;OPAL-No-Force-T38-Mode" -sip-listen 169.254.1.5
Look forward to you help!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
2) Do not use OPAL-Force-Fax-Mode in incoming router. It is not aplicapable here.
OPAL-No-Force-T38-Mode means that T38modem wait for t38 renvite from other side, and starts in audio-fax mode.
So you should simply use -route "sip:.*{TAB}sip:.*=modem:<dn> without OPAL-options if you want T38
3) If have problems with Opal-trunk (if will do with Opal trunk and still not work), then put your question at Opal-user maillist, there is a deadlock in Opal as for T38-incoming (with last trunks and still not fixed). I know how to fix but better to put Opal-developers attention to this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried starting t38modem without OPAL-options, but still cannot receive fax . H323 cannot receive fax either.
Is it the bug of Opal? I will try the last version, but as you mentioned, the last versions still have problem, can you tell me how to fix it? Thanks!!
To bpostow:
I have the trace. There is some difference. T38modem can receive INVITE message, and reply TRY, RING and 200 OK message, and swith to T38 mode, but cannot send any T38 packet. After a while, the call is cleared.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried the T38Modem last Version (1.2.1 with OPAL-3.9.0/3.9beta0, PTLIB-2.9.0/2.9beta0 ), but still fail to receice fax in sip mode . The problem has changed. after answering, T38modem don't send re-invite to change to T38 mode. Howeve H323 receiving and sending fax are both ok!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well… I thought everything was going to work… sadly… the *modem* portion of the t38modem is not functioning. (inbound calls meet with silence… outbound calls play the CHG… but fails to respond to the fax machine on the other side. any suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The revison 24174 works well, now T38modem can receive and send fax with MIcrosoft Fax. Thanks!
Another little problem for sending fax: after sending all fax pages, the call is cleared immediately while the gateway is decoding last several fax packets. so the last packets are discarded. Can t38modem be configured to delay call clear after sending fax?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've build the revision 24174 for windows xp and when I start t38modem.exe with or without command line args it just crashes:
Unhandled exception at 0x1010faf4 in t38modem.exe: 0xC0000005:
Access violation reading location 0x0000001.
What could be the cause? Waiting for your help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
А чем вы строили проекты? Дело в том, что я не смог собрать ptlib и opal с пом. vc++2005 (error LNK2019: unresolved external symbol … 39 error(s), 0 warning(s)) и собрал их с пом. vc++2003, а для сборки t38modem использовал vc++2005 (там нет проекта для 2003). Может с этим и связаны проблемы?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, I finally rebuilt the whole project with vc++2005 Express Edition and now it starts ok.
But I still can't receive faxes: now I can hear the CHG signal from t38modem but fax machine is unable to set up connection. I'm trying to check this chain:
fax->spa2102->asterisk->t38modem->com0com->ventafax
There was an additional bag:
…24135 Applied patch to fix issues with udp/tcp SIP transports and the correct Request URI in the active SIP dialog, thanks Samuel Widmer
"If to try original 24174 with incoming call:
PSTN-> Provider Sipnet -> faxopal(t38)
t38 is failed…"
This bug(24135) does not allow to have incoming T38 with faxopal, but not always: only in some cases.
And I did not see problems with T38modem, only with FaxOpal. Nevertheless probably it's your case.
This was fixed in 24193, but too late because of the main new bug in 24191(after 24191 incoming T38 does not work in all cases both with T38modem and FaxOpal).
Regarding the current situation, it is quite hopeless. Unfortunately, at present there is no time and energy to fight with Robert.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, could you help please:
I build opal 3.10.11 and ptlib 2.10.11 and finally PeteDavidson/t38modem/opal with VS 2010 & MSVC++ 10.0. seems running with no problem
my topology is: Microsoft Fax --> Standard Modem 33600 (CNCA0) --> com0com (CNCB0) --> T38modem --> VoIP(sip) Gateway (192.168.0.8:5060) --> phone line to PSTN
Does your gateway support T.38? You should verify that. Also you need to get a wireshark network trace of all traffic between your system and the gateway.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your reply Sir.
Yes. The gateway support T.38 and actually it show connection switch to T.38FAX codec when a sending fax call ongoing.
I will get network trace tomorrow and post it here.
by the way is this schematic correct about what protocol involved here?
MS Fax (Standard modem 36kbps) <--T.30--> com0com <--T.30--> t38modem <--T.38--> Voip gateway <--T.30--> Phone line to PSTN
Last edit: Omid 2015-06-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thank you for your reply Sir.
yes. The gateway support T.38 and actually it show connection switch to
T.38FAX codec when a sending fax call ongoing.
I will get network trace tomorrow and post it here.
by the way is this schematic correct about what protocol involved here?
MS Fax (Standard modem 36kbps) <--T.30--> com0com <--T.30--> t38modem
<--T.38--> Voip gateway <--T.30--> Phone line to PSTN
Hi. Here is wireshark packet capture between PC running t38modem (192.168.0.100) and VoIP gateway (192.168.0.8).
Is the problem is about training phase?
I want to send fax using MIcrosoft Fax between T38modem and sip gateway. MIcrosoft Fax can send fax to gateway, but cannot receive fax from gateway. After MIcrosoft Fax answer and T38 negotiating is completed, no T30 negotiating, T38modem doesn't send any T38 packet(such as DIS).
The test topolgy is: MIcrosoft Fax --com0com---T38modem---sip-->gateway---fax
T38modem version is 1.2.0 with opal 3.67, ptlib 2.6.6
The command is : t38modem -n -tttt -o trace.log -p \\.\CNCB0 -route "sip:.*=modem:<dn>;OPAL-Force-Fax-Mode;OPAL-No-Force-T38-Mode" -sip-listen 169.254.1.5
Look forward to you help!!
1)First of all, use last versions:
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/trunk ptlib
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/trunk opal
cvs -z3 -d:pserver:anonymous@t38modem.cvs.sourceforge.net:/cvsroot/t38modem co -P t38modem
2) Do not use OPAL-Force-Fax-Mode in incoming router. It is not aplicapable here.
OPAL-No-Force-T38-Mode means that T38modem wait for t38 renvite from other side, and starts in audio-fax mode.
So you should simply use -route "sip:.*{TAB}sip:.*=modem:<dn> without OPAL-options if you want T38
3) If have problems with Opal-trunk (if will do with Opal trunk and still not work), then put your question at Opal-user maillist, there is a deadlock in Opal as for T38-incoming (with last trunks and still not fixed). I know how to fix but better to put Opal-developers attention to this.
Have you done a packet trace? If you take a look at my question, we may have the same issue…
I have tried starting t38modem without OPAL-options, but still cannot receive fax . H323 cannot receive fax either.
Is it the bug of Opal? I will try the last version, but as you mentioned, the last versions still have problem, can you tell me how to fix it? Thanks!!
To bpostow:
I have the trace. There is some difference. T38modem can receive INVITE message, and reply TRY, RING and 200 OK message, and swith to T38 mode, but cannot send any T38 packet. After a while, the call is cleared.
ah, ok, it sounds like you get one more step forward from where I get…
I have tried the T38Modem last Version (1.2.1 with OPAL-3.9.0/3.9beta0, PTLIB-2.9.0/2.9beta0 ), but still fail to receice fax in sip mode . The problem has changed. after answering, T38modem don't send re-invite to change to T38 mode. Howeve H323 receiving and sending fax are both ok!!
The current opal trunk is broken, so try
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/trunk -r 24174 ptlib
svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/trunk -r 24174 opal
cvs -z3 -d:pserver:anonymous@t38modem.cvs.sourceforge.net:/cvsroot/t38modem co -P t38modem
That seems to have done the trick… спасибо я благодарен
When I use those versions, I get a bus error with no trace log created…:
Brians-mini$ t38modem.OPAL -n -o trace.log.0422 -p ttypb -route "modem:1.*=sip:<dn>@64.136.174.30" -route "sip:.*=modem:<dn>" -ttttt -u "5555555555" -stun stunserver.org
Bus error
Possible you build with one lib version but run with another. Check with "ldd t38modem.OPAL".
Possible it's a new OPAL bug for your OS.
Possible you need to rebuild codecs.
Well… I thought everything was going to work… sadly… the *modem* portion of the t38modem is not functioning. (inbound calls meet with silence… outbound calls play the CHG… but fails to respond to the fax machine on the other side. any suggestions?
The revison 24174 works well, now T38modem can receive and send fax with MIcrosoft Fax. Thanks!
Another little problem for sending fax: after sending all fax pages, the call is cleared immediately while the gateway is decoding last several fax packets. so the last packets are discarded. Can t38modem be configured to delay call clear after sending fax?
I've build the revision 24174 for windows xp and when I start t38modem.exe with or without command line args it just crashes:
Unhandled exception at 0x1010faf4 in t38modem.exe: 0xC0000005:
Access violation reading location 0x0000001.
What could be the cause? Waiting for your help.
Ну это разбирайтесь. Если ptlib24174+opal24174+t38modem(trunk) то все копилируется и работает: у меня на XP ничего не вылетает.
А чем вы строили проекты? Дело в том, что я не смог собрать ptlib и opal с пом. vc++2005 (error LNK2019: unresolved external symbol … 39 error(s), 0 warning(s)) и собрал их с пом. vc++2003, а для сборки t38modem использовал vc++2005 (там нет проекта для 2003). Может с этим и связаны проблемы?
http://www.voipinfo.ru/forum/viewtopic.php?f=1&t=11906
vc++2005 Express Edition
sdk win 2003
no need to use expat now
see also d@vinchi » Сб дек 26, 2009 6:12 am at that topic
Thanks, I finally rebuilt the whole project with vc++2005 Express Edition and now it starts ok.
But I still can't receive faxes: now I can hear the CHG signal from t38modem but fax machine is unable to set up connection. I'm trying to check this chain:
fax->spa2102->asterisk->t38modem->com0com->ventafax
2010/05/05 11:46:29.296 COM20(e):6d0 <- {
0d 0a 43 4f 4e 4e 45 43 54 0d 0a ..CONNECT.. }
2010/05/05 11:46:30.687 Media Patch:2784 -> v21frame {
ff c8 01 00 f6 1f 21 01 01 01 01 18 ……!….. }
2010/05/05 11:46:30.718 COM20(e):6d0 <- {
0d 0a 4f 4b 0d 0a ..OK.. }
2010/05/05 11:46:30.781 COM20(e):6d0 -> AT+FRH=3
2010/05/05 11:46:35.750 COM20(e):6d0 Reset state stRecvBegWait
2010/05/05 11:46:35.750 COM20(e):6d0 COM20 T38Engine ResetModemState stateModem(5) != stmIdle, reset
2010/05/05 11:46:35.750 COM20(e):6d0 -> 1 bytes of binary
2010/05/05 11:46:35.921 COM20(e):6d0 -> AT+FTH=3
…
2010/05/05 11:47:08.562 COM20(e):6d0 -> AT+FTH=3
2010/05/05 11:47:08.562 COM20(e):6d0 <- {
0d 0a 43 4f 4e 4e 45 43 54 0d 0a ..CONNECT.. }
2010/05/05 11:47:09.593 Media Patch:2784 -> v21frame {
ff c8 5f .._ }
2010/05/05 11:47:09.625 COM20(e):6d0 <- {
0d 0a 4f 4b 0d 0a ..OK.. }
2010/05/05 11:47:10.671 COM20(e):6d0 -> AT
2010/05/05 11:47:10.671 COM20(e):6d0 <- {
0d 0a 4f 4b 0d 0a ..OK.. }
2010/05/05 11:47:10.859 COM20(e):6d0 -> ATH0
It look like t38modem does not switched from command mode. Is it waiting for some specific command?
I've rebuilt t38modem with opal+ptlb revision 24319 and now it sends and receives faxes ok.
There was an additional bag:
…24135 Applied patch to fix issues with udp/tcp SIP transports and the correct Request URI in the active SIP dialog, thanks Samuel Widmer
"If to try original 24174 with incoming call:
PSTN-> Provider Sipnet -> faxopal(t38)
t38 is failed…"
This bug(24135) does not allow to have incoming T38 with faxopal, but not always: only in some cases.
And I did not see problems with T38modem, only with FaxOpal. Nevertheless probably it's your case.
This was fixed in 24193, but too late because of the main new bug in 24191(after 24191 incoming T38 does not work in all cases both with T38modem and FaxOpal).
Regarding the current situation, it is quite hopeless. Unfortunately, at present there is no time and energy to fight with Robert.
Hi, could you help please:
I build opal 3.10.11 and ptlib 2.10.11 and finally PeteDavidson/t38modem/opal with VS 2010 & MSVC++ 10.0. seems running with no problem
my topology is: Microsoft Fax --> Standard Modem 33600 (CNCA0) --> com0com (CNCB0) --> T38modem --> VoIP(sip) Gateway (192.168.0.8:5060) --> phone line to PSTN
Voip Gateway is a Soundwin H.323/SIP S404(4FXO) http://bit.ly/1dpU3He
run it with:
t38modem.exe -n -t -o trace.log -p \.\CNCB0 --no-h323 --route "modem:.=sip:<dn>@192.168.0.8:5060" --route "sip:.=modem:<dn>"
Send and receive call both answered but no fax send or received.
I attach both Send and recieve trace log. could you help me about what is wrong?
Last edit: Omid 2015-06-16
Does your gateway support T.38? You should verify that. Also you need to get a wireshark network trace of all traffic between your system and the gateway.
Thank you for your reply Sir.
Yes. The gateway support T.38 and actually it show connection switch to T.38FAX codec when a sending fax call ongoing.
I will get network trace tomorrow and post it here.
by the way is this schematic correct about what protocol involved here?
MS Fax (Standard modem 36kbps) <--T.30--> com0com <--T.30--> t38modem <--T.38--> Voip gateway <--T.30--> Phone line to PSTN
Last edit: Omid 2015-06-16
Yes, your schematic is correct.
On Tue, Jun 16, 2015 at 9:11 AM, Omid omidiii@users.sf.net wrote:
--
Pete Davidson
Senior Software Developer
Embedded Systems
O +1 859 825 4999
M +1 859 338 3426
F +1 859 232 6267
Pete@Lexmark.com
http://www.lexmark.com/
www.lexmark.com
Hi. Here is wireshark packet capture between PC running t38modem (192.168.0.100) and VoIP gateway (192.168.0.8).
Is the problem is about training phase?
Last edit: Omid 2015-06-17