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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Phone Manager Login Problems

Status
Not open for further replies.

ChrisHerrington

Technical User
Oct 14, 2009
31
US
OK lets get this out of the way first. I do not want an answer of a networking problem on this. I have a new IP500 running the newest version of IP Manager. I have phone mananger 4.2.25. It does not matter what operating system what firewall etc, when I try to connect to phone manager it tells me unable to connect. I was able to connect each machine one time for just under 2 minutes, then they never worked again. I do not have any problems with the phones they work like a champ. This is a 1000 base network with a brand new cisco POE switch. There are no loops everything is using cat 6 cable. When discovering the IP500 it finds that just fine all the time from any machine, I do not get this message until I try to click on the user list. This is not a DNS issue the email notification is working fine. I have exchange 2007, Windows server 2008, and XP, Vista, Windows 7 machines they all work with everything else except for the phone manager lite/pro software. Does anyone have anything they think might be relevent to add other than a networking issue? Thanks BTW my IP office manager workstation is Windows 7 and with some work I was able to make it work just fine even though it is not supported. System Status is the only thing that does not work from this PC.
 
Now we are getting somewhere. That worked but not really a solution. My network worked fine before the IP 500. There is no way I can go without a gateway on my network. I am using DHCP (Windows 2008) for all my clients. Is there a work around with the IP500 Config to allow me to keep my gateway?
 
I think you have a tftp issue, it's sending but not responding.

it think it should respond with

<---SendAckMsg(0)

So something is blocking port 69 like tlpeter mentioned.

Try to type the line below in a cmd prompt;

Tftp -i XXX.XXX.XXX.XXX get nasystem/nasystem/who_is avaya.txt

Then look in the C:\Documents and Settings\user> for Avaya.txt

If it's not there then tftp is blocked in the network.

Avaya_Red.gif

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

Dain Bramaged
___________________________________________
 
There are no internal ports blocked on my network. And no gateway works like a champ.
 
what ip address/subnet/gateway do you get from the DCHP server?

Avaya_Red.gif

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

Dain Bramaged
___________________________________________
 
The gateway is the router. gateway is 192.168.1.200, ip office 192.168.1.254, manager pc 192.168.1.252, dhcp 192.168.1.3
 
Check the default gateway on the switch.

Avaya_Red.gif

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

Dain Bramaged
___________________________________________
 
have seen ip500 with crappy lan ports before. Phone manager and voicemail was unstable at best but manager changes were fine.

Could you swap lan1 with lan2 to test?

See what my brain does when it's not thinking about phones.
 
The switch is unmanaged. I am using the Cisco Router for my firewall and NAT. Everything inside nat is wide open no port blocking at all.

 
I did that already even had both ports plugged it with DHCP off on both of them it doesn't seem to matter. I am just curious what the gateway would have to do with being able to see the ip500 and it is intermittent. Sometimes I can get connected.
 
I guess I could always put a route in the router to rout port 69 always to my ip office. I am not sure why in the world I should ever have to do this but I will try it.
 
well I did not want anyone thinking ai had two dhcp server going one on the IP500 and a windows server 2008
 
ok it is fixed for some reason the phone manager software uses the gateway to go look for the IP 500 to connect to tftp when it reached the router(Gateway) it did not know where to go from there. I put a static tcp route in the router to point the gateway for anything using port 69 back to the IP 500 and now it works just fine.

Yeah guys I know it was a network issue but not near the kind of network issue I was worried about getting solutions to like latency and crap like that. This was a routing problem not caused by my network but more because the IP 500 uses the gateway for something and cannot directly contact the ip address of the UNIT.

I wish someone could explain this to me because I would think it would use the ip address always. There is never any need for it to use the gateway to look for an internal ip address.

Thanks for all the help.
I appreceiate everyone that posted response.

Bas1234 thanks for getting me to look in the right location. Removing the gateway would have been the last thing that I would have tried.
 
Ok I spoke too soon it only worked on a few pc they were all xp. Now I am out of options.
 

Do you have an iproute in the ip500 to the gateway ?
You could try to add one like this:

0.0.0.0
0.0.0.0
192.168.1.200


Personaly i would change the ipaddress of the ipoffice and not let it have a 254 address !!!




ACS - Implement 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!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top