[OpenSIPS-Users] dialog-dlg-repl capability State=not synced in a 2-node cluster, but dialog-prof-repl State=Ok

[Hari Radhakrishnan]

Hi Opensips Team,

We are facing an issue with a 2-node opensips cluster in opensips-2.4
running on Ubuntu.
We would be really grateful if you could help with this. We have spent a
few days putting
DBG statements in the code, but didn't get anywhere significant.

The setup uses db_text module, with two separate files (having same data),
in each node.
The opensips instances are running on AWS EC2 in the same subnet (security
groups are
enabled).

With this setup (please see clusterer_list_cap output below), I get this.
Ideally, we only
require *dialog_replication_cluster* enabled. But if
*profile_replication_cluster* is not enabled,
the dialogs do not get replicated.
Cluster:: 1

Capability:: dialog-dlg-repl State=not synced

Capability:: dialog-prof-repl State=Ok

This is an Active-Passive setup, with keepalived enabled to switch-over the
Virtual IP.

When I enable INFO logs, I see these messages on startup -

*2019-06-04T05:14:53.909986+10:00 edge-opensips
/usr/local/sbin/opensips[6519]: ERROR:dialog:dlg_replicate_profiles: Failed
to replicate dialog profile*

*2019-06-04T05:14:54.011064+10:00 edge-opensips
/usr/local/sbin/opensips[6519]: ERROR:dialog:dlg_replicate_profiles: All
destinations in cluster: 1 are down or probing*

*2019-06-04T05:14:54.011096+10:00 edge-opensips
/usr/local/sbin/opensips[6519]: ERROR:dialog:dlg_replicate_profiles: Failed
to replicate dialog profile*

*2019-06-04T05:14:54.013319+10:00 edge-opensips
/usr/local/sbin/opensips[6414]: INFO:core:probe_max_sock_buff: using snd
buffer of 416 kb*

*2019-06-04T05:14:54.013336+10:00 edge-opensips
/usr/local/sbin/opensips[6414]: INFO:core:init_sock_keepalive: TCP
keepalive enabled on socket 8*

*2019-06-04T05:14:54.014216+10:00 edge-opensips
/usr/local/sbin/opensips[6461]: INFO:clusterer:handle_internal_msg: Node
[2] is UP*


When I enable DBG logs, these messages appear.
We saw that *dialog-dlg-repl*  capability remains in *CAP_SYNC_PENDING
state. *


*2019-06-04T05:39:52.583634+10:00 edge-opensips
/usr/local/sbin/opensips[8867]: DBG:clusterer:cl_register_cap: Registered
capability: dialog-prof-repl*

*2019-06-04T05:39:52.583651+10:00 edge-opensips
/usr/local/sbin/opensips[8867]: DBG:clusterer:cl_register_cap: Registered
capability: dialog-dlg-repl*

*2019-06-04T05:39:52.583659+10:00 edge-opensips
/usr/local/sbin/opensips[8867]: DBG:clusterer:cl_request_sync: requesting
dialog-dlg-repl sync in cluster 1*

*2019-06-04T05:39:52.583668+10:00 edge-opensips
/usr/local/sbin/opensips[8867]: DBG:clusterer:cl_request_sync: failed to
find sync source*

The following logs keep running all the time (right after startup, without
any calls).
It appears that it is retrying to send some message but is stuck in a big
loop
due to a state which does not get changed. Similar logs are seen on the
other
node as well.

*2019-06-04T05:39:53.599460+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: INFO:clusterer:handle_internal_msg: Node
[2] is UP*

*2019-06-04T05:39:53.599467+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:clusterer:match_node: matched node 2*

*2019-06-04T05:39:53.599483+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: con found in state 0*

*2019-06-04T05:39:53.599485+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: tcp connection found
(0x7feee3585a98), acquiring fd*

*2019-06-04T05:39:53.599492+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: c= 0x7feee3585a98,
n=16, Usock=303*

*2019-06-04T05:39:53.599545+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: after receive_fd: c=
0x7feee3585a98 n=8 fd=304*

