I've installed Kamailio on 2 different servers. They share the same PostgreSQL database for users etc.
I've setup a single domain, sip.my-domain.com, with latency responds to the 2 servers.
So a user will always land on the server with the fastest responds in a respective area of the world.
However, it seems as if 2 users are registered on different Kamailio servers - even though they share the same database - they cannot call each other?
Have I misunderstood something?
I've enabled WITH_NAT.
And I do have usrloc db_mode = 3.
On Thu, Nov 26, 2015 at 4:00 PM, Michael Nielsen mic.niel84@gmail.com wrote:
I've installed Kamailio on 2 different servers. They share the same PostgreSQL database for users etc.
I've setup a single domain, sip.my-domain.com, with latency responds to the 2 servers.
So a user will always land on the server with the fastest responds in a respective area of the world.
However, it seems as if 2 users are registered on different Kamailio servers - even though they share the same database - they cannot call each other?
Have I misunderstood something?
I've enabled WITH_NAT.
On Thursday 26 November 2015 16:00:09 Michael Nielsen wrote:
I've setup a single domain, sip.my-domain.com, with latency responds to the 2 servers.
So a user will always land on the server with the fastest responds in a respective area of the world.
What does this mean? How do you do this?
However, it seems as if 2 users are registered on different Kamailio servers - even though they share the same database - they cannot call each other?
Have I misunderstood something?
If the endpoints communicate directly to a sipserver and they have different adresses, a router/firewall/nattranslation will not match the traffic from any other adres to the translated port.
You could try branching to the other kamailio instance on failure to solve this.
Or you could try to use the socket column in the location table to figure out if the invite needs to be handled localy.
Or you might be able to abuse Path on registration (by inserting a Path header manually)
I'm using Amason's Route 53 DNS service with latency. So my A-records contains 2 IP's and Amazon keeps track of latency so it will deliver the correct IP for a given user.
These two IP contains identical installations of Kamailio - which share the same postgresql database. I've set usrloc db_mode = 3 so there's no cache in location of users in memory...
But NAT seems to be an issue even though WITH_NAT is enabled :(
On Thu, Nov 26, 2015 at 4:37 PM, Daniel Tryba d.tryba@pocos.nl wrote:
On Thursday 26 November 2015 16:00:09 Michael Nielsen wrote:
I've setup a single domain, sip.my-domain.com, with latency responds to
the
2 servers.
So a user will always land on the server with the fastest responds in a respective area of the world.
What does this mean? How do you do this?
However, it seems as if 2 users are registered on different Kamailio servers - even though they share the same database - they cannot call
each
other?
Have I misunderstood something?
If the endpoints communicate directly to a sipserver and they have different adresses, a router/firewall/nattranslation will not match the traffic from any other adres to the translated port.
You could try branching to the other kamailio instance on failure to solve this.
Or you could try to use the socket column in the location table to figure out if the invite needs to be handled localy.
Or you might be able to abuse Path on registration (by inserting a Path header manually)
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On Thursday 26 November 2015 16:41:52 Michael Nielsen wrote:
I'm using Amason's Route 53 DNS service with latency. So my A-records contains 2 IP's and Amazon keeps track of latency so it will deliver the correct IP for a given user.
So the endpoints communicate with different IPs?
These two IP contains identical installations of Kamailio - which share the same postgresql database. I've set usrloc db_mode = 3 so there's no cache in location of users in memory...
But NAT seems to be an issue even though WITH_NAT is enabled :(
And I explained the reason and possible workarounds on my assumtions based on provided information.
Yes, the endpoints communicate with different IPs. Client 1 with sip1.my-domain.com and client 2 with sip2.my-domain.com.
On Thu, Nov 26, 2015 at 4:51 PM, Daniel Tryba d.tryba@pocos.nl wrote:
On Thursday 26 November 2015 16:41:52 Michael Nielsen wrote:
I'm using Amason's Route 53 DNS service with latency. So my A-records contains 2 IP's and Amazon keeps track of latency so it will deliver the correct IP for a given user.
So the endpoints communicate with different IPs?
These two IP contains identical installations of Kamailio - which share
the
same postgresql database. I've set usrloc db_mode = 3 so there's no cache in location of users in memory...
But NAT seems to be an issue even though WITH_NAT is enabled :(
And I explained the reason and possible workarounds on my assumtions based on provided information.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Daniel Tryba -
Michael Nielsen