HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] T.30 T2 timeout, expected signal not received



Hi Lee,

You're absolutely right - as always ... It appeared that signal level on transmitter side is less then -25dB - where it should be max -2.5... -5dB ... now we're talking with telco to figure out what's going on on the line.

Thanks,
Marcin

Lee Howard pisze:
Marcin Giedz wrote:
I'm facing some problems with sending facsimiles from Hylafax+ version 5.2.7 using IAX modems + Sangom CARD + Asterisk. Connection is established but during "send phase" something goes wrong. Here is the log from last session:

lis 26 13:41:32.34: [ 4853]: SESSION BEGIN 000017120 XXXX
lis 26 13:41:32.34: [ 4853]: HylaFAX (tm) Version 4.4.4

lis 26 13:41:56.11: [ 4853]: RECV received frame number 33
lis 26 13:41:56.11: [ 4853]: RECV assumed RCP frame with block end
lis 26 13:41:56.11: [ 4853]: --> HDLC<5:FF C0 61 96 D3>
lis 26 13:41:56.11: [ 4853]: MODEM input buffering disabled
lis 26 13:41:56.11: [ 4853]: --> [10:NO CARRIER]
lis 26 13:41:56.11: [ 4853]: <-- [9:AT+FRH=3\r]
lis 26 13:41:56.42: [ 4853]: --> [7:CONNECT]
lis 26 13:42:02.72: [ 4853]: --> [2:10 03]
lis 26 13:42:02.72: [ 4853]: --> [10:NO CARRIER]
lis 26 13:42:02.72: [ 4853]: MODEM No carrier
lis 26 13:42:02.72: [ 4853]: <-- [9:AT+FRH=3\r]
lis 26 13:42:02.91: [ 4853]: --> [7:CONNECT]
lis 26 13:42:12.91: [ 4853]: MODEM TIMEOUT: receiving HDLC frame data
lis 26 13:42:12.91: [ 4853]: <-- data [1]
lis 26 13:42:12.92: [ 4853]: --> [2:]
lis 26 13:42:12.92: [ 4853]: --> [2:OK]

Just to be clear - on the receive-side you're using HylaFAX 4.4.4 and a hardware modem on ttyS7.


What happens is that the received audio is broken in the middle of Phase C. Thus the "assumed RCP frame with block end". This will happen, for example, with jitter. The receiving modem then goes to listen for the partial-page message (+FRH=3 - V.21 HDLC), the receiving modem erroneously reports CONNECT (twice) on V.17 audio, and then the receive-side gives up.

So there was a glitch in the audio and then a small modem bug on the receiver mixed with a less-tolerant HylaFAX operation on the receiver caused the failure.

Start analyzing the audio path to figure out why it's being disturbed. Even if the receiver didn't have a problem in recovering from this you'd still want the audio problem to be fixed.

Thanks,

Lee.


-- Pozdrawiam Marcin Giedz Wiceprezes Zarządu

ARISE M.Giedz, T.Żebruń Sp.j.
mob. +48 502 537 157
mail: marcin.giedz@xxxxxxxx

ul. Waliców 11
00-851 Warszawa
tel./fax +48 (22) 583 93 40
http: www.arise.pl

ARISE M.Giedz, T.Żebruń Sp.j. z siedzibą w Świerże, ul. Jana Pawła II 44, 22-175 Dorohusk, zarejestrowana przez Sąd Rejonowy - Sąd Gospodarczy w Lublinie, XI Wydział Gospodarczy Krajowego Rejestru Sądowego, pod nr KRS 0000267203; REGON 060191418; NIP 563-230-12-18; z pokrytym w całości kapitałem zakładowym wynoszącym 24,000.00 zł.





____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*




Project hosted by iFAX Solutions