Re: [rtcweb] SIP MUST NOT be used in browser?[was RE: Remote recording - RTC-Web client acting as SIPREC session recording client]

[Igor Faynberg <[e-mail]>]

Well,  maybe we should take it off-line--I will be happy to explain a 
few things in October. Just some in-line answers:

On 9/8/2011 10:30 AM, Harald Alvestrand wrote:
>> I thought I had already proposed a subset: INVITE, SUBSCRIBE/NOTIFY, 
>> and REFER.
> ...
>
> That's the commands. What are the parameters?

My proposal is to populate the methods with parameters in the JavaScript 
application.
>
> As I've said before, unless I've misunderstood what SUBSCRIBE/NOTIFY 
> are for (I think they are just for presence), 

No, no, no! Not just for presence, although it can be used for presence. 
  These precious methods came from PINT, how could you forget this! 
  They allow the client to subscribe for an event at the server and then 
receive notifications asynchrously.  This specific feature cannot be 
implemented using HTTP (just as INVITE cannot).  We used them in PINT 
pretty much to enable the client to learn when PSTN call is 
disconnected, but the SIP group had found many other uses later.

Again, my objective is to ensure that SIP (with all its bell and 
whistles) can be supported by a JS application.  I am just starting to 
study the code kindly sent my way a few minuts ago, but when I am 
convinced that this can be done based on WebSocket alone, I will stop 
harping on this.

Igor