Re: [OpenSIPS-Users] openSIPS - Dialog Replication Error

[Dipteshkumar Patel]

Hello Sharad,

Whenever OpenSIPS replicate the dialogs among all the nodes then it
contains socket parameters for caller and callee. Using these sockets the
packets will be sent in both directions. so your all the OpenSIPS node
should listen on same ip(Mostly it is Virtual IPs or Elastic IPs). If your
OpenSIPS servers listen IPs does not match then OpenSIPS discards the
replication due to non listening socket.

You can follow below steps to configure your system to listen on non-local
ip address.

Edit the line in /etc/sysctl.conf that reads net.ipv4.ip_nonlocal_bind to
the following:


*net.ipv4.ip_nonlocal_bind = 1*

and Add listen parameter in opensips.cfg so all the nodes are listening on
same IPs.

Thanks & Regards
*Diptesh Patel*
Software Developer
Ecosmob Technologies Ltd,
Ahmedabad
Mo:*+919898962659*


On Sun, Jan 5, 2020 at 6:31 AM Sharad Kumar via Users <
users@lists.opensips.org> wrote:

> Hi guys,
>
> We are trying to do dialog replication in openSIPS2.4 cluster and getting
> this error -
> ERROR:dialog:dlg_replicated_create: Replicated dialog doesn't match
> caller's listening socket udp:10.0.0.21:5060
>
> Both openSIPS are listening on different IP Addresses subnet and I am well
> aware of this thing that openSIPS will only do dialog replication if we
> have common listening interface between 2 instances. Is there any work
> around to achieve it ? Because we have both instances on AWS.
> OpenSIPS 1 - 10.0.0.21:5060
> openSIPS 2 - 10.0.1.21:5060
> Any help or ideas will be appreciated.
>
> Thanks
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.



*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] proto smpp inbound

[volga629 via Users]

Getting this error where  none of the smpp clients can't bind to 
opensips

Seems like issue related to github





Jan  5 02:40:27 sms /usr/sbin/opensips[6760]: 
INFO:core:probe_max_sock_buff: using snd buffer of 416 kb
Jan  5 02:40:27 sms /usr/sbin/opensips[6760]: 
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 526
Jan  5 02:40:27 sms /usr/sbin/opensips[6760]: 
INFO:proto_smpp:smpp_conn_init: smpp_conn_init called
Jan  5 02:40:27 sms /usr/sbin/opensips[6690]: 
ERROR:proto_smpp:handle_bind_transceiver_cmd: NULL params



This example jasmin SMS log where it try binds as client to opensips 
SMPP server


2020-01-05 02:40:27 INFO 15172 Establishing TCP connection to 
192.168.1.30:2776
2020-01-05 02:40:27 INFO 15172 Connecting to IPv4Address(TCP, 
'192.168.1.30', 2776) ...
2020-01-05 02:40:27 WARNING  15172 SMPP connection established from 
192.168.1.30 to port 51066

