BCM 50 to CS 1000 speech path timing issue

[telecom116]

Setting up a new BCM 50 with IP trunks to connect to a CS 1000 4.5 with Signalling server. We have local POTS lines coming in to the BCM 50 that we use forwarding to a central ACD queue on the CS 1000. The problem we are experiencing is after the agent answers the call, and transfers the call back to the BCM 50, the outside caller cannot hear to the BCM 50 user for 23 seconds; then 17 seconds later the inside caller can finally hear the outside caller.

The ACD agent can even do a non-blind transfer and can talk to the inside caller prior to pressing the <CONNECT> key and we still experience the same timing issues with the call. Any ideas what might be happening? Nortel was experiencing "high call volume" last night and couldn't even get a ticket open.

 

[telecom116]

I think I found the problem. The DCH on the CS 1000 did not have TAT in the RCAP. Set the setting and are having no problems at this time.

 

[dkoby]

You may also want to make sure the timing is in sync between the BCM50 and the signalling server.

 

[telecom116]

For some reason our speech path timing issue has come back this afternoon, for no apparent reason. Check that TAT was still on on both ends and it is.

dkoby, my BCM 50 timing is NTP off of a stratum 3 source; the Sig Server is not centrally timed; can you give me more info on why this should affect TAT?

Also, can someone with a similar mixed CS1000/BCM network give me the RCAP on the CS side?

 

[3Sixty]

What patches have you applied on the BCM 50 I know there is a parch regarding CS 1000 I just can not remember if it is only for the SRG.

Marshall

http://www.nortelsupport.net

 

[telecom116]

Patches sort of make sense now. After our vendor called ETAS they found that the patches were up to date on the call server, but no patches were installed on the signalling server. Some patches were for speech path issues, along with some QoS and jitter.

 

[telecom116]

Update on the speech path problems between a CS1000 and BCM50

1 - no patches on the Sig Server and MC32 (see above)

2 - Vendor hadn't installed major patches on the BCM50 (the 'ol, "I assumed someone else had already done it, so I didn't check on it" problem)

After these patches were installed, speech path issues were resolved, however, if a customer that came in on a BCM50 analog trunk, IP to the CS1000, and was transferred back to the BCM50, they did not receive ringback. Problem fixed by some kind of "private, hidden" patch, I believe to the CS1000 platform.