On 23/02/16 05:20, Arsen Hovhanissian wrote:
> Sorry forgot to specify (in-memory) not using the DB, I feel like using the
> DB for such a task would be such a drag on it
>
The dialog profile items replication should be possible, but full dialog
state in-memory replication would result also in act
Sorry forgot to specify (in-memory) not using the DB, I feel like using the DB
for such a task would be such a drag on it
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.o
Since this thread is open, I wanted to ask, is it possible to replicate dialog
data over to multiple nodes as well?
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-
Hi,
Interesting discussion going on. Ive to ask can OP use shared location
table between different kamailio servers and use db mode 3.
All he has to do is if UA B calls UA A via Kamailio2 he just needs to find
the received socket and if it is not local Kamailio2 then route to the IP
maybe attach a
Hi,
If you have following:
UA A > Kamilio 1
UA B > Kamailio 2
With path you just make sure that all calls are routed to that server where
UA initially registered.
So if UA A is calling UA B, call will go in such way: UA A=> Kamilio 1 =>
Kamailio 2 => UA B.
I hope I answered your quest
Actually I think something is not clear here. Suppose I want to use two
Kamailio servers such that a client which is registered on server A is able
to call another client registered on server B. In this case I use DB_MODE
3. Both servers have access to location database but sockets are non-local
an
On Wed, Feb 03, 2016 at 01:48:50PM +0330, Gholamreza Sabery wrote:
> Actually I think something is not clear here. Suppose I want to use two
> Kamailio servers such that a client which is registered on server A is able
> to call another client registered on server B. In this case I use DB_MODE
> 3.
On Mon, Feb 01, 2016 at 09:17:41AM +0100, Federico Cabiddu wrote:
> a solution in this case could be making usage of Path header (
> https://tools.ietf.org/html/rfc3327).
> You have to load the path module
> http://www.kamailio.org/docs/modules/devel/modules/path.html
> and enabled its usage in reg
The solution I am using is to have each Kamailio servers read
subscriber/location data from a local database server. Each of these local
databases is replicated from a Master database. We have db_mode=3 for sqlops,
so it's always reading from the database to identify the user/phone.
-H
On 20
Also one of the most siplies ways to resolve your issue is using queries at
the databases that select needed fields from db with (where
socket="").
2016-02-01 11:43 GMT+03:00 Gholamreza Sabery :
> All right. Thank you so much.
>
> On Mon, Feb 1, 2016 at 11:47 AM, Federico Cabiddu <
> federico.ca
All right. Thank you so much.
On Mon, Feb 1, 2016 at 11:47 AM, Federico Cabiddu <
federico.cabi...@gmail.com> wrote:
> Hi,
> a solution in this case could be making usage of Path header (
> https://tools.ietf.org/html/rfc3327).
>
> You have to load the path module
>
> http://www.kamailio.org/docs
Hi,
a solution in this case could be making usage of Path header (
https://tools.ietf.org/html/rfc3327).
You have to load the path module
http://www.kamailio.org/docs/modules/devel/modules/path.html
and enabled its usage in registrar module
http://www.kamailio.org/docs/modules/devel/modules/reg
Hi Alex,
You are right. :)
With kind regards,
2016-02-01 10:09 GMT+02:00 Alex Balashov :
> On 02/01/2016 02:59 AM, Jurijs Ivolga wrote:
>
> I think you need to make record routing, so it will keep initial(to what
>> user registered) Kamailio in signaling path.
>>
>
> Ah, no. Record-Route is for
On 02/01/2016 02:59 AM, Jurijs Ivolga wrote:
I think you need to make record routing, so it will keep initial(to what
user registered) Kamailio in signaling path.
Ah, no. Record-Route is for INVITEs only. You're thinking of Path.
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimet
Yes I want to distribute my users across multiple Kamailio servers. It
seems a good idea than you Alex I will try it!
On Mon, Feb 1, 2016 at 11:10 AM, Alex Balashov
wrote:
> Here's a thought, though:
>
> If your goal is really for users registered on one server to be able to
> easily call users
Hi,
I think you need to make record routing, so it will keep initial(to what
user registered) Kamailio in signaling path.
I hope it will helps.
With kind regards,
Jurijs
2016-02-01 9:33 GMT+02:00 Gholamreza Sabery :
> Thank you so much Alex. I tried REGISTER replication and DM_MODE 3. But my
Here's a thought, though:
If your goal is really for users registered on one server to be able to
easily call users registered on another server, you probably don't care
to replicate or share the 'location' table per se. You just want one
Kamailio server to call the right Kamailio server to re
On 02/01/2016 02:33 AM, Gholamreza Sabery wrote:
in these scenarios Kamailio will give you a non-local socket error
It's a warning, not an error. Right?
I don't remember how we solved that...
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, G
Thank you so much Alex. I tried REGISTER replication and DM_MODE 3. But my
problem here is that in these scenarios Kamailio will give you a non-local
socket error. I want to have multiple Kamailio servers so that a user that
is registered on one server can easily call other users on another server.
Although, the core `dmq` module is a big help in providing a
distribution vehicle for messaging you do wish to replicate into a
'cluster':
http://kamailio.org/docs/modules/4.3.x/modules/dmq.html#dmq.f.dmq_t_replicate
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center Nort
Hi Gholamreza,
Most Kamailio functionality can be used in an active-active way as long
as there is a database persistence layer that can be shared among them:
In particular, since you asked about the registrar: you can use
`db_mode` 3 with `usrloc` to achieve this persistence:
http://kamail
Dear Hossein; I know about Corosync and Pacemaker and I implemented
something using these tools with Ansible (
https://github.com/ghrst/Kamailio-HA). But my question here is about
active-active scenarios not an active-passive one!
On Mon, Feb 1, 2016 at 2:14 AM, Hossein Aghaie
wrote:
> hi Ghola
hi Gholamreza Sabery
you should be implement HA on your server.you can use the
pacemaker/corosync or other software for run and configuration HA on
your server.
On 1/31/16, Gholamreza Sabery wrote:
> I am trying to create a cluster of Kamailio servers. I want users that are
> registered on one s
I have something similar and I use the following architecture:
NGCP-A-subscribres A||sip trunk between A and B
||NGCP-B-subscribers B
||sip trunk between B and C
|NGCP-C-Subscribers C
||sip trunk between A and C
|NGCP-A---
I am trying to create a cluster of Kamailio servers. I want users that are
registered on one server to be able to contact and call users on other
servers. How can I implement this in Kamailio?
PS: My servers are in a private network and I do not have DNS.
__
25 matches
Mail list logo