*2019-06-04T05:39:53.599552+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:proto_bin_send: sending via
fd 304...*

*2019-06-04T05:39:53.599560+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:async_tsend_stream: Async
successful write from first try on 0x7feee3585a98*

*2019-06-04T05:39:53.599562+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:proto_bin_send: after write:
c= 0x7feee3585a98 n/len=48/48 fd=304*

*2019-06-04T05:39:53.599565+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:clusterer:msg_send_retry: sent bin
packet to node [2]*

*2019-06-04T05:39:53.599574+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_read_req: tcp_read_req
end*

*2019-06-04T05:39:53.599689+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_read_req: Using the
global ( per process ) buff*

*2019-06-04T05:39:53.599698+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_parse_headers: received a
COMPLETE message*

*2019-06-04T05:39:53.599700+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_handle_req: completely
received a message*

*2019-06-04T05:39:53.599702+10:00 edge-opensips
/usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_handle_req: Nothing more
to read on TCP conn 0x7feee35857e0, 

Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 )

[Frank Lee]

Hello Bogdan,

 

Thank you very much for looking into this for me.  So you guys actually
check the data type of each field before query is done?  Do you know of
anyone who has a TSQL script that generate all the tables for Opensips
2.4.5?   I do see you guys have a link that has the table structure for
opensips tables:

 

https://opensips.org/html/docs/db/db-schema-devel.html#AEN9331

 

Is this information "complete" and is the data field type "correct" for
2.4.5?  Because it seesm the table field type was used for 1.11 is
"different" from the 2.4.5?  And is that why my Microsoft sql server table
that worked for 1.11 no longer works for 2.4.5?

 

Frank

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Monday, June 3, 2019 12:27 AM
To: OpenSIPS users mailling list ; Frank Lee

Subject: Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL
2016 )

 

Hi Frank,

There were no changes in the db_unixodbc driver in OpenSIPS for some time.
Maybe something changed in the unixodbc driver for MS SQL.

Based on the this log:
   core:db_table_version: invalid type (1) or nul (0)

I see that that the "table_version" from the version table is returned as
BIGINT, while OpenSIPS expects INT. Of course, this is something we can
quickly adjust.

In regards to the 'avp_db_query', could you post the level 3 logs
corresponding to the query ? Maybe it will give us a clue.

Regards,




Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/25/2019 07:33 AM, Frank Lee wrote:

Hello, 

 

Was there some major change between version 1.11 and 2.4.5 on supporting of
the ODBC connection of Microsoft SQL Server?  It seems I had 1.11 running
fine on SQL server (or at least partial table on sql server such as location
table).  But now I use 2.4.5  it seems all the module that uses odbc
connector instead of the mysql connector it will have the error below

 

core:db_table_version: invalid type (1) or nul (0)

 

Thus, I changed all the module to use mysql connector (except the AVPOPS
Module because I have custom query in the script which need to query the
Microsoft sql server) which made Opensips start out fine.  But as soon as it
uses the avp_db_query in the script it seems it would not work.  Alhtough I
don't see any error in the syslog file (although I had log_level set to 3,
do I need to set it higher?)

 

Anyway, it just seems all the query/support to Microsoft SQL server doesn't
run right in 2.4.5 vs 1.11.

 

Is there some dependency that I am suppose to install which is different?  

 

I had my 1.11 run on Debian 7.  Now we are moving to Azure cloud, I had run
Ubuntu 18.04 since Debian 7 is not support on Azure.

 

I had install odbc version 2.3.4 and also tdsodbc 1.00

 

Are these not to correct version to interface between 2.4.5 and Microsoft
sql server (I tried both version msssql 2008 and 2016).

 

Anyway, any  pointer or help will be greatly appreciated!

 

Thank you!

 

 

From: Frank Lee [mailto:fr...@wtild.com] 
Sent: Friday, May 24, 2019 10:58 AM
To: 'users@lists.opensips.org  '
 
Subject: Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 )

 

Hello,  

 

