[OpenSIPS-Users] gsm modem SMS module

Bogdan-Andrei Iancu bogdan at opensips.org
Sat Jan 4 10:35:13 EST 2020


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
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, volga629 at 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: 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 at 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
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200104/75c91243/attachment.html>


More information about the Users mailing list