<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2>Carlos,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2>you may use CCME instead of SRST in case of CallManager
failure. This aproach provide you more features than SRST, like hunt groups,
basic ACD, and if configured properly, entire CallManager failure can be totally
invisible for the enduser.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2>Defenetly, my recomendation is to go to the CCME SRST
Fallback support because this can provide more features than SRST. You may find
more info on:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2><A
href="http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_guide_chapter09186a00807e0566.html">http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_guide_chapter09186a00807e0566.html</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=859583500-19082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><SPAN
class=859583500-19082007></SPAN><FONT face=Arial><FONT color=#0000ff><FONT
size=2>Mladen<SPAN class=859583500-19082007></SPAN></FONT></FONT></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of
</B>CarlosOrtiz@bayviewfinancial.com<BR><B>Sent:</B> Friday, August 17, 2007
6:25 PM<BR><B>To:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> [cisco-voip]
CME vs SRST<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Can CME be used as a fallback from
Call Mgr instead of SRST? I have never thought so......but a previous admin has
a CME config on a router at a location that has the following excerpt:</FONT>
<BR><BR><FONT size=2><TT>ephone-hunt 1 sequential<BR>pilot 4700<BR>list 4739,
4740, 4743, 4744<BR>final 9XXXXXXXXXX<BR>preference 3 secondary 7<BR>timeout 16,
16, 16, 16<BR>!<BR>ephone-hunt 2 sequential<BR>pilot 4799<BR>list 4702,
4701<BR>final 9XXXXXXXXXX<BR>timeout 16, 0</TT></FONT><FONT
size=3><TT><BR></TT></FONT><BR><FONT face=sans-serif size=2>The purpose of this
config as explained by the business was when in "SRST" (I know this was CME
config) </FONT><FONT face=sans-serif color=red size=2>to route calls to a
specific DID, hunt through lines and as a last resort dial outbound to a telco
analog line with a mailbox to leave a message (important).</FONT> <BR><BR><FONT
face=sans-serif size=2>We did SRST testing for all of our locations locations
about 2 months ago and this particular location did not function at all with
this "CME" config. I have since converted them to SRST, had an outage and
their calls did work.</FONT> <BR><BR><FONT face=sans-serif size=2>The business
is claiming that this worked at one time during SRST but I am skeptical.
I am thinking that the previous admin told him it was configured but there was
no real testing done. Can anyone shed some light on this. I need to
know:</FONT> <BR><BR><FONT face=sans-serif size=2>1) Can CME be used instead of
SRST?</FONT> <BR><FONT face=sans-serif size=2>2) Can I accomplish what they want
via SRST? (see red above - I think I can with the alias command but need to
check)</FONT> <BR><BR><BR><FONT face=sans-serif size=2> Below is the full
CME config if needed.</FONT> <BR><BR><BR><FONT face=sans-serif
size=2> </FONT><FONT size=2><TT>telephony-service<BR>srst mode
auto-provision all<BR>srst dn line-mode dual<BR>max-ephones 100<BR>max-dn
200<BR>ip source-address 10.X.X.X port 2000<BR>max-conferences 8 gain -6<BR>web
admin system name X password X<BR>dn-webedit <BR>time-webedit
<BR>transfer-system full-consult<BR>!<BR>ephone-dn 1
dual-line<BR>number 4744<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 2 dual-line<BR>number
4743<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 3
dual-line<BR>number 4702<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 4 dual-line<BR>number
4745<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 5
dual-line<BR>number 4739<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 6 dual-line<BR>number
4742<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 7
dual-line<BR>number 4740<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 8 dual-line<BR>number
5539<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 9
dual-line<BR>number 4701<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 10 dual-line<BR>number
4710<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 11
dual-line<BR>number 1010<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 12 dual-line<BR>number
4703<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 13
dual-line<BR>number 1012<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 14 dual-line<BR>number
4704<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 15
dual-line<BR>number 4636<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 16 dual-line<BR>number
4705<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 17
dual-line<BR>number 4706<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone-dn 18 dual-line<BR>number
4707<BR>description XXXXXXXXXX<BR>name XXXXXXXXXX<BR>!<BR>ephone-dn 19
dual-line<BR>number 7045<BR>description XXXXXXXXXX<BR>name
XXXXXXXXXX<BR>!<BR>ephone 1<BR>mac-address 0016.4766.AB7C<BR>button
1:1<BR>!<BR>ephone 2<BR>mac-address 0015.F907.6BE1<BR>!<BR>ephone
3<BR>mac-address 000E.833C.AE08<BR>button 1:3<BR>!<BR>ephone
4<BR>mac-address 0011.5C0E.6108<BR>button 1:4<BR>!<BR>ephone
5<BR>mac-address 0015.F914.1515<BR>!<BR>ephone 6<BR>mac-address
0015.F914.0E19<BR>button 1:6<BR>!<BR>ephone 7<BR>mac-address
0015.F914.11FF<BR>button 1:7 2:15<BR>!<BR>ephone 8<BR>mac-address
0015.F914.0E4C<BR>button 1:9<BR>!<BR>ephone 9<BR>mac-address
00E0.7524.B312<BR>button 1:10<BR>!<BR>ephone 11<BR>mac-address
0015.FA0B.7202<BR>button 1:12<BR>!<BR>ephone 12<BR>mac-address
0017.9486.B302<BR>button 1:14<BR>!<BR>ephone 13<BR>mac-address
000F.2398.4524<BR>button 1:16<BR>!<BR>ephone 14<BR>mac-address
0012.0194.F685<BR>button 1:17<BR>!<BR>ephone 15<BR>mac-address
000F.2356.8144<BR>button 1:2<BR>!<BR>ephone 16<BR>mac-address
0014.A917.9FB7<BR>button 1:13 2:18<BR>!<BR>ephone-hunt 1
sequential<BR>pilot 4700<BR>list 4739, 4740, 4743, 4744<BR>final
9XXXXXXXXXX<BR>preference 3 secondary 7<BR>timeout 16, 16, 16,
16<BR>!<BR>ephone-hunt 2 sequential<BR>pilot 4799<BR>list 4702, 4701<BR>final
9XXXXXXXXXX<BR>timeout 16, 0<BR></TT></FONT><BR></BODY></HTML>