Conference call problem

[xjswx]

I have a customer with an IP412. Manager 4.0.7

The problem is whenever someone, anyone, on any phone tries to do a conference call - once the third party is connected, the call quality drops to where you can barely hear each other and there appears to be static on the call.

Otherwise, first and second party can talk normally and first party and third party can talk normally. It's only when the 3 calls are joined together when this happens. And it only happens when the conference call is initiated from their switch.

The system is using 2 T1's(1 PRI and 1 T1)
It is grounded, each module.

Tonight I plan on upgrading it to 4.0.14.

Any ideas?

 

[kwing112000]

Do you know if the calls are going out on the T1 or the PRI? It sounds like they go out on the T1. That may be the issue. try changing it to the PRI and then test.

 

[xjswx]

Actually,I am on site right now.

The customer is only using the PRI.

I just upgraded the system to 4.0.14, no change. I think this is going to take some tweaking with the telco vendor. I cannot see any reason in the office programming that would cause this. like I said, it all works fine, unless you initiate a conference call.

 

[kwing112000]

Are you clocking off of the PRI? Maybe a timing issue.

 

[xjswx]

The upgrade didn't work.

I also tested by using the conference feature internally, had the same problem, just not as bad. I think when conference calls are being made, the problem is there, but when and external conference call is made, the T1 amplifies it.

I suggested they change out the IP 412 main module and see how that goes. Might be a bad processor.

 

[ProviderReborn]

Try disabling the AGC see if that helps.

ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.

 

[SuperJenks]

We had a couple of situations where the conference chip burned out on 412's. Apparantly at one point, this was a some what common problem. We had the same symptoms you are experiencing, severe static, some times the system would just reboot. Turned the system monitor traces we provided to our distributer show the problem and was immediately Identified. I would try replacing it as you suggested or open up a case with avaya.