Re: [hylafax-users] receive error

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Dirk Salva wrote:

> On Sun, Jun 18, 2006 at 04:00:47PM -0700, Lee Howard wrote:
>  
>
> > However, the rest of your log shows *a lot* of data loss occurring 
> > between sender and receiver.  My guess is that you need to have your 
> > phone lines checked... or you're using VoIP.
> >    
>
> No, I don't think so. It was an analogue call about ISDN with Siemens
> PABX, that's the point why I'm wondering.
>
> Jun 18 12:06:17.26: [ 8123]: <-- [9:AT+FRH=3\r]
> Jun 18 12:06:17.73: [ 8123]: --> [7:CONNECT]
> Jun 18 12:06:18.70: [ 8123]: --> [2:OK]
> Jun 18 12:06:18.70: [ 8123]: SEND recv CTR (confirm continue to correct)
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 1
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 2
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 3
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 7
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 8
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 9
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 10
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 11
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 12
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 13
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 16
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 17
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 19
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 20
> Jun 18 12:06:18.70: [ 8123]: SEND send frame number 21
> Jun 18 12:06:18.71: [ 8123]: SEND send frame number 22
> Jun 18 12:06:18.71: [ 8123]: SEND send frame number 23
> Jun 18 12:06:18.71: [ 8123]: SEND send frame number 24
> Jun 18 12:06:18.71: [ 8123]: DELAY 200 ms
> Jun 18 12:06:18.91: [ 8123]: <-- [10:AT+FTM=96\r]
> Jun 18 12:06:18.94: [ 8123]: --> [7:CONNECT]
> Jun 18 12:06:18.94: [ 8123]: <-- data [1038]
> Jun 18 12:06:19.33: [ 8123]: <-- data [1035]
> Jun 18 12:06:19.73: [ 8123]: <-- data [1036]
> Jun 18 12:06:20.13: [ 8123]: <-- data [1034]
> Jun 18 12:06:21.28: [ 8123]: <-- data [980]
> Jun 18 12:06:21.79: [ 8123]: <-- data [2]
> Jun 18 12:06:23.65: [ 8123]: --> [2:OK]

Well, this log compared with the other one shows no apparant 
dissynchronization. So on the receive-side it was saying +FCERROR after 
AT+FRM=96 when the sender was sending with AT+FTM=96. This can only mean 
that either 1) the modems are incompatible with their V.29 modulators 
(not likely since this is the same kind of modem on both ends), or 2) 
the line problems are corrupting the audio to a point that it is 
tricking the receiver into thinking that the V.29 signalling is V.21 
(this would seem more believeable at this point).

So, you really need to start investigating why there is so much audio 
corruption going on. You can monitor results by watching the logs. If 
you see a lot of FCS errors and PPR signals, etc. then you know that 
there is still audio distortion occurring.

Lee.


____________________ 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*