keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
× Questions about G400/G410 Cards.

G400P - MiniCom access?

12 years 3 days ago #8070 by krzysioD
update to receive smses, just add:
[GSM1]
device = /dev/vmodem0
send_delay = 25

the send_delay, makes every write delayed about 25 ms - because there is no real handshake in pty mode.
to reproduce, stop asterisk, reload dahdi to bring card into sane mode
socat PTY,link=/dev/vmodem0,raw,echo=0,wait-slave,perm-early=666,user=smsd,crnl EXEC:"/usr/local/bin/g4term 2",pty,crnl &
socat PTY,link=/dev/vmodem1,raw,echo=0,wait-slave,perm-early=666,user=smsd,crnl EXEC:"/usr/local/bin/g4term 4",pty,crnl &
socat PTY,link=/dev/vmodem2,raw,echo=0,wait-slave,perm-early=666,user=smsd,crnl EXEC:"/usr/local/bin/g4term 6",pty,crnl &
socat PTY,link=/dev/vmodem3,raw,echo=0,wait-slave,perm-early=666,user=smsd,crnl EXEC:"/usr/local/bin/g4term 8",pty,crnl &

So reading sms from sim card works:

2012-05-15 10:24:42,7, GSM1: -> AT+CPMS?
2012-05-15 10:24:42,7, GSM1: Command is sent, waiting for the answer
2012-05-15 10:24:42,7, GSM1: <- AT+CPMS? +CPMS: "SM",3,25,"SM",3,25,"SM",3,25 OK
2012-05-15 10:24:42,6, GSM1: Checking memory size
2012-05-15 10:24:43,7, GSM1: -> AT+CPMS?
2012-05-15 10:24:43,7, GSM1: Command is sent, waiting for the answer
2012-05-15 10:24:43,7, GSM1: <- AT+CPMS? +CPMS: "SM",3,25,"SM",3,25,"SM",3,25 OK
2012-05-15 10:24:43,6, GSM1: Used memory is 3 of 25
2012-05-15 10:24:43,6, GSM1: Trying to get stored message 1
2012-05-15 10:24:43,7, GSM1: -> AT+CMGR=1
2012-05-15 10:24:43,7, GSM1: Command is sent, waiting for the answer
2012-05-15 10:24:44,7, GSM1: <- AT+CMGR=1 +CMGR: 1,,29 07918497908913F0040B918405145775F70000215041516071800BD4F29C0ED283E0ECFA1C OK
2012-05-15 10:24:44,5, GSM1: SMS received, From: 48504XXXXXX
2012-05-15 10:24:44,6, GSM1: Wrote an incoming message file: /var/spool/sms/incoming/GSM1.ZdB7wa
12 years 2 days ago #8073 by krzysioD
I think - that g4term should not echo commands, as this should work:

# gnokii --identify
GNOKII Version 0.6.29
IMEI : AT+CGSN
Manufacturer : AT+CGMI
Model : AT+GMM
Product name : AT+GMM
Revision : AT+CGMR
12 years 1 day ago #8077 by darkobodnaruk
Hi, I'm having trouble loading the kernel module opvxg4xx. I installed everything through the chan_extra-2.0.3 install script. Both dahdi.ko and opvxg4xx.ko are freshly built as you can see from the date:
root@smsubuntu:/usr/src# l /lib/modules/2.6.32-33-server/dahdi/dahdi.ko
-rw-r--r-- 1 root root 156648 2012-05-17 16:57 /lib/modules/2.6.32-33-server/dahdi/dahdi.ko

root@smsubuntu:/usr/src# l /lib/modules/2.6.32-33-server/dahdi/opvxg4xx/opvxg4xx.ko
-rw-r--r-- 1 root root 60816 2012-05-17 16:57 /lib/modules/2.6.32-33-server/dahdi/opvxg4xx/opvxg4xx.ko

But when trying to load the module:

root@smsubuntu:/usr/src# lsmod|grep dahdi
dahdi_dummy 2760 0
dahdi_transcode 6836 0
dahdi 210885 2 dahdi_dummy,dahdi_transcode
crc_ccitt 1675 1 dahdi

