Hello, On 27/10/15 12:17, Sebastian Damm wrote: > Hi, > > when inspecting dmq a bit further, I found that in fact there is an > autodiscovery built in. When I told registrar 1 and registrar 2 to > send to receiver, and told receiver to only send to itself, everything > worked. Until the receiver went offline. Then it got disabled by the > registrars and no packets got replicated anymore after it came back > online until the registrars were restarted, too. > > Since we don't want this situation, I told the receiver to send to a > dns record containing all registrars. This way, after the receiver > came back up, the registrars got notified and started replicating > their usrloc again. But they didn't send to the receiver only, but > also to the other registrar. > > Since we have quite an amount of registration traffic on the > registrars (and actually there are more than two of them), we don't > want to send this traffic multiple times through our network. > > Is there any way we can force the dmq module to send only to the > configured receiver? I guess a patch to add a mod parameter to control this behaviour needs to be done. I expect to not be something complex to implement.
Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat _______________________________________________ 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
