<HTML dir=ltr><HEAD><TITLE>Re: [cisco-voip] ccm 4-2 remote branch attendant console problem</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3199" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText31156 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi Justin</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Unfortunately they customer wil not budge from the fact that he wants Qing -- Can try again. For the HQ I did set up a demo for them where we use IPCC express and agents combined with the ac client and they were not even keen on this - a case of I baught it make it work. For branches - even if they give in to the IPCC express idea I can not use it because I can not allow the voice media across the wan for all attendant calls in a branch to the central IPCC express.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I will keep it in mind anyway - maybe we get (or the customer gets ) so desperate that we have no choice but to look at other alternatives like the one you mention -- thanks</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I am opening a tac case tomorrow </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>erik</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Justin Steinberg [mailto:jsteinberg@gmail.com]<BR><B>Sent:</B> Mon 2007-11-12 21:34<BR><B>To:</B> Erik Erasmus (E)<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] ccm 4-2 remote branch attendant console problem<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Does this environment absolutely require AC call queuing ? If you can<BR>get away from this need, maybe you can switch from AC hunt groups to<BR>CM hunt groups. You could still use AC software for call control,<BR>just not TCD for call routing.<BR><BR>The benefit of this is that since you're on CM4.2 you could use the<BR>hlog key to control call flow.<BR><BR>I know this doesn't directly answer your question, but it's atleast an<BR>option if it fits.<BR><BR>Justin<BR><BR>On Nov 12, 2007 2:21 PM, Erik Erasmus (E) <ErasmuE4@telkom.co.za> wrote:<BR>><BR>><BR>> I have a customer on 4-2-3 sr3 with central cluster and one branch both<BR>> sides using cisco attendant consoles. Had issues with the attendants for<BR>> months now. before we were on sr3 we had calls stuck in the attendant Qs.<BR>> Cisco promissed this will be fixed in sr3 and we loaded it -- will wait and<BR>> see -- lasted a couple of days now. We also had a problem at the branch<BR>> attendants. Randomly - once a day or sometimes twice a day or some times not<BR>> at all the attendants receives a call from the pstn on the voice gateway<BR>> PRIs but the caller and the called attendant can not hear each other for<BR>> several seconds - eventually the voice stream come through and they talk.<BR>> The attendant then needs to treansfer the caller to an Ip phone in the<BR>> branch and this alos fails - the transfer just doesn't want to happen. When<BR>> we reset tcd service and cti manager things start working again. I am going<BR>> to open a tac case again but not that hopeful so looking for ideas. Have<BR>> already checked:<BR>><BR>> wan - 256 Kbps MPLS circuit from central ccm cluster to branch - looks good<BR>> and not highly utilised<BR>> QoS - wan and lan looks good<BR>> call manager config looks fine because 99.9% of time things work correctly<BR>> attendant PCs and apps fine and latest 4-2-3 sr 3 builds<BR>> happens at all three remote attendats so no one PC or port etc problem<BR>> lan switches look fine<BR>> voice gateway - configured like many others and clocking looks fine<BR>> remote branch runs MOH multicast from flash<BR>><BR>> as said will open a tac case but can not rely on this only - with stuck in Q<BR>> it took several weeks before cisco admitted it was a bug.<BR>><BR>> Unforunately the customer does not have sasu or ucss so can not upgrade to<BR>> anything and with call centres etc hanging of the CCM cluster not something<BR>> one would just tackle lightly one afternoon. Keeping sharp objects away from<BR>> myself because I am getting depressed<BR>><BR>> any ideas<BR>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>> This e-mail is subject to the Telkom SA electronic communication legal<BR>> notice, available at :<BR>> <A href="http://www.telkom.co.za/TelkomEMailLegalNotice.PDF">http://www.telkom.co.za/TelkomEMailLegalNotice.PDF</A><BR>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>><BR>> _______________________________________________<BR>> cisco-voip mailing list<BR>> cisco-voip@puck.nether.net<BR>> <A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR></FONT></P></DIV></BODY></HTML>