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: 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: 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: 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: Modem is not clear to send
Jan 4 12:15:44 sms opensips: Jan 4 12:15:44 [21648]
INFO:sms: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
On Sat, Jan 4, 2020 at 17:07, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:
Doesn't look like a good init :(.
Check for the logs from a process listed (in ps) as `SMS receiver` -
this is the process handling the modems. Try starting with DBG log
level, so you can see what the opensips is trying to do with the
modem.
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:02 PM, volga...@networklab.ca
<mailto:volga...@networklab.ca> wrote:
Hello Bogdan,
On startup we get
Jan 4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms:put_command
<info:sms:put_command>: Modem is not clear to send
Jan 4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms:initmodem
<info:sms:initmodem>: INFO:initmodem <info:initmodem>: Checking if
Modem is registered to the network
Jan 4 12:01:07 sms /usr/sbin/opensips[20542]: INFO:sms:put_command
<info:sms:put_command>: Modem is not clear to send
Jan 4 12:01:07 sms /usr/sbin/opensips[20542]:
WARNING:sms:initmodem: Modems seems to try to reach the network!
Let's wait a little bit
Is this modem locked ?
volga629
On Sat, Jan 4, 2020 at 16:54, Bogdan-Andrei Iancu
<bog...@opensips.org> <mailto:bog...@opensips.org> wrote:
Hi Volga,
Wooow....using this ancient module....modem support - it is like
dark ages :P..
First of all, at OpenSIPS startup, is the modem successfully
initialized ?
Best 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/3/20 10:20 PM, volga629 via Users wrote:
Hello Everyone,
I need help identify issue with gsm modem connection in opensips.
I tried send with external application and no problem everything
works, but with opensips get messages
Jan 3 15:09:38 sms /usr/sbin/opensips[16430]:
NOTICE:core:do_workers_auto_scaling: score 15/15 -> ripping proc
23 from group 1 (with 16 procs), estimated load -> 0
Jan 3 15:09:38 sms /usr/sbin/opensips[16462]:
NOTICE:core:udp_process_graceful_terminate: process 23 received
RPC to terminate from Main
Jan 3 15:09:38 sms /usr/sbin/opensips[16462]:
INFO:core:dynamic_process_final_exit
<info:core:dynamic_process_final_exit>: doing self termination
Jan 3 15:09:39 sms /usr/sbin/opensips[16430]:
NOTICE:core:handle_sigs: process 23/16462 did selfexit with status
0
Jan 3 15:09:40 sms /usr/sbin/opensips[16430]:
NOTICE:core:do_workers_auto_scaling: score 15/15 -> ripping proc
22 fr om group 1 (with 15 procs), estimated load -> 0
Jan 3 15:09:40 sms /usr/sbin/opensips[16461]:
NOTICE:core:udp_process_graceful_terminate: process 22 received
RPC to terminate from Main
Jan 3 15:09:40 sms /usr/sbin/opensips[16461]:
INFO:core:dynamic_process_final_exit
<info:core:dynamic_process_final_exit>: doing self termination
Jan 3 15:09:40 sms /usr/sbin/opensips[16440]:
INFO:sms:put_command <info:sms:put_command>: Modem is not clear to
send
Jan 3 15:09:40 sms /usr/sbin/opensips[16440]:
NOTICE:sms:initmodem: NOTICE:initmodem: Waiting 2 sec. before
retrying
Jan 3 15:18:55 sms /usr/sbin/opensips[17250]:
INFO:sms:put_command <info:sms:put_command>: Modem is not clear to
send
Jan 3 15:18:55 sms /usr/sbin/opensips[17250]: INFO:sms:initmodem
<info:sms:initmodem>: INFO:initmodem <info:initmodem>: Checking if
Modem is registered to the network
Jan 3 15:18:56 sms /usr/sbin/opensips[17250]:
INFO:sms:put_command <info:sms:put_command>: Modem is not clear to
send
**Messages log when modem is plugged* *
*
*
*Jan 3 14:36:06 sms kernel: option1 ttyUSB0: GSM modem (1-port)
converter now disconnected from ttyUSB0*
*Jan 3 14:36:06 sms kernel: option 1-2:1.0: device disconnected*
*Jan 3 14:36:06 sms kernel: option1 ttyUSB1: GSM modem (1-port)
converter now disconnected from ttyUSB1*
*Jan 3 14:36:06 sms kernel: option 1-2:1.1: device disconnected*
*Jan 3 14:36:06 sms kernel: option1 ttyUSB2: GSM modem (1-port)
converter now disconnected from ttyUSB2*
*
*
*
*
*Configuration *
*
*
*[root@sms tmp]# lsusb*
*Bus 001 Device 013: ID 19d2:0031 ZTE WCDMA Technologies MSM
MF110/MF627/MF636*
*
*
*
*
*#### SMS*
*loadmodule "sms.so"*
*modparam("sms", "modems", "ZTE[d=/dev/ttyUSB1;p=my sim
pin;m=NEW;b=9600]")*
*modparam("sms", "links", "ZTE[D1]")*
*modparam("sms", "networks", "D1[m=10]")*
*modparam("sms", "max_sms_parts", 12)*
*modparam("sms", "sms_report_type", 2)*
*
*
*
*
* what is not clear in configuration is what need to be set if
modem in Paraguay *
*1.1.2. Numbering Plan*
**
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
