• Save
Migrating to open unified communication
Upcoming SlideShare
Loading in...5
×
 

Migrating to open unified communication

on

  • 1,264 views

A short presentation with some things I've discovered being important in Unified Communication migration projects I've worked on. Presentation from the Uninett Telephony Workshop in Trondheim, May ...

A short presentation with some things I've discovered being important in Unified Communication migration projects I've worked on. Presentation from the Uninett Telephony Workshop in Trondheim, May 2012.

Statistics

Views

Total Views
1,264
Views on SlideShare
1,260
Embed Views
4

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 4

http://plantronics.sociview.com 2
http://edvina.net 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Migrating to open unified communication Migrating to open unified communication Presentation Transcript

  • Moving to a newUC Platform10 slides, 10 bullets to remember Olle E. Johansson * oej@edvina.net * Twitter oej © Copyright Edvina AB, Sollentuna, Sweden 2012. All rights reserved.
  • 1. Learn and lab• Install an Asterisk or a FreeSwitch server• Buy a few different SIP phones• Get SIP softphones• Understand the technology• Attend this workshop!
  • 2. Take inventory• Check all the PSTN lines • PRI lines, internal leased lines, alarms, elevator phones, POS connections• Check current equipment • Protocol support in phones and PBX • SIP or PRI trunks in the PBX
  • 3. List used PBX services• List all current PBX services• Try to understand who uses what• Who depends on what?• Find the set that few uses and no one depends on and delete it from the list• Focus on the important services and the new services - presence and IM
  • 4. Identities and name space• The address plan is important• Phone numbers and internal numbers• SIP addresses • Both email-style and numeric• Domain management• LDAP/AD integration
  • 5. Migrate, migrate• Is there a way to connect the new platform with the old• Can you migrate department by department or in some other way?• Synch this with cancellation of old lines
  • 6. Integrate• There is a cost of managing user accounts and groups• Try to build on the IT-departments systems • LDAP, Active Directory• The new system needs to be managed like any server - SNMP, Nagios/Icinga and other management platforms
  • 7. Work with open source• Build local knowledge and participate• Or hire consultants and have them contribute back• Consider sharing source code with fellow institutions• Look at it from a professional and financial point of view.
  • 8. Security• Consider which type of security that is needed for every use case• CDRs and logs contains important information• Some phone calls or networks may need security
  • 9. Integrate cell phones• Mobile extensions• Control PBX services in smart phones• Callback, dial-through• Wifi/Softphone reachability when travelling• Make cell phone users part of the platform
  • 10. It’s all about marketing• You have to sell the new platform to the users • Before you do the switch!• Let them be part of the project• Make it easy to learn and use• This requires hard work
  • Most important:Use open standard protocols to get interoperability in your realtime communications network. AVOID VENDOR LOCK-INS.