Hi Sasmita,
The functions that allow you the send custom messages in the cluster at
script level are still there in opensips 3.0, so yes, you can implement
something similar to that blog post.
Regards,
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com
On 09/06/2019 11:25 AM, Sasmita Panda wrote:
Ok . Thank you .
I got a document for geo distributed clustering which uses redis as
cache . This uses opensips 2.4 . I had tested this architecture also .
This is working fine .
https://saevolgo.blogspot.com/2018/01/opensips-geo-distributed-clustering.html
Can I use this kind of scripting with opensips 3.0 to use redis cache ?
If not , then to use redis I have to use opensips2.4 with clustering .
Am I right ?
*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/
On Fri, Sep 6, 2019 at 1:31 PM Giovanni Maruzzelli <[email protected]
<mailto:[email protected]>> wrote:
it cannot work
documentation say that explicitly
"Currently, the metadata information may be published to NoSQL
databases which support key/multi-value column-like associations.
Example known backends to support these abstractions at the time
of writing are MongoDB and Cassandra."
https://opensips.org/html/docs/modules/3.0.x/usrloc.html
On Fri, Sep 6, 2019 at 9:53 AM Sasmita Panda <[email protected]
<mailto:[email protected]>> wrote:
Hi All ,
I have tested opensips 3.0 federated cachedb cluster with
mongo db as cache db .
But in my company we are using redis as cache db.
loadmodule "cachedb_redis.so"
loadmodule "db_cachedb.so"
modparam("cachedb_redis",
"cachedb_url","redis:group1://192.168.0.213:6379/
<http://192.168.0.213:6379/>")
modparam("db_cachedb","cachedb_url","redis:group1://192.168.0.213:6379/
<http://192.168.0.213:6379/>")
modparam("usrloc", "cachedb_url",
"redis:group1://192.168.0.213:6379/ <http://192.168.0.213:6379/>")
In place of mongodb I have replace redis . But its not working
. I am not getting any data the redis cache . Please help me .
*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/
On Mon, Sep 2, 2019 at 1:07 PM Sasmita Panda
<[email protected] <mailto:[email protected]>> wrote:
*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/
---------- Forwarded message ---------
From: *Giovanni Maruzzelli* <[email protected]
<mailto:[email protected]>>
Date: Mon, Sep 2, 2019 at 12:40 PM
Subject: Re: [OpenSIPS-Users] need some help using
opensips 3.0 cluster module .
To: OpenSIPS users mailling list <[email protected]
<mailto:[email protected]>>
Sasmita, how possibly you can do that?
How you then associate a machine with an id?
Would you create a new database field for the MAC of the
machine?
-giovanni
On Mon, Sep 2, 2019 at 8:54 AM Sasmita Panda
<[email protected] <mailto:[email protected]>> wrote:
Hi All ,
In clustering , every opensips node has its own node id .
modparam("clusterer", "my_node_id", 2)
I want to read this value from from the DB . Is this
possible or not ? If yes , how will I do this ?
Please do help me .
*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/
On Thu, Aug 8, 2019 at 12:44 PM Sasmita Panda
<[email protected] <mailto:[email protected]>> wrote:
Thank you so much for the explanation .
*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/
On Wed, Aug 7, 2019 at 6:46 PM Liviu Chircu
<[email protected] <mailto:[email protected]>>
wrote:
Sasmita,
Dialog replication is not meant to work on
such a cluster. Since dialogs
retain more
state than registration, they are more
sensitive to the IP of the
current node.
If you want high-availability for dialogs, the
basic unit of deployment
shifts from
1 server to 2 servers (an active/backup
pair). And in order to have the
same IP on
both servers, you must use VRRP-capable
software, such as keepalived.
Deploy as many pairs as needed in each
location according to your
traffic volume, and
make sure to give each pair its own Virtual
(highly available) IP that
can automatically
move from the active node to the backup in
case the former one catches fire.
PS: this information should be included in the
dialog replication blog
post, so make
sure to read it closely.
Liviu
On 8/6/19 1:25 AM, Sasmita Panda wrote:
> | id | cluster_id | node_id | url
| state |
> no_ping_retries | priority | sip_addr |
flags | description |
> | 1 | 1 | 1 |
bin:192.168.0.x:5555 | 1 |
> 3 | 50 | 192.168.0.x | seed | Node A
|
> | 2 | 1 | 2 |
bin:192.168.0.y:5555 | 1 |
> 3 | 50 | 192.168.0.y | seed | Node B
|
> | 3 | 1 | 3 |
bin:192.168.0.z:5555 | 1 |
> 3 | 50 | 192.168.0.z | seed | Node C
_______________________________________________
Users mailing list
[email protected]
<mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Sincerely,
Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Sincerely,
Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
