Mobile Communicator presentation

| No Comments | No TrackBacks

I attended an online seminar today on Cisco's Unified Mobile Communicator, Cisco's plan to put the "unified" communications environment (corporate directory, phone, voicemail, presence, conferencing, and e-mail) all on your data/application-enabled cell phone.

You can view the product information for Unified Mobile Communicator here.

Two things make this solution unattractive.

One, it's tightly-coupled and Cisco-proprietary. It's locked in with Cisco's products--Unity unified messaging, Meeting Place, and of course Call Manager. What if I want to connect to another voicemail or e-mail server? And from what I can tell from the presentation, it's not using standard protocols such as SIP or IMAP to communicate with home base.

Two, it requires a big pile of new hardware in the datacenter to make it work. This needs to be integrated into the individual component servers (Unified Communications Manager/CallManager, Unity, MeetingPlace).

The first thing will keep Penn State away from this mobile communications solution. Penn State does not use unified messaging (our Unity setup is voicemail-only) which removes both the VM and e-mail functionality. We don't use Meeting Place. What's left then besides having voice capabilities? Yes, your cell phone already does that. Forward your VoIP phone to your cell and be mobile.

Mobile users at PSU can put together a suite of tools for their data-enabled cell devices to send and receive e-mail (POP/IMAP), instant-message (various protocols), and search the corporate directory (LDAP) but are for now without a way to tightly integrate with the campus PBX or voicemail.

No TrackBacks

TrackBack URL: https://blogs.psu.edu/mt4/mt-tb.cgi/7386

Leave a comment

March 2009

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31        

Contact Me


AIM: TNS BillS

View William Simon's profile on LinkedIn

Donate

Make a gift
Like this blog? Support education and research at Penn State by donating any amount to an area of your choice.

Subscribe

Blogroll

Disclaimer

We are Penn State, but I am not. Opinions expressed on this blog are those of the author and do not represent the opinions of The Pennsylvania State University or any division therein, including but not limited to the author's workgroup, department, administrative unit, or campus. Technologies and ideas discussed on this blog do not describe a production service unless noted.