sundance-communications.com/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems IP Office 412

Has anyone run into any issues on a IP Office 412 with VM Pro where the customer gets garbled VM messages. They are hooked into their network. As soon as I bypass the network and hook it directly from the IPO to the VM server everything clears up.

I believe its a situation with their network, but can anyone recommend what I can do to help them fix this problem?

Before someone asks this already has been upgraded to the latest software on both the IPO and VM Pro. This has been an issue from the install, (installed by an independent person). We are now stuck on trying to solve the mystery.

Thanks,

Dave

Odds are that it IS their network. Since it sounds like you don't take care of their network, your best bet would be to connect the voicemail server directly to the IPO on one interface(using a different subnet) and if they actually use network functions(phone manager,voip,etc)then connect the other interface to their network.

Yeap, we always run a network sniffer program on the customer LAN before the sale to make sure of the integrity of their network.
Then we always run a dedicated PC for VM.

Are these all IP Phones? Hope not. IPOFFICEGUY is correct. I always connect the VM Pro PC directly to the IPO.

Good Luck.

doubled,
The VMPRO working properly when the NIC is patched directly to the 412 port proves there is no issue with the VMPRO, or IPO. There is nothing that can be done in all probability with the Avaya equipment to remedy the situation since this proves the issue is not with the IPO in all probability.

That said, we will need to see the network design to even begin to help fix the network issues.

I am dealing with a similar situation, and have made the following discoveries, however have yet been able to solve the problem.

The ip office only communicates with the switch at 100half without causing port errors, however whenever you are running at half duplex, then you are asking for collisions.

The ip office does not send DSCP bits to and from the voicemail even though it is set to. This makes QOS on the network level difficult.

I have hooked the voicemail directly up to the ip office on the second NIC of the IP office via crossover cable, and created it's own subnet. I verified with Wireshark that the data is using this direct connection.

I can resolve the problem by unplugging the lan from the first net card, however then phone manager software does not work.

The system is running the latest software

Voicemails played directly on the voicemail server are clean

The same voicemails played over a digital phone are garbled

Is there possibly a processor issue on the ip office where it is getting bogged down by all of the phone manager connections from the LAN, and therefore it is lacking the power to process the voip voicemail on the other interface? There are approx 100 phone manager clients connecting?

While there is not a ton, I do see a slightly larger then normal number of broadcasts coming into the first nic from the office LAN Could this be bogging the processor down?

Could there be a codec transcoding problem from the voicemail back to the ip office?

You need to manually set the nic and the switch port to 100 full. (see the manual).

Is the IPO on the same LAN as all the PC's running Phone manager?

I do not see the documentation (for the 412) on the web site you listed. I have been told by other Avaya techs that the port in the 412 will ONLY run 100 half. Do you know the procedure to change the port speed/duplex. I can do it on all other hardware (switch, and voicemail)

The phone manager software is all on the local lan that is directly connected to the first net card on the 412. The Voicemail is directly connected to the second nic on the 412 via a crossover cable

jlumby,
Find a qualified tech on the IPO, and they should be able to handle this for you. I would not recomend you try to deal with this yourself, as the information you have been provided about the IPO is very poor.

I'm an ass from the start. I always don't have the right answer. I have some good idea's

Make the application new on it's own computer. Save the copy and re install it.

Sure, network stuff is a huge variable for the application.

I would never ever install the application on a computer that other's have any use for. Trust me.
Just don't plug this stuff into your network.

Get a fresh computer for no bullshit. Besides,If your going outlay this type of application for the customer then get a new cleared hard drive and re-install xp microheadic problems.


Then if the application persists we start looking at the customer T-1 provider or the rest of the slow speed boggled internet.

As if it's used as, " Ive got a new IP phone system" I'm at the end of technology and my unified communications found the guy in the cave called..USAMA BIN LADEN with a cell phone. Send me a bottle with a note in it.

Without It's true intended use. Then tell me the true problems of the network without Ip phones?

If you don't have a bunch of IT guys hanging around in a cave for your new fortune 10,000 corp. Take a close look of what you bought regarding the savings expectations.

Sorry for the rant.