[SR-Users] DMQ htable replication issue.

José Seabra joseseabra4 at gmail.com
Mon May 11 13:29:23 CEST 2015


DMQ sip message received from another kamailio:

<sip:htable at 10.0.20.100:5060>#015#012From:
<sip:htable at 10.0.20.101:5060>;tag=16d781b5e523d368d90ec40507eac972-5d82#015#012CSeq:
10 KDMQ#015#012Call-ID:
4c4a0dd935347969-24970 at 10.0.20.101#015#012Content-Length:
119#015#012User-Agent: Voicis VSIP Proxy 1.X#015#012Max-Forwards:
1#015#012Content-Type:
application/json#015#012#015#012{"action":1,"htname":"fscache","cname":"8ee2d948-71b7-1233-efac-fa163ea4443f","type":2,"strval":"10.0.20.106","mode":1}
 M=KDMQ R=sip:htable at 10.0.20.100:5060 F=sip:htable at 10.0.20.101:5060 T=
sip:htable at 10.0.20.100:5060 IP=udp:10.0.20.101:5060 ID=
4c4a0dd935347969-24970 at 10.0.20.101

Everytime that kamailio sends  a DMQ to htable it generates a new cname.

Regards


2015-05-11 12:21 GMT+01:00 José Seabra <joseseabra4 at gmail.com>:

> Hello there,
>
> I'm using DMQ module to replicate an htable between several kamailio
> servers, what i'm noticing is that DMQ is sending the information from one
> server to another, but the htable name is not the same, for example:
>
> The original htable name is $sht(fscache=>queue:2), this htable is
> replicated to another server and the name (queue:2) will be replaced to
> some random value  like this:
>
> $sht(fscache=>3c34e55ae6f9-rsf8qhhwntvw)
>
> What happens is that the other server cannot get the data replicated,
> because in script kamailio is looking for $sht(fscache=>queue:2) that is
> the original name.
>
>
>
> My kamailio version is 4.2.2, i have tested also with version 4.2.4 but I
> got the same behavior.
>
> This is an expected behavior or a bug?  In case of expected behavior how I
> can  configure it in order to get the value replicated from one server to
> another?
>
> Thank you for your help
>
> --
> Cumprimentos
> José Seabra
>



-- 
Cumprimentos
José Seabra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150511/2ea6983f/attachment.html>


More information about the sr-users mailing list