Recent changes to support-requests

Rotate t38modem with logrotate (RHEL 6)

2015-01-20T17:33:13.428000Z

Hello,
I dont know if this is the right place to shoot questions.
Anyway, sorry for that, and let me know where may I find some light about this.
We have t38modem logging a lot (-ttt).
Dily we have 6GB files of logs.
We are trying to configure logrotate so we can rotate logs when the grow bigger than 200M.
The config for logrotate is made.
{
size 200M
copytruncate
rotate 300
compress
missingok
maxage 7
}
The problem is that log does not empty.
The gz log file is created, but the log is not emplty we thing because it is in use by t38modem.

The question is, how can we rotate the log without stop the t38modem app?

Thanks a lot.

Best regards,
Mariano.

SIP to Analog

2011-07-20T03:09:08Z

I'm trying to setup a hylafax installation that will accept faxes from a SIP based PBX (zultys) and send faxes through an analog modem (ttyS0).

I'm using t38modem 2.0 with the SIPPDU patch and spanDSP plugin.

T38Modem Version 2.0.0 (OPAL-3.9.0/3.9beta0, PTLIB-2.9.0/2.9beta0 (svn:24174)) by Vyacheslav Frolov on Unix Linux (2.6.32-28-server-x86_64)

Using the following parameters:

t38modem -ttttt -o /var/log/t38modem.log --sip-proxy T38modem:1234@192.168.100.31 --sip-disable-t38-mode --sip-register T38modem@192.168.100.31,1234,192.168.100.79, --ptty "+/dev/ttyT38-1,+/dev/ttyT38-2,+/dev/ttyT38-3" --no-h323 --route "sip:.*=modem:<dn>"

Hylafax receives the fax and stores it in the RECVQ directory.

I don't get a message back to the PBX that the fax was sent, so it keeps trying.

Also, I was hoping to configure the route so that Hylafax spooled up the fax and sent it out the analog modem (ttyS0)

Thank you for taking a look.

Mark

t38modem 2.0 does not receive fax

2011-06-27T15:04:52Z

Hi, I'm using T38Modem 2.0.0 with HylaFAX+ 5.5.0 and Asterisk 1.8.4.3.

I call t38modem with:
/usr/local/sbin/t38modem -tttt -o /var/log/t38modem0.log --no-h323 -u T38modem0 --sip-listen udp$1.2.3.7:6060 --sip-t38-udptl-redundancy '2:I,9:L,32767:H' --ptty +/dev/ttyT380 --route modem:.*=sip:<dn>@1.2.3.7 --route sip:.*=modem:<dn>

After a fax call, the connection with t38modem is established, HylaFAX reports "ANSWER: FAX CONNECTION DEVICE '/dev/ttyT380'", but a fax is never received.

In the tcpdump I see the correct handshaking between Asterisk and T38Modem, but finaly T38Modem switches to "recvonly" and Asterisk answers with "SIP/2.0 488 Not acceptable here" and the call ends shortly after that (see attached dump-file).

I applied the small fix from Request ID: 3317275 that made it possible to establish the connection at all.

Thanks a lot, sf4thg

t38modem update and CallerID change

2011-06-19T16:31:43Z

Hello guys,

I updated from t38modem 1.0 to t38modem 2.0 and now I am having problems with the destination number in order to dispatch the fax (I am running Hylafax 4.0 and SIP). Anyhow the information provided by t38modem 2.0 regarding to the destination number has changed. I can see that when the modem is ringing Hylafax correctly gets all NDID, NMBR and NAME but these fields don't correspond to the ones provided by the version 1.0. I have roll back to 1.0 but I would be interested in knowing if there is anything I can do to fit it to my scenario.
This is a special case in which the call comes from a PBX which is forwarding the call to the t38modem (but it is not the actual recipient of the call).

Does this anything to do with the new opal version?May I modify something on the source to get the ancient values?

Thank you very much
Felipe

t38modem 2.0 on SIP can send but not receive

2011-06-16T11:28:57Z

Hi, I set up HylaFAX 6.0.5 to use t38modem 2.0.
t38modem registers to a SIP PBX (voispeed) which does not support t38, so I start t38modem this way:

t38modem2-static-opal \ --no-h323 \ --sip-disable-t38-mode \ --ptty +/dev/ttyx01 \ --sip-proxy 121:sma11210@192.168.1.250 \ --sip-register 121@192.168.1.250,sma11210 \ --route "sip:.*=modem:<dn>" \ --route "modem:.*=sip:<dn>@192.168.1.250" \ --username 121

I can send fax with no problem at all but I can\'t even get past the first page when I receive...

I can't upload a trace file (Uploaded file must be no larger than 256k.)
So here is a link http://bcube.bzone.it/trace.log

Call Fails on Avaya System

2010-07-30T21:32:20Z

Setup:

Avaya System (172.26.195.72 and 172.26.195.75) with two MPF\'s running ptlib/opal/t38modem (sender 172.26.195.50, receiver 172.26.195.52)

ptlib and opal at rev 24174. t38modem at current trunk.

Call fails when receiver gets +FCERROR to the AT+FRH=3 command when trying to receive DCS. Looks like to me that t38modem receives all packets for the DCS, but does not send them up. It then sends +FCERROR when the V.17 data comes.

I am attaching wireshark trace, and +ttttt t38modem traces from sender and receiver.

What level of opal to use?

2010-07-28T20:36:09Z

When using the current trunk of t38modem, what is the best level of opal and ptlib?

H.323 problem on Cisco UC520

2010-05-28T01:53:17Z

On a Cisco UC520 I cannot send a fax from one t38modem to another t38modem using H.323. It works just fine for SIP. My test setup is a linux machine with two t38modem ttys. I use efax to send from one to the other through the UC520. I have attached a network sniff and the t38modem log.

Here is the t38modem command:

./t38modem -n -p +/home/pete/ttyx0,+/home/pete/ttyx1 --route "modem:.*=h323:<dn>@192.168.10.1" --route "h323:.*=modem:<dn>" --no-sip --h245tunneldisable -ttttt -o t38modem.log

Here is the UC520 setup:

voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
redirect ip2ip
fax protocol t38 version 0 ls-redundancy 5 hs-redundancy 2 fallback none
sip
registrar server
no update-callerid
!
!
dial-peer voice 2 pots
destination-pattern 602
port 0/0/1
!
!
dial-peer voice 540 voip
destination-pattern 540
session target ipv4:192.168.10.14
session transport udp
codec g711ulaw
fax rate 14400
no vad
!
dial-peer voice 541 voip
destination-pattern 541
session target ipv4:192.168.10.14
session transport udp
codec g711ulaw
fax rate 14400
no vad
!

t38modem (w/SIP) for a windows build

2010-04-02T08:38:46Z

I'm looking for a t38modem build that supports SIP to run on a Win 2003 server. I have tried TimeFax but am unable to get it to use SIP. TimeFax only wants to run with H.323. I don't have access to MSVisual C++ so I am unable to build from source myself. Any suggestions or assistance would be greatly appreciated.

How do I build a statically linked t38modem?

2010-03-24T17:54:53Z

I am using Linux RHEL4 and I need to build t38modem with static linking of ptlib and opal. Is there a way to do this?