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. <br><br><div><span class="gmail_quote">
On 10/17/06, <b class="gmail_sendername">Erik Erasmus (E)</b> <<a href="mailto:ErasmuE4@telkom.co.za">ErasmuE4@telkom.co.za</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><font color="#000000" face="Arial" size="2">Hi</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">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.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">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</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">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.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">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.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">Any advise will be appreciated.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">erik erasmus</font></div>
<div><font face="Arial" size="2">Telkom SA Ltd</font></div>
<div><font face="Arial" size="2"></font> </div></div>
<table><tbody><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>
<a href="http://www.telkom.co.za/TelkomEMailLegalNotice.PDF" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.telkom.co.za/TelkomEMailLegalNotice.PDF</a><br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
</font></td></tr></tbody></table>
<br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br></blockquote></div><br><br clear="all"><br>-- <br>kris seraphine