The idea is to use SRV records instead of a dispatcher by setting $rd to a DNS
SRV enabled host (with all hosts having the same prio and weight).
Problem is that when authentication is required the flow is as follows (with 2
hosts):
1:
UAC INVITE/REGISTER -> LB -> SIP0
SIP0 401 with nonce1 challenge -> LB -> UAC
UAC ACK -> LB -> SIP0
2:
UAC INVITE/REGISTER with nonce1 response -> LB -> SIP1
SIP1 401 with nonce2 challenge -> LB -> UAC
UACK ACK -> LB -> SIP1
3:
UAC INVITE/REGISTER with nonce2 response -> LB -> SIP0
SIP0 401 with nonce1 challenge -> LB -> UAC
UACK ACK -> LB -> SIP0
4: UAC either gives up or goes to 2
Using the dispatcher module this can be solved by using a hash over either
from/to/request URI. I can't find any hints for forcing the dialog to 1
backend.
BTW the idea is to keep the loadbalancing proxy as simple/stupid as possible
(no db), the backends have a shared db.
Hi all,
I have searched for instructions for setting up Kamailio with mediaproxy instead of rtpproxy, but I can't find anything. I found only OpenSips pages and some other outdated examples but the config does not apply very much on kamailio.cfg.
As much as I could find out is that Kamailio natively supports rtpproxy and OpenSips works with mediaproxy.
Is there any solution for Kamailio with mediaproxy?
Thank you!
Filip
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi,
What are the statistics that should be used to monitor a Kamailio instance?
I currently looked at shmem_real_used_size, shmem_used_size,
dialogs_active_dialogs. However, I'm looking for other statistics that
represent the load on the instance.
Thanks,
Mickael
I'm looking at the dlg_ontimeout function [dlg_handlers.c:1369] and I
understand the code, the DLGCB_EXPIRED callbacks are not called when the
send_bye parameter is set to 1.
I'm looking at the block 1399-1408.
From: Mickael Marrache [mailto:mickaelmarrache@gmail.com]
Sent: Wednesday, April 15, 2015 3:53 PM
To: sr-users(a)lists.sip-router.org
Subject: RE: No CDR is written when dialog timeouts
I also confirm the cdr_on_create() [acc_cdr.c:718] function is called since
I can see the debug statement "dialog '%p' created!".
From: Mickael Marrache [mailto:mickaelmarrache@gmail.com]
Sent: Wednesday, April 15, 2015 3:48 PM
To: sr-users(a)lists.sip-router.org
Subject: No CDR is written when dialog timeouts
Hi,
I'm testing the dialog timeout scenario and I see that no CDR is written.
This is my configuration:
modparam("acc", "cdr_enable", 1)
modparam("acc", "cdr_expired_dlg_enable", 1)
modparam("acc", "cdr_start_on_confirmed", 1)
modparam("acc", "cdr_log_enable", 0)
modparam("acc", "cdr_on_failed", 0)
I can confirm the cdr_on_expired() [acc_cdr.c:684] function is not called
since I don't see the debug statement "dialog '%p' expired!\n".
(I precise that CDR generation works fine for regular hangup scenario.)
Any idea what can cause the issue?
Thanks,
Mickael
Hi,
I'm looking for a way to differentiate between regular hangup and dialog
timeout.
In both case, the dialog:end event is called. Do you know which information
can I use in the event route to differentiate between the two cases?
Thanks,
Mickael
Hi,
I get the following warning when a dialog timeout occurs:
kamailio[18889]: WARNING: dialog [dlg_req_within.c:214]: bye_reply_cb():
inconsitent dlg timer data on dlg 0x7f422986e448 [3547:6673] with clid
'mycvJWgmbmOSD5XQrcStKAKoTfW12XeR' and tags
'C5mlsaZCdTmybNSYgvWr75MBxWa5hVyA' 'L1ZzszpZ1MYO6qlQQ3FYYRWQYtF4F75r'
Am I doing something wrong?
Thanks,
Mickael