MiCollab app on cell phones sending re register error

[sally.washick]

Users including myself and others are getting this issue: The MiCollab app on my work phone woke me up with a ringing sound 6 times throughout the night last night. I turned the sound notifications off in settings but the ringing persisted. I didn’t get a notification of a missed call or anything in the iPhone Notification Center but I eventually found that it was trying to “call” me with a Re-Register name.

It will happen randomly in the middle of the night or early morning and it shows 000000 (6 zeros)  It shows up in my twinned work cell (used with MiCollab app) and then shows in call log as "Re-Register" MiCollab Audio time and then clicking on it takes us to the MiCollab app like it's going to call out to the 6 zeros.  It is waking up some of our psychiatrists at night.  Others it doesn't ring but if we happen to be looking at the phone, we see it flash and then go away but shows in call log.

We have a ticket with our vendor but no response yet.  Has anyone else had this issue.  We all use Verizon iPhones and myself and co-worker of all things Mitel/MiCollab at our .org have the latest iOS update and that did not fix it.  We also are now testing taking off the Audio, Web conferencing on 3 of the 5 known devices/staff that have this issue.

[CraigB]

I have experienced the same thing in the past few days, though I'm not sure what the cause is.
iPhone 7, IOS 13.4.1
MiCollab Client: Server Version: 8.1.1.13, Client Version: 9.1.312 (build: 264)
 

[sarond]

I had the same issue when my iPhone updated to 9.1.311, Mitel released 9.1.312 the next day and I haven't had the issue since.

My server version is 9.1.2.102-01

There is an article about this in the Mitel KMS KB. AL273 - New iOS 13 SDK support in MiCollab iOS Client 9.1.3

Although it was only supposed to show a notification, not audibly ring. My experience was the same, phone would ring for a second or 2. It was annoying as hell.

Ask you vendor to search the above KMS article. I'd say you're going to need a patch and/or upgrade to you server.

 

[CraigB]

@Saround  Thanks for the information.

[mitelrvtd]

I'll go ahead and put here that I'm also having this issue.

MiCollab Server: 8.1.2.8
Client Version: 9.1.375 (build 289)

Haven't contacted our vendor yet as we have very few using it but sure is annoying.
Thanks

[johnp]

Some earlier 8.0 versions require updating before they can be patched

[pmhaynes]

The patch can be added to any micollab running on MSL 10.6 and above
if your running on MSL 10.5 then its an upgrade

[catdaddyx2]

One suggestion I saw was the block the re-register caller using your call history. It's not supposed to affect how calls are forwarded to your phone.
We have server version 8.1.2.8 and client version 9.1.375.  I'm not really in the mood to go through a phone system upgrade just for this minor issue.