2020-01-05 02:40:27 INFO 15172 Connection made to 192.168.1.30:2776
2020-01-05 02:40:27 WARNING  15172 Requesting bind as transceiver
2020-01-05 02:40:57 ERROR15172 Request timed out after 30 secs: PDU 
[command: bind_transceiver, sequence_number: 1, command_status: ESME_ROK

system_id: ''
password: ''
system_type: ''
interface_version: 52
addr_ton: EnumValue(, 
3, 'UNKNOWN')
addr_npi: EnumValue(, 
4, 'UNKNOWN')

address_range: None
]
2020-01-05 02:40:57 ERROR15172 Bind failed [[Failure instance: 
Traceback (failure with no frames): 'jasmin.vendor.smpp.pdu.error.SMPPRequestTimoutError'>: Request timed 
out after 30 secs: PDU [command: bind_transceiver, sequence_number: 1, 
command_status: ESME_ROK



volga629

On Fri, Jan 3, 2020 at 23:32, volga629 via Users 
 wrote:

Hello Everyone,
I am trying inbound proto smpp bind as transmitter and connection 
failing.

Opensips as ESME (External Short Messaging Entity).

Jan  3 23:48:05 sms /usr/sbin/opensips[13242]: 
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 527
Jan  3 23:48:05 sms /usr/sbin/opensips[13242]: 
INFO:proto_smpp:smpp_conn_init: smpp_conn_init called
Jan  3 23:48:05 sms /usr/sbin/opensips[13140]: 
ERROR:proto_smpp:handle_bind_transmitter_cmd: NULL params
Jan  3 23:48:10 sms /usr/sbin/opensips[13242]: 
INFO:proto_smpp:smpp_conn_clean: smpp_conn_clean called


It loading both connections as client, but not as server

Jan  4 00:23:20 sms /usr/sbin/opensips[15628]: INFO:proto_s 
mpp:load_smpp_sessions_from_db: Loaded 2 SMSc servers
Jan  4 00:23:20 sms /usr/sbin/opensips[15628]: 
INFO:proto_smpp:send_bind: binding session with system_id "smppclient"
Jan  4 00:23:20 sms /usr/sbin/opensips[15628]: 
INFO:core:probe_max_sock_buff: using snd buffer of 416 kb
Jan  4 00:23:20 sms /usr/sbin/opensips[15628]: 
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 6
Jan  4 00:23:20 sms /usr/sbin/opensips[15628]: 
INFO:proto_smpp:smpp_conn_init: smpp_conn_init called


How to load server connections ?

volga629



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips call-cacenter module document

[Pradeep Kumar]

Hi Bogdan,

Thanks for your response. Yes, I already read this document and able to
place calls to the logged-in agents through their skill. Currently, as soon
as the agent logged-in, the agent state shows as Ready. Is it possible to
set the agent state to not-ready or other custom modes while the agent is
logged-in?  Also I would like to know what is the minimum configuration
needs to be added for b2b_logic. Please advise.

Regards,
 Pradeep


On Sat, Jan 4, 2020 at 10:37 AM Bogdan-Andrei Iancu 
wrote:

> Hi,
>
> have you read this doc:
> https://opensips.org/html/docs/modules/2.4.x/call_center.html
> ?
>
> 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 12/19/19 5:59 PM, Pradeep Kumar wrote:
>
> Hi,
>
> I have installed Opensips 2.4.6 and trying to setup the call-center module
> with agent login functionalities. I would like to know what are the minimum
> configurations needs to be added in the Opensips config file  and how to
> configure call-center and the b2b_logic modules. Is there any helpful
> documentation available to configure the call-center and the b2b_logic
> modules. Can any one please help me with this? Thanks in advance.
>
> Regards,
>  Pradeep
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Call-center module setup

[Pradeep Kumar]

Hi,

I have installed OpenSIPS 2.4.6 and now trying to setup the call-center
module with agent login functionalities. I would like to know what are the
minimum configurations needs to be added in the Opensips config file  and
how to configure call-center and the b2b_logic modules. Is there any
helpful documentation available to configure the call-center and the
b2b_logic modules? Thanks in advance.

Regards,
 Pradeep
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] openSIPS - Dialog Replication Error

[Sharad Kumar via Users]

Hi guys,

We are trying to do dialog replication in openSIPS2.4 cluster and getting this 
error -
ERROR:dialog:dlg_replicated_create: Replicated dialog doesn't match caller's 
listening socket udp:10.0.0.21:5060

Both openSIPS are listening on different IP Addresses subnet and I am well 
aware of this thing that openSIPS will only do dialog replication if we have 
common listening interface between 2 instances. Is there any work around to 
achieve it ? Because we have both instances on AWS.
OpenSIPS 1 - 10.0.0.21:5060
openSIPS 2 - 10.0.1.21:5060
Any help or ideas will be appreciated.

Thanks___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensipsctl dispatcher - show and dump

[Bogdan Andrei IANCU]

Thank you Diptesh,You may be right, only the holy manual knows eveything 
;).Regards, BogdanSent from my Samsung Galaxy smartphone.
 Original message From: Dipteshkumar Patel 
 Date: 1/4/20  19:27  (GMT+02:00) To: OpenSIPS users 
mailling list  Subject: Re: [OpenSIPS-Users] 
opensipsctl dispatcher - show and dump Hello Bogdan,I want to correct you.  The 
`dump` cmd gives the data from OpenSIPS memory  (via MI), while the `show` 
gives the data from DB. Am I right?Don't mind, you know OpensSIPS better than 
me :).Thanks & RegardsDiptesh PatelSoftware Developer Ecosmob Technologies Ltd, 
AhmedabadMo:+919898962659On Sat, Jan 4, 2020 at 9:17 PM Bogdan-Andrei Iancu 
 wrote:
  

  
  
