Hi,
I am trying connecting to remote devices(say device1 and device2) via same modem. Am able to connect to device1 using wvdial ,However cannot connect to device2 via wvdial the ppp deamon is created and dies within seconds,following is the output am getting
-> WvDial: Internet dialer version 1.41
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2
ATQ0 V1 E1 S0=0 &C1 &D2
OK
--> Sending: ATM0
ATM0
OK
--> Modem initialized.
--> Sending: ATDT 5006
--> Waiting for carrier.
ATDT 5006
CONNECT 115200
Welcome
--> Carrier detected. Waiting for prompt.
login:
--> Looks like a login prompt.
--> Sending: pspt
pspt
Password:
--> Looks like a password prompt.
--> Sending: (password)
~[7f]}#@!}!}!} $}!}$}%\}#}%B#}%}%}&H[05]U.}'}"}(}"}1}$}%\}3})}#} @I}/Bu|K~
--> PPP negotiation detected.
--> Starting pppd at Tue Jun 29 09:43:17 2004
--> PPP daemon has died! (exit code = 16)
--> Disconnecting at Tue Jun 29 09:43:37 2004
--> Auto Reconnect will be attempted in 5 seconds
--> pppd error! Look at files in /var/log for an explanation.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2
ATQ0 V1 E1 S0=0 &C1 &D2
OK
--> Sending: ATM0
ATM0
OK
--> Modem initialized.
--> Initializing modem.
--> Sending: ATZ ....

Also note that am able to connect to device2 via windows dialer connection.
the OS am using is Red Hat 8.1 AS
Following is the modem and driver information
Name : dgdm Relocations: (not relocateable)
Version : 1.1 Vendor: Digi International
Release : 1 Build Date: Fri 26 Mar 2004 03:46:28 PM EST
Install date: Fri 26 Mar 2004 03:47:46 PM EST
Group : Applications/Communications Source RPM: dgdm-1.1-1.src.rpm
Size : 4336344 License: GPL
Packager : Scott Kilau <scottk at digi dot com>
URL : http://www.digi.com/
Summary : The Dense Modem Drivers and System Software
Description :
This packages contains the device drivers and the supporting management
applications for the following Digi International adapter families:
Digi DataFire RAS
Digi DataFire DSP cPCI
Digi AccelePort RAS
Digi AccelePort Xp

modinfo /lib/modules/2.4.9-e.3smp/misc/dgdm.o
filename: /lib/modules/2.4.9-e.3smp/misc/dgdm.o
description: "Driver for dxb2 based product line"
author: "Digi International, http://www.digi.com"
license: "GPL"
parm: indevice string
parm: outdevice string
parm: printdevice string
parm: specdevice string
parm: ramdevice string
parm: dspramdevice string
parm: flashdevice string
parm: vpdalldevice string
parm: iodevice string
parm: regdevice string
parm: gdbdevice string
parm: dmabufdevice string
parm: rawdxbdevice string
parm: major int, description "Default major number"
parm: tty int, description "Run as tty (Serial and Callout) driver"
parm: print int, description "Enable Transparent Print"
parm: control int, description "Register Control devices"
parm: isdn int, description "Run as an ISDN driver"
parm: debug int, description "Driver debugging level"
parm: rawreadok int, description "Bypass flip buffers on input"
parm: cook_size int, description "Size of each channels LD cook buffer"
parm: loopback int, description "All tty channels are loopbacks"
parm: intr_period int, description "Period for interrupts"
parm: polling int, description "Poll boards instead of using interrupts"
parm: download int, description "If not set, we do not download the FEP"
parm: gdb int, description "If set, we are trying to GDB very early"
parm: dxb_align int, description "If set, force alignment of DXB struct"
parm: print_waits int, description "If set, FEP will wait when print buf full"
parm: erase_nvm int, description "If set, FEP will erase NV parms at start"
parm: rxbufsize int, description "Drv rx dxb (not flip) buf size. Power of 2."
parm: trcbuf_size int, description "Debugging trace buffer size. 1M default."
parm: latency int, description "Set the LD low latency flag,"
parm: alt_fail_open int, description "Enable alternate failed open behavior"
parm: fillmem long, description "Fill memory with value before loading FEP"
parm: dxbttyname string, description "Name of DXB serial device"
parm: usrlibdir string, description "Directory where firmware is located"


What is the problem in connecting to device2.