Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mitelrvtd

Pages: [1] 2 3 4
1
Thank you, we hadn't found that.
However it is disabled, and it is starting to look like our firewall might be forwarding to the LAN side.

Appreciate the reply.

2
We are able to access the Server-Manager WebUI login screen from the external interface of our MBGs.

The external IP address is not listed in Trusted Networks, just the LAN side IP.

I thought we had this disabled in the past but we are not sure how to disable the external access.

Thank you

3
Thank you both for the replies.

Sounds like these are my options for this.

I'm guessing a lot of people use a service for this type of thing but my use case is very simple and I'll probably do it in the Micollab\MiVoice.

Thanks again.


4
So the extension we use is a Button Directory Number on our Phantom extension. We use the Phantom extension for a bunch of directory numbers.

I'm guessing we would need to make a dedicated account for the extension we are forwarding so we could add Micollab to it?

Thanks

5
Call Forwarding is working fine. We have it set up on a Phantom extension so users can use the *65 feature code with the Phantom extension to change the number the calls forward to.

This is an on-call type setup where the forward is rotated to different people's cell phones on nights and weekends.

We need these on-call people to be able to change the forwarding number when they are offsite. Like dial-in on their cell phone to change the call forwarding.

What could we set up for them to call in and change the forwarding number?

Thank you

6
We were on 9.4 SP1 and upgraded to 10.0 SP1

Previously I think it was a complaint with the system that an external call that would get transferred internally by an AA or similar would have an internal call ring cadence. Because the call would not hold the information that it was an external call.

It almost seems like they may have fixed this now and transferred external calls are keeping their external call ring cadence where they did not before.
Trying to test this but wanted to see if anyone knows if this was officially "fixed".
Thanks

7
We are planning the upgrade now. Our partner is not coming to us about upgrades, we are going to inquire with them annually at this point if they don't reach out.
Thanks again.

8
Thank you both.

Good to know we should expect annual upgrades.

They are pointing us to KMS QA2243 which seems like there is something to it.


***************
Title= MiCollab 9.5 is not compatible with MiVB 9.4 when 69xxw (Wi-Fi) devices are registered.

This document explains the MiVB compatibility with MiCollab application when 69xxw (Wi-Fi) devices are registered to MiVB and recommends the MiCollab application be upgraded to MiCollab 9.6 or higher prior to upgrading MiVB 9.4 or higher.

To support the new 69xxw device, the following table summarizes MiCollab-MiVB compatibility.

Table 1: MiCollab-MiVB compatibility for the support of 69xxw

MiCollab MIVB 69xxw supportability

9.6 or higher MiVB 9.4 or higher 69xxw device type is fully supported and configurable as 69xxw in the User and Service Configuration (USC). For 69xxw device currently configured as 69xx type in the USC, MIVB automatically converts from 69xx to 69xxw type in USC when 69xxw devices register to MiVB.

9.6 or higher MiVB 9.3 or below Due to the limitation that MiVB 9.3 or below does not support 69xxw device type in USC, 69xxw device should be configured as 69xx.

9.5 or below MiVB 9.4 or higher Due to the limitation that MiCollab 9.5 or below does not support 69xxw device type in USC, this configuration is NOT supported. MiCollab 9.5 or below can no longer edit 69xxw user after 69xxw device is registered to MiVB.

9.5 or below MiVB 9.3 or below 69xxw devices are configured as 69xx only.

To avoid running into the unsupported combination of MiCollab 9.5 and MiVB 9.4 scenario, Mitel highly recommends that Micollab Application be upgraded to MiCollab 9.6 or higher first. This requirement is critical for the support of 69xxw (Wi-Fi) devices in the SDS distribution between MiCollab and MiVB.

In the event MVB has been upgraded to 9.4 or higher first, MiCollab 9.5 or below is still able to synchronize and works with MiVB as long as no 69xxw (Wi-Fi) devices are registered to MiVB. Such conditions will be extremely challenging for an end-user/system administrator to manage.

69xxw devices are likely to register to MiVB 9.4 in one of the following scenarios:

1. 69xxw devices were configured as 69xx previously in the USC of MiVB 9.3 or below, after the upgrade to MiVB 9.4 or higher, MiVB automatically converts and updates device type from 69xx to 69xxw; or

2. Running MiVB 9.4 or higher, a new user is to be installed and is initially configured as a 69xx in USC form. During the installation, a 69xxw device is received and registered to MIVB. MiVB in turn converts to 69xxw type in USC during the successful device registration.

There is no impact to user operation and/or MIVB operation. However, when 69xxw devices are updated in USC of MIVB, SDS distributes the new device 69xxw to Micollab server running 9.5 with the following symptoms:


9
Our partner states our MiVM, Micollab, and MBGs need to be updated to support the 69xxw phones.

We are on:
MiVB 9.4
Micollab: 9.5
MBG: "MiVoice Border Gateway 11.3.0.68" (this is just what I see on the MBG server manager pages)

Could someone confirm that we would need to upgrade to support the phones?
The firmware upgrade guide for this device states 9.1 or higher.




10
Thank you, just finally found it. Was looking in the server manager.
Didn't realize it was a phone setting.
Thank you for the help.

11
We have one agent phone that when a call comes in a "Call Info" CallerID window comes up on the 5320e display. They have to click the Close option before they can click the line key to answer the call.
This only happens on one phone that has the same COS as all the others.
I failed finding where this feature is set.
Thanks if someone knows.

12
I have the urls for all the other clients but don't know where this one is on the server if someone does.
Thanks

14
Thanks for replying.
Yeah the Mitel branded wireless headsets don't even say they are compatible with the 5300.

Starting to look like the 5300 series phones just don't support that functionality at all without a lifter.
Thanks again

15
Mitel MiVoice Business/MCD/3300 / 5320e headset compatibility guide
« on: June 03, 2022, 01:53:43 PM »
Hello,
I have found the mitel headset compatibility guide but it only covers 6900 IP Phones, 6800 SIP Phones, and IP400
Phones.

https://productdocuments.mitel.com/legacypdf/Devices%20and%20Accessories/Headsets/Headset%20Compatibility%20Guide/All%20Releases/en/Headset%20Compatibility%20Guide.pdf?_gl=1*plu26p*_ga*MTY1ODg2NTQ3OS4xNjM5MTUzODI3*_ga_GJ2SLN9QSE*MTY1NDI3NzkwNC44LjAuMTY1NDI3NzkwNS4w&_ga=2.234847838.1770223284.1654277905-1658865479.1639153827

We use 5320e phones.

I know a lot of headsets are "compatible" but we specifically what to know which ones the on/off-hook functions with the headset button (without a lifter).
We use Sennheiser Officerunner now but they do not support that functionality.

If anyone has a guide for the 5320e phones or knows some good headsets that have the on/off-hook function.

Thanks!


Pages: [1] 2 3 4