<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Redundancy with CUMI API</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=" />
  <subtitle>Redundancy with CUMI API</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=</id>
  <updated>2013-05-24T13:44:31Z</updated>
  <dc:date>2013-05-24T13:44:31Z</dc:date>
  <entry>
    <title>Redundancy with CUMI API</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11640561" />
    <author>
      <name>Kenneth Wong</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11640561</id>
    <updated>2013-02-06T22:20:32Z</updated>
    <published>2013-02-06T22:20:32Z</published>
    <summary type="html">I am using an application that utilized the CUMI API to read, play, send voicemail messages from Unity Connection cluster. The application itself didn't implement any logic for redundancy in case of failure.
Is there anyway to implement some kinds of redundant logic outside of the application? For example, front end the Unity Connection cluster by a load balancer or special configuration done inside Unity Connection.

Thanks,
Ken</summary>
    <dc:creator>Kenneth Wong</dc:creator>
    <dc:date>2013-02-06T22:20:32Z</dc:date>
  </entry>
</feed>

