<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3199" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#000000 size=2>I have a customer on 4-2-3 sr3 with central cluster and one branch both sides using cisco attendant consoles. Had issues with the attendants for months now. before we were on sr3 we had calls stuck in the attendant Qs. Cisco promissed this will be fixed in sr3 and we loaded it -- will wait and see -- lasted a couple of days now. We also had a problem at the branch attendants. Randomly - once a day or sometimes twice a day or some times not at all the attendants receives a call from the pstn on the voice gateway PRIs but the caller and the called attendant can not hear each other for several seconds - eventually the voice stream come through and they talk. The attendant then needs to treansfer the caller to an Ip phone in the branch and this alos fails - the transfer just doesn't want to happen. When we reset tcd service and cti manager things start working again. I am going to open a tac case again but not that hopeful so looking for ideas. Have already checked:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>wan - 256 Kbps MPLS circuit from central ccm cluster to branch - looks good and not highly utilised</FONT></DIV>
<DIV><FONT face=Arial size=2>QoS - wan and lan looks good</FONT></DIV>
<DIV><FONT face=Arial size=2>call manager config looks fine because 99.9% of time things work correctly</FONT></DIV>
<DIV><FONT face=Arial size=2>attendant PCs and apps fine and latest 4-2-3 sr 3 builds</FONT></DIV>
<DIV><FONT face=Arial size=2>happens at all three remote attendats so no one PC or port etc problem</FONT></DIV>
<DIV><FONT face=Arial size=2>lan switches look fine</FONT></DIV>
<DIV><FONT face=Arial size=2>voice gateway - configured like many others and clocking looks fine</FONT></DIV>
<DIV><FONT face=Arial size=2> remote branch runs MOH multicast from flash</FONT></DIV>
<DIV> </DIV>
<DIV>as said will open a tac case but can not rely on this only - with stuck in Q it took several weeks before cisco admitted it was a bug.</DIV>
<DIV> </DIV>
<DIV>Unforunately the customer does not have sasu or ucss so can not upgrade to anything and with call centres etc hanging of the CCM cluster not something one would just tackle lightly one afternoon. Keeping sharp objects away from myself because I am getting depressed </DIV>
<DIV> </DIV>
<DIV>any ideas </DIV></BODY></HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
This e-mail is subject to the Telkom SA electronic communication legal notice, available at :<br>
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
</font></td></tr></table>