root@smsubuntu:/usr/src# modprobe opvxg4xx
FATAL: Error inserting opvxg4xx (/lib/modules/2.6.32-33-server/dahdi/opvxg4xx/opvxg4xx.ko): Unknown symbol in module, or unknown parameter (see dmesg)

root@smsubuntu:/usr/src# dmesg
[2426674.142472] opvxg4xx: disagrees about version of symbol dahdi_hdlc_putbuf
[2426674.142477] opvxg4xx: Unknown symbol dahdi_hdlc_putbuf
[2426674.142748] opvxg4xx: disagrees about version of symbol dahdi_hdlc_getbuf
[2426674.142751] opvxg4xx: Unknown symbol dahdi_hdlc_getbuf
[2426674.143318] opvxg4xx: disagrees about version of symbol dahdi_register
[2426674.143321] opvxg4xx: Unknown symbol dahdi_register
[2426674.143456] opvxg4xx: Unknown symbol _dahdi_receive
[2426674.143712] opvxg4xx: disagrees about version of symbol dahdi_unregister
[2426674.143715] opvxg4xx: Unknown symbol dahdi_unregister
[2426674.144148] opvxg4xx: disagrees about version of symbol dahdi_hdlc_finish
[2426674.144151] opvxg4xx: Unknown symbol dahdi_hdlc_finish
[2426674.144563] opvxg4xx: Unknown symbol _dahdi_transmit

Messages like these usually mean that the versions don't match, but it's all automatically built from your sources. Any idea what could be wrong?

Regards,Darko
12 years 1 day ago #8078 by Joe.Yung
Hi Darko,

Can you do these steps on the command line?

1. /etc/init.d//dahdi restart

2. modprobe opvxg4xx

3. dahdi_genconf

4. dahdi_cfg -vvvv

To make system automatically loads opvxg4xx, you will be able to edit /etc/dahdi/modules, and insert a line `opvxg4xx` at the end of the file. Save and exit it.

12 years 20 hours ago #8079 by darkobodnaruk
[font=Helvetica, Arial, sans-serif]This is my output (I have added opvxg4xx to /etc/dahdi/modules before): [/font]

root@smsubuntu:~# /etc/init.d/dahdi restart
Unloading DAHDI hardware modules: done
Loading DAHDI hardware modules:
dahdi: done dahdi_dummy: done dahdi_transcode: done opvxg4xx: error
Running dahdi_cfg: done.
root@smsubuntu:~# modprobe opvxg4xx
FATAL: Error inserting opvxg4xx (/lib/modules/2.6.32-33-server/dahdi/opvxg4xx/opvxg4xx.ko): Unknown symbol in module, or unknown parameter (see dmesg)
root@smsubuntu:~# dahdi_genconf
root@smsubuntu:~# dahdi_cfg -vvvv
DAHDI Tools Version - 2.5.0

DAHDI Version: 2.2.1
Echo Canceller(s):
Configuration
======================


Channel map:


0 channels to configure.

root@smsubuntu:~#



[font=Helvetica, Arial, sans-serif]Does "0 channels" mean my card is not recognized? With lspci -vvvvv I can see this: [/font]



05:00.0 Class ff00: Device 1b74:0100 (rev 01)
Subsystem: Device 1b74:0104
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 10
Region 0: Memory at fbaf0000 (32-bit, non-prefetchable) [size=64K]
Kernel modules: opvxg4xx


[font=Helvetica, Arial, sans-serif]Regards, [/font]
[font=Helvetica, Arial, sans-serif]Darko [/font]

i] Last edited by darkobodnaruk at 2012-5-18 18:35 [/i
12 years 12 hours ago #8080 by darkobodnaruk
Ok, my bad. Using modinfo I found that that another dahdi (2.2) was loaded instead of the one I thought it as. After removing that old version, the driver now loads.
Time to create page: 0.048 seconds
Powered by Kunena Forum