[SR-Users] DMQ problems

Charles Chance charles.chance at sipcentric.com
Thu Jul 5 12:33:31 CEST 2018


I'll take a look - which version are you using?

Cheers,

Charles

On 5 July 2018 at 11:17, Aleksandar Sosic <alex.sosic at evosip.cloud> wrote:

> On Mon, Jul 2, 2018 at 2:55 PM Charles Chance
> <charles.chance at sipcentric.com> wrote:
> > Hi Aleksandar,
> > [...]
> > You do not, in fact, need to maintain a dedicated node who's only role
> is "DMQ server" as you have described it. I would recommend removing it
> completely and allowing your other nodes to discover/communicate between
> themselves.
>
> Ok Thanks for your inputs, seems a good idea and I think we're on a
> good path to solve our issues.
>
> > Omitting the notification address should not cause an issue - what error
> do you see in your log when it fails to start? If you get rid of the "DMQ
> server' node as suggested above, though, this should be a none-issue.
>
> It does cause an issue:
> ```
>  0(51) DEBUG: <core> [core/parser/parse_uri.c:1254]: parse_uri(): uri
> too short: <> (0)
>  0(51) ERROR: dmq [dmq.c:218]: mod_init(): notification address invalid
>  0(51) ERROR: <core> [core/sr_module.c:990]: init_mod(): Error while
> initializing module dmq
> (/usr/lib/x86_64-linux-gnu/kamailio/modules/dmq.so)
> ERROR: error while initializing modules
> ```
>
> Maybe a feature request could be to just start kamailio even if it
> does not resolve a dns record for the dmq notification_address? This
> would solve us some problems in a highly mutable infrastructure like
> ours:
>
> ``` 0(88) ERROR: dmq [notification_peer.c:336]:
> add_server_and_notify(): error adding notification node
>  0(88) ERROR: dmq [dmq.c:304]: child_init(): cannot retrieve initial
> nodelist from sip:proxy-service:5061
>  0(88) ERROR: <core> [core/sr_module.c:944]: init_mod_child(): error
> while initializing module dmq
> (/usr/lib/x86_64-linux-gnu/kamailio/modules/dmq.so) (idx: 0 rank: 0
> desc: [main])
>  0(88) ERROR: <core> [main.c:1711]: main_loop(): error in init_child```
>
> So just to recap:
> - Not specifying a notification_address DOES give issues
> - Having a DNS record for the notification_address that does not
> resolve makes kamailio to crash
>
> Any possibility to have this solved/enhanced?
>
> Thanks,
> --
> Aleksandar Sosic
> mail: alex.sosic at evosip.cloud
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>

-- 
Sipcentric Ltd.
                Company registered in England & Wales no. 
7365592. Registered
                office: Faraday Wharf, Innovation 
Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20180705/01dc8db8/attachment.html>


More information about the sr-users mailing list