RE: vgetty Help

Configure Modem to answer call
using HAYES Commands

ALL external and internal PCI voice modems since they were first
developed have been manufactured to comply to the Hayes standard.
When you turn on your modem or reset it, your modem loads the
?active configuration profile? into non-volatile memory (NVRAM). The
active configuration profile is a group of configuration settings,
derived from the values of the modem?s internal S registers, that
define how the modem will operate. The active configuration profile
can be either the factory default, or one of two user defined
profiles. The first time your modem is turned on, the factory
default profile is loaded into the ?active profile' in non-volatile
memory (NVRAM). The factory default profile is stored in the modem?s
read-only memory (ROM) and cannot be changed. The factory default
profile contains standard settings which allow the majority of users
to use their modem without ever knowing about the Hayes standard.
Modems are not factory configured to answer incoming calls by
default, so you will have to manually create your own user profile,
enable auto answer on first ring, save it to one of the user
profiles in NVRAM, and tell the modem to use it as the default
profile on power up and reset.

Use the 'tip' command to send Hayes commands to permanently
configure the modem to answer incoming calls.

Note: The Hayes modem commands are capital letters and the '0' is a
zero.


On the command line enter

tip comX # where X is the com port your modem is on.
AT&F0 # load the factory default profile0 into current profile.
ATS0=1 # tell current profile to answer on first ring.
AT&W0 # write current profile to saved user profile0.
AT&Y0 # tell modem to load user profile0 as default on power
up.


Use the keyboard ~ key followed by the . key to exit tip.


The above is from the FreeBSD install guide at www.a1poweruser.com

Now I know nothing about vgetty so this is a shot in the dark, But I
would think
changing your init-string handed to the modem via mgetty.config:
from this

ATS0=0Q0&D3&C1

to this

ATS0=1 should do the trick if you have configured vgetty
correctly.

Or just follow the above instructions and update the modems internal
config and
remove the init string statement from vgetty and be done with it.

Good luck.


-----Original Message-----
From: owner-freebsd-questions@xxxxxxxxxxx
[mailto:owner-freebsd-questions@xxxxxxxxxxx]On Behalf Of Robert
McIntosh
Sent: Tuesday, June 27, 2006 11:09 PM
To: freebsd-questions@xxxxxxxxxxx
Subject: Re: vgetty Help


Thanks fbsd,

