<p>For example, I have four kamailio instance for register, one kamailio instance recv REGISTER, it copy to other three kamailio instance by dmq_usrloc.<br>
In this scene, I set notification_address to domain sip:ka.ns.com:5060 which resolve to all four kamailio instance(which recv REGISTER).In this way, <strong>I do not need to build a separate kamailio cluster only for notification server.</strong></p>
<pre><code>modparam("dmq", "server_address", "sip:10.6.1.200:5260")
modparam("dmq", "notification_address", "sip:ka.ns.com:5260")
# This configuration, ka.ns.com only resolve to 10.6.1.200, kamailio can not normal start.
it report : 
dmq [notification_peer.c:345]: add_server_and_notify(): error adding notification node
dmq [dmq.c:299]: child_init(): cannot retrieve initial nodelist from sip:ka.ns.com:5260
</code></pre>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/pull/1308#issuecomment-343027892">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZW754QmmGI2rxTHKfRtw5TzyuBXeks5s0mMEgaJpZM4QWFuo">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AF36ZZL0jxDfls6LLTWpqrDiFktpUP22ks5s0mMEgaJpZM4QWFuo.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/kamailio/kamailio/pull/1308#issuecomment-343027892"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@zhangst in #1308: For example, I have four kamailio instance for register, one kamailio instance recv REGISTER, it copy to other three kamailio instance by dmq_usrloc.\r\nIn this scene, I set notification_address to domain sip:ka.ns.com:5060 which resolve to all four kamailio instance(which recv REGISTER).In this way, **I do not need to build a separate kamailio cluster only for notification server.**\r\n\r\n```\r\nmodparam(\"dmq\", \"server_address\", \"sip:10.6.1.200:5260\")\r\nmodparam(\"dmq\", \"notification_address\", \"sip:ka.ns.com:5260\")\r\n# This configuration, ka.ns.com only resolve to 10.6.1.200, kamailio can not normal start.\r\nit report : \r\ndmq [notification_peer.c:345]: add_server_and_notify(): error adding notification node\r\ndmq [dmq.c:299]: child_init(): cannot retrieve initial nodelist from sip:ka.ns.com:5260\r\n```"}],"action":{"name":"View Pull Request","url":"https://github.com/kamailio/kamailio/pull/1308#issuecomment-343027892"}}}</script>