Hi,
  
  The `dump` cmd gives you the data from DB, while the `show` gives
  you the data from OpenSIPS memory (via MI). And during runtime,
  the in-memory status of a destination may change (due pinging or
  script/MI disabling), while the DB status is not change (still,
  see
https://opensips.org/html/docs/modules/2.4.x/dispatcher.html#param_persistent_state).
  
  Best 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 12/18/19 10:10 AM, solarmon wrote:


  
    Hi,


A question about the opensipsctl dispatcher show and dump
  commands. They seem to show different 'state' for each
  endpoint.


For example:
  
  
  When using "opensipsctl dispatcher show":

++---++---+---++--+---+--+
| id | setid | destination            | socket              
 | state | weight | priority | attrs | description  |
++---++---+---++--+---+--+
|  1 |     1 | sip:A.B.C.D:5060   | udp:W.X.Y.Z:5060 |     2
| 1      |        0 |       | |

When using "opensipsctl dispatcher dump":

        SET:: 1
                URI:: sip:A.B.C.D:5060 state=Active
first_hit_counter=0
                        socket:: udp:W.X.Y.Z:5060
  





Why are the 'state' different? In "opensipsctl dispatcher
  show" it says the state is "2", which is for 'Probing' as I
  understand it. (and 0 is for "Active"?). But for  "opensipsctl
  dispatcher dump"  it shows it as "Active".



On the OpenSIPS Control Panel web GUI, it shows it as DB
  State as Active and Memory State as green dot (for Active).


Why does  "opensipsctl dispatcher show" has the state as
  "2" for Probing instead of "0" for Active?


  
  
  
  ___
Users mailing list
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



DisclaimerIn addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of the 
originator and do not necessarily represent those of the Company or its sister 
concerns. Any liability (in negligence, contract or otherwise) arising from any 
third party taking any action, or refraining from taking any action on the 
basis of any of the information contained in this email is hereby 
excluded.ConfidentialityThis communication (including any attachment/s) is 
intended only for the use of the addressee(s) and contains information that is 
PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, 
or copying of this communication is prohibited. Please inform originator if you 
have received it in error.Caution for viruses, malware etc.This communication, 
including any attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be compatible 
with your systems. You shall carry out virus/malware scanning on your own 
before opening any attachment to this e-mail. The sender of this e-mail and 
Company including its sister concerns shall not be liable for any damage that 
may incur to you as a result of viruses, incompleteness of this message, a 
delay in receipt of this message or any other computer problems. ___
Users mailing list
Users@lists.opensips.org

Re: [OpenSIPS-Users] opensipsctl dispatcher - show and dump

[Dipteshkumar Patel]

Hello Bogdan,

I want to correct you.
 The `dump` cmd gives the data from OpenSIPS memory  (via MI), while the
`show` gives the data from DB. Am I right?

Don't mind, you know OpensSIPS better than me :).

Thanks & Regards
*Diptesh Patel*
Software Developer
Ecosmob Technologies Ltd,
Ahmedabad
Mo:*+919898962659*


On Sat, Jan 4, 2020 at 9:17 PM Bogdan-Andrei Iancu 
wrote:

> Hi,
>
> The `dump` cmd gives you the data from DB, while the `show` gives you the
> data from OpenSIPS memory (via MI). And during runtime, the in-memory
> status of a destination may change (due pinging or script/MI disabling),
> while the DB status is not change (still, see
> https://opensips.org/html/docs/modules/2.4.x/dispatcher.html#param_persistent_state
> ).
>
> Best 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 12/18/19 10:10 AM, solarmon wrote:
>
>   Hi,
>
> A question about the opensipsctl dispatcher show and dump commands. They
> seem to show different 'state' for each endpoint.
>
> For example:
>
> When using "opensipsctl dispatcher show":
>
>
> ++---++---+---++--+---+--+
> | id | setid | destination| socket| state |
> weight | priority | attrs | description  |
>
> ++---++---+---++--+---+--+
> |  1 | 1 | sip:A.B.C.D:5060   | udp:W.X.Y.Z:5060 | 2 | 1  |
>  0 |   | |
>
> When using "opensipsctl dispatcher dump":
>
> SET:: 1
> URI:: sip:A.B.C.D:5060 state=Active first_hit_counter=0
> socket:: udp:W.X.Y.Z:5060
>
>
> Why are the 'state' different? In "opensipsctl dispatcher show" it says
> the state is "2", which is for 'Probing' as I understand it. (and 0 is for
> "Active"?). But for  "opensipsctl dispatcher dump"  it shows it as "Active".
>
> On the OpenSIPS Control Panel web GUI, it shows it as DB State as Active
> and Memory State as green dot (for Active).
>
> Why does  "opensipsctl dispatcher show" has the state as "2" for Probing
> instead of "0" for Active?
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.



*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensipsctl dispatcher - show and dump

[Bogdan-Andrei Iancu]

Hi,

The `dump` cmd gives you the data from DB, while the `show` gives you 
the data from OpenSIPS memory (via MI). And during runtime, the 
in-memory status of a destination may change (due pinging or script/MI 
disabling), while the DB status is not change (still, see 
https://opensips.org/html/docs/modules/2.4.x/dispatcher.html#param_persistent_state).


Best 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 12/18/19 10:10 AM, solarmon wrote:

  Hi,

A question about the opensipsctl dispatcher show and dump commands. 
They seem to show different 'state' for each endpoint.


For example:

When using "opensipsctl dispatcher show":

++---++---+---++--+---+--+
| id | setid | destination            | socket  | state | weight | 
priority | attrs | description  |

++---++---+---++--+---+--+
|  1 |     1 | sip:A.B.C.D:5060   | udp:W.X.Y.Z:5060 |     2 | 1     
 |        0 |       | |


When using "opensipsctl dispatcher dump":

        SET:: 1
                URI:: sip:A.B.C.D:5060 state=Active first_hit_counter=0
                        socket:: udp:W.X.Y.Z:5060


Why are the 'state' different? In "opensipsctl dispatcher show" it 
says the state is "2", which is for 'Probing' as I understand it. (and 
0 is for "Active"?). But for  "opensipsctl dispatcher dump"  it shows 
it as "Active".


On the OpenSIPS Control Panel web GUI, it shows it as DB State as 
Active and Memory State as green dot (for Active).


Why does  "opensipsctl dispatcher show" has the state as "2" for 
Probing instead of "0" for Active?



___
Users mailing list
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

Re: [OpenSIPS-Users] Fate of dbtext

[Bogdan-Andrei Iancu]

Hi Robert,

No, not at all - the db_text module is very alive and kicking, no plans 
to retire it :).


And yes, the old opensipsctl also provided some DB provisioning 
capabilities which are not YET supported by the CLI. The future plan is 
to incorporate this provisioning functionality into CLI also, but in a 
different way. Rather than directly doing DB provisioning from CLI (so 
actually manipulating the dbtext files), we are considering the option 
of exposing via OpenSIPS MI an DB API, so the CLI will be able to do the 
DB provisioning by using OpenSIPS as DB engine - in this way we will be 
sure that the CLI will support all the DB backends existing in OpenSIPS.


Best 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 12/18/19 2:45 AM, Robert Dyck wrote:

With opensips 3.0 the new tool for accessing opensips is opensips-cli. The
database module of opensips-cli only accepts the SQL variants. Does this mean
that dbtext will in the future be deprecated? Eventually not supported?
Rob



___
Users mailing list
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

Re: [OpenSIPS-Users] Opensips call-cacenter module document

[Bogdan-Andrei Iancu]

Hi,

have you read this doc:
    https://opensips.org/html/docs/modules/2.4.x/call_center.html
?

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 12/19/19 5:59 PM, Pradeep Kumar wrote:

Hi,

I have installed Opensips 2.4.6 and trying to setup the call-center 
module with agent login functionalities. I would like to know what are 
the minimum configurations needs to be added in the Opensips config 
file  and how to configure call-center and the b2b_logic modules. Is 
there any helpful documentation available to configure the call-center 
and the b2b_logic modules. Can any one please help me with this? 
Thanks in advance.


Regards,
 Pradeep

___
Users mailing list
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

Re: [OpenSIPS-Users] gsm modem SMS module

[Bogdan-Andrei Iancu]

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, 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: 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  -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0   -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0   +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   +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  -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0   -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0   +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   +FCLASS=0 -- OK

Found a modem on /dev/ttyUSB1.
Modem configuration written to /etc/wvdial.conf.
ttyUSB1: Speed 9600; init "ATQ0 V1 E1 S0=0   +FCLASS=0"
ttyUSB2: Speed 9600; init "ATQ0 V1 E1 S0=0   +FCLASS=0"

volga629



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] gsm modem SMS module

