Re: [hylafax-users] Hylafax and egetty

[Branko Markovic <bramar@xxxxxxxx>]

	These are modem answers for different commands. Both commands
AT+FCLASS=8 and AT#CLS=8 will put modem into a voice mode, and after
that (as you can see) I gave him AT#VLS=4 and got OK from modem. As you
can see, modem won't answer with OK when script send him AT#VLS=4. I
will try to find out in egetty.pl where is Nested command in shell
script, but... :)

AT S7=45 S0=0 L1 V1 X3 &c1 E1 Q0
OK
AT
OK
AT+FCLASS=8
OK
AT#CLS=8
OK
AT#VLS=4
OK

On Mon, 2005-06-06 at 10:25 -0400, George Bell wrote:
> > 06/03 08:18:23   shell(1): HELLO VOICE PROGRAM
> > 06/03 08:18:23   vm(1): READY
> > 06/03 08:18:23   vm: initialized communication
> > 06/03 08:18:23    vm: Got pipe signal
> > 06/03 08:18:23    vm: queued event SIGNAL_SIGPIPE at position 0002
> > 06/03 08:18:23    vm: unqueued event SIGNAL_SIGPIPE at position 0002
> > 06/03 08:18:23    vm: voice_handle_event got event SIGNAL_SIGPIPE with
> > data <_>
> > 06/03 08:18:23   shell(1): DEVICE DIALUP_LINE
> > 06/03 08:18:23    vm: queued event RESET_WATCHDOG at position 0003
> > 06/03 08:18:23   voice command: 'AT#VLS=4' -> 'OK'
> > 06/03 08:18:23    vm: Got pipe signal
> > 06/03 08:18:23    vm: queued event SIGNAL_SIGPIPE at position 0004
> > 06/03 08:18:23    vm: AT#VLS=4
> > 06/03 08:18:23    vm: unqueued event RESET_WATCHDOG at position 0003
> > 06/03 08:18:23    vm: voice_handle_event got event RESET_WATCHDOG with
> > data <_>
> > 06/03 08:18:23    vm: unqueued event SIGNAL_SIGPIPE at position 0004
> > 06/03 08:18:23    vm: voice_handle_event got event SIGNAL_SIGPIPE with
> > data <NUL>
> > 06/03 08:18:23   shell(2): ENABLE EVENTS
> > 06/03 08:18:23  vm: Nested command in shell script
> > 06/03 08:18:23   vm(2): ERROR
> 
> The voice library gives you a Nested command error whenever you give it
> one command before it is finished with another(an explanation of this
> error can be found in {mgetty source root}/voice/doc/Readme.voice_shell)
> In this case it appears that the previous command AT#VLS=4, which is
> supposed to take the modem off-hook, didn't execute properly, causing
> the next comman "Enable Events" to fail.  You'll need to look more
> closely into what is causing this.  Turn off faxgetty again and start
> minicom.  Manually change into voice mode.  I normally do this with "AT
> +FCLASS=8" but it appears on the Rockwell the appropriate command is
> "AT#CLS=8".  I am not sure of this as I'm not familiar with the Rockwell
> commands.  If you have difficulty with this you may need to consult the
> Rockwell manual.  Once in voice mode, try to manually command the modem
> to go off-hook with the command "AT#VLS=4".  How does the modem respond
> to this command?
> 
> George
> 
> 
> 
> ____________________ 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*
-- 
---------------
Branko Markovic
bramar@xxxxxxxx
ICQ#: 132044291



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