Mitel Forums - The Unofficial Source
Mitel Forums => MiVoice Office 250/Mitel 5000 => Topic started by: GCD on June 27, 2019, 01:05:09 PM
-
I have a Mivoice Office 250 system with firmware 6.2.5.81. I am connecting a Mitel conference room phone model UC360 which connects as a SIP phone. This is the only phone in its SIP phone group. I set a very secure authentication password. The phone connects and works fine but I keep getting this error anyway. The authentication password is not blank and is not the extension number. It is 15 characters consisting of capital, lowercase symbols and numbers. Enable In-bound Authentication is set to No. If I change that then the phone won't connect. If I clear the alarm it comes right back. I have a cordless phone configured exactly the same way as far as I can tell and it isn't causing any alarms. The UC360 and the PBX are on the same LAN.
What else can I do to clear this alarm?
Thanks!
-
I have a Mivoice Office 250 system with firmware 6.2.5.81. I am connecting a Mitel conference room phone model UC360 which connects as a SIP phone. This is the only phone in its SIP phone group. I set a very secure authentication password. The phone connects and works fine but I keep getting this error anyway. The authentication password is not blank and is not the extension number. It is 15 characters consisting of capital, lowercase symbols and numbers. Enable In-bound Authentication is set to No. If I change that then the phone won't connect. If I clear the alarm it comes right back. I have a cordless phone configured exactly the same way as far as I can tell and it isn't causing any alarms. The UC360 and the PBX are on the same LAN.
What else can I do to clear this alarm?
Thanks!
Odd that you are still getting it with a password like that... but if you go to System - Flags you can find "SIP Phone Group - Password Alarm" and change the flag to NO and you won't get that alarm anymore.
-
Acejavelin is correct, This will stop the alarm from happening. Had the same issue. :)
-
It is odd and I'm very curious to know why but I did turn off that flag and it did clear the alarm so I guess that solved the issue.
Thanks!