Amir,
Thanks for your reply. You almost certainly know that debugging
progresses by cutting the problem into pieces.
So that possibility is now excluded: in certain countries, possibly not
all, the phone numbers of mobile phone ISP's contain strings with a
number of 9's, possibly similar in purpose to the leading and closing
bar codes start and end delimiters. Just a guess.
Sorry that I cannot help more.
Jacques
Amir Levin wrote:
Hi Jacques,
99999 is just a random choice, any number gives ERROR. It seems it
ignores the number and ATD gives an error, doesnt matter what comes
after that.
If I connect it though the serial port it works perfectly.
Thu, Feb 28, 2008 at 4:45 PM, Jacques Goldberg
<Jacques.Goldberg@xxxxxxx> wrote:
Amir,
Does
> --> Sending: ATDT9999999
suggest in any way that you are not using a straight plain usual phone
company hardwaried line, but rather a mobile phone?
If my guess is right, the mobile phone company is the place to ask which
number string you should use.
But my guess is wrong and 9999999 is a random choice.
Jacques
Amir Levin wrote:
> Same error as with minicom:
>
> --> WvDial: Internet dialer version 1.60
> --> Initializing modem.
> --> Sending: ATZ
> ATZ
> OK
> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> OK
> --> Modem initialized.
> --> Sending: ATDT9999999
> --> Waiting for carrier.
> ATDT9999999
> ERROR
> --> Invalid dial command.
> --> Disconnecting at Thu Feb 28 14:42:24 2008
>
> On Thu, Feb 28, 2008 at 2:27 PM, Marvin Stodolsky
> <marvin.stodolsky@xxxxxxxxx> wrote:
>> RE: Modem Identifier: ATI -- Agere OCM V.92 Ver2.7a (Jun 14 2004)
>>
>> Voice Mercury DP2SH mode-ii SERIAL
>>
>> Edit your personal information into /etc/wvdial.conf , deleting the <
>> > and ; symbols.
>> Then you should be able to dial out with root permission command:
>> # wvdial
>>
>> MarvS
>>
>>
>>
>> On Thu, Feb 28, 2008 at 2:28 AM, Amir Levin <amir.levin@xxxxxxxxx> wrote:
>> > It's a Serial modem connected through USB cable so its not identified
>> > with scanModem:
>> >
>> > -------------------------- System information ----------------------------
>> > CPU=x86_64,
>> > This is Linux version 2.6.23-hardened-r7 (root@saros) (gcc version
>> > 3.4.6 (Gentoo Hardened 3.4.6-r2 p1.5, ssp-3.4.6-1.0, pie-8.7.10)) #2
>> > SMP Tue Feb 26 18:53:09 IST $
>> > scanModem update of: 2008_02_25
>> >
>> > USB modem not detected by lsusb
>> >
>> > === Finished modem firmware and bootup diagnostics section. ===
>> >
>> > However wvdial detected and output as follows:
>> >
>> > Scanning your serial ports for a modem.
>> >
>> > Modem Port Scan<*1>: S0 S1 S2 S3
>> > ttyUSB0<*1>: ATQ0 V1 E1 -- OK
>> > ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK
>> > ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK
>> > ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
>> > ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
>> > ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
>> > ttyUSB0<*1>: Modem Identifier: ATI -- Agere OCM V.92 Ver2.7a (Jun 14
>> >
>> > 2004) Voice Mercury DP2SH mode-ii SERIAL
>> > ttyUSB0<*1>: Speed 4800: AT -- OK
>> > ttyUSB0<*1>: Speed 9600: AT -- OK
>> > ttyUSB0<*1>: Speed 19200: AT -- OK
>> > ttyUSB0<*1>: Speed 38400: AT -- OK
>> > ttyUSB0<*1>: Speed 57600: AT -- OK
>> > ttyUSB0<*1>: Speed 115200: AT -- OK
>> > ttyUSB0<*1>: Speed 230400: AT -- OK
>> > ttyUSB0<*1>: Speed 460800: AT -- Speed 460800: AT -- Speed 460800: AT
>> > -- Max speed is 230400; that should be safe.
>> > ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
>> >
>> > Found a modem on /dev/ttyUSB0.
>> > Modem configuration written to /etc/wvdial.conf.
>> > ttyUSB0<Info>: Speed 230400; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
>> >
>> >
>> >
>> >
>> > On Thu, Feb 28, 2008 at 1:40 AM, Marvin Stodolsky
>> > <marvin.stodolsky@xxxxxxxxx> wrote:
>> > > Amir,
>> > >
>> > >
>> > > Browse http://linmodems.technion.ac.il and download scanModem.gz .
>> > > Within a Linux partition
>> > > gunzip scanModem.gz
>> > > To make it executable:
>> > > chmod +x scanModem
>> > > Run diagnositics with:
>> > > ./scanModem
>> > > Only the ouput ModemData.txt should be sent to Discuss@xxxxxxxxxxxxx
>> > >
>> > > MarvS
>> > >
>> > >
>> > >
>> > > On Wed, Feb 27, 2008 at 1:45 PM, Amir Levin <amir.levin@xxxxxxxxx> wrote:
>> > > > I have 2 external serial modems (Trendnet TFM-560X), working perfectly.
>> > > >
>> > > > Recently I purchased a new server which comes with only USB connections.
>> > > > So I bought a serial to USB adapter (Prolific PL2303) which has a good
>> > > > kernel support. I recompiled the kernel with driver and dmesg shows
>> > > > that the kernel found it correctly:
>> > > >
>> > > >
>> > > > Code:
>> > > > usbcore: registered new interface driver usbserial
>> > > > drivers/usb/serial/usb-serial.c: USB Serial Driver core
>> > > > drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
>> > > > pl2303 2-2:1.0: pl2303 converter detected
>> > > > usb 2-2: pl2303 converter now attached to ttyUSB0
>> > > > usbcore: registered new interface driver pl2303
>> > > > drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
>> > > >
>> > > > When I communicate with the modem through minicom, every command
>> > > > works except ATD/ATDT:
>> > > >
>> > > > Code:
>> > > > Welcome to minicom 2.2
>> > > >
>> > > > OPTIONS: I18n
>> > > > Compiled on Feb 26 2008, 19:24:47.
>> > > > Port /dev/ttyUSB0
>> > > >
>> > > > AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
>> > > > OK
>> > > > ATI0
>> > > > Agere OCM V.92 Ver2.7a (Jun 14 2004) Voice Mercury DP2SH mode-ii SERIAL
>> > > > OK
>> > > > ATI1
>> > > > 0418
>> > > > OK
>> > > > ATI4
>> > > > 18
>> > > > OK
>> > > > ATI5
>> > > > OCM ,0,19
>> > > > OK
>> > > > ATD
>> > > > ERROR
>> > > > ATDT9
>> > > > ERROR
>> > > >
>> > > > I tested with 2 different kernels and it's just the same...
>> > > > Anyone had a similar problem?
>> > > > Any clue for a solution?
>> > > >
>> > > > Thanks.
>> > > >
>> > >
>> >
>>
>
>
>
