Hi Bob, Yes, sr-dev would probably be more appropriate. Or if you would like to send a patch directly or raise a pull request on Github, that would be fine also.
SRV support is probably the way to go, since adding multiple addresses in config suggests a prior knowledge of nodes in advance, which doesn't fit with the DMQ ideology. I did start but got sidetracked with other commitments, as happens increasingly more often lately! Cheers, Charles On 4 March 2015 at 13:20, Robert Boisvert <rdboisv...@gmail.com> wrote: > Charles, > > I am working with the team that requested the SRV enhancement. I have > some time now to do some coding and would like to work on a patch to allow > multiple notification addresses. Would you be willing to discuss this? We > can take this conversation offline or move it to SR-Dev if you like. > > Thank you for considering this, > Bob > > On Wed, Mar 4, 2015 at 4:17 AM, Charles Chance < > charles.cha...@sipcentric.com> wrote: > >> Hello Bob, >> >> It is only possible to specify one notification address. So it is >> important to make sure it points initially to an active node. >> >> Once it has joined the cluster, the active node list is shared between >> all servers, so it should not matter which servers are up or down later. >> >> But for now, the notification address must be active at least on startup. >> It seems we may need to add SRV support to the dmq module at some point, >> when there is some spare time :-) >> >> Cheers, >> >> Charles >> On 3 Mar 2015 23:39, "Robert Boisvert" <rdboisv...@gmail.com> wrote: >> >>> Hello all, >>> >>> I would like to setup a DMQ bus where servers can come on and offline >>> and have DMQ continue working with the online servers. I'm having trouble >>> understanding how to do that with the notification address. Can someone >>> point me in the right direction? >>> >>> More specifically, suppose I have five servers named A, B, C, D, and E. >>> I would like all of them to be on the DMQ bus when active but they may come >>> up at different times. For example, when A, B and C start I want each of >>> them to be on the same DMQ bus. However, the way I understand it, if I >>> make E the notification address none will be on the bus because E is not >>> active. >>> >>> I could create a circular notification chain where A uses B as a >>> notification server, B uses C, and so on. Of course, there are problems >>> when one or more servers are missing from the chain. >>> >>> Any help on this is greatly appreciated. >>> >>> Thanks, >>> Bob >>> >>> _______________________________________________ >>> 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 >>> >>> >> www.sipcentric.com >> >> Follow us on twitter @sipcentric <http://twitter.com/sipcentric> >> >> Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered >> office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, >> Birmingham Science Park, Birmingham B7 4BB. >> _______________________________________________ >> 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 >> >> > > _______________________________________________ > 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 > > -- *Charles Chance* Managing Director t. 0121 285 4400 m. 07932 063 891 -- www.sipcentric.com Follow us on twitter @sipcentric <http://twitter.com/sipcentric> Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.
_______________________________________________ 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
