New iOS 13 SDK support in MiCollab iOS Client 9.1.311

iOS 13 SDK Update

Reminder: 23rd June 2020
It is now one week until the iOS 13 SDK updated client is added to the Apple App Store (ETA June 30th 2020).
Customers with Automatic Downloads (for App updates) enabled on their iPhone device, will automatically upgrade on that date.
If the Customer's MiCollab Server has not been patched, or upgraded to Release 9.1 SP3 FP2 (also released on June 30th 2020), then users may report the behaviour changes documented in this KMS article.

If users do report behaviour changes immediately after updating the client version (or around the date of 30th June), and you have not patched the server, before contacting Mitel Product Support, please either:

  • Apply the patch to a version for which a patch has been created (see article SO5082).
  • Upgrade to a version for which there is a patch, then apply the patch (see article SO5082)
  • Upgrade to 9.1 SP3 FP2.

====================================================================


iOS client version 9.1.311 was uploaded to the App Store on 7th April 2020. This version implemented the changes described within this article.
However, due to an unrelated issue regarding a failure to answer some softphone calls, the App Store was subsequently updated with version 9.1.312, (which re-introduced the previous 9.1.205 version).

The softphone call issue is under investigation, and the iOS 13 SDK will be re-introduced at a later date (expected to still include the changes within this article).
It is therefore recommended that the patches from 

 

KMS document SO5082 be applied in preparation for the future client release.
This article will be updated when the release date for the iOS 13 SDK is known.


MiCollab for Mobile iOS client has been updated to include the new Apple iOS 13 SDK as per Apple developer requirements. With the new SDK from Apple, MiCollab Client softphone users connecting to pre 9.1 servers will notice some changes in the user experience.
 
Mitel has taken every step to comply with iOS 13 SDK requirements and mitigate any impacts to the previous iOS client user experience.
 
It is Mitel’s recommendation that your environmental components are updated to the following to ensure a seamless transition to the latest Apple software included with our new client.


MiCollab Server Versions
 

MiCollab Server Version Version Patch required OVA Build Version required
MiCollab 8.0 SP2 8.0.2.10 See KMS document SO5082 See KMS document SO5082
MiCollab 8.1.2 8.1.2.8 See KMS document SO5082 See KMS document SO5082
MiCollab 9.0 FP1 9.0.0.104 See KMS document SO5082 See KMS document SO5082
MiCollab 9.1 or higher 9.1.2.4 For MiCollab 9.1 or higher, patch is not required

 
 
 
 
 
 
 


 

 

MiCollab Client (stand-alone UCA) Server Versions

MiCollab Client Server (UCA) Version Version Patch required OVA Build Version required
MiCollab Client 8.0 SP2 8.0.2.10 See KMS document SO5082 See KMS document SO5082
MiCollab 8.1.2 8.1.2.8 See KMS document SO5082 See KMS document SO5082
MiCollab 9.0 FP1 9.0.0.102 See KMS document SO5082 See KMS document SO5082
MiCollab 9.1 or higher 9.1.2.1 For MiCollab 9.1 or higher, patch is not required

  
 
 
 
 
 




 

 

MiCollab MiVBx Server Version

MiVBx (vUCC) 8.1.2.502 Version Patch required OVA Build Version required
MiCollab 8.1.2.501 8.1.2.502 See KMS document SO5082 See KMS document SO5082

  
 

 



 
Recommendations:

  • Where users are managed using Mobile Device Management or manual notifications from administrators, it is a recommendation the administrator only allow upgrade of the mobile iOS clients once the MiCollab Servers and MiCollab Client Servers have been upgraded or patched, as per KMS article:
 SO5082 New iOS 13 SDK support in MiCollab iOS Client 9.1.3 - Server patches 



 



MiCollab Client Server - iOS Mobile Client experience.

Mobile Clients connected to a pre-9.1 MiCollab server will periodically see a re-registering of the SIP Softphone (every 9 hours).
The client will display a registration screen, which acts like an incomming call, resulting in a visual and audiable notification to the client (See image below).




Users may also notice entries in their Call History, showing a Missed Call from 'Re-Register', with number '000000'




This periodic screen and call history entries can be avoided by applying the upgrades or patches mentioned above.

The patches will modify the server push notification behaviour in line with requirements for iOS 13 SDK, allowing pre-9.1 servers to make use of the same functionality already included in 9.1 server, whereby users will not see these screens.



Call Managers (PBX)
Call Managers running with the versions below will allow a 30-day SIP registration period. Previous versions registration timers were shorter and in rare occasions causes call to go to voicemail.
For improved end user experience, we recommend using the call manager versions below to enable longer registration timers.
Please reference call manager documentation to modify these timers.
 
Component Version
MiVoice 5000 7.1 K1A6_01
MiVO 400 R6.1 HF3
MiVB 9.0.1.21
MX-ONE configuration: MaxRegistrationTime*
Hebt u meer vragen? Een aanvraag indienen

Opmerkingen