Re: Unspecified Transmit Phase C Error

On 05/09/2018 01:51 PM, Brian wrote:
> To add another layer on this, the remote device stayed connected for 
> 64mins (this is a long distance fax) and we have had others that, 
> according to the remote site and our phone company, have gone on for 
> hours even though we see this as ended.
>
> May 08 13:04:11.47: [ 3625]: Unspecified Transmit Phase C error
> May 08 13:04:11.47: [ 3625]: <-- [9:AT+FRS=7\r]
> May 08 13:04:11.49: [ 3625]: --> [2:OK]
> May 08 13:04:11.49: [ 3625]: <-- [9:AT+FTH=3\r]
> May 08 13:04:11.51: [ 3625]: --> [7:CONNECT]
> May 08 13:04:11.51: [ 3625]: <-- data [3]
> May 08 13:04:11.51: [ 3625]: <-- data [2]
> May 08 13:04:12.59: [ 3625]: --> [2:OK]
> May 08 13:04:13.59: [ 3625]: <-- [5:ATH0\r]
> May 08 13:04:13.71: [ 3625]: --> [2:OK]
> May 08 13:04:13.71: [ 3625]: SESSION END
>
> It looks like it hangs up correctly. Is there anything we can do to 
> ensure that the line is indeed hung up?

The modem sent a hangup signal to the PBX (presumably Asterisk). So, if 
the call did not disconnect then something is wrong downstream on the 
call (Asterisk, telco, etc.)

Furthermore, it's difficult for me to conceive that the receiver did not 
hang up for that long of a time, either... unless they both have the 
same type of bug on their PBXes.

Thanks,

Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe [email protected] < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*