Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)

[Randell Jesup <[e-mail]>]

On 9/15/2011 10:34 AM, Roman Shpount wrote:
> The only potential problem with mobile applications and javascript 
> based signaling code is the effect of maintaining registrations for 
> long periods of time while waiting for a call on battery life and 
> network utilization. A regular SIP library can be designed is such a 
> way that the device will go into sleep mode and will wake up when a 
> SIP packet is received. JavaScript will need to open a connection to a 
> server and send ping messages at regular, fairly short, intervals, 
> that will cause device to wake up every time ping message needs to be 
> sent and to consume both power and network capacity. Such 
> applications, running for the long periods of time can seriously 
> decrease battery lifetime. On the other hand, doing this during an 
> active call has a negligible effect on both power consumption or 
> network utilization, since device is already running and sending media.

+1

Any suggested solutions, other than "require (native) SIP"?   (Since 
SIP-in-JS would I assume fall into the case above.)

-- 
Randell Jesup
[e-mail]