Hello, On 12/05/15 10:50, José Seabra wrote: > Hello Daniel, > > This issue was my mistake, I have a htable called fscache that > connects the call-ids of each call with freeswitch ip, and now I'm > re-using the same htable to save other information that i need and > replicate it to others kamailios through DMQ. > The random values in cname field that i saw are the call-ids of calls > that are saved in this htable. this was my confusion. > > Really sorry for my mistake, maybe i need vacations :) no problem, just wanted to be sure there is no hidden issue that popped up with your use case. But vacation is always good, of course!
Cheers, Daniel > > BR > > José Seabra > > 2015-05-11 18:49 GMT+01:00 José Seabra <joseseab...@gmail.com > <mailto:joseseab...@gmail.com>>: > > Hi Daniel, > Tomorrow i will do more tests in order to have sure about that, > because maybe i did something wrong. but tomorrow i will report > back to you. > > Thank you > BR > José Seabra > > 2015-05-11 15:53 GMT+01:00 Daniel-Constantin Mierla > <mico...@gmail.com <mailto:mico...@gmail.com>>: > > Hello, > > to be sure is no problem there -- is it like if you use item > name "queue:2" you get issues? It should not matter if inside > item name is ":" or "::" -- that is part of static string. > > Or it was no relation with the ":" inside the item name -- > somehow I couldn't understand exactly where you had the problem. > > Cheers, > Daniel > > > On 11/05/15 13:55, José Seabra wrote: >> Hello >> >> I found the root cause of this issue, I'm concatenate the >> field cname "queue:2", and the correct is "queue::2", with >> this last concatenation i don't have any issue, >> >> Sorry for my mistake. >> >> Regards >> José Seabra >> >> 2015-05-11 12:29 GMT+01:00 José Seabra <joseseab...@gmail.com >> <mailto:joseseab...@gmail.com>>: >> >> DMQ sip message received from another kamailio: >> >> <sip:htable@10.0.20.100:5060 >> <http://sip:htable@10.0.20.100:5060>>#015#012From: >> <sip:htable@10.0.20.101:5060 >> >> <http://sip:htable@10.0.20.101:5060>>;tag=16d781b5e523d368d90ec40507eac972-5d82#015#012CSeq: >> 10 KDMQ#015#012Call-ID: >> 4c4a0dd935347969-24970@10.0.20.101#015#012Content-Length >> >> <http://4c4a0dd935347969-24970@10.0.20.101#015%23012Content-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@10.0.20.100:5060 >> <http://sip:htable@10.0.20.100:5060> >> F=sip:htable@10.0.20.101:5060 >> <http://sip:htable@10.0.20.101:5060> >> T=sip:htable@10.0.20.100:5060 >> <http://sip:htable@10.0.20.100:5060> >> IP=udp:10.0.20.101:5060 <http://10.0.20.101:5060> >> ID=4c4a0dd935347969-24970@10.0.20.101 >> <mailto:4c4a0dd935347969-24970@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 >> <joseseab...@gmail.com <mailto:joseseab...@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 >> >> >> >> >> >> >> >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing >> list >> sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla > http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - > http://www.linkedin.com/in/miconda > Kamailio World Conference, May 27-29, 2015 > Berlin, Germany - http://www.kamailioworld.com > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users > mailing list > sr-users@lists.sip-router.org > <mailto:sr-users@lists.sip-router.org> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > > > -- > Cumprimentos > José Seabra > > > > > -- > Cumprimentos > José Seabra -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com
_______________________________________________ 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
