Jump to content
2600Hz Community

4.0 Upgrade Status - Known Issues


Darren Schreiber
 Share

Recommended Posts

Hi everyone,
     As noted, we expected some issues today with the 4.0 upgrade. I wanted to keep a public list in the hopes of avoiding duplicate submissions for issues we already know about, and also to keep you all informed. I'll update the top part of this post as the day progresses.

     Here are the issues we are currently seeing and working on:

* FIXED: International calls fail - DNS issue causing failure to route to our international carriers (US calling and E911 are via IP so they were OK)
* FIXED: Customers who ONLY allow G729 codec are having codec negotiation issues.
* FIXED: Webhooks were not firing in some zones.
* FIXED: Conference entry tones are missing when parties join the conference
* FIXED: Email to fax not working.
* FIXED: Numbers should now be properly appearing in all accounts. If your account was somehow missed, please drop support an email and we'll fix you up.
* FIXED: We have received multiple reports of voicemails not being received and have determined that an issue with recording and storing the messages impacted a percentage of voicemails left. Voicemails are now being stored properly.
* FIXED: DISA Caller ID not respected for calling outbound (rare feature usage scenario)
* FIXED: BLFs for parking slots are not working reliably (though in testing)
* FIXED: Voicemails that weren't stored properly after the initial 4.0 upgrade have been recovered. They have been placed back into customers mailboxes as "new" messages. This should also trigger the MWI indicator on customer's phones and are available in the voicemail manager application. The messages will lack a valid Caller ID. Unfortunately customers who are missing the Caller ID on a message will need to pair up the voicemail's date/time with CDRs to identify (or guesstimate) the Caller's information.
* FIXED: Duplicate voicemail to email messages are being generated on some older accounts (one branded and one un-branded). This is being fixed.
* FIXED: Click-to-call changed slightly in how it functions, updates via UPDATE package to show dialed number on the screen. One customer had customizations that relied on Caller ID being the field where this data was delivered. We will be making a change to attempt to appease this client.
* FIXED: Many requests came in previously to show the local IP of the phone in the debug tool, not the public IP. This was to help partners figure out exactly which phone at a client's site was attached. We made this change, but now people want the public IP as well (which makes sense). We are working to add both so you can use both.
* FIXED: MWI not illuminating if a user has multiple voicemail boxes. Only the first voicemail box count is being checked. The old strategy used to be that you'd be sent the total voicemails in ALL mailboxes. We are reverting to the old behavior.


This concludes the rollout of 4.0 and all major known bugfixes we have learned of.

Last Update: December 10th, 2016 @ 1:30pm PST
Link to comment
Share on other sites

They are not a bug. They are by design, but nobody likes it. It ensures the message gets through always in case there's an ecallmgr issue (there are two ecallmgr's, hence two notices).

However we have heard this complaint enough that we are changing the way we do it soon, which should de-dupe them.

But it's not a bug.
Link to comment
Share on other sites

@Darren, please have a developer review "clicktocall." I am certain that it's issuing the account's callerID for <contact_number> when it should be the other way around. Also, please have them review the entire "clicktocall" process as there is something else going wrong that my developers can't pinpoint. Prior to the upgrade "clicktocall" has worked for us flawlessly for two years and we haven't made any code changes on our part, but now our CRM integration app is broken.  
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...