VM Pro clipping 1

[jtierney]

3.1 2901 on a 406V2 connected to a WIN XP Server running 3.1 (15) VM Pro. NIC set to 100/H. Server is plugged into LAN port 7 on 406. Customer LAN connected to port 8.

The .wavs are fine when played using media player on a PC/laptop. When messages/greetings/Auto Att's accessed via IPO, the caller hears drops in the conversation, almost like a pause. No static or completely lost words. Problem continues when customer LAN is removed from scenario.

Any thoughts?

JT

 

[bwilch]

Are you running a virus scanner on the PC?

 

[JeSTeROCK]

Sounds like the server specs aren't good enough or virus scan as bwilch said

 

[kwing112000]

I had the same problem on 3.0(59) with VM Pro 3.0(17). I replaced the PC and problem went Away. I have seen so mony issues with Dell Dimension PC's. The Dimension is really a home line of PC.

 

[intrigrant]

IPO 406V2 has 100Mb full duplex ports so why setting the NIC to 100Mb Half duplex? Change it and see if it helps.

 

[JayNEC]

The ports on the 406 are autonegotiating.
Sometimes two autonegotiating devices can "float" between settings. By hard setting a port you nail it down.

However, because in this case - one end is autonegotiating. If the other end is set to full duplex, the auto end will always fall to half duplex.

Then you end up with a duplex mismatch and all kinds of problems - collisions etc.

 

[intrigrant]

Quote:
"Sometimes two autonegotiating devices can "float" between settings. By hard setting a port you nail it down.
However, because in this case - one end is autonegotiating. If the other end is set to full duplex, the auto end will always fall to half duplex."

Why would a auto-end always fallback to halfduplex?
Sounds strange and not very logical to me...

Nevertheless, i have never had problems with VM Pro and speech quality like this and i have never changed the NIC settings, always left it automatic.

 

[JayNEC]

The auto end will try to negotiate the duplex setting with the other end. Because the other end is nailed, it won't respond. The auto end then must assume that it's connected to a dumb device that can't negotiate (such as a hub). So it therefore falls back to half.

A quick search pulls this up:

http://e2epi.internet2.edu/case-studies/SC02/DuplexMismatch.html

Avaya's implementation guide also states this...

 

[JayNEC]

Here's a much better article:

http://www.cites.uiuc.edu/network/autosense.html

 

[intrigrant]

Thanks, thats good to know.

 

[derry163]

Just upgraded the vm to 3.0.19 (from 2.0.17 I beleive) and 406 to 3.0.69. Same exact clipping problem. PC specs are P-4 1.8 256 ram. Did min specs go up from the 2.0x days?



Also when phone is in DND and you make an outside call, if it doesn't start ringing right away (like calling a cell phone or what not) the studder dial tone comes back untill the call starts to ring....weird huh? If your not in DND calls go out normaly. Did not have this problem with 3.0.59.

 

[tlpeter]

For VMlite you need P4 2.4 at least
You need more speed

 

[ronCTS]

We had the same problem with a 2.1 version on a 412. Avaya advised us to changing the power setting to not go on stand by, not use screen saver, or any of the power save options. We also made sure to use 100/H like you have it. There is also a batch file that can be installed to open the ports on the XP filewall for the Avaya software. If you don't have it, turn off the XP firewall to see if that solves the problem. You may want to see if there is any Anti Virus software running on the PC also. I believe that we also uninstall and reinstall the VM Pro software. (Make sure to back it up before uninstalling it.) After all of that, the problem stopped. It may have been the reinstallion of the software that have fixed it but XP firewall has given us many other problems.

 

[crumthwacket]

Easy on the stars Sizbut! The star should go to Tech1958 from an earlier post, not Superikey - and you already gave one to Tech1958 for this.

 

[crumthwacket]

Sorry - earlier post belongs on the "List of No User Features" thread

 

[IPGuru]

I had similar problems with VM pro on a site that had upgraded from alchemy
the cause turned out to be old alchemy apps (phone manager) attempting to download the cfg from the IPO & failing
this caused exesive network trafic to the IPO & prevented the Voicemail trafic.
check your network for anything trying to do a tftp transfer from the IPO
also make sure the ipo is connected to a switch not a hub to reduce data collisions (connecting the VM PC direct to the IPO can also help)