Re: DMQ Status Flapping Between Active and Pending.
satyaprakash ch via sr-users <[email protected]>
| Newsgroups | gmane.comp.voip.ser |
|---|---|
| Message-ID | <CAO-xAtG+K0DP2CHsUWF5mCJPOW9qMf9rxFY0rXtmCpSVfbu6uQ@mail.gmail.com> |
HI, Thanks for the reply. Yes, I already tried using *ngrep* and was able to see the *KDMQ* and *200 OK* messages. However, when the status is *active*, the trace continues normally. But when the status changes to *pending*, the trace stops and only resumes once the status becomes *active* again. On Mon, Oct 6, 2025 at 5:19 PM Henning Westerholt <[email protected]> wrote: > Hello, > > > > first step is usually a packet trace, e.g. with ngrep. Have a look what is > actually send and received for the DMQ protocol on the two Kamailio servers. > > > > Cheers, > > > > Henning > > > > *From:* satyaprakash ch via sr-users <[email protected]> > *Sent:* Sunday, October 5, 2025 9:15 PM > *To:* Kamailio (SER) - Users Mailing List <[email protected]> > *Cc:* satyaprakash ch <[email protected]> > *Subject:* [SR-Users] DMQ Status Flapping Between Active and Pending. > > > > Hi, > > I have *two Kamailio presence servers running version 5.8.4*. I am using > *DMQ* to synchronize the active_watchers and presentity tables, but the > synchronization does not seem to be occurring consistently. > > During investigation, I observed that the *DMQ status repeatedly toggles > between **active** and **pending*, even though there is *no packet loss* > detected. > > *Output of dmq_nodes:* > > { > host: 192.168.18.96 > port: 5070 > proto: * > resolved_ip: 192.168.18.96 > status: pending > last_notification: 0 > local: 0 > } > { > host: 192.168.18.99 > port: 5070 > proto: * > resolved_ip: 192.168.18.99 > status: active > last_notification: 0 > local: 1 > } > > Any suggestions on what could cause this behavior would be greatly > appreciated. > __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!