Search results for query: *

An update. There is a "push to talk button" that is actually labelled HOLD on these phones. It is not a hold button so I guess I will just peel off the sticker that they placed on it.

I am installing secure 9620L PDB SIP phones and the handset has no audio. The speaker works fine but the microphone is disabled on purpose. Is there a special power requirement? If I plug in a regular 9620L phone it works fine. Any thoughts? Joe

I am installing a 4.0 with exchange 2007 back end and I am getting this error, I remember it being a password problem with an MSS back end and I have changed the password on the AD server twice and still can't get by this. Here are the last few lines of the mmrep.xml Detail Value="14:04.09...

I get this alarm whenever the MEDPRO loses connectivity with the processor( ie. firmware upgrades, patch cord swap, etc..)I know what causes it but the only way I can seem to remove it is to reset the server and that seems a bit extreme. I don't see any reference to it in the documentation...

We did a reset system 4 and that worked and now the IP softphones are working.

Yeah, we tried 3 different extensions too.

We are trying to login to a CLAN board and it never seems to get there, a list trace of the PC show this 12:38:55 rcv RRQ endpt 10.36.1.161:14745 switch 10.36.0.48:1719 ext 12:39:00 rcv RRQ endpt 10.36.1.161:14745 switch 10.36.0.48:1719 ext 12:39:05 rcv RRQ endpt 10.36.1.161:14745 switch...

I have something similar. If we plug in a phone and then don't put an extension right away ie within 5 minutes it goes to discovering 10.x.x.x and the only way to get it back is to unplug the phone and plug it back in. These are "temp" desks so different users go in every day. "hold reset"...

The IP addresses are correct in configure server and the LSP shows in service/idle it is a CM 3.0.1 in the main server so list survivable is not valid command.

I have an LSP that was recently installed and the translations were saved on the initial install but has failed every night since. Tha sw versions are different but i thought the LSP could be higher than the main server. I can sftp to the LSP and the network stuff all looks good. I have 4 other...

hey Mitch, if you reset the gateway does it still work? I found 1 that the card worked until a reset. I have downgraded my 3 gateways to 25.30 and they work and Avaya told me they were aware of the problem and are working on it.

Never mind, I guess it just likes to give you a scary warning. After I upgraded BankB and it reset to BankA the firmware was in fact upgraded.

I am trying to upgrade a g250 to 27.27.0 using the USB port and it seems to load OK but after it finishes writing the file to the gateway I get "Lifetime validation test failed" in my last erroe field and the firmware stays at 26.31.0, what am i doing wrong? Joe

Were you able to fix this?? I am having a problem with 3.1 MSS back end, I can call a phone with notify me but it will not call the paging system. Here is what we have in there. I am trying to have MM outcall a number, extension 23111 wait for a prompt for a pager number 148 and then send the...

The MSS gives a major alarm every time this happens though. I think that avaya can change the threshold on just that alarm though so that it won't call our alarmtrax every 17 hours.

Has anybody else installed a 3.1? I am at another site that was installed by someone else and there are 1642 errors here as well, every 17 hours and 19 minutes. Must be a bug somewhere. This one has SP 1 also. Avaya tier 3 is still looking.

Thanks Ken I looked at that and Private was the first choice. Hopefully TAC can resolve or they will get an alarm from the MSS every 17 hours and 41 minutes.

Yes the MAS is working fine. It can't really tell if it fails during the heartbeat error but I may be able to find out today. I have a ticket opened and maybe they can come up with something. Maybe the Extreme I am plugged into for the Private LAN or the Cisco for the Corporate LAN does maint...

I am getting this error in only 1 of 3 MAS's every 17 hours and 41 minutes. I have 3.1 with SP1 and 310104 patch. This alarms the MSS also with alarm code 900 major, I thought the patch would fix it but it has not. The timing is exact too 17:41 every time. Any thoughts before I call Avaya??

Spelling counts in the trusted server fields on the MSS. DAMN I cannot beleive I missed that.