1 Oct
2018
1 Oct
'18
3:39 a.m.
Charles,
Thanks, that indeed fixed the problem. Now the nodes are only listed
once.
Thanks for the quick response.
Jan
Charles Chance schreef op 2018-10-01 09:33:
Hi Jan,
Setting multi_notify parameter should fix.
Cheers,
Charles
On Mon, 1 Oct 2018 at 08:26, <jenus(a)cyberchaos.nl> wrote:
[3];alias=10.10.10.10~1055~1","contact2":"sip:+31101234567@10.10.10.10:5060
> [4]
>>> [6]"}
>> >>>
"lifetime":7200 is in the serialized data, and when i check on
> the
>>> other node with "kamcmd dlg.list" i see that the lifetime data is
>>> not updated.
>> >>> Thanks,
>> >>> Jan
>> >>>
_______________________________________________
>>> Kamailio (SER) - Users Mailing List
>>> sr-users(a)lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> >>> --
>>> Daniel-Constantin Mierla -- www.asipto.com [5] [1]
>>> www.twitter.com/miconda [6] [2] -- www.linkedin.com/in/miconda
> [7] [3]
>>> Kamailio World Conference -- www.kamailioworld.com [8] [4]
>>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --
>>> www.asipto.com [5] [1]
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users(a)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.
> >> Links:
>> ------
>> [1] http://www.asipto.com
>> [2] http://www.twitter.com/miconda
>> [3] http://www.linkedin.com/in/miconda
>> [4] http://www.kamailioworld.com
>> [5] http://sip:dialog@10.10.10.12:5060
>> [6] http://sip:+31101234567@10.10.10.10:5060
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users(a)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.
Links:
------
[1] http://10.10.10.1:5060
[2] http://sip:dialog@10.10.10.12:5060
[3] http://sip:sipuser@10.10.10.10:1057
[4] http://sip:+31101234567@10.10.10.10:5060
[5] http://www.asipto.com
[6] http://www.twitter.com/miconda
[7] http://www.linkedin.com/in/miconda
[8] http://www.kamailioworld.com
Charles,
I have the follwing parameters configured:
# ----- dmq params -----
modparam("dmq", "server_address", "sip:10.10.10.1:5060
[1]")
modparam("dmq", "num_workers", 4)
modparam("dmq", "ping_interval", 90)
modparam("dmq", "notification_address",
"sip:sip04.voip.domain.test:5060")
And the output of dmq.list_nodes is:
{
host: 10.10.10.2
port: 5060
resolved_ip: 10.10.10.2
status: active
last_notification: 0
local: 0
}
{
host: sip03.voip.domain.test
port: 5060
resolved_ip: 10.10.10.1
status: active
last_notification: 0
local: 0
}
{
host: sip04.voip.domain.test
port: 5060
resolved_ip: 10.10.10.2
status: active
last_notification: 0
local: 0
}
{
host: 10.10.10.1
port: 5060
resolved_ip: 10.10.10.1
status: active
last_notification: 0
local: 1
}
As you can see the nodes are listed twice, one time with the ip and
one
time with the hostname. If i change the notification_address to a ip
address the duplicate entry's are gone.
Thanks,
Jan
Charles Chance schreef op 2018-09-28 20:54:
{"action":2,"h_entry":1328,"h_id":409,"state":4,"start_ts":1538036606,"lifetime":7200,"tag1":"1635359980","tag2":"as2d80799c","cseq1":"21","cseq2":"0","route_set1":"","route_set2":"","contact1":"sip:sipuser@10.10.10.10:1057
Hello,
Can you share your dmq config (modparams) and the output of
dmq.list_nodes?
Cheers,
Charles
On Thu, 27 Sep 2018 at 12:51, Jan Hazenberg <jenus321(a)gmail.com>
wrote:
> In the output of "kamcmd dmq.list_nodes" i see nodes twice. One
with
> ip address of the host and one with the
hostname of the host.
> Jan
> On Thu, Sep 27, 2018 at 12:47 PM Jan
Hazenberg
<jenus321(a)gmail.com>
> wrote:
> Daniel,
> It indeed sends duplicate DMQ
messages, one to the ip of the
other
> node and one to the hostname of the other
node.
> Unknown request: KDMQ
sip:dialog@sip04.voip.domain.acc:5060 |
> (application/json)
> Unknown request: KDMQ sip:dialog@10.10.10.12:5060 [2] [5] |
> (application/json)
> Is there any way to disable this?
> Thanks,
> Jan
> On Thu, Sep 27, 2018 at 11:50 AM
Daniel-Constantin Mierla
> <miconda(a)gmail.com> wrote:
> Hello,
> the log message says that the dialog
was already added to the
timer.
> Do you see retransmissions of the DMQ
requests on the network
with
> ngrep/wireshark/...?
> Cheers,
> Daniel
> On 27.09.18 10:40, Jan Hazenberg
wrote:
> Hello,
> I'm trying to replicate active
dialogs using the DMQ module. I
see
> the dialogs on the other nodes but it
generates a error message
in
> the logs on all the nodes:
> Sep 27 10:17:31 sip04
/usr/sbin/kamailio[27367]: CRITICAL: dialog
> [dlg_timer.c:130]: insert_dlg_timer(): Trying to insert a bogus
dlg
> tl=0x7efdca1bebf8 tl->next=0x7efdca14cb80
tl->prev=0x7efdca14cb80
> Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog
> [dlg_dmq.c:309]: dlg_dmq_handle_msg(): Unable to insert dlg timer
> 0x7efdca1beb98 [2643:3725]
> Even with the timeout_avp option
disabled i still see the error
> messages. I tested this on kamailio 5.0.3 and 5.1.3 with the same
> results.
> With debug enabled i see the correct
data is replicated to the
other
nodes:
dlg_dmq_replicate_action(): sending serialized data