MiVoice Business and NuPoint Voicemail

[Imbru]

The background:
- NuPoint v18.0.0.49 (running on MiCollab 7.0.0.99/ Mitel Standard Linux 10.3.38 / OVA 7.0.0.95)
- MiVoice Business Release level: 9.2 / Active software load: 9.2.0.59 / Platform: Industry Standard Server
- Devices: 5360IP
- Upgraded from MiVoice Business 7.2 to 9.2 using remote full install on the ISS (performed a full backup prior) and didn't have an issue.
- DB was restored and came up clean, with no errors, system is "green" and functions normally.
- Auto attendant set up for line group 1, trunks are set to dial voice mail hunt group (6000) during night service

The issue:
- Calling the NuPoint VM hunt group (6000 in my case) rings the AUTO ATTENDANT and does NOT prompt "Hello user, enter your PIN..."
- Same issue when going off-hook and pressing the MAILBOX button
- Same issue when using the messaging app on the device
- This was working fine prior to the MiVoice Business update

Settings that I checked:
- VM hunt group
- HCI re-route
- Call coverage services
- Leaving a message works fine, MWI lamp is functional
- Auto attendant works as intended during night service
- etc.?

The VM box still exists, I can press enter the extension, press "*" and then log into it normally.

It's seems like the NuPoint no longer recognizes an internal caller, so immediately routes to the auto-attendant.

Any ideas?

 

[Billz66]

Why is the micollab so old?
that would have been my first step , upgrade micollab to latest before upgrading the MIVB.
i suspect thats probably the issue



If I never did anything I'd never done before , I'd never do anything.....

 

[Imbru]

Sure it's old - but would not have suspected that this would cause an issue with NuPoint, since they're not related (correct me if I'm wrong!).

We're just hitting the NuPoint line group to access VM box - where does MiCollab come into the picture?

Having said that - YES - upgrading is on the list, was just scheduled for some time after the MiVoice Business upgrades - looks like I need to accelerate this...

 

[kwbMitel]

Sure it's old - but would not have suspected that this would cause an issue with NuPoint, since they're not related (correct me if I'm wrong!).

It always helps to read the Release Notes:

[pre]
Application Minimum Software Requirements
MiCollab 9.4, 9.3, 9.2, 9.1.3, 9.0, 8.1.2., 8.1.1, 8.1, 8.0 SP2 FP3 [/pre]

On a side note: 7.0 was released in 2015 and there have been around 20 releases since then. To expect it to work is more of a stretch than not

 

[Imbru]

You bet - I did read the release notes. Just curious WHAT MiCollab has to do with this ONE VM function. Everything else is functioning properly. If it was a major incompatibility you'd think I'd be having more issues than I do now.

Guess I like to dig a little deeper than the "it's not shown as compatible, so too bad" attitude of software upgrades.

Thanks for the input...

 

[kwbMitel]

The Server is called MiCollab, the app is called Nupoint

Even you in your original post noted that the Software version was "running on MiCollab 7.0.0.99/ Mitel Standard Linux 10.3.38 / OVA 7.0.0.95"

For the record, it is more than 20 releases behind, it is closer to 40
[pre]
9.3.1.14 MiCollab 9.3 SP1 2021-07-01
9.3.0.31 MiCollab 9.3 2021-04-01
9.2.0.202 MiCollab 9.2 FP2 2021-02-01
9.2.0.104 MiCollab 9.2 FP1 2020-12-01
9.2.0.32 MiCollab 9.2 2020-10-01
9.1.3.302 MiCollab 9.1 SP3 FP3 2020-08-01
9.1.3.205 MiCollab 9.1 SP3 FP2 2020-06-01
9.1.3.107 MiCollab 9.1 SP3 FP1 2020-05-01
9.1.3.12 MiCollab 9.1 SP3 2020-04-01
9.1.2.4 MiCollab 9.1 2020-01-01
9.1.0.15 MiCollab 9.1 2019-12-01
9.0.0.104 MiCollab 9.0 FP1 2019-11-01
9.0.0.29 MiCollab 9.0 2019-10-01
8.1.2.104 MiCollab 8.1.2.1 2019-08-01
8.1.2.8 MiCollab 8.1.2 2019-05-01
8.1.1.108 MiCollab 8.1.1 FP1 2019-03-01
8.1.1.11 MiCollab 8.1.1 2018-12-01
8.1.0.101 MiCollab 8.1 FP1 2018-11-01
8.1.0.61 MiCollab 8.1 2018-09-01
8.0.2.301 MiCollab 8.0 SP2 FP3 2018-08-01
8.0.2.202 MiCollab 8.0 SP2 FP2 2018-07-01
8.0.2.101 MiCollab 8.0 SP2 FP1 2018-04-01
8.0.2.10 MiCollab 8.0 SP2 2018-03-01
8.0.1.9 MiCollab 8.0 SP1 2017-12-01
8.0.0.301 MiCollab 8.0 FP3 2017-11-01
8.0.0.202 MiCollab 8.0 FP2 2017-10-01
8.0.0.103 MiCollab 8.0 FP1 2017-10-01
8.0.0.40 MiCollab 8.0 2017-08-01
7.3.0.204 MiCollab 7.3 PR2 2017-05-01
7.3.0.106 MiCollab 7.3 PR1 2017-03-01
7.3.0.30 MiCollab 7.3 2017-02-01
7.2.2.13 MiCollab 7.2.2 PR2 2016-12-01
7.2.2.12 MiCollab 7.2.2 PR1 2016-11-01
7.2.2.11 MiCollab 7.2.2 2016-10-01
7.2.1.13 MiCollab 7.2.1 PR2 2016-09-01
7.2.1.12 MiCollab 7.2.1 PR1 2016-08-01
7.2.0.26 MiCollab 7.2 2016-07-01
7.1.0.55 MiCollab 7.1 PR1 2016-04-01
7.1.0.35 MiCollab 7.1 2016-03-01
7.0.0.98 MiCollab 7.0 PR2 2016-01-01
7.0.0.95 MiCollab 7.0 PR1 2015-11-01
7.0.0.78 MiCollab 7.0 2015-10-01
[/pre]

 

[Imbru]

Yup - I am aware, and understand the differences between the server and the apps - thanks for the info.

My previous comment still applies - guess I approach things a little differently, trying to find out why this ONE FUNCTION does not work on the NuPoint APP.

Moving on, unless someone else has any other recommendations other than "upgrade it" (which is planned).

 

[kwbMitel]

Based on your experience, I would surmise that the positioning or format of the messaging between the MiVB and the MiCollab (Nupoint) has been adjusted. This is not the only possibility but it fits the facts.

I've seen your issue before but it's been too long to remember where or what the solution was.

It is best practice to keep things at least nominally the same version.

On the off chance that it is not the version causing the issue, I'll keep trying to remember when/where this happened to me.