This is the first time I use this mail message, so let me know if this is
not the correct way of posting question.

 

Anyway, I am running Opensips 2.4.5 and when I use MYSQL database on all
module, opensips runs fine.  But as soon as I switch over the database
source to use ODBC driver (which is linked to Microsoft SQL server 2016), I
get this error.  What is It mean?

 

May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]:
ERROR:core:db_table_version: invalid type (1) or nul (0) version columns for
subscriber

May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]:
ERROR:core:db_check_table_version: querying version for table subscriber

May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]:
ERROR:uri:mod_init: Invalid table version.

 

I first created the MySQL table usinmg the command:

 

opensipsdbctl create

 

And then I transfer the tables to MSSQL using the:

 

Microsoft SQL Server Migration Assistant 8.1 for MySQL

 

All the table named corrected and all the index was created too.

 

Thank you very much!

 

Frank

 






___
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] Sending multiple request from OpenSIPS to multiple destinations

[Ali Shirvani]

Sure, thanks for the clarification.

Regards,
Ali

On Mon, Jun 3, 2019 at 3:34 PM Bogdan-Andrei Iancu 
wrote:

> Please keep the list CC'ed to the discussion.
>
>
> Parallel forking means to send an incoming INVITE to multiple SIP
> destinations in the same time - how / where the destinations are fetched
> from , it is not relevant.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 2019
>   https://www.opensips.org/events/Summit-2019Amsterdam/
>
> On 06/03/2019 01:56 PM, Ali Shirvani wrote:
>
> Hi Bogdan-Andrei,
>
> Thanks for your reply. As I know parallel forking works when same user
> registered with multiple devices. In this scenario we have multiple users
> instead of same user.
> Does parallel forking works for multiple users? I want to implement simple
> PTT scenario.
>
> Regards,
> Ali
>
> On Mon, Jun 3, 2019 at 12:33 PM Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Ali,
>>
>> That is called SIP parallel forking and you can do it by using the
>> append_branch() function [1] or $branch variable [2] in order to add
>> multiple destinations for an INVITE.
>>
>>
>> [1] https://opensips.org/Documentation/Script-CoreFunctions-2-4#toc3
>> [2] https://opensips.org/Documentation/Script-CoreVar-2-4#toc21
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS Summit 2019
>>   https://www.opensips.org/events/Summit-2019Amsterdam/
>>
>> On 06/01/2019 06:30 PM, Ali Shirvani wrote:
>>
>> Hi all,
>>
>> Is it possible to send multiple initial request to multiple destinations?
>> something like b2bua but with multiple destinations.
>>
>> I draw the diagram in this gist:
>> https://gist.github.com/alishir/23d2bf5358ef138d1c1f2cfa72cde028
>>
>> Regards,
>> Ali
>>
>>
>> ___
>> 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] Load Balancer cluster Opensips 3.0

[Bogdan-Andrei Iancu]

Please keep the list CC'ed to the discussion.

Thanks for the info, it seems to be an OpenSIPS bug - the anycast token 
is missing in the locally generated requests (like this OPTIONS). Could 
you open a bug report on the github tracker please ?


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 06/03/2019 02:02 PM, Антон Ершов wrote:

Hi Bogdan,
node1 send

2019/06/03 16:01:17.484626 10.50.0.1:5060  -> 
10.7.0.201:5070 

OPTIONS sip:10.7.0.201:5070  SIP/2.0
Via: SIP/2.0/UDP 10.50.0.1:5060;branch=z9hG4bK119b.69e9c536.0
To: sip:10.7.0.201:5070 
From: >;tag=7f64a078bf34d12f31433ecf357bd91b-968b

CSeq: 10 OPTIONS
Call-ID: 0fa7a2ed14e0d2fe-14840@10.50.0.1 


Max-Forwards: 70
Content-Length: 0
User-Agent: OpenSIPS (3.0.0 (x86_64/linux))

and does not receive an answer as it goes to the second node

node 2 send and receive answer

