Messages

1

Mitel MiVoice Business/MCD/3300 / Re: 3300 CX - Twinning - External Calls

« on: June 20, 2023, 11:27:00 AM »

Thanks I'll look at that.

Can't twin via copper LS - rings once at the desk phone and then "transfers" to the copper trunk (twinned cell).

I've long since forgotten why (buried somewhere in this forum) but has something to do with how LS trunks handle the handoff.

2

Mitel MiVoice Business/MCD/3300 / 3300 CX - Twinning - External Calls

« on: June 20, 2023, 02:09:49 AM »

We have TWINNING set up with no problem.  Presence button to turn twinning off and on, cell number as EHDU, using a SIP trunk so it actually works.

When calling internal (extension to extension) - everything works as advertised - BOTH cell and desk extension works fine.

HOWEVER - when transferring an external call to an extension (or getting to an extension via the auto attendant during lunch/after hours) the cell phone does not ring (just the internal extension).

External calls are on copper LS trunks - the twinned call to cell goes out on SIP.

Any ideas?

3

Mitel Software Applications / NuPoint - CALL FLOW - TWO DIGIT Menu Structure

« on: December 20, 2021, 03:52:43 PM »

Any way to get TWO DIGIT MENUS in NuPoint?

We currently have a department that has >10 people, and management wants that all on the same menu tree (i.e., press 1 for user 1... press 19 for user 19...) (YES I KNOW that makes for a long recording - that's an uphill battle with management I'm not interested in fighting)

As a workaround, we have MULTI-KEY set up as a BLIND TRANSFER TO DIALED EXT, and the recording states "dial 1001 for user 1... dial 1002 for user 2, etc.).

Just trying to find a way to do that in the call flow without exposing the extension (which is not a big deal in the long run if we're forced to do that)...

4

Mitel Software Applications / Re: MiVoice Business and NuPoint Voicemail - "Message" Button not going to VM box

« on: October 13, 2021, 12:51:54 PM »

Yes this was slated to be completed at some point - looks like I need to accelerate the timeline.

In the meantime, users can use the workaround...

5

Mitel Software Applications / MiVoice Business and NuPoint Voicemail - "Message" Button not going to VM box

« on: October 13, 2021, 02:44:07 AM »

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
- May not be relevant, however log files show "SFA(002) - Invalid event UPDATE_CALLER from vmemo(22758) while in state R1" when accessing VM... (?)

Settings that I checked:
- VM hunt group
- HCI re-route
- Call coverage services (points to NuPoint box and VM hunt group)
- Leaving a message works fine, MWI lamp is functional
- Auto attendant works as intended during night service
- Dial plan = [4,4,4,4,4,4,a,4,4] (we use 4-digit extensions)
- etc.?

The VM box still exists, I can press MAIL button (off hook), 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?