Hi Shane,
dialog_ng started as a prototype by us quite a while ago to form the basis of dialogs in our IMS implementation using Kamailio. We took quite a lot from the existing dialog module at the time and then built the additional functionality on top. There were some things (like dlg_manage) that we did not move across.... and this is bad.... so I apologise.
Right now to get a dialog recorded you need to define a flag in the modparam: modparam("dialog_ng", "dlg_flag", 10)
And then when you want to track a dlg do something like:
if (is_method("INVITE")) { setflag(10); ... }
We have had a lot of other work to focus on and haven't spent too much time on dialog_ng but we will certainly put some effort into making it easier to use and more complete.
Cheers Jason
On Thu, Feb 5, 2015 at 8:03 PM, Shane Harrison Shane.Harrison@imgtec.com wrote:
Thanks Daniel - that clarity helps. Apologies if I should have been able to glean that from the docs - I just didn't see it in my reading. FYI, dialog-ng has deprecated the dlg_mange() function.
Can anybody who has used or involved in writing the dialog-ng module shed some light on what the new mechanism is for creating an early dialog structure?
Cheers and thanks Shane
From: sr-users [sr-users-bounces@lists.sip-router.org] on behalf of Daniel-Constantin Mierla [miconda@gmail.com] Sent: 06 February 2015 00:02 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Using dialog_ng
Hello,
I haven't used the dialog_ng module, but (as expected based on the dialog module) if you only set the FLT_DIALOG flag, then the dialog is created when calling t_relay(). The dialog module has dlg_manage() function which creates the dialog immediately, maybe that's in dialog_ng as well.
Cheers, Daniel
On 04/02/15 05:28, Shane Harrison wrote:
Hi all,
I think the lack of response to my previous thread is probably because
it was too complicated. I have now narrowed my problem down after further archive readings .
I am trying to use the dialog_ng module along with the
ims_charging_module. Upon reception of an INVITE, a call to the Ro_CCR() from the request_route script is made. That function does a check that the dialog record exists (binds to dialog module and does a "get_dlg(msg)" call) - this fails i.e. dialog is not found.
Running kamailio 4.2.2 and relevant sections of kamailio.cfg are: modparam("dialog_ng", "dlg_flag", FLT_DIALOG) modparam("dialog_ng", "timeout_avp", "$avp(DLG_TIMEOUT_AVP)") modparam("dialog_ng", "detect_spirals", 1) modparam("dialog_ng", "profiles_no_value", "orig ; term")
request_route { # NAT detection route(NATDETECT);
# Set DLG flag to track dialogs using dialog2 if (!is_method("REGISTER|SUBSCRIBE")) setflag(FLT_DIALOG); # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); if (is_method("INVITE")) { set_dlg_profile("orig"); Ro_CCR("CHARGING_CCR_REPLY", "orig", "SCUR", "","30","CCR_location");
}So my question is, "should the above logic create a dialog record on the
initial INVITE?" and if yes then "what possible reasons might there be for the Ro_CCR() function not be able to detect it exists?"
Cheers Shane Harrison
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users