Question about GS trks.

[DaVinici]

I have a r3v6 w/ the std gs trks.....problem is on outbound
calls..when the called party answers there is a 1.5 second
delay before they can here me...
We just changed from copper wire to a ti channel bank for the GS trks...still same problem. any Ideas.

 

[HmmG3]

I had the exact same problem with some Loop Start trunks. After some testing, I noticed the mute sound was when the Tone/Clock board (TN2182) was connected to the trunk. After replacing the Tone/Clock board, the problem went away. Since this was done less then an hour ago, I can't say with 100% certainty that this was the issue. I'll post again if the problem resumes.

 

[DaVinici]

thanks for your input. I think this situation has been going on for a long time. The customer thinks it is part of
the way the system works.

 

[HmmG3]

Sorry, I spoke too soon. Two days later I got an E-mail from the site saying the problem is still there (but not for every call). Back to troubleshooting.

 

[DaVinici]

Don't sound like a 2182 tone clock card would create the situation. There is probably a setting somewhere in the
system parms that needs a change. I do know that its not the GS trks causing the 1 second delay....just on outbound
calls do I hear the delay....go figure.

 

[1a22ip]

Its been a log time since I worked with GS trks. One question I have is if answer supervision is set right. Also answer supervision timeout is at 0.

Like I said It's been a long time
Ed

1a2 to ip I seen it all

 

[DaVinici]

I didn't install the switch....I have not looked at any of the settings. I will check it out next week...thankd for the input

 

[HmmG3]

After a quick chat with the an Avaya Software Specialist, I finally got this problem resolved at one of my sites. He recommeneded trying the first two things first (which didn't work in my case):
1. Set the Cut-Through setting to Yes in the trunk group properties.
2. If that doesn't work, change the trunk type to wats.

Finally, check to see if "Answer Supervision by Call Classifier" is set to Yes under the customer options. Ours was and once it was turned off by Avaya, the problem went away. Why it took several months for this to pop up is beyond me, but it was the problem.