[sr-dev] dmq server address question

Charles Chance charles.chance at sipcentric.com
Tue Feb 20 09:47:43 CET 2018


Hi Juha,

You’re not missing anything. DMQ only works with UDP.

I agree the parameter naming is confusing - I have an improvements branch
that I’ve been working on recently and it includes some updates to
documentation. I will make sure this is one of them :)

Cheers,

Charles


On Tue, 20 Feb 2018 at 05:49, Juha Heinanen <jh at tutpro.com> wrote:

> I tried to configure dmq module according to README, but got this kind
> of error:
>
> Feb 20 07:32:55 rautu /usr/bin/pres-serv[17983]: ERROR: dmq [dmq.c:228]:
> mod_init(): server_uri is not a socket the proxy is listening on
>
> In the config I have:
>
> modparam("dmq", "server_address", "sip:192.26.133.10:5080")
>
> and just above the error message there is this in syslog:
>
> Feb 20 07:32:55 rautu pres-serv[17959]: Listening on
> Feb 20 07:32:55 rautu pres-serv[17959]: tcp: 192.26.133.10
> [192.26.133.10]:5080
>
> i.e., server is listening on the same ip/port as in server_address.
>
> I tried also by configuring
>
> modparam("dmq", "server_address", "tcp:192.26.133.10:5080")
>
> since "sip" is not a transport protocol of a socket, but that was
> rejected with "server address invalid" error message.
>
> It is confusing that error message refers to server_uri, when modparam
> is called server_address.
>
> I must be missing something. Any ideas what it is?
>
> -- Juha
>
> _______________________________________________
> Kamailio (SER) - Development Mailing List
> sr-dev at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
>
-- 
*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-dev/attachments/20180220/9eb31ec3/attachment-0001.html>


More information about the sr-dev mailing list