The ACS6000 is available with a built-in analog modem which can be used for Out-of-band (OOB) management. The unit supports terminal based logins and PPP logins. The client/caller requires a compatible modem with a standard configuration for dial-out. He can use a terminal program like Hyperterm, Minicom, Picocom or Putty or a PPP client to dial into the ACS6000.
Dial-in
---------
This is a configuration example for dial-in.
On this example PPP is using PAP and the username "dialin" for authentication.
1) Ports -> Auxiliary Ports
Status: Enabled
Speed: 38400
Init Chat: "" \d\d\d+++\d\d\dATZ OK
PPP Address: Local Configuration
Local IPv4 Address: 10.10.10.1
Remote IPv4 Address: 10.10.10.2
PPP Authentication: By Appliance
Protocol: PAP
Save
2) Users -> Local Accounts -> User Names -> Add
User Name: dialin
Password: <password>
Confirm password: <password>
Save
3) Ports > Dial-In Profile > Settings
Log In To Appliance: Enable
PPP Connection: Enable
Save
Note:
On PPP sessions the log message "Cannot determine ethernet address for proxy ARP" is uncritical.
Callback
------------
This is a configuration example for callback, a working dial-in configuration is required.
On this example the user "cbuser" is used to trigger a callback to the phone number 20. To trigger the callback, dial into the ACS6000 and login as "cbuser".
1) Ports > Dial-In Profile > Settings
Log In To Appliance: Callback
PPP Connection: Callback
Save
2) Ports > Dial-In Profile > Secure Dial-in > Callback Users > Add
Callback User: cbuser
Callback Number: 20
Save
Note:
If the callback log /var/log/mgetty.callback shows "dialup: got 'NO DIALTONE'" then the modem is unable to detect the dialtone of the telephone system. To switch off dialtone detection use the following init chat configuration:
Ports -> Auxiliary Ports
Init Chat: "" \d\d\d+++\d\d\dATZ OK ATX3 OK
Save
If a callback is triggered then it can take several minutes till the ACS6000 gives up to call the user back. During this time it is not possible to dial-in or trigger another callback. To force a timeout, login as root on the ACS6000 and execute "killall callback".
Logging and Troubleshooting
-----------------------------------------
This section contains logging and troubleshooting information. They are helpful if something doesn't work as expected.
The file /var/log/mgetty.ttyM1 contains the modem log, e.g. the command "tail -f /var/log/mgetty.ttyM1" can be used as root to display the appended data as the file grows. The file /var/log/mgetty.callback contains the callback log. Below are log examples of working connections to help troubleshooting:
1) Modem Initialisation
--
02/24 16:20:57 yM1 mgetty: interim release 1.1.33-Apr10
02/24 16:20:57 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in)
02/24 16:20:57 yM1 check for lockfiles
02/24 16:20:57 yM1 locking the line
02/24 16:20:57 ##### failed dev=ttyM1, pid=20853, got signal 15, exiting
02/24 16:20:57 yM1 lowering DTR to reset Modem
02/24 16:20:58 yM1 send: \d\d\d+++\d\d\dATZ[0d]
02/24 16:21:01 yM1 waiting for ``OK'' ** found **
02/24 16:21:02 yM1 waiting...
2) Dial-in with terminal based login
02/24 16:33:47 yM1 wfr: waiting for ``RING''
02/24 16:33:47 yM1 send: ATA[0d]
02/24 16:33:47 yM1 waiting for ``CONNECT'' ** found **
02/24 16:34:35 yM1 send:
02/24 16:34:35 yM1 waiting for ``_'' ** found **
02/24 16:34:42 ##### data dev=ttyM1, pid=21636, caller='none', conn='38400', name='', cmd='/bin/login', user='ts'
3) Hang up
--
02/24 16:35:13 yM1 mgetty: interim release 1.1.33-Apr10
02/24 16:35:13 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in)
02/24 16:35:13 yM1 check for lockfiles
02/24 16:35:13 yM1 locking the line
02/24 16:35:14 yM1 lowering DTR to reset Modem
02/24 16:35:15 yM1 clean_line: only 500 of 668 bytes logged
02/24 16:35:15 yM1 send: \d\d\d+++\d\d\dATZ[0d]
02/24 16:35:18 yM1 waiting for ``OK'' ** found **
02/24 16:35:18 yM1 waiting...
4) Dial-in to trigger callback
02/24 17:21:53 yM1 wfr: waiting for ``RING''
02/24 17:21:53 yM1 send: ATA[0d]
02/24 17:21:53 yM1 waiting for ``CONNECT'' ** found **
02/24 17:22:13 yM1 send:
02/24 17:22:13 yM1 waiting for ``_'' ** found **
02/24 17:22:18 ##### data dev=ttyM1, pid=26169, caller='none', conn='38400', name='', cmd='/sbin/callback', user='cbuser'
--
02/24 17:22:19 yM1 mgetty: interim release 1.1.33-Apr10
02/24 17:22:19 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in)
02/24 17:22:19 yM1 check for lockfiles
02/24 17:22:19 yM1 locking the line
02/24 17:22:19 yM1 lowering DTR to reset Modem
02/24 17:22:20 yM1 clean_line: only 500 of 912 bytes logged
02/24 17:22:20 yM1 send: \d\d\d+++\d\d\dATZ[0d]
02/24 17:22:23 yM1 waiting for ``OK'' ** found **
02/24 17:22:23 yM1 send: ATX3[0d]
02/24 17:22:23 yM1 waiting for ``OK'' ** found **
02/24 17:22:24 yM1 waiting...
02/24 17:22:43 yM1 lock not made: lock file exists (pid=26388)
5) Callback (/var/log/mgetty.callback)
02/24 17:22:43 PID for mgetty on line ttyM1: 26389
02/24 17:22:43 yM1 no config file found: /etc/mgetty+sendfax/callback.config
02/24 17:22:43 yM1 initializing modem...
02/24 17:22:43 yM1 send: ATQ0V1H0[0d]
02/24 17:22:43 yM1 waiting for ``OK'' ** found **
02/24 17:22:43 yM1 send: AT+FCLASS=0[0d]
02/24 17:22:43 yM1 waiting for ``OK'' ** found **
02/24 17:22:43 yM1 dialing 20...
02/24 17:22:43 yM1 mdm_send: 'ATD20'
02/24 17:22:43 yM1 dialup: got 'ATD20'
02/24 17:23:06 yM1 dialup: got 'CONNECT 38400'
02/24 17:23:06 yM1 got CONNECT, success!
02/24 17:23:07 ##### callback: success, device=/dev/ttyM1, mgetty=26389
6) Terminal based login on the callback connection
02/24 17:23:07 yM1 Got callback signal from pid=26388!
02/24 17:23:07 yM1 stealing lock file from pid=26388
02/24 17:23:49 ##### data dev=ttyM1, pid=26389, caller='none', conn='', name='', cmd='/bin/login', user='shell'
7) Hang up the callback connection
--
02/24 17:26:03 yM1 mgetty: interim release 1.1.33-Apr10
02/24 17:26:03 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in)
02/24 17:26:03 yM1 check for lockfiles
02/24 17:26:03 yM1 locking the line
02/24 17:26:04 yM1 lowering DTR to reset Modem
02/24 17:26:05 yM1 clean_line: only 500 of 1503 bytes logged
02/24 17:26:05 yM1 send: \d\d\d+++\d\d\dATZ[0d]
02/24 17:26:08 yM1 waiting for ``OK'' ** found **
02/24 17:26:08 yM1 send: ATX3[0d]
02/24 17:26:08 yM1 waiting for ``OK'' ** found **
02/24 17:26:08 yM1 waiting...
8) Dial-in with PPP
02/24 17:34:26 yM1 wfr: waiting for ``RING''
02/24 17:34:26 yM1 send: ATA[0d]
02/24 17:34:26 yM1 waiting for ``CONNECT'' ** found **
02/24 17:34:46 yM1 send:
02/24 17:34:46 yM1 waiting for ``_'' ** found **
02/24 17:34:47 ##### data dev=ttyM1, pid=27094, caller='none', conn='38400', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'
9) Hang up PPP session
--
02/24 17:36:50 yM1 mgetty: interim release 1.1.33-Apr10
02/24 17:36:50 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in)
02/24 17:36:50 yM1 check for lockfiles
02/24 17:36:50 yM1 locking the line
02/24 17:36:51 yM1 lowering DTR to reset Modem
02/24 17:36:51 yM1 send: \d\d\d+++\d\d\dATZ[0d]
02/24 17:36:54 yM1 waiting for ``OK'' ** found **
02/24 17:36:55 yM1 send: ATX3[0d]
02/24 17:36:55 yM1 waiting for ``OK'' ** found **
02/24 17:36:55 yM1 waiting...