[volga629 via Users]

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  -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0   -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0   +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   +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  -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0   -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0   +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   +FCLASS=0 -- OK

Found a modem on /dev/ttyUSB1.
Modem configuration written to /etc/wvdial.conf.
ttyUSB1: Speed 9600; init "ATQ0 V1 E1 S0=0   +FCLASS=0"
ttyUSB2: Speed 9600; init "ATQ0 V1 E1 S0=0   +FCLASS=0"

volga629

On Sat, Jan 4, 2020 at 17:07, Bogdan-Andrei Iancu  
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 


OpenSIPS Summit, Amsterdam, May 2020
  
OpenSIPS Bootcamp, Miami, March 2020
  

On 1/4/20 5:02 PM, volga...@networklab.ca 
 wrote:

Hello Bogdan,
On startup we get

Jan  4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms:put_command 
: Modem is not clear to send
Jan  4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms: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 
: 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 
  wrote:

Hi Volga,

 Wooowusing this ancient modulemodem 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 


OpenSIPS Summit, Amsterdam, May 2020
  
OpenSIPS Bootcamp, Miami, March 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 

Re: [OpenSIPS-Users] gsm modem SMS module

[Bogdan-Andrei Iancu]

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
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 wrote:

Hello Bogdan,
On startup we get

