Re: [rtcweb] We are moving beyond the assumptions on which O/A is based

[Ted Hardie <[e-mail]>]

On Tue, May 14, 2013 at 11:34 AM, Paul Kyzivat <[e-mail]>wrote:

Certainly. If the web server supporting the browser


I assume by this you meant the javascript application; it's possible for
the web server to support the CLUE semantics but a particular client not to
(e.g. a mobile client connecting to the server).


> does't support clue then this isn't going to result in a clue call. But
> that would only come up for *received* calls, and receiving such a call via
> rtcweb depends on having an app that is at least addressable by a clue
> client. That means it must have a sip address. If so, then at least it will
> probably be able to connect as a "legacy" sip device.
>
>
So, just to confirm my understanding, in this scenario, the webrtc client
is sitting in an open screen somewhere, connected to a web server (it could
be headless, but bare with me).  When a CLUE conference starts that the
webserver believes is of interest to the webrtc client it uses the existing
connection to notify it and give it conference details.  Is that right so
far?

If that is the case, I'm not sure what you mean by "must have a SIP
address".  Can you clarify this?

My concern it that it be *possible* to do this with rtcweb, preferably
> obscure gateway code.
>
>
I'm assuming that a "without" is missing here, but can you confirm?

regards,

Ted


>         Thanks,
>         Paul
>
>