2019/06/03 16:01:26.320354 10.50.0.1:5060  -> 
10.7.0.201:5070 

OPTIONS sip:10.7.0.201:5070  SIP/2.0
Via: SIP/2.0/UDP 10.50.0.1:5060;branch=z9hG4bK894b.277e074.0
To: sip:10.7.0.201:5070 
From: >;tag=7f64a078bf34d12f31433ecf357bd91b-9e0e

CSeq: 10 OPTIONS
Call-ID: 73aebff26b2035c7-17475@10.50.0.1 


Max-Forwards: 70
Content-Length: 0
User-Agent: OpenSIPS (3.0.0 (x86_64/linux))


2019/06/03 15:52:26.490325 10.7.0.201:5070  -> 
10.50.0.1:5060 

SIP/2.0 200 OK
Via: SIP/2.0/UDP 
10.50.0.1:5060;rport=5060;received=10.50.0.1;branch=z9hG4bK894b.277e074.0
Call-ID: 73aebff26b2035c7-17475@10.50.0.1 

From: >;tag=7f64a078bf34d12f31433ecf357bd91b-9e0e

To: ;tag=z9hG4bK894b.277e074.0
CSeq: 10 OPTIONS
Accept: application/dialog-info+xml, application/xpidf+xml, 
application/cpim-pidf+xml, application/simple-message-summary, 
application/pidf+xml, application/pidf+xml, 
application/dialog-info+xml, application/simple-message-summary, 
application/sdp, message/sipfrag;version=2.0
Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, 
BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER

Supported: 100rel, timer, replaces, norefersub
Accept-Encoding: text/plain
Accept-Language: en
Server: Asterisk PBX 16.1.0
Content-Length:  0

my config node 1

