Single Line SIP extensions not ringing when in groups

[acejavelin]

So I haven't done a Mitel installation for a long time, and this is the first one I have done that purely virtual and the analogs are all SIP extensions on a 48-port Grandstream...

I have a few instances where the Single Line SIP extensions are not ringing as part of groups.

First one is a 6930 desk phone and an analog cordless connected to a SIP extension on a Grandstream device (Full Service, stand-alone extension)... Calling the analog cordless directly works fine as does calling the 6930 desk phone, but if you call the Ring Group that is set to Ring All that contains both devices, only the 6930 rings.

For another user, we built a MDUG with a 6930 and a SIP extension both setup as Multi-User Devices under the same user, both can make calls fine, but when you call the Prime DN, only the deskphone rings and not the SIP analog extension.

Is there something unique about single line SIP extensions here? I am a little confused as to why this isn't working... I haven't done a MiVB install for a long time, but I have done hundreds and don't recall ever running across this before...

[lundah]

Any difference if you put the devices in a Personal Ring Group instead of an MDUG? I know I have working PRG

[acejavelin]

Any difference if you put the devices in a Personal Ring Group instead of an MDUG? I know I have working PRG

I am going to go onsite tomorrow and investigate further, I will let you know... It's all been remote for the last week with temps in the negative double digits and being over an hour away.

[acejavelin]

Alright... This turned out to be easier than I thought, those three specific ports on the Grandstream were not registered. They appeared to be registered on the GS port status but in the Mitel they showed LOCKED AuthFailure (but they could place calls out?!?!). Rebooting the Grandstream then showed them as not registered and I reset the sip password many times and couldn't get it to clear. Finally I removed the extensions from the GS until SIP EXT xxx didn't show the LOCKED message anymore (about 10 minutes) then put them back into the GS with the same credentials (copy and pasted) and they showed registered in both the Mitel and Grandstream and everything worked as expected. Very weird...

[lundah]

Alright... This turned out to be easier than I thought, those three specific ports on the Grandstream were not registered. They appeared to be registered on the GS port status but in the Mitel they showed LOCKED AuthFailure (but they could place calls out?!?!). Rebooting the Grandstream then showed them as not registered and I reset the sip password many times and couldn't get it to clear. Finally I removed the extensions from the GS until SIP EXT xxx didn't show the LOCKED message anymore (about 10 minutes) then put them back into the GS with the same credentials (copy and pasted) and they showed registered in both the Mitel and Grandstream and everything worked as expected. Very weird...

I find that different ATA's require the password in different places in the "Access and Authentication" tab in Users and Services Configuration in the MiVB. For my Audiocodes MP-11x, I have to enter it in the "User PIN" fields, but for the Grandstreams, I have to enter it in the "SIP Password" field. Also saving a new value here will reset the lockout timer. It follow the DISA lockout timer normally.

[sarond]

You can also usually unlock the lockout by maintenance command BUSY RESET {EXT}

The same command also logs out a hot desk user.