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
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.
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
*Fr
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: Bogda
"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", &qu
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
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
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
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
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]
10 matches
Mail list logo