loadmodule "load_balancer.so"
modparam("load_balancer", "db_url", 
 "postgres://postgres:1q2w3e4r@10.3.0.1/opensips2 
")

modparam("load_balancer", "probing_reply_codes", "501, 503, 403, 404")
modparam("load_balancer", "cluster_id", 1)
modparam("load_balancer", "cluster_sharing_tag", "node_SKN")
modparam("load_balancer", "probing_from", "sip:hchecker@10.50.0.1 
")

modparam("load_balancer", "probing_verbose", 1)

and node 2

loadmodule "load_balancer.so"
modparam("load_balancer", "db_url", 
 "postgres://postgres:1q2w3e4r@10.3.0.1/opensips2 
")

modparam("load_balancer", "probing_reply_codes", "501, 503, 403, 404")
modparam("load_balancer", "cluster_id", 1)
modparam("load_balancer", "cluster_sharing_tag", "node_PRM")
modparam("load_balancer", "probing_from", "sip:hchecker@10.50.0.1 
")

modparam("load_balancer", "probing_verbose", 1)


maybe I misunderstood how it should work?



пн, 3 июн. 2019 г. в 10:53, Bogdan-Andrei Iancu >:


Hi Anton,

That is an interesting combination - pinging via an anycast
interface.

Could you paste here the OPTIONS and its reply, to check if it is
correctly built from the anycast perspective ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 2019
   https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/27/2019 03:16 PM, Антон Ершов wrote:


Hello friends!

I'm testing new features of opensips 3. And I discovered the
following situation.

Configured cluster module in Anycast Сonfiguration. Load balanser
module

has cluster_sharing_tag. The lb module sends "options" to the
host from the common address, but the answer goes to the nearest
opensips node of the cluster. From what the remote host in lb is
considered inaccessible.

Something is not configured or I did not understand correctly how
the load balanser should work in a cluster



___
Users mailing list
Users@lists.opensips.org 

Re: [OpenSIPS-Users] Sending multiple request from OpenSIPS to multiple destinations

[Bogdan-Andrei Iancu]

Please keep the list CC'ed to the discussion.


Parallel forking means to send an incoming INVITE to multiple SIP 
destinations in the same time - how / where the destinations are fetched 
from , it is not relevant.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 06/03/2019 01:56 PM, Ali Shirvani wrote:

Hi Bogdan-Andrei,

Thanks for your reply. As I know parallel forking works when same user 
registered with multiple devices. In this scenario we have multiple 
users instead of same user.
Does parallel forking works for multiple users? I want to implement 
simple PTT scenario.


Regards,
Ali

On Mon, Jun 3, 2019 at 12:33 PM Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Ali,

That is called SIP parallel forking and you can do it by using the
append_branch() function [1] or $branch variable [2] in order to
add multiple destinations for an INVITE.


[1] https://opensips.org/Documentation/Script-CoreFunctions-2-4#toc3
[2] https://opensips.org/Documentation/Script-CoreVar-2-4#toc21

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 2019
   https://www.opensips.org/events/Summit-2019Amsterdam/

On 06/01/2019 06:30 PM, Ali Shirvani wrote:

Hi all,

Is it possible to send multiple initial request to multiple
destinations? something like b2bua but with multiple destinations.

I draw the diagram in this gist:
https://gist.github.com/alishir/23d2bf5358ef138d1c1f2cfa72cde028

Regards,
Ali


___
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] first_hit_counter

[Олег Подгуйко via Users]

Thank you so much!


>Понедельник,  3 июня 2019, 11:00 +03:00 от Bogdan-Andrei Iancu 
>:
>
>Hi Oleg,
>
>The "first_hit_counter" tells you how many times that destination
>  was selected (from the first time/usage, and not via a failover)
>  for routing.
>
>In regards to the provisioning fields, see 
>https://opensips.org/Documentation/Install-DBSchema-2-4#AEN4366
>
>Regards,
>Bogdan-Andrei Iancu
>
>OpenSIPS Founder and Developer
>  https://www.opensips-solutions.com
>OpenSIPS Summit 2019
>  https://www.opensips.org/events/Summit-2019Amsterdam/
>
>On 05/30/2019 10:32 PM, Олег Подгуйко
>  via Users wrote:
>>Hello!
>>
>>The question is about dispatcher module. I'm interested in one
>>  parameter.
>>
>>Sometimes I use this command
>>
>>[opodguyko@xx-spx-1 ~]$ opensipsctl fifo ds_list
>>PARTITION:: default
>>SET:: 1
>>URI::  sip:10.10.31.21:5060 state=Active first_hit_counter=13
>>socket:: udp:10.10.31.11:5060
>>attr:: test
>>[opodguyko@xx-spx-1 ~]$
>>
>>
>>Could you explain what does it means "first_hit_counter"
>>parameter?
>>
>>I haven't found anything  at all about it in your documentation.
>>
>>It would also be interesting to understand why the following
>>parameters are needed
>>
>>state(int) weight(string) priority(int)
>>
>>The documentation gives a very poor description.
>>Thank you.
>>
>>-- 
>>Oleg Podguyko
>>
>>___
>>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] Removing a node from a cluster

[Bogdan-Andrei Iancu]

Hi Vitalii,

That's a good one and we are aware of it. Basically there is no nice way 
to remove a node from the cluster. The only way (and an unpleasant one) 
is to remove the node from DB, stop all nodes and start them again :(


I will open a ticket for this.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/31/2019 06:44 PM, Vitalii Aleksandrov wrote:

Hi,

What is the correct way of removing a cluster node?
I have a cluster with a number of proxies. Removed one of them from a 
DB and called "opensipsctl fifo clusterer_reload" on all proxies.
Then checked "fifo clusterer_list" and removed node is still there 
since it was learned from other nodes which still new about removed one.
Now removed node is no longer in a DB but all remained cluster nodes 
try to establish connections to it.



___
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] Sending multiple request from OpenSIPS to multiple destinations

[Bogdan-Andrei Iancu]

Hi Ali,

That is called SIP parallel forking and you can do it by using the 
append_branch() function [1] or $branch variable [2] in order to add 
multiple destinations for an INVITE.



[1] https://opensips.org/Documentation/Script-CoreFunctions-2-4#toc3
[2] https://opensips.org/Documentation/Script-CoreVar-2-4#toc21

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 06/01/2019 06:30 PM, Ali Shirvani wrote:

Hi all,

Is it possible to send multiple initial request to multiple 
destinations? something like b2bua but with multiple destinations.


I draw the diagram in this gist: 
https://gist.github.com/alishir/23d2bf5358ef138d1c1f2cfa72cde028


Regards,
Ali


___
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] first_hit_counter

[Bogdan-Andrei Iancu]

Hi Oleg,

The "first_hit_counter" tells you how many times that destination was 
selected (from the first time/usage, and not via a failover) for routing.


In regards to the provisioning fields, see 
https://opensips.org/Documentation/Install-DBSchema-2-4#AEN4366


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/30/2019 10:32 PM, Олег Подгуйко via Users wrote:

Hello!

The question is about dispatcher module. I'm interested in one parameter.

Sometimes I use this command

[opodguyko@xx-spx-1 ~]$ opensipsctl fifo ds_list
PARTITION:: default
SET:: 1
URI:: sip:10.10.31.21:5060 state=Active first_hit_counter=13
socket:: udp:10.10.31.11:5060
attr:: test
[opodguyko@xx-spx-1 ~]$


Could you explain what does it means "first_hit_counter" parameter?

I haven't found anything  at all about it in your documentation.

It would also be interesting to understand why the following 
parameters are needed


state(int) weight(string) priority(int)

The documentation gives a very poor description.


Thank you.

--
Oleg Podguyko


___
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] Load Balancer cluster Opensips 3.0

