gsm modem (wavecom m1306b) on aix 5.3




hi,

i'm developing a java application which is able send out sms

right now, this application needs to be deployed into aix 5.3

previously i was using rxtx serial comm for sun solaris, rh linux and win2k
when it comes to aix, i'd discovered not much info can be found in the web

anyhow, i'm trying to setup the gsm modem in aix 5.3 first

what i'd done here is
1. connect the machine with the modem
2. smitty tty -> add tty -> tty rs232 asyn terminal
-> sa2 available 01-s3 standard i/o serial port
3. baudrate 115200, parity none, bits 8, stop bits 1, flow control rts(hardware)

this is the parameter after set, tty=/dev/tty2, paranet adapter=sa2

finally, when i insert the command "stty < /dev/tty2" (i even try "/usr/sbin/getty /dev/tty2")
suppose i can get a "ok" response from gsm modem, but anyhow i didnt get any of it
i'd follow the parameter setting provided by wavecom m1306b technical spec

please help

hi,

this is what i'd tried

the ibm machine model 7028-6e4 consist 3 physical serial port (sa0 - s1, sa1 - s2, sa2 - s3)

to make life easy, i only create a tty0 point to sa0 using smitty

smitty tty
-> tty rs232 asynchronous terminal
-> sa0 available 01-s1 standard i/o serial port

i'd followed the parameter setup given by technical spec of wavecom m1306b.
http://www.jandrew-elec.com/m1306b.pdf where

baudrate - 115200
parity - none
data bit - 8
stop bit - 1
flow ctrl - rts (hardware)


initially we suspect it could be the modem problem, but it works in window 2000 server

anyway, let's move to the next part

i'd vi /usr/lib/uucp/devices file and uncomment the line below
direct tty0 - 115200 direct

ps: i even tried this
direct tty0 - any direct

after that, i try to connect to the modem using this command
cu -ml tty0

and this is the response the machine gave
cu: 0835-028 the connection failed. can't access device.

well, so i tried to chmod the /dev/tty0 to 666
but once i did it, and cu again, it just hung there and no "connected" message prompt out

have i miss up some steps?

hi,

the problem solved,
i think it's because of the machine's driver problem
when i change to another aix machine,
connection success
anyhow, will further investigate if it's really because of physical machine problem