16 Oct
2008
16 Oct
'08
9:31 p.m.
The cookie attribute is not used at all in mode 2. Inspect your
traffic and you will see that there are no rr coockes and the dialog
matching is working ok (in mode 2).
The record-route mechanism is used as a _hook_ by the dialog module to
intercept in dialog requests. I don't know how to put this better in
words ...
Hope that this clarifies your dialog matching issue.
So ... the dlg_match_mode works as advertised in the doc as long as
you have a proper implementation of the record rote mechanism.
For mode 0 and 1 you will have cookies in the Record-Route headers.
For mode 2 you will have no cookies in the Record-Route headers and
the matching will still work.
Regards,
Ovidiu Sas
On Thu, Oct 16, 2008 at 1:58 PM, Alex Balashov
<abalashov(a)evaristesys.com> wrote:
Yep. That was the conclusion I came to as well; even though
dlg_match_mode insinuates that the cookie attribute is optional,
implying there are other ways to match subsequent requests as well,
it is actually not.
On Thu, October 16, 2008 1:45 pm, Ovidiu Sas wrote:
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (706) 338-8599
That was
the topic of my original post: how to correlate dialogs purely
based on SIP attributes without the use of loose-routing.
short answer: you can't (and the matching method doesn't matter).
proper loose-routing is a must.