Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

One way audio after a few minutes after upgrade.

Status
Not open for further replies.

Bas1234

Technical User
Dec 10, 2007
6,760
NL
Hello all,

We have 5 IP500's in a SCN all had 4.2.4 without any problems. After upgrading to 5.0.8 One way audio after a few minutes occurred. Downgrading back to 4.2.4 resolved it. Now they have put the error on caveats;

CQ89037 | One way talk path occurs in the middle of a conversation across the SCN | 5.0.8 | SP_RELEASE_1Q10_5.0 | 3-Available

Did an upgrade to 5.0.15 and the error came back. We used G.711 as a system wide codec, DMP ticked on the user but untick (also tried to turn DMP on)on the SCN links. The setup was still in a "Star" network.

Any of you who have the same problem?

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
PS.

It's Internal, external and over SCN. The network is a 1 Gig fibre network, only one of the 5 has a VPN connection.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
odd we had the opposite recently. v4.2 switch decided to only offer one way speech.

upgraded to 5 sorted it!

we have around 8 switches in star mpls.

perhaps there is a bug in the vcm firmware in v5?
 
We have 2 customers with more then 4 IP500 running 5.0.15. (new install). And 2 customers like above the one who where "upgraded" to 5.0.15 And they have the one way audio problem.

I think the upgrade causes this but i'm not sure, and i'm not (yet) going to re-program those IP500's.

Let see how it goes today, upgraded 1 site (4 IP500) to 4.2.23.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Try the mesh network and see what happens.
It must be related to something else.
If an upgrade does do this you could try a factory default and shoot back a config (use the reset button)



ACSS - SME (IP Office)
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Try the default method that tlpeter suggests and also, delete and recreate the IP lines. I'm pretty sure I've seen corruption caused by v4 to v5 upgrades on IP lines (you'll notice that the configuration form in Manager looks different).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top