Avaya VM on XP Pro

[timbath]

I have a legacy Avaya Cybergear system using Voicemail running on Windows XP Pro SP3.

I recently had to change the IP address to fit a new scheme on SBS 2008. The address was 172.26.2.2 with subnet 255.255.0.0. The new address is 172.26.1.110 with subnet 255.255.255.0. I challenged the server installers of the server that this was a class B address and the subnet mask was wrong. They pointed me to a Microsoft article about SBS 2008 saying this was how it should be configured:

http://blogs.technet.com/b/sbs/archive/2008/09/16/sbs-2008-supported-networking-topology.aspx

So, I changed the LAN1 setting and IPRoute setting to 172.16.1.0 and 255.255.240.0 but now have problems with connectivity over the network - ping is erratic and voicemail has a serious echo. I have tried to revert the IP settings but this makes no difference.

Any help much appreciated. I realise best advice is to upgrade but that's not an option.

Thanks

 

[Westi]

did you change the IP address of the phone system too and if so did you change the IP route as well?

Joe W.

FHandw., ACSS

insanity is just a state of mind

 

[timbath]

Thanks for the response.

I changed the IP and subnet of the system and the IPRoute.

I have changed both back to the original settings.

 

[Westi]

try to ping the new address and see if you have a duplicate address on the network that screws it up, I had that happen before. If that is not the case then it might be the ip route

Joe W.

FHandw., ACSS

insanity is just a state of mind

 

[tlpeter]

I really do nto understand all those VMPro migration problems.
I just installed an VMPro today while the original was still running.

Changed the IP address within the IPO and saved it.
It went from the old to the new within 20 seconds.




Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

A yard full of tards

 

[Bas1234]

172.16.1.0 and 255.255.240.0 does not work in a "Network Class B" change the Subnet to 255.255.0.0 on your LAN1

IProute needs to be 0.0.0.0/0.0.0.0/172.16.X.X (X.X=Gateway)

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

Dain Bramaged
___________________________________________

 

[timbath]

172.16.1.0 and 255.255.240.0 does not work in a "Network Class B" change the Subnet to 255.255.0.0 on your LAN1IProute needs to be 0.0.0.0/0.0.0.0/172.16.X.X (X.X=Gateway)"

Tell Bill Gates as the TCP/IP stack on SBS 2008 is clearly different and does not work properly with a class B subnet!

 

[timbath]

One thing I failed to mention in the original post was that my XP machine is virtual, running on VM Ware server on the SBS 2008 box.

 

[Bas1234]

Running VMware should be no problem at all, running al lot of different customers (20 or so) on VMware using 2k3/2k8/WinXP using VMPro >4.2x

Vmware is supported by AVAYA from >6.x (could be 5.0.20), but it work and never had any issues, except a licence server is not recommended on a VMware machine because of USB/Dongle problems.

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

Dain Bramaged
___________________________________________

 

[TomMills]

It's not supported on 5.0(20) bas i checked recently. :-(

Also
"I have a legacy Avaya Cybergear system"
so what version is the voicemail?

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[timbath]

The whole problem stems from, and started with, the IP change. It has been working for 6 years previously!

 

[timbath]

I'm still having this echo problem and inconsistent ping results to my unit.

The IP address is 172.26.1.110 and subnet 255.255.255.0.

I have edited the IPRoute but each time I reboot it adds another route all by itself. So my IPRoute are:

172.16.1.0 255.255.255.0 (correct)
172.16.1.0 255.240.0.0 (added by Manager)

So it looks like the unit thinks some traffic is external to my LAN hence the network connectivity issues and manifested by voicemail echo.

Any ideas anyone... PLEASE!

 

[jamie77]

I've never seen Manager add an IP Route.

Since you have a CyberGear, are you using the the correct Argent Manager program?? Alchemys did wierd things if you used the wrong Manager.

Also remember that Alchemys need a reboot to change just about everything properly.

Jamie Green

Football is not a matter of life and death-It is far more important!!!!

 

[mattKnight]

And Alchemy applications were never supported on XP - real or virtual, SP1, SP2 or SP3.

The first step would be to build decidcated win2k box and install VM on that and then see if your issue continues.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[tlpeter]

Or ditch it and buy an ip500v2


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[timbath]

mattknight

Thank you. However, it all worked fine but we had to change the subnet to comply with SBS 2008 and that is what made everything go wrong. I think the only option is to switch the whole network to a class C address scheme.