<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:blue;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>So the ‘CME as SRST’ is just
setting the CME as the ‘Default Gateway’ or ‘SRST Reference’
in the UCM Device Pool. I was anticipating more back end communication between
CME and UC to create a real dynamic SRST environment. That makes a lot more
sense to me now.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> kmarus@gmail.com
[mailto:kmarus@gmail.com] <b><span style='font-weight:bold'>On Behalf Of </span></b>kmarus<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, December 18, 2008
9:23 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Michael Thompson<br>
<b><span style='font-weight:bold'>Cc:</span></b> Kelemen Zoltan;
cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip]
CME-in-SRST mode with Extension Mobility</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>There is 2 ways to setup
cme-as-srst. The way that learns the extensions like normal srst does, will not
work with ext mobility. But, if you use the static setup (prebuild extensions),
where you create all your ephone and ephone-dn's,then yes, it's fine. In that
scenario though, you will need to maintain phone configs in two places, the
cme-as-srst, and the cm. You will also need to create the EM device profiles in
both places. <br>
<br>
More info see here: <a
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmesrst.html#wp1011673">http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmesrst.html#wp1011673</a><br>
<br clear=all>
<br>
<br>
<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Wed, Dec 17, 2008 at 9:54 PM, Michael Thompson <<a
href="mailto:mthompson729@gmail.com">mthompson729@gmail.com</a>> wrote:<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>good to know, didn't realize that the new 4.3 / 7.0 CME supported EM.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>do you have a link on
what the distinctions are between SRST and CME for fallback? from a
coding standpoint, there isn't a ton of difference. if you can take full
advantage of things like hunts, etc of CME...that's pretty damn cool in my book.<o:p></o:p></span></font></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Wed, Dec 17, 2008 at 9:33 AM, Kelemen Zoltan <<a
href="mailto:keli@carocomp.ro" target="_blank">keli@carocomp.ro</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>for the record, later CME versions (4.3+, I think) do support EM, and
CME can be used instead of SRST for SRST-like fallback nowadays :)<br>
<br>
I haven't done this, so this isn't more than my 2c, but I think on one hand it
should work, but on the other, users, etc. will all need to be locally defined
and thus it has a good probability of confusing the users when the system goes
into fallback mode. The previously logged-in phones might fall back to a logout
profile, usernames/passwords are certainly not synchronized between the two
systems, so they might not match, and so on.<br>
<br>
regards,<br>
Zoltan<br>
<br>
Michael Thompson wrote:<o:p></o:p></span></font></p>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><br>
I don't think that CME supports EM in any form.<br>
<br>
What is it you mean by CME in SRST?<br>
<br>
------------------------------------------------------------------------<br>
<br>
*From:* <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
*On Behalf Of *kmarus<br>
*Sent:* Tuesday, December 16, 2008 7:42 PM<br>
*To:* <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
*Subject:* [cisco-voip] CME-in-SRST mode with Extension Mobility<br>
<br>
I am aware that Unified SRST does not support Extension Mobility however does
CME in SRST fallback mode support Extension Mobility?<br>
<br>
<br>
Thanks in advance.<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
cisco-voip mailing list <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>