Yes, you are right - it does say that. Indeed the case is illegal.
My point is tht I don't understand why one would keep state of *calls*
independently of *dialogs* when there is no useful correlation between
different dialogs that share the same callid?
BUT, for whatever reason, I guess you ar
I think we cannot infer from rfc...just based on most of the implementations
We check a received message based on the dialog-id and not the call-id.
As in your case FTag changed it is not matching so it should be taken as new
call.
But I did see a text in 3261:
8.1.1.4
All SIP UAs must have a me
RFC 3261 does say the call-id has to be spatially and temporally unique.
How can we draw the inference from the RFC that a UA must accept a
call-id, for a new INVITE from another UA, that could only be generated
by it ?
-Original Message-
From: Kanumuri, Sreeram [mailto:[EMAIL PROTECTED]
I agree with Paul
I think the call must not be rejected.
As per 3261 we identify incoming message to be part of the existing Call with
the dialog-id. But not with the Call-id.
There can be some implementations which might use Call-id as the handle f
billing/monitoring purposes. It's up to the
Arunachalam Venkatraman (arunvenk) wrote:
> The sequence of processing a received message at a SIP UA ia to identify
> the call, then the dialog within the call and then the transaction
> within the dialog.
> If the call is found, then an existing dialog must be found. If the
> from-tag is change
The sequence of processing a received message at a SIP UA ia to identify
the call, then the dialog within the call and then the transaction
within the dialog.
If the call is found, then an existing dialog must be found. If the
from-tag is changed, that would not occur.
The UA should reject the INVI
On Wed, 2008-10-29 at 08:07 -0700, KASTURI Narayanan (kasnaray) wrote:
> Hi ,
>
> I have a question on a specific behavior seen with a Proxy, the behavior
> is as follows.
>
> UACProxy
> |---Invite(req-URI:A, callid:1, Ftag=1)->|
> |
Hi ,
I have a question on a specific behavior seen with a Proxy, the behavior
is as follows.
UACProxy
|---Invite(req-URI:A, callid:1, Ftag=1)->|
||
|