[Serusers] non-unique call id problem
Klaus Darilion
klaus.mailinglists at pernau.at
Sun Jun 27 22:44:01 CEST 2004
This should not happen:
Rfc3261: 8.1.1.4
In a new request created by a UAC outside of any dialog, the Call-ID
header field MUST be selected by the UAC as a globally unique
identifier over space and time unless overridden by method-specific
behavior. All SIP UAs must have a means to guarantee that the Call-
ID header fields they produce will not be inadvertently generated by
any other UA.
Maybe your accounting problem can be solved by using not only the
call-id as identifier, but also the to-tag and the from-tag. These
should also change for new dialogs.
regards,
klaus
Greg Fausak wrote:
> What I mean is that the call-id is used for multiple dialogs.
> It isn't unique for different calls. So, if my UAC makes a call, hangs up,
> then makes another call, both calls have the same call-id, the
> ACC accounting is showing that the same call ID is being used over
> and over. Is this a UAC bug?
>
> ---greg
>
> On Jun 27, 2004, at 4:42 AM, Andrei Pelinescu-Onciul wrote:
>
>> On Jun 26, 2004 at 18:22, Greg Fausak <greg at addabrand.com> wrote:
>>
>>> I am seeing non-unique call IDs from a UA.
>>> SHould I reject a call if the Call-ID is not unique? Has
>>> anyone else messed with this? It is a big accounting problem!
>>
>>
>> What do you mean by non-unique call id? Is it changing during the call?
>> (the call id is supposed to change for each new call)
>>
>>
>> Andrei
>>
>>
> Greg Fausak
> www.AddaBrand.com
> (US) 469-546-1265
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
More information about the sr-users
mailing list