Hello Bogdan,
Yes I think module need to be refactored , I can't get any useful
information from debug. All what I see that opensips access modem, but
actually it can't pass even init properly. I tested with kannel and it
works 100%.
I used command lsof -u opensips | grep -i usb that show me that
opensips keep device open.
volga629
On Sat, Jan 4, 2020 at 17:35, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:
You should see some DBG log with "opening modem" - this is the very
beginning of the modem init sequence. Try to grab all the logs (from
the same proc) starting with that line.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
<https://www.opensips-solutions.com/>
OpenSIPS Summit, Amsterdam, May 2020
<https://www.opensips.org/events/Summit-2020Amsterdam/>
OpenSIPS Bootcamp, Miami, March 2020
<https://opensips.org/training/OpenSIPS_Bootcamp_2020/>
On 1/4/20 5:19 PM, volga...@networklab.ca
<mailto:volga...@networklab.ca> wrote:
In debug level 4 I see
Jan 4 12:15:43 sms opensips: Jan 4 12:15:43 [21648]
ERROR:sms:initmodem: Modem is not registered to the network
Jan 4 12:15:43 sms opensips: Jan 4 12:15:43 [21648]
INFO:sms:put_command <info:sms:put_command>: Modem is not clear to
send
Jan 4 12:15:43 sms opensips: Jan 4 12:15:43 [21649]
DBG:freeswitch:apply_socket_commands: applying FS socket commands
Jan 4 12:15:44 sms opensips: Jan 4 12:15:44 [21648]
INFO:sms:put_command <info:sms:put_command>: Modem is not clear to
send
Jan 4 12:15:44 sms opensips: Jan 4 12:15:44 [21648]
WARNING:sms:checkmodem: modem wants the PIN again!
Jan 4 12:15:44 sms opensips: Jan 4 12:15:44 [21648]
WARNING:sms:checkmodem: re -init the modem!!
Jan 4 12:15:44 sms opensips: Jan 4 12:15:44 [21648]
INFO:sms:initmodem <info:sms:initmodem>: init modem ZTE on
/dev/ttyUSB1.
Jan 4 12:15: 44 sms opensips: Jan 4 12:15:44 [21649]
DBG:freeswitch:apply_socket_commands: applying FS socket commands
Jan 4 12:15:44 sms opensips: Jan 4 12:15:44 [21648]
INFO:sms:put_command <info:sms:put_command>: Modem is not clear to
send
Jan 4 12:15:44 sms opensips: Jan 4 12:15:44 [21648]
INFO:sms:initmodem <info:sms:initmodem>: INFO:initmodem
<info:initmodem>: Checking if Modem is registered to the network
But not really true, because wvdialconf is report ok
[root@sms ~]# wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: S0 S1 S2 S3
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB1<*1>: ATQ0 V1 E1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB1<*1>: Modem Identifier: ATI -- Manufacturer: ZTE INCORPORATED
ttyUSB1<*1>: Speed 9600: AT -- OK
ttyUSB1<*1>: Max speed is 9600; that should be safe.
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB2< *1>: Modem Identifier: ATI -- Manufacturer: ZTE INCORPORATED
ttyUSB2<*1>: Speed 9600: AT -- OK
ttyUSB2<*1>: Max speed is 9600; that should be safe.
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttyUSB1.
Modem configuration written to /etc/wvdial.conf.
ttyUSB1<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
ttyUSB2<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
volga629
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
