Re: [OpenSIPS-Users] - Clustering

2023-01-18 Thread Nitesh Divecha
And using following:

Node#1
# opensips -V

version: opensips 3.3.2 (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.
main.c compiled on  with gcc 11

Node#2
# opensips -V
version: opensips 3.3.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: bf7c0eb89
main.c compiled on 14:53:50 Aug 30 2022 with gcc 10


Both Nodes are using OpenSIPS Control Panel 9.3.2.



On Wed, Jan 18, 2023 at 12:15 PM Nitesh Divecha 
wrote:

> Hello All,
>
> I got two nodes in cluster formation and they are in sync. Running CLI
> opensips-cli -x mi ul_dump | grep "AOR\":\|Contact\":" on both nodes I can
> see ALL the registered endpoints . For testing purposes I have two
> endpoints registered on each node so a total four endpoints are visible.
>
> Node #1 - IP: 66.x.x.1, registered endpoint 2001 and 2002
> Node #2 - IP: 3.x.x.9, registered endpoint 5467901 and 5467902
>
> Endpoints in Node#1 can call each other (2001 <--> 2002) and endpoints in
> Node#2 can call each other (5467901 <--> 5467902)
>
> root@archer:/etc/opensips# opensips-cli -x mi ul_dump | grep
> "AOR\":\|Contact\":"
> "AOR": 5467901@3.x.x.9,
> "Contact":sip:5467901@143.x.x.7:29100,
> "AOR": 5467902@3.x.x.9,
> "Contact":sip:5467902@143.x.x.7:5062,
> "AOR": 2002@66.x.x.1,
> "Contact":sip:2002@143.x.x.6:12339;ob,
> "AOR": 2001@66.x.x.1,
> "Contact":sip:2001@143.x.x.6:5060;ob,
>
> But none of the nodes can call each other... Meaning Node#1-2001 or 2 can
> not call Node#2-5467901 or 2 and vice versa... On log it shows SIP 404, Not
> Found... and looking further in detail it shows it is only looking for the
> endpoint in the same Node, meaning when 2001 calls 5467901 it is looking
> for 5467901@66.x.x.1 on Node#1 instead of 5467901@3.x.x.9 on Node#2.
>
>
>  USeR LOCation module
> loadmodule "usrloc.so"
> modparam("usrloc", "nat_bflag", "NATED_CALLEE")
> modparam("usrloc", "location_cluster", 2)
> modparam("usrloc", "working_mode_preset", "full-sharing-cluster")
>
> route[to_user] {
> # do lookup with method filtering
> if (!lookup("location","m")) {
> if (!db_does_uri_exist("$ru","subscriber")) {
> send_reply(404,"Not Found");
> xlog("ERROR: rU is: ($rU) and ru is: $ru --> Not
> Found\n");
> exit;
> }
> if(isflagset('HUNTGROUP')) {
> route(huntgroup);
> }
> t_reply(480, "Temporarily Unavailable");
> exit;
> }
> $acc_extra(TYPE) = "USER";
> route(relay);
> }
>
>
> Any help will be highly appreciated...
>
> Cheers,
> Nitesh
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] - Clustering

2023-01-18 Thread Nitesh Divecha
Hello All,

I got two nodes in cluster formation and they are in sync. Running CLI
opensips-cli -x mi ul_dump | grep "AOR\":\|Contact\":" on both nodes I can
see ALL the registered endpoints . For testing purposes I have two
endpoints registered on each node so a total four endpoints are visible.

Node #1 - IP: 66.x.x.1, registered endpoint 2001 and 2002
Node #2 - IP: 3.x.x.9, registered endpoint 5467901 and 5467902

Endpoints in Node#1 can call each other (2001 <--> 2002) and endpoints in
Node#2 can call each other (5467901 <--> 5467902)

root@archer:/etc/opensips# opensips-cli -x mi ul_dump | grep
"AOR\":\|Contact\":"
"AOR": 5467901@3.x.x.9,
"Contact":sip:5467901@143.x.x.7:29100,
"AOR": 5467902@3.x.x.9,
"Contact":sip:5467902@143.x.x.7:5062,
"AOR": 2002@66.x.x.1,
"Contact":sip:2002@143.x.x.6:12339;ob,
"AOR": 2001@66.x.x.1,
"Contact":sip:2001@143.x.x.6:5060;ob,

But none of the nodes can call each other... Meaning Node#1-2001 or 2 can
not call Node#2-5467901 or 2 and vice versa... On log it shows SIP 404, Not
Found... and looking further in detail it shows it is only looking for the
endpoint in the same Node, meaning when 2001 calls 5467901 it is looking
for 5467901@66.x.x.1 on Node#1 instead of 5467901@3.x.x.9 on Node#2.


 USeR LOCation module
loadmodule "usrloc.so"
modparam("usrloc", "nat_bflag", "NATED_CALLEE")
modparam("usrloc", "location_cluster", 2)
modparam("usrloc", "working_mode_preset", "full-sharing-cluster")

route[to_user] {
# do lookup with method filtering
if (!lookup("location","m")) {
if (!db_does_uri_exist("$ru","subscriber")) {
send_reply(404,"Not Found");
xlog("ERROR: rU is: ($rU) and ru is: $ru --> Not
Found\n");
exit;
}
if(isflagset('HUNTGROUP')) {
route(huntgroup);
}
t_reply(480, "Temporarily Unavailable");
exit;
}
$acc_extra(TYPE) = "USER";
route(relay);
}


Any help will be highly appreciated...

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


Re: [OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 in K8s environment

2022-05-02 Thread Bogdan-Andrei Iancu

Hi Jonathan,

If you set log level to 4 (DBG), do you see any logs when the pinging 
should be attempted ?


Best Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 23rd May - 3rd June 2022
  https://opensips.org/training/OpenSIPS_eBootcamp_2022/

On 4/27/22 12:30 AM, Jonathan Hunter wrote:


Hi Bogdan.

Just to follow up I have been trying to make openSIPS send SIP options 
in the same environment to websocket registered users, and I just cant 
get it to send even though the branch flags are set.


I now have these settings defined for NAThelper;

loadmodule "nathelper.so"

modparam("nathelper", "natping_interval", 10)

modparam("nathelper", "ping_nated_only", 0)

modparam("nathelper", "sipping_method", "OPTIONS")

modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")

modparam("nathelper", "sipping_from", "sip:pinger@")

modparam("nathelper", "received_avp", "$avp(rcv)")

modparam("nathelper", "ping_threshold", 5)

modparam("nathelper", "max_pings_lost", 3)

modparam("nathelper", "natping_partitions", 4)

modparam("nathelper", "remove_on_timeout_bflag", "SIPPING_RTO")

modparam("nathelper", "natping_tcp", 1)

modparam("nathelper", "cluster_id", 1)

modparam("nathelper", "cluster_sharing_tag", "node/2=active")

Also have pinging_mode set for usrloc, and this is in a 
federation-cachedb-cluster with 2 opensips containers running 
active/active.


If I use t_new_request I can send a SIP OPTIONS message out, so I 
assume I am missing a parameter or its mis configuration? Or could it 
be environment, this is a k8s setup.


Any advice/tips would be great.

Thank you .

Jon

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for 
Windows


*From: *Jonathan Hunter <mailto:hunter...@hotmail.com>
*Sent: *25 April 2022 15:28
*To: *Bogdan-Andrei Iancu <mailto:bog...@opensips.org>; OpenSIPS users 
mailling list <mailto:users@lists.opensips.org>
*Subject: *Re: [OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 
in K8s environment


Hi Bogdan,

Thank you for the reply I can see there are tcp connections but I 
don’t seem to get anything. I assume it may well be k8s related?.


I also cant seem to get NAT ping working, I assume this should work 
out to websocket connections as long as flags are set?


The outputs are;

  "ID": 131797,

    "Type": "ws",

    "State": 0,

    "Remote": "10.10.51.228:35462",

    "Local": "10.10.2.91:8081",

    "Lifetime": "2022-04-25 14:11:31",

    "Alias port": 35462

    }

    ]

And location shows;

"AORs": [

    {

    "AOR": "61067470a372a031a7495a1a@",

    "Contacts": [

    {

    "Contact": 
"sip:c0r0d0i7@b0ek39eabrvf.invalid;transport=wss",


    "ContactID": "4544061655272656153",

    "Expires": 519,

    "Q": "",

    "Callid": "jbbvtjp2l7bujcom73s3",

    "Cseq": 2,

    "User-agent": "SIP.js/0.20.0",

    "Received": 
"sip:10.10.51.228:35462;transport=ws",


    "State": "CS_NEW",

    "Flags": 0,

    "Cflags": "WS_DEVICE SIPPING_RTO 
SIPPING_ENABLE",


    "Socket": "ws::8081",

    "Methods": 5439

    }

    ]

    }

    ]

However I cant seem to also get opensips to send SIP keepalive with 
these settings;


 NAThelper module

loadmodule "nathelper.so"

modparam("nathelper", "received_avp", "$avp(rcv)")

modparam("nathelper", "natping_tcp",1)

modparam("nathelper", "natping_interval", 5)

modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")

modparam("nathelper", "remove_on_timeout_bflag", "SIPPING_RTO")

modparam("nathelper", "sipping_from", "sip:pinger@DOMAIN")

modparam("nathelper", "max_pings_lo

Re: [OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 in K8s environment

2022-04-26 Thread Jonathan Hunter
Hi Bogdan.

Just to follow up I have been trying to make openSIPS send SIP options in the 
same environment to websocket registered users, and I just cant get it to send 
even though the branch flags are set.

I now have these settings defined for NAThelper;

loadmodule "nathelper.so"
modparam("nathelper", "natping_interval", 10)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper", "sipping_method", "OPTIONS")
modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")
modparam("nathelper", "sipping_from", "sip:pinger@")
modparam("nathelper", "received_avp", "$avp(rcv)")
modparam("nathelper", "ping_threshold", 5)
modparam("nathelper", "max_pings_lost", 3)
modparam("nathelper", "natping_partitions", 4)
modparam("nathelper", "remove_on_timeout_bflag", "SIPPING_RTO")
modparam("nathelper", "natping_tcp", 1)
modparam("nathelper", "cluster_id", 1)
modparam("nathelper", "cluster_sharing_tag", "node/2=active")

Also have pinging_mode set for usrloc, and this is in a 
federation-cachedb-cluster with 2 opensips containers running active/active.

If I use t_new_request I can send a SIP OPTIONS message out, so I assume I am 
missing a parameter or its mis configuration? Or could it be environment, this 
is a k8s setup.

Any advice/tips would be great.

Thank you .

Jon


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

From: Jonathan Hunter<mailto:hunter...@hotmail.com>
Sent: 25 April 2022 15:28
To: Bogdan-Andrei Iancu<mailto:bog...@opensips.org>; OpenSIPS users mailling 
list<mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 in K8s 
environment

Hi Bogdan,

Thank you for the reply I can see there are tcp connections but I don’t seem to 
get anything. I assume it may well be k8s related?.

I also cant seem to get NAT ping working, I assume this should work out to 
websocket connections as long as flags are set?

The outputs are;

  "ID": 131797,
"Type": "ws",
"State": 0,
"Remote": "10.10.51.228:35462",
"Local": "10.10.2.91:8081",
"Lifetime": "2022-04-25 14:11:31",
"Alias port": 35462
}
]

And location shows;

"AORs": [
{
"AOR": "61067470a372a031a7495a1a@",
"Contacts": [
{
"Contact": 
"sip:c0r0d0i7@b0ek39eabrvf.invalid;transport=wss",
"ContactID": "4544061655272656153",
"Expires": 519,
"Q": "",
"Callid": "jbbvtjp2l7bujcom73s3",
"Cseq": 2,
"User-agent": "SIP.js/0.20.0",
"Received": "sip:10.10.51.228:35462;transport=ws",
"State": "CS_NEW",
"Flags": 0,
"Cflags": "WS_DEVICE SIPPING_RTO SIPPING_ENABLE",
"Socket": "ws::8081",
"Methods": 5439
}
]
}
]

However I cant seem to also get opensips to send SIP keepalive with these 
settings;

 NAThelper module
loadmodule "nathelper.so"
modparam("nathelper", "received_avp", "$avp(rcv)")
modparam("nathelper", "natping_tcp",1)
modparam("nathelper", "natping_interval", 5)
modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")
modparam("nathelper", "remove_on_timeout_bflag", "SIPPING_RTO")
modparam("nathelper", "sipping_from", "sip:pinger@DOMAIN")
modparam("nathelper", "max_pings_lost", 2)
modparam("nathelper", "cluster_id", 9)
modparam("nathelper", "cluster_sharing_tag", "node/2=active")


Am I missing something here?

Many thanks

Jon

Sent from 
Mail<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3FLinkId%3D550986&data=05%7C01%7C%7C5f60e807488b4d6ea4d808da26c7ce66%7C84df9e7fe9f640afb435%

Re: [OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 in K8s environment

2022-04-25 Thread Jonathan Hunter
Hi Bogdan,

Thank you for the reply I can see there are tcp connections but I don’t seem to 
get anything. I assume it may well be k8s related?.

I also cant seem to get NAT ping working, I assume this should work out to 
websocket connections as long as flags are set?

The outputs are;

  "ID": 131797,
"Type": "ws",
"State": 0,
"Remote": "10.10.51.228:35462",
"Local": "10.10.2.91:8081",
"Lifetime": "2022-04-25 14:11:31",
"Alias port": 35462
}
]

And location shows;

"AORs": [
{
"AOR": "61067470a372a031a7495a1a@",
"Contacts": [
{
"Contact": 
"sip:c0r0d0i7@b0ek39eabrvf.invalid;transport=wss",
"ContactID": "4544061655272656153",
"Expires": 519,
"Q": "",
"Callid": "jbbvtjp2l7bujcom73s3",
"Cseq": 2,
"User-agent": "SIP.js/0.20.0",
"Received": "sip:10.10.51.228:35462;transport=ws",
"State": "CS_NEW",
"Flags": 0,
"Cflags": "WS_DEVICE SIPPING_RTO SIPPING_ENABLE",
"Socket": "ws::8081",
"Methods": 5439
}
]
}
]

However I cant seem to also get opensips to send SIP keepalive with these 
settings;

 NAThelper module
loadmodule "nathelper.so"
modparam("nathelper", "received_avp", "$avp(rcv)")
modparam("nathelper", "natping_tcp",1)
modparam("nathelper", "natping_interval", 5)
modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")
modparam("nathelper", "remove_on_timeout_bflag", "SIPPING_RTO")
modparam("nathelper", "sipping_from", "sip:pinger@DOMAIN")
modparam("nathelper", "max_pings_lost", 2)
modparam("nathelper", "cluster_id", 9)
modparam("nathelper", "cluster_sharing_tag", "node/2=active")


Am I missing something here?

Many thanks

Jon

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

From: Bogdan-Andrei Iancu<mailto:bog...@opensips.org>
Sent: 18 April 2022 13:59
To: OpenSIPS users mailling list<mailto:users@lists.opensips.org>; Jonathan 
Hunter<mailto:hunter...@hotmail.com>
Subject: Re: [OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 in K8s 
environment

Hi Jonathan,

Maybe the k8s layer (the ingress ??) sticks its tails in there - could you 
check at opensips level if the TCP conn is still seen as up ? Use the mi 
list_tcp_conns MI function
https://www.opensips.org/Documentation/Interface-CoreMI-3-2#toc4<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips.org%2FDocumentation%2FInterface-CoreMI-3-2%23toc4&data=04%7C01%7C%7C4bdabd460c654a24286508da213b3532%7C84df9e7fe9f640afb435%7C1%7C0%7C637858835416369371%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=CSDFYoaIZkVDUF2xCeS93WFEpo8bHgSuf9d2%2BsasX4U%3D&reserved=0>


Best regard,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  
https://www.opensips-solutions.com<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips-solutions.com%2F&data=04%7C01%7C%7C4bdabd460c654a24286508da213b3532%7C84df9e7fe9f640afb435%7C1%7C0%7C637858835416369371%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=36EkFVPCeFaljYrES8cKks7TXkj%2F6fSyoQ7EEHyCy1A%3D&reserved=0>

OpenSIPS eBootcamp 23rd May - 3rd June 2022

  
https://opensips.org/training/OpenSIPS_eBootcamp_2022/<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensips.org%2Ftraining%2FOpenSIPS_eBootcamp_2022%2F&data=04%7C01%7C%7C4bdabd460c654a24286508da213b3532%7C84df9e7fe9f640afb435%7C1%7C0%7C637858835416369371%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ndJ1csbScmWVYCzMlysiEAKeKWBQDO44rAkpT%2B%2F0HZA%3D&reserved=0>
On 4/13/22 6:08 PM, Jonathan Hunter wrote:
Hi All,

Has anyone managed to get presence working when using an active/active opensips 

Re: [OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 in K8s environment

2022-04-18 Thread Bogdan-Andrei Iancu

Hi Jonathan,

Maybe the k8s layer (the ingress ??) sticks its tails in there - could 
you check at opensips level if the TCP conn is still seen as up ? Use 
the mi list_tcp_conns MI function

https://www.opensips.org/Documentation/Interface-CoreMI-3-2#toc4


Best regard,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 23rd May - 3rd June 2022
  https://opensips.org/training/OpenSIPS_eBootcamp_2022/

On 4/13/22 6:08 PM, Jonathan Hunter wrote:


Hi All,

Has anyone managed to get presence working when using an active/active 
opensips setup with k8s ?


Everything works apart from presence, In particular when a websocket 
user disconnects due to a client crash.


I ideally would want to use event_route[E_CORE_TCP_DISCONNECT] to then 
grab the disconnect when it comes in via websockets/tcp, however I 
cant seem to get it to trigger. Could this be due to the underlying 
hooks OpenSIPS uses to interact with with OS with TCP or something else?


As I would use the event route, to then remove the registration from 
the location table, as otherwise I have duplicate entries in both 
location and the presentity list.


Is this something anyone else has encountered?

I have tried using clustering with both presence and pua and have same 
issues, whereby after an unwanted disconnect subsequent NOTIFY 
messages contain more than one id per entity;


entity="sip:61067470a372a031a7495a1a@domain">


id="0x7ffe75896760">openxmlns="urn:ietf:params:xml:ns:pidf" 
id="0x7ffd0716b390">open


I need to stop this occurring ideally, any help much appreciated.

Many thanks

Jon

Sent from Mail  for 
Windows



___
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


[OpenSIPS-Users] Clustering Presence opensips 3.2/3.3 in K8s environment

2022-04-13 Thread Jonathan Hunter
Hi All,

Has anyone managed to get presence working when using an active/active opensips 
setup with k8s ?

Everything works apart from presence, In particular when a websocket user 
disconnects due to a client crash.

I ideally would want to use event_route[E_CORE_TCP_DISCONNECT] to then grab the 
disconnect when it comes in via websockets/tcp, however I cant seem to get it 
to trigger. Could this be due to the underlying hooks OpenSIPS uses to interact 
with with OS with TCP or something else?

As I would use the event route, to then remove the registration from the 
location table, as otherwise I have duplicate entries in both location and the 
presentity list.

Is this something anyone else has encountered?

I have tried using clustering with both presence and pua and have same issues, 
whereby after an unwanted disconnect subsequent NOTIFY messages contain more 
than one id per entity;


openopen

I need to stop this occurring ideally, any help much appreciated.

Many thanks

Jon



Sent from Mail for Windows

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


Re: [OpenSIPS-Users] Clustering 2.4 and 3.0

2019-10-16 Thread Alexey Kazantsev via Users


Hi Răzvan,
thank you.
 
So, 2.4 will be the best choice as it it LTS.
 
>Hi, Alexey!
>
>Most likely clustering 2.4 and 3.0 versions would not work, due to
>different replication packets versions.
>
>Best regards,
>Răzvan
 
---
BR, Alexey
http://alexeyka.zantsev.com/
 ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] Clustering 2.4 and 3.0

2019-10-16 Thread Răzvan Crainea

Hi, Alexey!

Most likely clustering 2.4 and 3.0 versions would not work, due to 
different replication packets versions.


Best regards,
Răzvan

On 10/16/19 7:40 AM, Alexey Kazantsev via Users wrote:

Hi list,
is it a good/bad idea to create a cluster of 2.4 and 3.0 versions?
Or it’s of vital importance to have the same version of instances in the 
cluster?

The idea is to create a federated user location cluster. [1]
[1] 
https://opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation

---
BR, Alexey
http://alexeyka.zantsev.com/

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



--
Răzvan Crainea
OpenSIPS Core Developer
  http://www.opensips-solutions.com

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


[OpenSIPS-Users] Clustering 2.4 and 3.0

2019-10-15 Thread Alexey Kazantsev via Users

Hi list,
 
is it a good/bad idea to create a cluster of 2.4 and 3.0 versions?
Or it’s of vital importance to have the same version of instances in the 
cluster?
 
The idea is to create a federated user location cluster. [1]
 
[1]  
https://opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation
 
---
BR, Alexey
http://alexeyka.zantsev.com/___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users