November 2009 Archives

Training: Unity Connection 7.x day 2

By Bill on November 4, 2009 3:45 PM | No Comments | No TrackBacks
Directory Integration Options

  • Stand-alone (no integration)
  • Communications Manager's directory (uses AXL)
  • MS Active Directory
  • Unofficially... looks like it could be connected to other LDAP directories
  • LDAP can be used for authentication
Monitoring:  SNMP; nothing new there really.

Backup/Restore:  no more awful Exchange backups, of course.  Selective restore available if we wanted to restore individual users.

COBRAS migrates from Unity to Unity Connection:  users, settings, mailbox contents, handlers.  Cisco is continually improving this migration tool.  Export from Unity is simple; importing that data to Connection may involve a lot of resolution conflict.  Start with a clean Unity system for less importing pain.  

End-user Web Features

  • Unity assistant - per-user settings manager, like Communications Manager User Options site
  • Unity inbox - view, listen to, forward, reply, etc. to voice messages.  Play messages through the web browser or download to PC.  
  • Call transfer rules - set up your own auto-attendant.  Looks like a support nightmare.
For the ITS VoIP and voicemail offering, we could potentially proxy these web features like we currently do Communications Manager User Options.  The first two features in the list above could be really useful.  

Training: Implementing Cisco Unity Connection 7.x

By Bill on November 3, 2009 8:27 AM | No Comments | No TrackBacks

Day 1 of 4. What's Cisco Unity Connection all about?

  • Unity for those who don't want MS Exchange integration
  • Cisco's current (Linux-based) platform.  No Windows components for Connection 7.x
  • Hot redundancy/load balancing rather than failover
  • Modern features:  e-mail delivery of VM, visual voicemail, more
  • Calling search space/partitioning allows functional segmenting of the voice mail system
Licensing
  • Workspace licensing.  Per-phone cost is "slightly more" (instructor's words) than just phone licensing (a la carte) for use on Comms. Manager.  Avoiding WSL will probably cost more in the long run.
PBX Integration

  • CUCM (Skinny), SIP trunk to any SIP system, PIMG for Avaya/Nortel systems
  • Multiple integrations to same Unity system.  Several phone systems could participate in same Unity--CUCM, OpenSER, Avaya, CUCM over SIP trunk...
Installation

  • Identical to current Communications Manager installation
  • Connection is pre-configured to start most services by default, unlike CUCM which has most turned off by default
  • Use Realtime Monitoring Tool for server/cluster analysis, diagnostics, troubleshooting, stats
Administration looks like a familiar mix of Communications Manager 6.x screens and Unity 4.x screens.  Finishing off the day by setting up the lab.

« September 2009 | Main Index | Archives

Search


November 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          

Recent Posts

Recent Comments

  • Mark McKillen: Hi Bill, I love your 7906 with SIP working... I read more
  • Bill: I have also experienced the same with only getting low read more
  • NATHAN CORAOR: Hi Bill, I see there's no new XMeeting, but I'm read more
  • Richard Rauscher: My wife purchased a candlestick telephone for me a few read more
  • Bill: Are you using the 8.4.x firmware on your 7961? The read more
  • Peter: Do you know how to get the line text to read more
  • Chris: any chance you could email me the config you used read more
  • Bill: ITS has a soft phone project underway. It is being read more
  • Richard Rauscher: Does anyone at PSU use a soft phone? Can someone read more
  • Chris Kauffman: Blog away this week. I will be reading for certain. read more

Tag Cloud

Archives

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

VoIP News

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.