Hey Phillip,
you probably forgot to keep the mailing list in CC, I'll do that for you.
On 19.09.2011 08:43, Phillman25 Kyriacou wrote:
So you are saying that before, you called dlg_manage() on INVITEs only but now, you need that function on both INVITE and BYE/CANCEL messages?
That'd still qualify as a bug as the trigger to tracking the dialog (i.e., dlg_manage()) is required only once. After that, the dialog module makes sure that all dialog-related messages are properly processed. The only thing that's necessary for sequential requests to be tracked correctly is a call to loose_route() on such messages.
If you are sure that your Kamailio configuration didn't change between 3.1.2 and 3.1.5 w.r.t. dialog tracking or anything that could affect it, I'd be willing to take a closer look at this issue (giving you can provide me with more information on your scenario, like call flow examples or similar).
Cheers,
--Timo
Hey Timo
Thanks for your email.
Yes dlg_manage(); has to now be called on INVITE and BYE/CANCEL messages. Where would i have to call loose_route()? Only on INVITE? My configuration did not change between 3.1.2 and 3.1.5.
Call flow example: ==============
Cisco PGW ===> Kamailio 3.1.5 ===> VOIP PROVIDER or ASTERISK PABX
The below is my configuration.
# MANAGE ALL DIALOGS #============================= ====================== if (is_method("INVITE")) { if(is_method("INVITE") && !has_totag()) { $dlg_ctx(timeout_route) = 12; $dlg_ctx(timeout_bye) = 1; }
dlg_manage();
}
if(is_method("BYE|CANCEL"))
{
dlg_manage();
Please let me know if you need anything else.
Thanks Phillip
On Mon, Sep 19, 2011 at 11:47 AM, Timo Reimann timo.reimann@1und1.dewrote:
-
Phillman25 Kyriacou -
Timo Reimann