[Kamailio-Users] In-dialog request correlation without loose routing?

[Ovidiu Sas]

On Thu, Oct 16, 2008 at 12:06 AM, Alex Balashov
<abalashov at evaristesys.com> wrote:
> Ovidiu Sas wrote:
>>
>> On Thu, Oct 16, 2008 at 12:02 AM, Alex Balashov
>> <abalashov at evaristesys.com> wrote:
>>>
>>> Ovidiu Sas wrote:
>>>>
>>>> On Wed, Oct 15, 2008 at 11:46 PM, Alex Balashov
>>>> <abalashov at evaristesys.com> wrote:
>>>>>
>>>>> Ovidiu Sas wrote:
>>>>>>
>>>>>> On Wed, Oct 15, 2008 at 10:25 PM, Alex Balashov
>>>>>> <abalashov at evaristesys.com> wrote:
>>>>>>>
>>>>>>> Also, is there a way to get the dialog module to match subsequent
>>>>>>> in-dialog requests (i.e. re-INVITEs, ACKs, BYEs) without using the
>>>>>>> dialog correlator field that gets stamped into the Route: header, and
>>>>>>> therefore requiring the use of loose_route() to read and consume?
>>>>>>>
>>>>>>> I thought that switching the matching mode to pure SIP attributes
>>>>>>> only
>>>>>>> would do the trick, but it doesn't.  They won't match.
>>>>>>
>>>>>> I'm using the dialog module  in match mode 2:
>>>>>> modparam("dialog", "dlg_match_mode", 2)
>>>>>> and all my in dialog requests are matched.
>>>>>>
>>>>>> How do you know that you don't have a match?
>>>>>
>>>>> Because the profile count stays the same based on $fU and increases
>>>>> with
>>>>> every call, and doesn't get torn down when the dialogs end.
>>>>>
>>>> Is the BYE going through your server?
>>>> I don't have this issue.
>>>
>>> Yes.
>>>
>> Enable debug logs and check what's going on when the BYE is received.
>
> I did.  The debug logs from the dialog module, even with maximum verbosity
> turned on, are not very insightful.  The dialog is not correlated.
>
Post your config and the trace of a bad call (ngrep + kamailio logs).