vm w/o sound card

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

I didn't find this in any of the docs. vgetty works fine for me (I haven't
tried fax or data in that I rarely use them; voice alone is great). 
However, my sound card is not supported in linux (i have Redhat 5.1;
mgetty 1.1.14 btw), so I need an alternative way to listen to messages.

Ideally, I'd like to hear them through the handset I have connected to the
modem. However, when I use 'vm play -v -l ttyS1 -H <filename>' I get an error
saying 'vm: could not set voice device'. This happens when I try to 
record instead of play as well.

So, my next best option would be to play it through the 'line out' connection
to some speakers/headphones. However, if I use the "-s" option to vm,
sounds simply go to the internal modem speaker, which is unintelligable.
I can record fine from the 'line in' connection, so that's decent enough for
me.

Following is a selected portion of /var/log/vgetty.ttyS1 (since vgetty seems
to work fine, this should be just enough to indicate what sort of modem it
is):

10/30 21:20:49 yS1  vgetty: experimental test release 0.8.1 / 25Mar98
10/30 21:20:49 yS1  mgetty: experimental test release 1.1.14-Apr02
10/30 21:20:49 yS1  reading generic configuration from config file /etc/mgetty+sendfax/voice.conf
10/30 21:20:49 yS1  reading program vgetty configuration from config file /etc/mgetty+sendfax/voice.conf
10/30 21:20:49 yS1  reading port ttyS1 configuration from config file /etc/mgetty+sendfax/voice.conf
10/30 21:20:49 yS1  check for lockfiles
10/30 21:20:49 yS1  locking the line
10/30 21:20:50 yS1  lowering DTR to reset Modem
10/30 21:20:50 yS1  send: \dATQ0V1H0[0d]
10/30 21:20:51 yS1  waiting for ``OK'' ** found **
10/30 21:20:51 yS1  send: ATS0=0Q0&D3&C1[0d]
10/30 21:20:51 yS1  waiting for ``OK'' ** found **
10/30 21:20:51 yS1  mdm_send: 'ATI'
10/30 21:20:51 yS1  USR Courier/Sportster V.34(+) detected
10/30 21:20:51 yS1  mdm_send: 'ATI3'
10/30 21:20:52 yS1  additional info: 'Texas Instruments RK Voice 33600 Fax RS Rev. 1.15'
10/30 21:20:52 yS1  mdm_send: 'AT+FCLASS=2.0' -> OK
10/30 21:20:52 yS1  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
10/30 21:20:52 yS1  mdm_send: 'AT+FBO=1' -> OK
10/30 21:20:52 yS1  mdm_send: 'AT+FNR=1,1,1,0' -> OK
10/30 21:20:52 yS1  mdm_send: 'AT+FLI="49 89 xxxxxxxx"' -> OK
10/30 21:20:53 yS1  mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> OK
10/30 21:20:53 yS1  detecting voice modem type
10/30 21:20:53 yS1  US Robotics detected
10/30 21:20:54 yS1  US Robotics voice modem
10/30 21:20:54 yS1  This is a driver beta version. V0.4.b3


And here's part of the output of vm (from /var/log/vm.log), it seems to
detect the modem the same as vgetty:

10/30 23:51:49   voice command: 'AT&H1&R2&I0' -> 'OK'
10/30 23:51:50    vm: AT&H1&R2&I0
10/30 23:51:50    vm: unqueued event RESET_WATCHDOG at position 0000
10/30 23:51:50    vm: voice_handle_event got event RESET_WATCHDOG with data <
10/30 23:51:50    US Robotics: OK
10/30 23:51:50   tio_set_flow_control( HARD )
10/30 23:51:50   voice command: 'AT#VTD=3F,3F,3F' -> 'OK'
10/30 23:51:50    vm: AT#VTD=3F,3F,3F
10/30 23:51:50    US Robotics: OK
10/30 23:51:50  VTD setup successful
10/30 23:51:50   voice command: 'AT#VSD=1#VSS=1#VSP=70' -> 'OK'
10/30 23:51:50    vm: AT#VSD=1#VSS=1#VSP=70
10/30 23:51:50    US Robotics: OK
10/30 23:51:50   vm: leaving voice mode
10/30 23:51:50   voice command: 'AT#CLS=8' -> 'OK'
10/30 23:51:50    vm: AT#CLS=8
10/30 23:51:50    US Robotics: OK
10/30 23:51:50   vm: Restoring signal handlers
10/30 23:51:50   vm: entering voice mode
10/30 23:51:50   vm: Installing signal handlers
10/30 23:51:50   voice command: 'AT#CLS?' -> ''
10/30 23:51:50    vm: AT#CLS?
10/30 23:51:50    US Robotics: 8
10/30 23:51:51   voice command: '' -> 'OK'
10/30 23:51:51    US Robotics: OK
10/30 23:51:51   voice command: 'AT#CLS=8' -> 'OK'
10/30 23:51:51    vm: AT#CLS=8
10/30 23:51:51    US Robotics: OK
10/30 23:51:51    vm: queued event RESET_WATCHDOG at position 0001
10/30 23:51:51  USR: Unknown output device (7)