---------- Forwarded message ---------- From: catalina oancea catalina.oancea@gmail.com Date: 2009/5/27 Subject: Re: [Kamailio-Users] ACKed dialog remains in state 3 instead of 4 To: Alex Balashov abalashov@evaristesys.com
Hi Alex, thanks for answering
From what I know the record-route header is not compulsory, and
dialog-matching can also be done using rfc dialog-matching instead of the did parameter in record-route (modparam("dialog", "dlg_match_mode", 2)). This is what I am trying to use, I don't want to use the record-route header at all.
2009/5/27 Alex Balashov abalashov@evaristesys.com:
Catalina,
Unless I am missing something, dlg_manage() does not allow you to avoid setting Record-Route; how else will the endpoints know to send sequential messages through the proxy once the dialog is established?
The purpose of dlg_manage() is to provide an alternative to setting a flag for the purpose of indicating to Kamailio that the dialog the current INVITE seeks to establish should be statefully tracked and exposed to additional user-defined dialog module functionality (profiles, statistics, etc.) and other module functionality relying on internal API callbacks from the dialog module.
modparam("dialog", "dlg_flag", 4)
route { ...
# Process initial INVITE.
if(is_method("INVITE")) { ...
setflag(4); # Track this dialog.
}
}
-- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (678) 237-1775
-
catalina oancea