Jan  4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms:put_command: 
Modem is not clear to send
Jan  4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms: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: 
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 
 wrote:

Hi Volga,

Wooowusing this ancient modulemodem 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
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: 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: doing self termination
Jan  3 15:09:40 sms /usr/sbin/opensips[16440]: 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: 
Modem is not clear to send
Jan  3 15:18:55 sms /usr/sbin/opensips[17250]: INFO:sms: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: 
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
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

Re: [OpenSIPS-Users] gsm modem SMS module

[volga629 via Users]

Hello Bogdan,
On startup we get

Jan  4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms:put_command: 
Modem is not clear to send
Jan  4 12:01:06 sms /usr/sbin/opensips[20542]: INFO:sms: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: 
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  
wrote:

Hi Volga,

 Wooowusing this ancient modulemodem 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 


OpenSIPS Summit, Amsterdam, May 2020
  
OpenSIPS Bootcamp, Miami, March 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 
: 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 
: doing self termination
Jan  3 15:09:40 sms /usr/sbin/opensips[16440]: 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 
: Modem is not clear to send
Jan  3 15:18:55 sms /usr/sbin/opensips[17250]: INFO:sms: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 
: 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 





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Using t_new_request for generating Register

[Bogdan-Andrei Iancu]

Hi,

What exactly are you trying to achieve ? to make OpenSIPS to register 
against another SIP registrar server ?


Best 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 12/20/19 6:27 PM, Mehdi Shirazi wrote:

Hi
As recommended bogdan here[1] I want to use t_new_request for 
generating Register message.

How I can add headers like Contact to new generated message ?
Is it ok to use it on onreply_route? According to my tests in this 
route using force_send_socket befor t_new_request do not change socket.


Regards
M.Shirazi
[1]:https://opensips.org/pipermail/users/2016-February/033874.html


___
Users mailing list
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

Re: [OpenSIPS-Users] Failover in case of 408 - Request Timeout

[Bogdan-Andrei Iancu]

Hi Miteshkumar,

To achieve failover for 408, you need to arm a failure route for your 
INVITE, see https://www.opensips.org/Documentation/Script-Routes-3-0#toc3


This failure route will be trigger whenever your INVITE transaction will 
complete with a negative reply. In the failure route you can check what 
was the final negative reply (with t_check_status() from  TM module) and 
if 408, you can set a new destination and t_relay() again.


Best 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 12/26/19 12:12 PM, Miteshkumar Thakkar via Users wrote:
Thanks for your response. I will try it. But, that cannot be done 
using DNS failover of TM module by any means, right?


On Thu, Dec 26, 2019 at 3:17 PM David Villasmil 
> wrote:


Have you tried using the dispatcher module? Does exactly what you
want.

On Thu, 26 Dec 2019 at 08:41, Miteshkumar Thakkar via Users
mailto:users@lists.opensips.org>> wrote:

Hi,

I want to achieve failover in case of 408 - Request timeout.

One option I can see is DNS failover of TM Module. But, it
does failover in case of 503 as well. I do not want that.

I do not want failover in case of 503. I just want it, in case
of 408 - Request timeout.
How can I achieve this?

Any help is appreciated.

Thank You,
Mitesh
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-- 
Regards,


David Villasmil
email: david.villasmil.w...@gmail.com

phone: +34669448337


___
Users mailing list
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

Re: [OpenSIPS-Users] gsm modem SMS module

[Bogdan-Andrei Iancu]

