[SR-Users] DMQ problems

Charles Chance charles.chance at sipcentric.com
Sat Jun 23 18:26:04 CEST 2018


Hello,

Is there anything preventing the messages from reaching Kamailio? If you
have a pcap from one of the servers we may be able to see what’s happening.

Also, you have the notification address set to localhost - this should
instead point to one of the other nodes.

Cheers,

Charles

On Fri, 22 Jun 2018 at 21:35, Aleksandar Sosic <alex.sosic at evosip.cloud>
wrote:

> Hi,
>
> I've set up a dmq server for other kamailio nodes with this parameters:
> ```
> modparam("dmq", "server_address","sip:10.0.0.101:5060")
> modparam("dmq", "notification_address", "sip:127.0.0.1:5060")
> modparam("dmq", "multi_notify", 1)
> modparam("dmq", "num_workers", 4)
> modparam("dmq", "ping_interval", 15)
> ```
>

Why are you setting the notification address as localhost?


> On the kamailio nodes the config is the following:
> ```
> modparam("dmq", "server_address", "sip:10.0.0.x:5060")
> modparam("dmq", "notification_address", "sip:10.0.0.101:5060")
> modparam("dmq", "multi_notify", 1)
> modparam("dmq", "num_workers", 4)
> modparam("dmq", "ping_interval", 15)
> ```
>
> On the kamailio dmq server I've got this in the logs:
> ```
> 25(41) ERROR: dmq [notification_peer.c:596]:
> notification_resp_callback_f(): deleting server sip:127.0.0.1:5060
> because of failed request
> 25(41) ERROR: dmq [notification_peer.c:599]:
> notification_resp_callback_f(): not deleting notification_peer
> ```
>
> On the kamailio nodes the same thing with the ip of the dmq server:
> ```
> 25(112) ERROR: dmq [notification_peer.c:596]:
> notification_resp_callback_f(): deleting server sip:10.0.0.101:5060
> because of failed request
> 25(112) ERROR: dmq [notification_peer.c:599]:
> notification_resp_callback_f(): not deleting notification_peer
> ```
>
> The request route on the dmq server is simple as this:
> ```
> request_route {
> if(is_method("KDMQ")){
> dmq_handle_message();
> }
> }#end request_route
> ```
>
> I've tried with some xlog-s inside the if(is_method("KDMQ")) but they
> don't show up so the dmq_handle_message() is not even executed.
>
> I've also tried to bind the dmq server to a different port but with no
> success on making it work.
>
> The dmq.list_nodes shows only the dmq server IP and the current node
> IP, the IPs of other nodes are not shown:
> ```
> root at proxy-94b6ccf46-t8fx2:/# kamcmd dmq.list_nodes
> {
> host: 10.0.0.101
> port: 5060
> resolved_ip: 10.0.0.101
> status: active
> last_notification: 0
> local: 0
> }
> {
> host: 10.0.0.45
> port: 5060
> resolved_ip: 10.0.0.45
> status: active
> last_notification: 0
> local: 1
> }
> ```
> And it's the same on all other kamailio nodes: dmq server ip and local ip.
>
> The kamailio version on all the nodes is:
> 5.2.0~dev6+0~20180616010152.1138+xenial
>
> 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
>
-- 
*Charles Chance*
Managing Director

t. 0330 120 1200    m. 07932 063 891

-- 
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/20180623/8fe4178f/attachment.html>


More information about the sr-users mailing list