[Bogdan-Andrei Iancu]

Hi Anton,

That is an interesting combination - pinging via an anycast interface.

Could you paste here the OPTIONS and its reply, to check if it is 
correctly built from the anycast perspective ?


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/27/2019 03:16 PM, Антон Ершов wrote:


Hello friends!

I'm testing new features of opensips 3. And I discovered the following 
situation.


Configured cluster module in Anycast Сonfiguration. Load balanser module

has cluster_sharing_tag. The lb module sends "options" to the host 
from the common address, but the answer goes to the nearest opensips 
node of the cluster. From what the remote host in lb is considered 
inaccessible.


Something is not configured or I did not understand correctly how the 
load balanser should work in a cluster




___
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] local cache becomes empty

[Bogdan-Andrei Iancu]

Hi Alexey,

Try to see if you notice a pattern. Nevertheless I suspect some 
operational issue (removing the keys via MI or script).


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/29/2019 04:27 PM, Alexey Kazantsev via Users wrote:

   Values with timeout still existed.

I mean they exist the period of time defined as the timeout parameter.

---
BR, Alexey
http://alexeyka.zantsev.com/
___
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] ws and hold problem

[Bogdan-Andrei Iancu]

Hi Mikhail,

When using WS(S), for the messages coming from the WS(S) endpoint ( with 
Contact with "invalid") you need to do "fix_nated_contact()", to 
transform that contact into a routable SIP URI.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/25/2019 03:35 AM, Mikhail wrote:

Hi

opensips 2.4 and rtpengine.
webrtc SIP clients based on jsSIP 3.3.6
to accounts jssip1 and jssip2

jssip1 calls jssip2 or jssip2 calls jssip1 - call established
jssip1 place call on hold and then unhold - no problem
now if jssip2 place call on hold it receives SIP/2.0 476 Unresolvable 
destination (476/TM) from opensips and call brakes.

also in opensips.log there are a messages like this:
May 25 02:42:41 opensips-01 /usr/sbin/opensips[19704]: 
CRITICAL:core:mk_proxy: could not resolve hostname: 
"djgppiddv7t0.invalid"
May 25 02:42:41 opensips-01 /usr/sbin/opensips[19704]: 
ERROR:tm:uri2proxy: bad host name in URI 

May 25 02:42:41 opensips-01 /usr/sbin/opensips[19704]: 
ERROR:tm:t_forward_nonack: failure to add branches


what i found:

While call setup jsip1 sends initial invite:
INVITE sip:jsip2@192.168.18.78 SIP/2.0
Contact: 

