V3.1 [65] - Pretty sure it's a V1, but I'm not certain. Is there an easy way to tell?
Just trying to log in to the switch and load the config. so I can make some changes. That's when it gives me the error. Was working fine until last Friday when another user was in the switch working on button programming. Ever since then, no luck getting in.
I spoke with my Avaya dealer and they suggested rebooting the switch to see if that fixes it. I'll give that a try this evening.
Correct - enter the password, click OK, see the "Receiving ... from 00eb..., wait about 30 seconds, then see the "C:\Program Files\Avaya\IP Office\Manager\xxxxx.cfg not received OK" message in the status bar.
Any way to verify that? The person who was in the switch last on Friday afternoon swears up and down that the only changes they made were to phone button configurations.
Before you go any further with this I suggest you take copies of the .fcg and .bak files from the Manager folders on yours and PC you collegue was working on. Rename the files also to save any confusion.
Then download Snadboys Revelation v2.
With that you should be able to look under the stars in the System Password in each of the configs.
Look at the MOdified date of each file and start with the newest one.
Otherwise:
Try turning off your Caps lock on your PC!!!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Found the config file from Friday afternoon. Revelation shows the password as not changed. Guess we'll see what a reboot does. (CAPS lock... been there, done that.)
No firewall at all between the management server and the switch. No issues pinging the switch either, and tools like monitor and call status are working fine.
Speaking of monitor... never played with that before (I'm a Cisco phone guy, not Avaya), but when I try to get the config here's what I see in Monitor:
Call Status uses the same system password as the config.
So if that works then P/W is fine. have you tried rebooting the PC running Manager or using a different PC??
The Monitor output you see is the IPO getting the request for the config and trying to send it.
I seem to recall having a similar issues many moons ago and it was something to do with IP routes. It would fine the IPO on broadcast but couldn't send the file as IP routes were wrong.
Are you tring this from the same subnet??
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
No go. Rebooting the switch didn't fix it either. Can I force the config from Friday back down to the switch to see if maybe it can overwrite what's there?
Quick question: Should the file name I see in the tftp rquest in monitor match what I'm expecting? In monitor I see "config/'xtv~zo>", and xtv~zo is definitely not the name of my config file. Is the file corrupt on the server, or is this a normal naming convention?
Very strange. If the log is to be believed it does look like it's trying to send to the wrong place. The phone switch and the server are connected to the same switch, so that shouldn't be the issue, and there were zero network changes made on Friday when this stopped working.
I'm about out of patience with this, so I think it's time to take advantage of my service contract and let the vendor figure it out.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.