Re: [rtcweb] WebRTC-SIP interop: and why SDES-SRTP is a need

[Roman Shpount <[e-mail]>]

On Wed, Apr 4, 2012 at 8:42 PM, jesse <[e-mail]> wrote:

>
> On Apr 4, 2012 10:24 AM, "Roman Shpount" <[e-mail]> wrote:
> >
> > My assumption is that IP phones will migrate to WebRTC effectively
> eliminating SIP in end user devices.
>
> That is your academic assumption, why does IT department need to spend
> extra money to either desert or upgrade its existing SIP devices without
> substantial gain? After all, tons of users are still using window xp.
>
> Backward capability is a key to the success of new technology.
>
Please note the <sarcasm> tags.

On the more serious note, very few SIP end points offer working ICE
support. So, in a large sense, interop with them is not an option. Out of
the ones that do support ICE and SRTP, very few are actually connected
directly to a public internet. Most of them are connected to some sort of
PBX or an IP PBX type service. So, in reality you do not need to bridge
every IP phone with WebRTC. If a few PBX and hosted centrex vendors will
add support for WebRTC required features, we will get compatibility with
existing end points. To support the rest you will need to deploy some sort
of gateway.

In my personal opinion, tons of users use XP due to the fact that never MS
OS versions do not offer a significant reason to upgrade, while introducing
enough usability and operational issues to create a significant upgrade
hurdle (I am trying to be politically correct here). WebRTC enabled end
points, on the other hand, will offer significant benefits to traditional
SIP phones, since they will allow development of higher quality integrated
real time communications services. I hope this will drive a much quicker
standard adoption.
_____________
Roman Shpount