I will setup dnsmasq on each kamailio server, which will resolve
sip.example.com to own ip. And clients from this city will use this dns and
connect to sip.example.com
2017-11-30 9:17 GMT+03:00 Yuriy Gorlichenko :
> I this here is a way to share user for watcher from any
I this here is a way to share user for watcher from any domain using
rpc.subscribe command after handle_subscribe()
It is availible to make simple service that will be triggered by subscribe
request and make fake subscribe request with needed data for other domains.
Handle this subscribe also by
Hello,
So I understand that each server has its own FQDN and you want to point
users to their closest proxy, but are all servers part of the same
'logical' domain?
The SIP domain/realm does not have to be the same as the address/hostname
of the individual proxy server that is servicing a
I have some kamailio servers in each city: city1.example.com,
city2.example.com, city3.example.com.
Users in city1 connects to city1.example.com.
each kamailio has in config:
alias="city1.example.com"
alias="city2.example.com"
alias="city3.example.com"
modparam("dmq", "server_address",
Hello,
Why are you trying to operate across domains in the same DMQ cluster?
Usually, servers operating in different domains do not need to be aware of
each other's user location and/or subscription records - if a request is
for another domain, simply forward it to the server(s) responsible for
It is already replicated. but domains are not same.
2017-11-29 15:52 GMT+03:00 Yuriy Gorlichenko :
> Hi. Just replicate publish messages to second server.
>
> On Nov 29, 2017 19:46, "Aidar Kamalov" wrote:
>
>> Hello,
>>
>> I have two(or more)
Hi. Just replicate publish messages to second server.
On Nov 29, 2017 19:46, "Aidar Kamalov" wrote:
> Hello,
>
> I have two(or more) kamailio servers with dmq module and dmq_usrloc -
> sip1.example.com and sip2.example.com
> publish and subcribe replication works too.
>
Hello,
I have two(or more) kamailio servers with dmq module and dmq_usrloc -
sip1.example.com and sip2.example.com
publish and subcribe replication works too.
BLF works fine if clients connected to the same kamailio server, because in
active_watchers table stored with same domain