# vers. 0.76 # Fri Apr 26 13:59:42 2002 -Complete re-write in pygtk, so no more need for wx-windows and wxpython. Dropped the separate prefs program, so it's a little bigger, but loads about 3 times faster. - simplified the interface by ditching some buttons - added colour for new/old messages - added sortable columns - added send wav as email - added an option to edit a fax with, e.g., gimp - Moved stuff to system standard locations. Install ~~~~~~~ First, install vgetty rpms, of course. To install Voxpak unpack the tarball somewhere and copy the contents to the appropriate places. *If* you use the supplied config files for mgetty/vgetty, search and replace the mgetty/vgetty configs for 'yourname' and replace with your real login name. Also, change the fax number in mgetty.conf to your own. I have a USR 56k VDF modem, so you may need to change mgetty's init-chat string to match your own. - Add the respawn line for vgetty to your inittab (if you haven't done so already). It looks like this: 'mo:235:respawn:/sbin/vgetty /dev/modem' - Chown /var/spool/voice and fax (and subdirs) to root.uucp and make sure you are in uucp group. - Chmod the same to make sure group has rw permissions. - make yourself a greeting message and copy it into /var/spool/voice/messages and update the index The scripts for X pop-ups and file renaming/log writing etc. are included in the archive, you just need to configure mgetty/vgetty, so they know to use them. I happen to have Voxpak attached to the key combination of ctrl+shift+V, but you could put it on an icon or a menu if you prefer. Or just type 'voxpak' in an xterm. I'm using 'xbindkeys' and 'xbindkeys-config' from: http://hocwp.free.fr/xbindkeys/xbindkeys.html http://www.netchampagne.com/Xbindkeys_config/ wxWindows ~~~~~~~~~ No longer needed. Vgetty ~~~~~~ Poor vgetty gets a bad rap for being difficult to configure, but I think most of it is just a consequence of being on a multi-user operating system with permissions. Anyhow, after you install the rpms you'll need to add this line to your /etc/inittab mo:235:respawn:/sbin/vgetty /dev/modem This will run vgetty and make sure that it's running all the time. After answering the the phone vgetty actually *exits*. With this line in inittab, linux will run it again right away. Now, the device named in the line really could be /dev/ttySn where n is the number your modem is really attached to, but Voxpak can't handle that yet... The first internal modem on linux boxes seems to be ttyS3, so /dev/modem is really just a symlink to /dev/ttyS3. The external ports are normally ttyS0 and ttyS1. If you are using dial-up for the internet you probably have permissions for your modem device already. Otherwise, you should check and make sure. It's very important that your dialer, say Kppp or wvdial is creating lock files and that it's using the very same name. You might think that since both /dev/modem and /dev/ttyS3 resolve to the same device it wouldn't matter, but it *does*. The file in /var/lock is just a text file with the name of the device, so make sure they are both locking the device using the same name. If you get it wrong you will find that vgetty works fine, but you can never dial out! Next, configuring vgetty and mgetty themselves. They each have a configuration script in /etc/mgetty+sendfax. This is where you tell them which device to use (/dev/modem) and who should own the new files it creates for vox messages and faxes (you). If other people have logins on the machine and need access you could make a 'phone' group and add everyone to it. (I just use the 'uucp' group). Don't forget to chown /var/spool/voice and fax to, say root.uucp and ensure that they are group writable. There are lots of other things to play with in the vgetty config and they're either obvious or well commented. If you want to have file renaming and sticky notes etc. put in the paths to the scripts each program should use. For mgetty you do that by naming it beside the entry for 'cnd-program' for vgetty it's 'message_program'. You'll need to put in the whole path (e.g. '/usr/bin/cnd-program.py'), because vgetty is run as root and doesn't have your environment. While still root, issue a 'killall -9 vgetty'. This will kill vgetty, but the kernel will respawn it right away and it will have read your new config files. One last thing. I have lately discovered that mgetty can run a script after it receives a fax! This means that we can now have faxes renamed to date+caller-id -- the same as voice messages. It is not a configuration item. Both the name and the path to the script are hard-coded into the mgetty binary. The 'strings' program can be used to find out where mgetty expects the script to be found. Running 'strings /sbin/mgetty | grep new_fax' on my system returns: /etc/mgetty+sendfax/new_fax Hopefully Debian systems will show something equally appropriate. The 'new_fax' script hasn't had much testing, since I don't get faxed as a rule. Lemme know.