Notice: Maintenance Notice ***Service Impacting Upgrade***

Update timeline

1. scheduled Apr 19, 2016, 07:16 PM UTC

   Purpose: Upgrading our VoIP Panel from v3x top v4x Date: Saturday Morning of May 7th, 2016 Time: 00:00AM ET to 05:00AM ET Service Impacting: Yes (Up to 10 minutes) Maintenance Duration: 5 hours In depth description of upgrade impact: Presently MeloTel is VoIP Panel is released 3.7, however we are now planning a major release of our latest VoIP Panel Version 4. With this update comes some major improvements and paves the way for full utilization of WebRTC. Since MeloTel VoIP Panel Version 4 is a major release, the current release notes contain only the changes that, in our opinion, might affect existing customers. If you have any questions about how these changes affect you, please contact your MeloTel Account Manager directly. In VoIP Panel 4 email address of accounts should be unique. Preparation for Hubgets provisioning in VoIP Panel. Added support for multiple contacts per extension (SIP forking). Added user management roles (owner, administrator, member). Allow to enable/disable SIP presence and notifications using configuration directives. Added support to call extensions while calls are waiting in queue. Changed format for voicemails and recordings to mp3. Improved the security of the password hashing. Added meta information to VoIP Panel login page for a nicer preview. Added challenge for extensions behind NAT when they try to place calls without registering first. Added video support to echo function that can be involved with *52. Improved Intercom voice quality. Added Reason header text parameter in CANCEL requests for calls completed elsewhere. Removed requirement to supply voicemail password in phone terminal extension templates. Improved sounds quality. Improved usability with no ringing before queue answers call, when call comes from IVR. Fixed CallerID setting on UnifiedAPI transferred calls. Fixed possible issue with queue agents being considered unavailable. Fixed setting duplicate codecs on extension configuration. Fixed To number in Call Flows. Fixed silence detection in voicemail. Mark agent’s local channel as available after transfer. Fixed issue with concurrent calls being checked for ICR owner instead of ICR target. Fixed not allowing free calls when the charging limit on public calls is set to 0. Changed storage for Force MWI and Extension publish settings. Fixed several issues with parking BLF NOTIFY. Fixed redirect issues that could affect phone provisioning. Fixed Exit to operator during queue announcements. Users with empty voicemail passwords are no longer allowed to check their voicemail. Fixed conference recording to avoid possible deadlock. Another notice we would like to release to our existing and prospect customers in the following; In VoIP Panel v4 and newer versions the email address of a VoIP Panel User Accounts will be forced to be unique. This will impact users in the following ways; Each user under an organization will be required to use a unique email address. You will only be able to create accounts using a unique email address. Any existing users sharing the same email You won’t be able to make any changes under the “Edit User” section until you set a unique email address. This actually fixes a design mistake that created a lot of inconveniences and makes many features wanted to implement impossible. Email has evolved in the past years to become the de-facto standard for online identity. Virtually all platforms use email to identify users. Unfortunately for the VoIP Panel, it could not do the same, because email was not unique. Users in the VoIP Panel organizations could have the same email, leading to identity confusions and making impossible many future developments. For example: Users could not use the email in forgot password, but username. Username is also very easy to forget. Integration with many platforms is impossible since they use email in registration flows and rely on it, because it was unique (they identify the user). Login to the VoIP Panel by using your email address was impossible. Account invitations (allow customers to self grown their organization) was impossible since invitations should be sent by email. In fact, it was virtually impossible to create modern sign-up methods. User accounts on multiple organizations (federation) is also impossible without an unique identity. The list can continue… We postponed this change for many years due to its impact and effort and we’re sorry for not have pushed it earlier. We tried to make the change as easy-to-digest as possible: Provisioning requests *do not require email* – email should be filled only by the user at the first login. This was made in order not to break billing/provisioning integration. Notifications can be served to alternate email as well, so basically it’s possible to configure the system to gather notifications for multiple accounts on the same email address even if the primary email is not the same. As of 2016, it is hard to believe that users in an organization do not have an individual email. The email is not actually system unique, but organization unique. We will push another feature this year where a service provider can assign to each organization a service domain, like (voip.mycompany.com). The email will be unique at service domain level (which is identified by an organization). This has many benefits at the HTTP services and telephony level – for example you can trace and isolate attacks against a customer much easily. This functionality will be enabled only if you want to. Additionally it leads to account federation – have someone member of multiple organizations (for example a consultant). Big moves like this are part of our quest to continue to be the most feature rich and functional telecommunications provider in Canada. If you have further inquiries about this topic, please speak with your account manager.

2. scheduled May 06, 2016, 05:28 PM UTC

   This is a friendly reminder to our customers that tonight we will be performing a maintenance/upgrade to our VoIP infrastructure. Purpose: Upgrading our VoIP Panel from v3x top v4x Date: Saturday Morning of May 7th, 2016 Time: 00:00AM ET to 05:00AM ET Service Impacting: Yes (Up to 10 minutes) Maintenance Duration: 5 hours If you have further inquiries about this topic, please speak with your account manager.

3. scheduled May 07, 2016, 02:59 AM UTC

   Maintenance will begin as scheduled in 60 minutes.

4. in progress May 07, 2016, 04:01 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

5. in progress May 07, 2016, 04:01 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

6. monitoring May 07, 2016, 06:42 AM UTC

   Our maintenance has been completed. We are just verifying our services before marking this maintenance fully completed.

7. completed May 07, 2016, 06:50 AM UTC

   Our upgrade to VoIP Panel version 4 is now completed.