server resends  to jsip2 invite and replaces Contact with the real ip 
of jsip1:

INVITE sip:60s8k9ep@192.168.21.117:49882;transport=ws SIP/2.0
Contact: 


When jssip1 place call on hold or unhold, it sends invite to server with
INVITE sip:60s8k9ep@192.168.21.117:51630;transport=ws SIP/2.0
Contact: 

server resends  to jsip2 invite and do not changes Contact:
INVITE sip:60s8k9ep@192.168.21.117:51630;transport=ws SIP/2.0
Contact: 

Next, when jssip2 places call on hold, it sends invite:
INVITE sip:lp7tmvt6@djgppiddv7t0.invalid;transport=ws;ob SIP/2.0
and server can't resolve djgppiddv7t0.invalid, it expects real address 
here



does anybody have an idea, who is responsible for the problem - jssip, 
opensips or rtpengine ?



Laba Mikhail

___
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] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 )

[Bogdan-Andrei Iancu]

Hi Frank,

There were no changes in the db_unixodbc driver in OpenSIPS for some 
time. Maybe something changed in the unixodbc driver for MS SQL.


Based on the this log:
   core:db_table_version: invalid type (1) or nul (0)

I see that that the "table_version" from the version table is returned 
as BIGINT, while OpenSIPS expects INT. Of course, this is something we 
can quickly adjust.


In regards to the 'avp_db_query', could you post the level 3 logs 
corresponding to the query ? Maybe it will give us a clue.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 05/25/2019 07:33 AM, Frank Lee wrote:


Hello,

Was there some major change between version 1.11 and 2.4.5 on 
supporting of the ODBC connection of Microsoft SQL Server?  It seems I 
had 1.11 running fine on SQL server (or at least partial table on sql 
server such as location table).  But now I use 2.4.5 it seems all the 
module that uses odbc connector instead of the mysql connector it will 
have the error below


core:db_table_version: invalid type (1) or nul (0)

Thus, I changed all the module to use mysql connector (except the 
AVPOPS Module because I have custom query in the script which need to 
query the Microsoft sql server) which made Opensips start out fine.  
But as soon as it uses the avp_db_query in the script it seems it 
would not work.  Alhtough I don’t see any error in the syslog file 
(although I had log_level set to 3, do I need to set it higher?)


Anyway, it just seems all the query/support to Microsoft SQL server 
doesn’t run right in 2.4.5 vs 1.11.


Is there some dependency that I am suppose to install which is different?

I had my 1.11 run on Debian 7.  Now we are moving to Azure cloud, I 
had run Ubuntu 18.04 since Debian 7 is not support on Azure.


I had install odbc version 2.3.4 and also tdsodbc 1.00

Are these not to correct version to interface between 2.4.5 and 
Microsoft sql server (I tried both version msssql 2008 and 2016).


Anyway, any pointer or help will be greatly appreciated!

Thank you!

*From:* Frank Lee [mailto:fr...@wtild.com]
*Sent:* Friday, May 24, 2019 10:58 AM
*To:* 'users@lists.opensips.org' 
*Subject:* Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 )

Hello,

This is the first time I use this mail message, so let me know if this 
is not the correct way of posting question.


Anyway, I am running Opensips 2.4.5 and when I use MYSQL database on 
all module, opensips runs fine. But as soon as I switch over the 
database source to use ODBC driver (which is linked to Microsoft SQL 
server 2016), I get this error.  What is It mean?


May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: 
ERROR:core:db_table_version: invalid type (1) or nul (0) version 
columns for subscriber


May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: 
ERROR:core:db_check_table_version: querying version for table subscriber


May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: 
ERROR:uri:mod_init: Invalid table version.


I first created the MySQL table usinmg the command:

opensipsdbctl create

And then I transfer the tables to MSSQL using the:

Microsoft SQL Server Migration Assistant 8.1 for MySQL

All the table named corrected and all the index was created too.

Thank you very much!

Frank



___
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