This is a discussion on Re: Serial Telnet to PBX Switch - Protocols ; In article , Chris McKeever wrote: : I have been doing some searching for how I can connect from a linux : box to our phone PBX. Below is a thread that helped me get a good : portion of ...
In article <firstname.lastname@example.org>,
Chris McKeever wrote:
: I have been doing some searching for how I can connect from a linux
: box to our phone PBX. Below is a thread that helped me get a good
: portion of the way, but I am still a bit stuck.
: I have been successful in connecting through the serial port using
: minicom or kermit to the PBX from the linux command line. I however
: am faced with the issue that some of the commands that I want to
: perform just wont work.
: The PBX asks what type of terminal, the choices are:
: It seems that the most vanilla of these is the VT220.
If you are running Kermit from the Console window, your terminal
type is "Linux console". If you are running Kermit in an xterm or
similar window, your terminal type depends on the xterm program.
It's vt220 if you are using Xfree86 xterm:
Since that's what the PBX wants, that's what you should use.
: Kermit and minicom work, but I do not have the F3 key, which 'sends'
: the changes into the switch, for the most part, everything else is
: ** Kermit connects, but I have no backspace - believe it emulates a
: VT220, so I am confused as to this..am I mistaken here?
In Unix (including Linux), Kermit is a communication program, not a
terminal emulator (as it is in DOS or Windows). This is explained at
Your terminal emulator is the console or X window in which you are running
Kermit. The same is true for other Unix-based terminal programs (cu, tip,
telnet, ssh, etc) and I believe also of minicom.
: So I am trying to figure out how to get Kermit to behave nicely with
: the function keys and the backspace, or minicom to work with the
: function keys.
About Backspace, see:
and after reading the explanatory material, find the answer in the
section, "When C-Kermit Is the Client".
Function keys are another story. Unix applications (other than X-based
ones) can't see the function keys, so this must be handled by your xterm
setup, normally in the xmodmap configuration file. You can find some
(search for "xmodmap" -- there are various references throughout the
document.) You have to find out what characters a particular F key sends,
and then map the key to send them in in .xmodmaprc or whatever. If you
are using Xfree86 xterm (which does indeed emulate the vt220) then the
F keys should already be set up. Just make sure you are pushing the
right one. For example the DEC "Do" key is F16 (not F3).
On a real DEC terminal, F16 ("Do") sends ESC [ 29 ~ (that's Escape,
left bracket, 2, 9, and tilde, in sequence with no spaces).
Since you are probably using a PC keyboard, you'll find that there is no
F15 key -- PC F-keys only go up to F12, but DEC keyboards go up to F20.
So usually there is a mapping like Shift F1 = F13, Shift F2 = F14, etc.
Some people find this so annoying that they go out and purchase DEC
keyboards for their PCs :-) But it can all be handled in xmodmap too.
In Windows or DOS, you could do the mapping directly in Kermit, where
Kermit really is a terminal emulator since it can get (more or less)
directly at the keyboard and screen.