[cisco-voip] Subscriber capabilities in CUCM 6.1(2)
Wes Sisk
wsisk at cisco.com
Thu Apr 9 09:35:05 EDT 2009
That part is actually covered in the SRND, recommends SLB feature on
switches:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/cmapps.html#wp1043648
/wes
On Thursday, April 09, 2009 9:32:26 AM, Ryan Ratliff
<rratliff at cisco.com> wrote:
> The trick to getting EM to works is that your service URL can't point
> at the publisher. Since you can't change the value for the service
> URL with the publisher down you have to plan for this contingency
> ahead of time. I'm sure there are a number of people on this list
> that have built in redundancy for web services.
>
> -Ryan
>
> On Apr 9, 2009, at 9:05 AM, Wes Sisk wrote:
>
> in 6.x with publisher offline there is a new feature called 'user
> facing features' that should allow normal user activities. user
> facing features include:
> Call Forward All (CFA)
> Message Waiting Indication (MWI)
> Privacy Enable/Disable
> Do Not Disturb Enable/Disable (DND)
> Extension Mobility Login (EM)
> Monitor (for future use, currently no updates at the user level)
> Hunt Group Logout
> Device Mobility
> CTI CAPF status for end users and application users
> Credential authentication
> CCMAdmin, CCMUser, and AXL will be hendered with the publisher offline.
>
> There is another significant change in 6.x that may benefit other
> features. For the first time in the history of CM all features
> default to reading from the local database. Historically all services
> read from publisher db by default. The local database on subscribers
> are now writable for user facing features. Local subscriber database
> is also the default read location for all features except AXL,
> CCMAdmin, CCMUser.
>
> I looked for this in documentation both the release notes and SRND and
> did not find it clearly stated. there is vague mention of extension
> mobility when publisher is down in the release notes for CM6.0.
>
> Regards,
> Wes
>
>
> On Thursday, April 09, 2009 3:35:54 AM, Anthony Kouloglou
> <akoul at dataways.gr> wrote:
>> Hi All,
>> in a 6.1(2) cluster with one Publisher and one Subscriber, in case of
>> publisher failure what are the main features that i lose?
>> In older versions i remember that nothing was changeable, but now i
>> know that many things are editable (like CFA on extensions, or
>> extension mobility)
>> Is there a document describing what you ARE NOT capable of editing
>> when you are on Subscriber only?
>>
>> Regards
>> Anthony
>> _______________________________________________ cisco-voip mailing
>> list cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list