Hi Volga,

Wooowusing this ancient modulemodem 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
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: 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: doing self termination
Jan  3 15:09:40 sms /usr/sbin/opensips[16440]: 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: 
Modem is not clear to send
Jan  3 15:18:55 sms /usr/sbin/opensips[17250]: INFO:sms: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: 
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
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

Re: [OpenSIPS-Users] sipmsg_validate not detecting wrong user agent

[Bogdan-Andrei Iancu]

Hi Sharad,

The sipmsg_validate() function does not perform any checks on the 
content of the User-Agent hdr - it only checks if the hdr has a 
non-empty body.


Best 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 12/31/19 1:21 AM, Sharad Kumar via Users wrote:

Hi guys,

We are using openSIPS for edge proxy and one of our client is sending 
wrong user-agent which is not compliant with RFC.

This is the username which is being passed -
Asterisk PBX 1.8.23.0-1_centos5.go RPM by dem...@goautodial.com 
\r\n


Where @ is not allowed in user-agent header. We are using this 
function in openSIPS to validate SIP headers but this function not 
seems to be working and not rejecting that INVITE.

if (!sipmsg_validate("shrftc")){
  send_reply("400","Bad request/body");
  exit;
}

Thank you





___
Users mailing list
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

Re: [OpenSIPS-Users] Dialog profiles replication issues

[Bogdan-Andrei Iancu]

Hi Sammy,

OF course the replication is loop protected, otherwise it will simply 
not work :). Could you share all your modparams for the dialog module ?


Best 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 12/30/19 9:04 PM, SamyGo wrote:

Hi All,

Im trying to wrap my head around a problem with OpenSIPS 3.0 dialog 
profile replication. I've a cluster of OpenSIPS instances sharing 
dialog profiles with each other over clusterer/binary_proto layer.


As soon as I initiate a call on first instance they all start 
exchanging the dialog profiles in a never ending loop ! call needs to 
drop in order for it to clear up.


What is this behavior of dialog profile replication? Is it not loop 
protected ! i.e

A (send updated profile value) ---> B,C,D
B <-recv updated profile value
C <-recv updated profile value
D <-recv updated profile value
B   (send updated profile value) ---> A,C,D
C   (send updated profile value) ---> A,B,D
D   (send updated profile value) ---> A,B,C
and Loop over again!

Can anyone elaborate on this flow ! ?

Thats what I've observed from my network captures and logs. Here are 
the configs for sharing profiles.


loadmodule "dialog.so"
modparam("dialog","dlg_match_mode",1)
modparam("dialog","db_mode",2)
modparam("dialog", "profiles_with_value", 
"gatewayCalls;dids;userOutbound/b;userInbound/b;userTotalCalls/b")

modparam("dialog", "profile_replication_cluster", 1)
modparam("dialog", "replicate_profiles_check", 10)
modparam("dialog", "replicate_profiles_timer", 3000)


OpenSIPS version:
root@ip-172-31-26-36:~# /usr/local/sbin/opensips -V
version: opensips 3.0.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, 
Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
MAX_URI_SIZE 1024, BUF_SIZE 65535

poll method support: poll, epoll, sigio_rt, select.
git revision: ef33057
main.c compiled on 18:51:57 Dec  6 2019 with gcc 7


Thanks,

___
Users mailing list
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

Re: [OpenSIPS-Users] segfault drouting.so

[Антон Ершов]

Hello! everything is fine. fix works

сб, 4 янв. 2020 г. в 17:13, Bogdan-Andrei Iancu :

