You can use cu to test it, e.g. cu -lttyrf dir. Then type AT if you have a
modem on the portmaster port and see if you get OK.
I don't use this anymore because it has a lot of problems. It relies on the
in.pmd demon, which doesn't work as reliably for me on ComOS 3.14. The main
problem is that cu has no way of knowing if someone has dialed in on the port
you're trying to dial out on, or if another process is using the psuedo-tty
you selected (HP doesn't seem to always pick these in order). When this happens
cu just hangs in direct mode, or takes forever to timeout in dial out mode.
kermit has the same problems, of course.
I now use telnet for device service. I like it because I can just telnet to
the netport and it will pick the next available modem (port) automatically.
Plus I can telnet from any system on my network (with host device you have to
be on the system the port was assigned to to access it). Unfortunately, cu
won't work with telnet. Some kermits will let you use a -j option with a
hostname to do a network connection. This works, except you can't use the
kermit dial command, you have to dial with ATDT. We don't use cu or kermit
anymore though. There's a product from Microlink Technologies called SoftComm
that gives us a GUI comm program with kermit, X, Y and Zmodem transfers and the
ability to use telnet to get to a portmaster, then use it's phonebook to dial
out. This set up is really slick!
Regards,
Don.