Re: [OpenSIPS-Users] 3.0.1 Full sharing registrar - mysql write back not working

Ok, in this case we are running a central database per geographic location with two local instances per site, each site serves a unique domain. The goal is to have it setup such that clients will have registrations in two sites and are served by a single server per site, a VIP owner. The second

Re: [OpenSIPS-Users] Opensips 2.4.x and CP 8

Last comments in Changelog are the following dates 2019-07-22 Bogdan Iancu I think I downloaded 8.3.0 by mistake! f. Let me reinstall with 8.2.4 git Thanks for the catch. ___ Users mailing list Users@lists.opensips.org

Re: [OpenSIPS-Users] Opensips 2.4.x and CP 8

Jeff, I didn’t see this in your original post but have you verified you are using CP 8.2.4? Ben Newlin From: Users on behalf of Jeff Wilkie Reply-To: OpenSIPS users mailling list Date: Wednesday, November 6, 2019 at 1:03 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users]

Re: [OpenSIPS-Users] Recommended Radius client/server for AAA on 2.4.x under Debian 9

Any build and config docs to support radcli installation with opensips 2.4 and 3.x by chance? Thanks Jeff On Wed, Nov 6, 2019 at 4:56 AM Răzvan Crainea wrote: > radcli is the library we're using in our latest packages. > > Best regards, > Răzvan > > On 11/6/19 5:48 AM, qasimak...@gmail.com

Re: [OpenSIPS-Users] Opensips 2.4.x and CP 8

> > Thanks for the response. That document does not explain why I'm seeing a > POST error using the CP8. If I directly http to opensips using requests > for json it works properly using a GET. Why would the the CP generate a > POST using JSON? How do I turn that off? Any reload command in the

Re: [OpenSIPS-Users] 3.0.1 Full sharing registrar - mysql write back not working

The answer is: it depends.  If each of your servers has its own, local "location" table for persistency reasons, then you must remove "skip_replicated_db_ops".  This is our recommended way of ensuring persistency:  no more shared DB shenanigans, keep the tables private. However, if your

Re: [OpenSIPS-Users] 3.0.1 Full sharing registrar - mysql write back not working

Thanks Liviu, that helps a lot. My expectation was that the sync-from-cluster option would favour a sync operation from a local active peer via the binary interface on first boot, that sounded like the ideal behaviour as it should be fully up to date; especially in db write back mode. For our

Re: [OpenSIPS-Users] 3.0.1 Full sharing registrar - mysql write back not working

Hi Callum, In short: * "sync-from-cluster" will deny all DB writes.  It is useful in case you don't   mind the risk of losing all registrations in case the active node is offline   and you restart the backup for some reason.  On the positive side, you will   push a lot less queries to the

[OpenSIPS-Users] 3.0.1 Full sharing registrar - mysql write back not working

Hi All, I've been testing a new cluster based registrar config and noticed that the location records weren't being written back to the database. The issue appears resolved when I switch usrloc.restart_persistency from "sync-from-cluster" to "load-from-sql". This is acceptable however it seems

Re: [OpenSIPS-Users] Recommended Radius client/server for AAA on 2.4.x under Debian 9

radcli is the library we're using in our latest packages. Best regards, Răzvan On 11/6/19 5:48 AM, qasimak...@gmail.com wrote: You can use latest version of freeradius it has both client and server. Regards, Qasim On Wed, 6 Nov 2019 at 8:27 AM, Jeff Wilkie >

Re: [OpenSIPS-Users] OpenSIPs 2.2.3 SegFault

Hi, Ahmed! OpenSIPS 2.2 is quite an old version and is no longer supported for a while. If you have the possibility, I'd suggest you to migrate to 2.4, which is a stable LTS - if the issue occurs there, then we are able to investigate it and track down the problem. If you can't do that,

Re: [OpenSIPS-Users] force send socket for load balancer ping

Hi, Peter! Unfortunately this feature is not available for now for the load_balancer module. There's actually a feature request already for doing this :)[1]. For now, what you can do is to "catch" that OPTIONS message in the `local_route` and force the send socket over there. [1]