Bug 44950 - vgetty won't answer in voice mode Rockwell
Summary: vgetty won't answer in voice mode Rockwell
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mgetty
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-19 02:33 UTC by Ken
Modified: 2007-04-18 16:33 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2005-07-20 16:19:36 UTC


Attachments (Terms of Use)
vgetty log file (21.31 KB, text/plain)
2001-06-19 02:43 UTC, Ken
no flags Details

Description Ken 2001-06-19 02:33:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)

Description of problem:
With a Rockwell modem:

when vgetty sends
AT#CLS=8

Rockwell responds with:

OK
<DLE><h>

the <DLE><h> is standard according to Rockwell chipset modem manuals.

eventually the <DLE><h> causes vgetty to "leave voice mode"
and issue AT#CLS=0

thus, vgetty never can answer the telephone in voice mode

How reproducible:
Always

Steps to Reproduce:
1. every time vgetty starts up or respawns
2.
3.
	

Actual Results:  see above

Expected Results:  Expected that <DLE><h> would be ignored as normal status
report from modem after switching into voice mode. (per Rockwell chipset
manual).

Additional info:

Comment 1 Ken 2001-06-19 02:43:11 UTC
Created attachment 21286 [details]
vgetty log file

Comment 2 Jason Vas Dias 2005-07-20 16:19:36 UTC
Sorry for the long delay in processing this bug report - it slipped through
the cracks somehow.
Modern mgetty (eg 1.1.33) now handles the <DLE><h> sequence correctly.


Note You need to log in before you can comment on or make changes to this bug.