Our callback windows users have to add the &C0 command to the modem
extra configuration, so when the PM disconnects for calling back,
windows didn't notice it.
This doesn't work with the Supra internal modems, any idea why ???
Another thing, for the callback to work, the user also has to automated
the login with a script:
proc main
waitfor "ogin:"
transmit $USERID+"^M"
waitfor "assword:"
transmit $PASSWORD+"^M"
;
; Now the PM hangs up the line and callback. The modem has S0=1
;
waitfor "CONNECT"
endproc
This script really do nothing except send the login and password to the
PM. But if the users didn't install it, once the user modem answer the
callback, before even the modems ends with the connection negotiation,
windows hangs up. Anyone knows why ???
Cheers,
Diego.
-- Diego Manuel Sierra Gonzalez mailto:dsg@iac.es Ing. Telecomunicaciones, Centro de Calculo Fax#: +34 922 605210 INSTITUTO DE ASTROFISICA DE CANARIAS Pho#: +34 922 605285/00 Tenerife. Canary Islands. SPAIN http://www.iac.es
- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-modems' in the body of the message.