Re: Multiple m= lines

Thanks for quick response.

On Mon, Feb 20, 2012 at 2:42 PM, Saúl Ibarra Corretgé
<[email protected]>wrote:

> Hi,
>
> On Feb 20, 2012, at 9:10 AM, venu Y wrote:
>
> > Hi all,
> >
> > Case: Client A wants to offer two file transfers(two m= lines) using
> MSRP in an SIP session with client B.
> >
> > Client B, on receiving the offer, displays the two file names with
> options (Accept/Reject) to user and waits for his response.
> >
> > If the user, accepts first file and didn't inform any thing about second
> file... then how should Client B should respond?
> >
>
> What do you mean by "didn't inform anything"? How does that 200 OK look
> like?
>
> > 1. Should he force the user to give response to all offers at a time..
> >
>
> Of course, when you send the 200 OK all offered streams must be present in
> the answer, if you want to reject a stream just set the port to 0.
>
> > 2. Should he wait for a stipulated time, if no response is received from
> user, then he should opt for a default configured behaviour.
> >
> > 3. Is there any provision in offer/answer model, to inform the other
> party that..
> >
> > one m= line status is ready and other m= line decision is in pending...
> >
>
> I don't think that's possible. What you could do, for example, is learn
> the information (filename, hash, size) on the stream you don't want to
> accept right now, reject it and send a re-INVITE later, adding a new stream
> with that data and direction 'recvonly', thus *requesting* that the remote
> party sends you that file.
>
>
> Regards,
>
> --
> Saúl Ibarra Corretgé
> AG Projects
>
>
>
>


-- 
With Regards
Venu
93484 89945
[email protected]

_______________________________________________
Simple mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/simple