<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-7" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000066">
<tt>Hi,<br>
i thought in CUCM 6 and above, extension mobility was supported since
the database of the subscriber was read/right!<br>
<br>
Am i wrong?<br>
<br>
Cheers<br>
Anthony<br>
</tt><br>
Rakesh Kumar (IT) wrote:
<blockquote
cite="mid:810FE46AADEF62478AAB09DB687D8243101DD26A@EVSMAIL.Evalueserve.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.5726" name="GENERATOR">
<div dir="ltr" align="left"><span class="170151909-09042009"><font
color="#0000ff" face="Arial" size="2">hI,</font></span></div>
<div dir="ltr" align="left"><span class="170151909-09042009"></span> </div>
<div dir="ltr" align="left"><span class="170151909-09042009"><font
color="#0000ff" face="Arial" size="2">You will loose the following
feature :</font></span></div>
<div dir="ltr" align="left"><span class="170151909-09042009"></span> </div>
<div dir="ltr" align="left"><span class="170151909-09042009"><font
color="#0000ff" face="Arial" size="2">1. Extension mobility : user
will not be able to login and logout. Only existing user will be able
to use phone.</font></span></div>
<div dir="ltr" align="left"><span class="170151909-09042009"><font
color="#0000ff" face="Arial" size="2">2. No new phone can be
registered.</font></span></div>
<div dir="ltr" align="left"><span class="170151909-09042009"></span> </div>
<div dir="ltr" align="left"><span class="170151909-09042009"><font
color="#0000ff" face="Arial" size="2">Thanks & Regards,</font></span></div>
<div align="left"><font face="Arial" size="2"><strong>Rakesh Kumar </strong></font></div>
<div> </div>
<br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Anthony
Kouloglou<br>
<b>Sent:</b> Thursday, April 09, 2009 1:06 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a><br>
<b>Subject:</b> [cisco-voip] Subscriber capabilities in CUCM 6.1(2)<br>
</font><br>
</div>
<tt>Hi All,<br>
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?<br>
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)<br>
Is there a document describing what you ARE NOT capable of editing when
you are on Subscriber only?<br>
<br>
Regards<br>
Anthony<br>
</tt></blockquote>
</body>
</html>