Speaking Engagements & Private Workshops - Get Dean Bubley to present or chair your event

Need an experienced, provocative & influential telecoms keynote speaker, moderator/chair or workshop facilitator?
To discuss Dean Bubley's appearance at a specific event, contact information AT disruptive-analysis DOT com

Thursday, March 29, 2007

RIM risks marginalising itself in enterprise-controlled comms

Interesting to see that RIM has announced a new set of APIs for its Java developer environment. While there's a bunch of stuff in there which is obviously useful like the multimedia side, there's something conspicuously absent - support for SIP, via the JSR-180 Java API.

Assuming it's not lurking somewhere else in the depths of the release's specifications, this seems to put RIM at a serious disadvantage for developers looking to innovate communications applications within the IP domain, such as hooking up to enterprises' IP-PBXs or assorted Internet-based and enterprise applications.

I don't think I'll be alone in suggesting that SIP's omission will have been heavily influenced by the more paranoid and backward-looking of RIM's operator partners.

It's interesting to contrast this with the hugely pro-SIP attitude of Nokia's E-series and N-series groups, as well as Windows Mobile manufacturers. As far as I can see, this should limit RIMs attractiveness to the growing swarm of enterprise FMC systems providers, and their operator partners.

Looks like a missed chance to me.


Chinese Circus said...

Given operator resistance to naked SIP usage by enterprise workers, why do the Nokia E/N series groups not affected by operator pressure?

Peter J. Cranstone said...

It's all about the tools to make the "Ark" more comfortable. It's a big mistake to ignore SIP - but you know why they did.

Paul Golding said...

Currently, Blackberries don't support HTTP either - you need the BES as a proxy, which is why a lot of cool BB apps don't work on the ironically-named "Internet edition", like the potentially cool Gmail app.

Anonymous said...

Operator pressue is likely a partial reason for exclusion, but a more likely reason is their acquisition of Ascendent Systems last year. Based on the presentations and messaging coming out of the BlackBerry WES event last year it seems fairly certain that they will be releasing an enterprise-mobility voice integration solution (essentially a voice equivalent to their email solution). Alos keep in mind that the RIM general technology philisopy is to support standard protocols on the server side but used optimized proprietary protocols over-the-air... the proprietary OTA stuff is their secret sauce.