Re: [rtcweb] Agenda requests for Atlanta meeting

[Cullen Jennings <[e-mail]>]

On Oct 8, 2012, at 18:56 , Roman Shpount <[e-mail]> wrote:

> On Mon, Oct 8, 2012 at 9:41 PM, Cullen Jennings <[e-mail]> wrote:
> 
> On Oct 8, 2012, at 18:31 , Roman Shpount <[e-mail]> wrote:
> 
> > On Mon, Oct 8, 2012 at 9:26 PM, Cullen Jennings (fluffy) <[e-mail]> wrote:
> >
> > Well, what's the end user experience you're trying to achieve  - lets say we are talking about audio. Do you want to play the first one or the last one? If you want to bridge them into a party line, this is probably not how you want the SIP side to happen.
> >
> >
> > This is still serial forking. Imagine the following scenario: You are calling a phone number, you dial first provider who starts playing a dial tone then uses an UPDATE to connect you to a media server to play an announcement after which your call goes to voice mail (another dialog and another SDP). This is all fairly legal and not unusual for SIP scenarios. Nothing to do with party lines.
> 
> Ok, serial forking with early media seems like it should work. Seems like the browser would make the offer, that gateway turned into SIP invite that then went to sequential forking proxy that send sent the invite to UA A. UA A returns a 180 that gets mapped to PRANSWER, the proxy then forks to UA B that sends a 200 on a different dialog that gets mapped to answer.
> 
>  The only issue is the there is currently no way to map an UPDATE received in the early dialog to WebRTC API calls. I am probably OK with it not being handled until the cloning is implemented, but this shows that PRANSWER is not very useful even for the serial forking.
> 

How do you think this work in a SIP only system? Lets say A sends the invite with offer to proxy that forks to B. Then B does 180Rel followed by an update. Then the proxy forks to C on a new dialog. Do you think C can send send early media to A and A is actually going to play it? And what if B use still sending media - it that case A will be getting media from B and C at the same time. Do you have devices that do that?  Most people just seem to make voicemail work fine without needing to introduce this type of complexity. If you know what you want A to do in this case, I think we can figure out how to make that happen - there's been a lot of discussion about what a SIP device receiving early media from two places should do and there was never any really great answer other than don't do that.  

The meta issue here is thought this is serial forking at the signalling level in SIP, it is actually parallel forking from a SDP / media  point of view. 

The case that started this all was use UPDATE in awaited RFC says is not allowed. I'm not arguing there are not cases where clone would be useful, but I do think all the voicemail systems I am familiar with would work fine with the the simple PRANSWER.