Hello Adrian,
The actual question is IF there is SOMETHING that can be done directly
in the usrloc module to help with distributed scenario (to have some
built-in functionality to have an auto-of-the-box solution). I'm fully
aware you can combine the existing module with other kind of backends
Hello Muhammad,
Your approach is the correct one (from SIP perspective) IMHO. But there
are questions on the implementation side too - like the "Super Node" is
just a storage or it should have SIP capabilities? How much of this
behavior should be hardcoded in the registrar + usrloc module ?
The lookup function could be extended to determine which node is responsible
for a given SIP URI based on a one-way hashing function. Chord is an example of
algorithm that can be used to map the hashes to the nodes (practically is a
integer comparison where all SIP URIs are attracted by the next
Bogdan,
As you suggest, there are ways to achieve this now manually with
custom scripting and glue, it its not very straightforward. What I
think is the goal would be something drop in ready, that you could
just enable for distributed location versus normal location.
The solution may be to fork
Rudy,
You are one step ahead :) - indeed, we need to find the best approach on
the implementation side (different modules? flags/parameters?).
But the current step is finding the solution : how the distributed
version of usrloc would look like ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founde
Well, i am not much familiar with internals of opensips, i.e. its core and
modules and how they interact with each other. But as an abstract idea, i
suggest that both Base Node and Super Node should be opensips modules. No
change in standard registrar or usrloc modules are actually needed.
In the
Hi all,
First, thanks to all who spent the time and taking the vote. The results
are quite conclusive, I would say :
http://www.opensips.org/Vote/GitResult
~80% for going for GitHub. So, let's do it :).
As a plan of attack:
1) repository
a) converting SVN repo to GIT
Bugs item #3607052, was opened at 2013-03-06 07:08
Message generated for change (Comment added) made by umautone
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3607052&group_id=232389
Please note that this message will contain a full copy of the comment
