Hi,
There is nothing like two callids, It is a unique identifier for the
call-leg/session. Hence it should match with the request callid.
Regards,
Satyakumar
----- Original Message -----
From: "RAVI KUMAR" <[email protected]>
To: "Iñaki Baz Castillo" <[email protected]>
Cc: <[email protected]>
Sent: Thursday, May 20, 2010 12:08 AM
Subject: Re: [Sip-implementors] Two different callID in same invite message.
Thanks for your response!
I understand call-Id should be unique for one call and 4xx should be proper
response. Does any sip rfc mention what ideally we should do if we get two
different call-id.
rgds,
Ravi
On 5/19/10, Iñaki Baz Castillo <[email protected]> wrote:
>
> 2010/5/19 RAVI KUMAR <[email protected]>:
>
> > Now my question is what should be ideal behaviour in this case ?
> >
> > 1. we should not expect two different call-ID as a part of same invite
> > message at the first point itself as callID is unique for the call? We
> can
> > say invite itself is not proper ?
>
> This is invalid. 400 should be a proper response.
>
>
> > 2. we should process the invite message and check the integrity of
> message ?
> > since we have two different call - ID as a part of same invite
> message ,we
> > should send 4xx bad request.
>
> Yes, 400. No more.
>
>
> > 3. Concatenating the call-ID is nowhere expected ? Anyother possible
> > solution?
>
> It makes no sense at all.
>
>
> --
> Iñaki Baz Castillo
> <[email protected]>
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
The information contained in this e-mail message and/or attachments to it
may
contain confidential or privileged information. If you are not the intended
recipient, any dissemination, use, review, distribution, printing or
copying of the information contained in this e-mail message and/or
attachments to it are strictly prohibited. If you have received this
communication in error, please notify us by reply e-mail immediately and
permanently delete the message and any attachments.
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
