There seems to be a lot of confusion with this question. Let me try to
re-phrase what Romel was asking and provide an answer.
UA1 sends an INVITE to UA2. UA2 sends an INVITE with the Call-ID from UA1's
INVITE without sending a response.
In this scenario, UA1 would probably reject the UA2's INVITE because it is
still waiting for it's INVITE to complete.
What UA2 should do is send a final response accepting the INVITE, wait for
UA1 to send the ACK. Then UA2 can issue a re-INVITE with that same Call-ID.
(-:bob
Robert F. Penfield
Chief Software Architect
Acme Packet, Inc.
130 New Boston Street
Woburn, MA 01801
[EMAIL PROTECTED]
----- Original Message -----
From: "Ajit Kalele" <[EMAIL PROTECTED]>
To: "Romel Khan" <[EMAIL PROTECTED]>
Cc: "'Ramachandran Iyer'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Friday, August 10, 2001 2:41 AM
Subject: Re: [Sip-implementors] re-invite
> Romal,
>
> Please see my comments inline ..
>
> > But UAS can send re-invite.
>
> No. INVITE is a request, that can only be generated by a UAC.
>
> > I am not talking about sending responses from UAS.
>
> UASs are there only for accepting requests & generating responses.
>
> > Let me repharse what I asked:
> > WHAT WILL HAPPEN IF UAS RESPONDS BACK WITH AN INVITE WITH THE SAME
CALL_ID
> > after the UAS receives an Invite from an UAC.
>
> So if a UAC sends out a re-INVITE immediately after receiving an INVITE,
to
> the same client, it should respond with a 4xx response.
>
> >From a UA's point of view, the Call FSM is in CALLING state(after it has
sent
> INVITE & is awaiting a response), and it receives a call invitation from
the
> same UA it has initiated a call with. Even if the Call-Id is same (though
it
> is globaly unique) the Call FSM is NOT expecting an re-INVITE message, so
> either the request will be dropped or an error response will be generated.
>
> Also, I am not able to think of a scenarion where a UA needs to be in two
> calls with the same other UA, so the UAS should generate a 4xx response.
>
> Regards
> - Ajit
>
> *********************************************************
> Disclaimer
>
> This message (including any attachments) contains
> confidential information intended for a specific
> individual and purpose, and is protected by law.
> If you are not the intended recipient, you should
> delete this message and are hereby notified that
> any disclosure, copying, or distribution of this
> message, or the taking of any action based on it,
> is strictly prohibited.
>
> *********************************************************
> Visit us at http://www.mahindrabt.com
>
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
