<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html >
<head>
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
font-face
{font-family:Tahoma;}
font-face
{font-family:Verdana;}
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.EmailStyle18
{
font-family:Verdana;
color:navy;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<DIV id=idOWAReplyText71738 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Thanks to all for the
advice</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>will set it up in the lab and also test
during our staging before rolling out</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>erik erasmus</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Chris Soechting
[mailto:Chris@INXi.com]<BR><B>Sent:</B> Wed 2006-10-18 04:03<BR><B>To:</B> Erik
Erasmus (E); Kris Seraphine<BR><B>Cc:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> RE: [cisco-voip] attendant console
in remote SRST branch<BR></FONT><BR></DIV>
<DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">In SRST you can use
translation profiles or alias to make the pilot (1000) to ring to a
phone.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Regards,</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT> </P>
<DIV>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Chris Soechting, CCIE
#15782 (Voice), CCSP</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Sr. Consulting
Engineer</SPAN></FONT></P>
<P class=MsoNormal><B><FONT face=Verdana color=navy size=1><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">INX
Inc - InterNetwork Experts</SPAN></FONT></B><FONT face=Verdana color=navy
size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">7600 N. Capital of TX
Highway</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Bldg B, Ste
120</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Austin</SPAN></FONT><FONT
face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">, TX
78731</SPAN></FONT><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">IP Phone:
512.795.7107</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Fax:
512.795.8844</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Email: <A
title=mailto:chris@inxi.com href="mailto:chris@inxi.com"><FONT color=navy><SPAN
style="COLOR: navy"><SPAN title=mailto:chris@inxi.com><SPAN
title=mailto:chris@inxi.com><SPAN title=mailto:chris@inxi.com><SPAN
title=mailto:chris@inxi.com>chris@inxi.com</SPAN></SPAN></SPAN></FONT></SPAN></SPAN></A></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana">Web: <A
title=http://www.inxi.com/ href="http://www.inxi.com/"><FONT color=navy><SPAN
style="COLOR: navy"><SPAN title=http://www.inxi.com/><SPAN
title=http://www.inxi.com/><SPAN title=http://www.inxi.com/><SPAN
title=http://www.inxi.com/>www.inxi.com</SPAN></SPAN></SPAN></FONT></SPAN></SPAN></A></SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face=Verdana color=navy size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT> </P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Erik Erasmus
(E)<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, October 17,
2006 8:40 PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Kris
Seraphine<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B>
cisco-voip@puck.nether.net<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [cisco-voip] attendant console
in remote SRST branch</SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<DIV id=idOWAReplyText45007>
<DIV>
<P class=MsoNormal><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Hi
Kris</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">just to make sure - when you have a
wan outage currently - do you have no coverage for the main number at the remote
site or not?</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">My concern is that because the
attendant uses a pilot number and ac users to cover for the main number that
wehn the wan is down the pilot number is gone and inbound calls will just not
route into the site because unless I can do something under srst to create the
DN of the main number - it will not exist really. Or am I missing something.
Where I did attendant console before at an HQ - I used as an example a pilot of
say 1000 for the main number of 431 1000 etc with ac1 user on extension 5001 and
ac2 user on 5002 as an example and then in the huntgroup use ac1 and ac2 as
members but 1000 does not appear on their phones.</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">If one uses the same concept at a
remote branch things will work like you say when wan is up but when wan is down
that pilot does not exist and one also don't have that DN (the main
pilot) on any phone so when srst configures it does not know about the main
number for that site leaving us with a problem. I can live with not have the
line states etc etc while the wan is down - just need to somehow make the main
number reachable even if it is just on a single IP
phone.</SPAN></FONT></P></DIV></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Kris
Seraphine [mailto:baryonyx5@gmail.com]<BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wed 2006-10-18 03:08<BR><B><SPAN
style="FONT-WEIGHT: bold">To:</SPAN></B> Erik Erasmus (E)<BR><B><SPAN
style="FONT-WEIGHT: bold">Cc:</SPAN></B> cisco-voip@puck.nether.net<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [cisco-voip] attendant console
in remote SRST branch</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face="Times New Roman"
size=3><SPAN style="FONT-SIZE: 12pt">Hi<BR><BR>I support a centralized cluster
with 40+ remote sites; all of which use the attendant console. Most of the
sites are under 50 phones but a few are over 100. The AC works pretty well
over the WAN. The only problem that we occasionaly have that I attribute to the
WAN is that the parked calls sometimes don't disappear when a call is picked
up. The only reason I attribute this to a latency issue is that I don't
see this issue with any of my other customers who use the AC on the same LAN as
the servers. This customer currently doesn't prioritize the AC flows but
that's in the works. <BR><BR>As for WAN outages, you're pretty much out of
luck. There's no way to preserve the AC functionality when the
connection to the server is down. You can route calls to dns using alias
commands but line state, drag and drop will be gone. <BR><BR>The MPLS WAN has
been very reliable with maybe 6-7 outages during work hours over the last 12
months between all the sites. Only one outage was extended and that was
the local telco's fault. </SPAN></FONT></P>
<DIV>
<P class=MsoNormal><SPAN class=gmailquote><FONT face="Times New Roman"
size=3><SPAN style="FONT-SIZE: 12pt">On 10/17/06, <B><SPAN
style="FONT-WEIGHT: bold">Erik Erasmus (E)</SPAN></B> <<A
href="mailto:ErasmuE4@telkom.co.za">ErasmuE4@telkom.co.za</A>>
wrote:</SPAN></FONT></SPAN> </P>
<DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Hi</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I have a scenario now where a
customer wants to run an HQ and 5 remote branches with a centralised call
manager cluster and the branches on srst across an MPLS IP wan. The problem is I
have never proven the viability of running the attendant console that comes with
ccm 4-1/4-2 across a wan link. Looking for practical advise on workable
solutions.</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">1. Has anyone deployed this with
success - how heavy is attendant console on bandwidth (assume we can
configure propper QoS) - say 100 users in the branch</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">2. My biggest concern is what
happens when the branch goes into srst mode. How does one then cover for the
pilot number for the specific site. Normally when doing it at an HQ I use the
approach where I create the ac1, ac2 users etc for attendants and the pilot dn
is the main number like xxx 1000 etc. if one now configure ac users for the
remote site/s each with their own pilot number things should work Ok with the
WAN up but not sure how to provide cover for the main number when srst kicks in
and the entire attendant solution goes down. The branch can not afford having
the main pilot number un attended during a wan failure.</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Not using attendant console also
poses a problem for a big branch with 100 plus users with high inbound call
volumes to the site. Simply putting a 7960 down with an expansion module or two
will not do it. The attendants won't be able to effectively handle high call
volumes, no drag and drop, now line state info etc.</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Any advise will be
appreciated.</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">erik erasmus</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Telkom SA
Ltd</SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV></DIV>
<TABLE class=MsoNormalTable cellPadding=0 border=0>
<TR>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; BACKGROUND: white; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt"
bgColor=white>
<P class=MsoNormal><FONT face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>This
e-mail and its contents are subject to the Telkom SA Limited<BR>e-mail
legal notice available at <BR><A
href="http://www.telkom.co.za/TelkomEMailLegalNotice.PDF"
target=_blank>http://www.telkom.co.za/TelkomEMailLegalNotice.PDF</A><BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</SPAN></FONT></P></TD></TR></TABLE>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face="Times New Roman"
size=3><SPAN
style="FONT-SIZE: 12pt"><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR></SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><BR><BR clear=all><BR>-- <BR>kris seraphine
</SPAN></FONT></P></DIV></DIV></DIV>
</body>
</html>
<table><tr><td bgcolor=#ffffff><font color=#000000>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
This e-mail and its contents are subject to the Telkom SA Limited<br>
e-mail legal notice available at <br>
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
</font></td></tr></table>
<table><tr><td bgcolor=#ffffff><font color=#000000>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
This e-mail and its contents are subject to the Telkom SA Limited<br>
e-mail legal notice available at <br>
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
</font></td></tr></table>