> Hi Anton,
>
> You reported the crash also via GITHUB ->
> https://github.com/OpenSIPS/opensips/issues/1927
>
> I found and fix the crash, so, if you could confirm it, it will be great.
>
> Thanks and regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Bootcamp Pre-Registration
>   https://opensips.org/training/OpenSIPS_Bootcamp/
>
> On 12/26/19 10:38 AM, Антон Ершов wrote:
>
> Hi,
> I try to configure the drouting module but got an error.
> segfault at 140 ip 7fb2ee459051 sp 7fff321f0190 error 4 in
> drouting.so[7fb2ee43c000+39000]
>
> opensips -V
> version: opensips 3.0.1 (x86_64/linux)
> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
> Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535
> poll method support: poll, epoll, sigio_rt, select.
> git revision: 073131cc1
> main.c compiled on 02:46:25 Dec 24 2019 with gcc 4.8.5
>
> gdb /usr/sbin/opensips core.31574
> GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7
> Copyright (C) 2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> For bug reporting instructions, please see:
> ...
> Reading symbols from /usr/sbin/opensips...Reading symbols from
> /usr/sbin/opensips...(no debugging symbols found)...done.
> (no debugging symbols found)...done.
> [New LWP 31574]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `/usr/sbin/opensips -DDdd -f
> /etc/opensips/opensips.cfg.j2 -p python3.6 /etc/ope'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x7f01ad156051 in do_routing () from
> /usr/lib64/opensips/modules/drouting.so
> Missing separate debuginfos, use: debuginfo-install
> opensips-3.0.1.20191223.073131cc1-1.el7.x86_64
> (gdb) bt full
> #0  0x7f01ad156051 in do_routing () from
> /usr/lib64/opensips/modules/drouting.so
> No symbol table info available.
> #1  0x0042f57c in do_action ()
> No symbol table info available.
> #2  0x00434ad0 in run_action_list ()
> No symbol table info available.
> #3  0x00466a27 in eval_expr ()
> No symbol table info available.
> #4  0x004667a5 in eval_expr ()
> No symbol table info available.
> #5  0x0042f3ea in do_action ()
> No symbol table info available.
> #6  0x00434ad0 in run_action_list ()
> No symbol table info available.
> #7  0x00434bc6 in run_actions ()
> No symbol table info available.
> #8  0x00431c28 in do_action ()
> No symbol table info available.
> #9  0x00434ad0 in run_action_list ()
> No symbol table info available.
> #10 0x00432896 in do_action ()
> No symbol table info available.
> #11 0x00434ad0 in run_action_list ()
> No symbol table info available.
> #12 0x00434db8 in run_top_route ()
> No symbol table info available.
> #13 0x0043aa84 in receive_msg ()
> No symbol table info available.
> #14 0x0056c5b0 in udp_read_req ()
> No symbol table info available.
> #15 0x00551caa in io_wait_loop_epoll.constprop.6 ()
> No symbol table info available.
> #16 0x00554959 in udp_start_processes ()
> No symbol table info available.
> #17 0x0041e9ef in main ()
> No symbol table info available.
>
> in opensips-cli dr_number_routing return result. In config get segfault
>
> (opensips-cli): mi dr_number_routing partition_name=office group_id=25
> number=2345
> {
> "Matched Prefix": "234",
> "CARRIER": "dr25",
> "ATTRS": "D25"
> }
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] segfault drouting.so

[Bogdan-Andrei Iancu]

Hi Anton,

You reported the crash also via GITHUB -> 
https://github.com/OpenSIPS/opensips/issues/1927


I found and fix the crash, so, if you could confirm it, it will be great.

Thanks and regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Bootcamp Pre-Registration
  https://opensips.org/training/OpenSIPS_Bootcamp/

On 12/26/19 10:38 AM, Антон Ершов wrote:

Hi,
I try to configure the drouting module but got an error.
segfault at 140 ip 7fb2ee459051 sp 7fff321f0190 error 4 in 
drouting.so[7fb2ee43c000+39000]


opensips -V
version: opensips 3.0.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, 
Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
MAX_URI_SIZE 1024, BUF_SIZE 65535

poll method support: poll, epoll, sigio_rt, select.
git revision: 073131cc1
main.c compiled on 02:46:25 Dec 24 2019 with gcc 4.8.5

gdb /usr/sbin/opensips core.31574
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/sbin/opensips...Reading symbols from 
/usr/sbin/opensips...(no debugging symbols found)...done.

(no debugging symbols found)...done.
[New LWP 31574]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/opensips -DDdd -f 
/etc/opensips/opensips.cfg.j2 -p python3.6 /etc/ope'.

Program terminated with signal 11, Segmentation fault.
#0  0x7f01ad156051 in do_routing () from 
/usr/lib64/opensips/modules/drouting.so
Missing separate debuginfos, use: debuginfo-install 
opensips-3.0.1.20191223.073131cc1-1.el7.x86_64

(gdb) bt full
#0  0x7f01ad156051 in do_routing () from 
/usr/lib64/opensips/modules/drouting.so

No symbol table info available.
#1  0x0042f57c in do_action ()
No symbol table info available.
#2  0x00434ad0 in run_action_list ()
No symbol table info available.
#3  0x00466a27 in eval_expr ()
No symbol table info available.
#4  0x004667a5 in eval_expr ()
No symbol table info available.
#5  0x0042f3ea in do_action ()
No symbol table info available.
#6  0x00434ad0 in run_action_list ()
No symbol table info available.
#7  0x00434bc6 in run_actions ()
No symbol table info available.
#8  0x00431c28 in do_action ()
No symbol table info available.
#9  0x00434ad0 in run_action_list ()
No symbol table info available.
#10 0x00432896 in do_action ()
No symbol table info available.
#11 0x00434ad0 in run_action_list ()
No symbol table info available.
#12 0x00434db8 in run_top_route ()
No symbol table info available.
#13 0x0043aa84 in receive_msg ()
No symbol table info available.
#14 0x0056c5b0 in udp_read_req ()
No symbol table info available.
#15 0x00551caa in io_wait_loop_epoll.constprop.6 ()
No symbol table info available.
#16 0x00554959 in udp_start_processes ()
No symbol table info available.
#17 0x0041e9ef in main ()
No symbol table info available.

in opensips-cli dr_number_routing return result. In config get segfault

(opensips-cli): mi dr_number_routing partition_name=office group_id=25 
number=2345

{
    "Matched Prefix": "234",
    "CARRIER": "dr25",
    "ATTRS": "D25"
}


___
Users mailing list
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

Re: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes

[Bogdan-Andrei Iancu]

Hi Kirill,

sorry for the HUGE delay. Using your cfg files, I managed to start the 
latest 3.0, but the "reload_routes" does not crash at all - maybe 
because of this latest fix [1].


Could you grab the latest 3.0 and try again ?

[1] 
https://github.com/OpenSIPS/opensips/commit/fc728f0c5a8c012cb060f7490d9c31ff9e4fc590#diff-af2f1878a25d75ef415163dec6d0e654


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Bootcamp Pre-Registration
  https://opensips.org/training/OpenSIPS_Bootcamp/

On 8/29/19 3:32 PM, Kirill Galinurov wrote:
Hi Bogdan. I performed additional tests. opensips-cli -x mi 
reload_routes crashed when i use drouting module like this

route[to_operator]{
    route(get_groups_from_redis);###
   if 
(!do_routing($avp(groupid),,,$avp(route_number),$avp(gateway_attr),$avp(carrier_attr),"*")){
   xlog("do_routing: No rules matching the URI 
possibly number in rouming\n");

#   route(to_carrier);
   exit;
   } else {
   xlog("L_INFO", "do_routing: to operator 
$avp(route_number) using provider $avp(carrier_id) and gateway 
$avp(dr_gw_id)\n");
   xlog("L_INFO", "get_route: rule_attr - 
$avp(route_number)\n");
   xlog("L_INFO", "get_route: gw_attr   - 
$avp(gateway_attr)\n");
   xlog("L_INFO", "get_route: carr_attr - 
$avp(carrier_attr)\n");
   xlog("L_INFO", "get_route: carrier_id 
-$avp(carrier_id) \n");
   xlog("L_INFO", "get_route: gw_id - 
$avp(dr_gw_id)\n");
   xlog("L_INFO", "get_route: rule_id   - 
$avp(dr_rule_id)\n");
   xlog("L_INFO", "get_route: socket_id - 
$avp(dr_socket)\n");
   xlog("L_INFO", "get_route: source_ip - 
$avp(dr_socket){s.select,1,:}\n");
   $avp(matched_partition) = 
$var(matched_partition);
   xlog("Matched partition for number -- 
$avp(matched_partition) +++ rule_id is $avp(dr_rule_id)\n ");

#   route(set_carrier_callerid);
   exit;
   }
exit;

}


ср, 28 авг. 2019 г. в 13:19, Kirill Galinurov >:


Hi Bogdan. Did you reproduce the problem?



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS repository news

[Bogdan-Andrei Iancu]

This is awesome Nick!! You have no idea how many people you made happy 
by being able to install opensips-cli from the repositories :)


Many thanks

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Bootcamp Pre-Registration
  https://opensips.org/training/OpenSIPS_Bootcamp/

On 1/4/20 5:08 AM, Nick Altmann wrote:

Hi all,

From this moment opensips official repository includes packages for 
opensips-cli tool which required for opensips >= 3.0.
For deb-based distributives you'll need to add opensips-cli repository 
by hand: http://apt.opensips.org/packages.php?v=cli .
For yum-based distributives opensips-cli repository must be installed 
automatically with next update of opensips-yum package.


Feel free to report any issues with opensips-cli packaging.

Thank you.

--
Nick

___
Users mailing list
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