26 Feb
2007
26 Feb
'07
9:05 p.m.
Hi Michael,
as you give you the same answer as to Andy :) :
"To be honest I'm not fan of complicating my life just to support broken
stuff :)....doing dialog matching in traditional way (without using RR
stuff) is very costly and since complete, un-altered RR mirroring is
mandatory by RFC3261, I see no point of doing it different. "
I think the best approach is to force the UAC vendors to align to the
SIP specifications.
regards,
bogdan
Michel Bensoussan wrote:
Hi Bogdan
I'm agree with you, but we cannot control the UAS devices so we have
to handle the case it doesn't correctly mirror the RR header. Can we
base the dialog states on From and To headers? or Callid? I understand
the the rr_param is used for fast dialog matching (dialog README).
Checking dialog matching with headers (From, To, ...),
will consequently slowing the transaction?
Regards,
Michel.
Bogdan-Andrei Iancu wrote:
> Hi Michel,
>
> looking at the net capture, it seams that the UAS device (User-Agent:
> WLAN660-S VoIP PHONE) does not correctly mirror the RR header - it is
> removing the hdr parameters, mirroring only the URI, which is bogus.
>
> regards,
> bogdan