It seems that the init string command gives to this modem (which has
a
Conexant chipset, according to Creative's website) is incorrect.

This init-string handed to the modem via mgetty.config: (again, this
is
for vgetty)

ATS0=0Q0&D3&C1

I'm not familiar with Hayes compatible commands and hoping someone
has
some tips for me out there.

Thanks again,
Robert

fbsd wrote:
you have to use your modems native "AT" commands to tell it to
answer inbound calls and then save that config on the modem and
set
it as the default config to use when the modem is powered on.

-----Original Message-----
From: owner-freebsd-questions@xxxxxxxxxxx
[mailto:owner-freebsd-questions@xxxxxxxxxxx]On Behalf Of Robert
McIntosh
Sent: Monday, June 26, 2006 2:49 PM
To: freebsd-questions@xxxxxxxxxxx
Subject: vgetty Help


Hi,

I'm running into problems getting vgetty to function as an
answering
machine. I've got a Creative ModemBlaster V.92 Serial DE5621 on
/dev/cuaa1

I'll call my number and the modem simply does not pick up.

I the modem reports to be a voice modem from minicom, so I know it
has
this capability.

Here's my configuration and log sample.

Thanks in advance for any pointers,
Robert

#cat /usr/local/etc/mgetty+send/voice.conf (comments removed)


part generic
###
voice_log_level 4
voice_shell_log /var/log/vgetty_voice_shell.%s
voice_dir /var/spool/voice
phone_owner root
phone_group phone
phone_mode 0660
message_flag_file .flag
receive_dir incoming
message_dir messages
message_list Index
backup_message standard.rmd
port_speed 38400
voice_shell /bin/sh
port_timeout 10
dial_timeout 90
command_delay 100
dtmf_len 30
dtmf_threshold 40
dtmf_wait 7
ignore_fax_dle false
raw_data false
rec_compression 0
rec_speed 0
rec_silence_len 70
rec_silence_threshold 40
rec_remove_silence false
rec_max_len 300
rec_min_len 0
do_hard_flow true
beep_frequency 933
beep_length 1500
max_tries 3
retry_delay 5
watchdog_timeout 60
receive_gain -1
transmit_gain -1
enable_command_echo false
poll_interval 10
enable_compression_mapping_querry TRUE
compression_8bit_linear_signed 0
compression_16bit_linear_signed 0
compression_8bit_linear_unsigned 1
compression_8bit_ulaw 4
compression_8bit_alaw 5
compression_2bit_adpcm 140
compression_4bit_adpcm 141
compression_4bit_ima_adpcm 129

program vgetty
###
rings 3
answer_mode voice:fax:data
force_autodetect false
toll_saver_rings 0
rec_always_keep true
button_program
call_program
dtmf_program dtmf.sh
message_program
do_message_light false
ring_report_delay 15

program vm
###
voice_devices cuaa1
dialout_timeout 90
ringback_goes_away 70
ringback_never_came 100

program pvf
###
port cuaa1
rings 3
ring_type ring
answer_mode voice:fax:data
####

Output from the log...
#tail -f /var/log/vgetty.cuaa1
06/26 11:38:52 aa1 waiting...
06/26 11:39:11 aa1 wfr: waiting for ``RING''
06/26 11:39:11 aa1 wfr: waiting for ``RING''
06/26 11:39:17 aa1 wfr: waiting for ``RING''
06/26 11:39:23 aa1 reading ring_type ring configuration from
config
file /usr/local/etc/mgetty+sendfax/voice.conf
06/26 11:40:04 aa1 vgetty: timeout while reading character from
voice modem
06/26 11:40:15 aa1 vgetty: timeout while reading character from
voice modem
06/26 11:40:15 aa1 vgetty: Could not answer the phone. Strange...
--
06/26 11:40:15 aa1 vgetty: experimental test release 0.9.32 /
with
duplex patch
06/26 11:40:15 aa1 mgetty: interim release 1.1.34-Nov30
06/26 11:40:15 aa1 reading generic configuration from config file
/usr/local/etc/mgetty+sendfax/voice.conf
06/26 11:40:15 aa1 reading program vgetty configuration from
config
file /usr/local/etc/mgetty+sendfax/voice.conf
06/26 11:40:15 aa1 reading port cuaa1 configuration from config
file
/usr/local/etc/mgetty+sendfax/voice.conf
06/26 11:40:15 aa1 check for lockfiles
06/26 11:40:15 aa1 locking the line
06/26 11:40:15 aa1 lowering DTR to reset Modem
06/26 11:40:16 aa1 send: ATS0=0Q0&D3&C1[0d]
06/26 11:40:16 aa1 waiting for ``OK'' ** found **
06/26 11:40:16 aa1 mdm_send: 'ATI'
06/26 11:40:16 aa1 Generic Rockwell modem (56000)
06/26 11:40:16 aa1 mdm_send: 'ATI3'
06/26 11:40:16 aa1 mdm_send: 'ATI4'
06/26 11:40:16 aa1 additional info: 'a007040284C6002F'
06/26 11:40:16 aa1 modem quirks: 0004
06/26 11:40:16 aa1 mdm_send: 'AT+FCLASS=2' -> OK
06/26 11:40:16 aa1 mdm_send: 'AT+FCLASS=0' -> OK
06/26 11:40:16 aa1 mdm_send: 'AT+FAA=1;+FCR=1' -> OK
06/26 11:40:16 aa1 mdm_send: 'AT+FBOR=0' -> OK
06/26 11:40:16 aa1 mdm_send: 'AT+FLID="503.244.7197"' -> OK
06/26 11:40:17 aa1 mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
06/26 11:40:17 aa1 detecting voice modem type
06/26 11:40:18 aa1 Rockwell detected
06/26 11:40:30 aa1 vgetty: timeout while reading character from
voice modem
06/26 11:40:30 aa1 initializing ROCKWELL voice modem
06/26 11:40:30 aa1 vgetty: Modem returned ERROR
06/26 11:40:30 aa1 can't set silence period
06/26 11:40:30 aa1 vgetty: Modem returned ERROR
06/26 11:40:30 aa1 can't set transmit gain
06/26 11:40:30 aa1 vgetty: Modem returned ERROR
06/26 11:40:30 aa1 can't set record gain
06/26 11:40:30 aa1 vgetty: Modem returned ERROR
06/26 11:40:31 aa1 can't disable silence deletion
06/26 11:40:31 aa1 vgetty: Modem returned ERROR
06/26 11:40:31 aa1 can't set DLE responses
06/26 11:40:31 aa1 vgetty: Modem returned ERROR
06/26 11:40:31 aa1 can't set silence threshold
06/26 11:40:31 aa1 vgetty: Modem returned ERROR
06/26 11:40:32 aa1 waiting...
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe@xxxxxxxxxxx"



--
Robert McIntosh
mcintoshrt@xxxxxxxxx
rupreckt1553 (AIM)
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe@xxxxxxxxxxx"

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"