[cisco-voip] ccm 4-2 remote branch attendant console problem

[Justin Steinberg]

Does this environment absolutely require AC call queuing ?  If you can
get away from this need, maybe you can switch from AC hunt groups to
CM hunt groups.  You could still use AC software for call control,
just not TCD for call routing.

The benefit of this is that since you're on CM4.2 you could use the
hlog key to control call flow.

I know this doesn't directly answer your question, but it's atleast an
option if it fits.

Justin

On Nov 12, 2007 2:21 PM, Erik Erasmus (E) <ErasmuE4 at telkom.co.za> wrote:
>
>
> 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:
>
> wan - 256 Kbps MPLS circuit from central ccm cluster to branch - looks good
> and not highly utilised
> QoS - wan and lan looks good
> call manager config looks fine because 99.9% of time things work correctly
> attendant PCs and apps fine and latest 4-2-3 sr 3 builds
> happens at all three remote attendats so no one PC or port etc problem
> lan switches look fine
> voice gateway - configured like many others and clocking looks fine
>  remote branch runs MOH multicast from flash
>
> 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.
>
> 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
>
> any ideas
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  This e-mail is subject to the Telkom SA electronic communication legal
> notice, available at :
>  http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>