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 - lundah

Pages: [1] 2 3 ... 77
1
Look in your Detained User Updates, there should be an Update record for the user that you just need to check the checkbox for and then click "Save".

2
The problem with the 5304 phone is the design of the plastic pieces are not rigid enough to keep the parts of the hookset switch steady. So when someone stabs there finger at the number pad, it deforms the frame and closes the hook even though the handset is not in the cradle.  It's momentary, but enough to screw up the call.
I found a way to tie the plastic body layers together so it keeps the hookset stable.  Disassemble the phone and you will see a "well" that the hookswitch parts rest in.  You can tie the top layer down to the well by drilling 2 small holes at the bottom of the well and carefully thread some strong waxed lacing string through the holes and tie the circuit board down on top of it. I can provide pictures if you want to see how to do it.  It take about 30 minutes to do it which is usually a little less then buying a new phone (that will do the same thing eventually).

At this point the whole 5300 line has been EOL for a good 5+ years. You're better off just going ahead and spending the money for a 6905 or 6910.

3
The MiVB does not support hot desking on SIP phones.

4
What release are you running? Looks like there was a known issue that was fixed in MiVB 10.1.0.27.

5
Non-Mitel Chatter / Re: eFax service
« on: March 21, 2024, 09:13:26 AM »
I've been working with eGoldFax, which was recommended by both my Mitel partner and our managed print vendor. Their pricing was better.

We use Sharp MFP's and they have a web app that replaces the existing Fax application on the machines, so it makes it a simple switch for walk-up send jobs. I'm still in the pilot stage of that rollout, but going well so far.

6
Mitel Software Applications / Re: CCMWeb Reports - Call Volume
« on: March 19, 2024, 03:48:04 PM »
Traffic reporting out of the MiVB doesn't report data on SIP trunks, you probably have to go the DNIS Group route.

7
You could create a second ring group with all of the same members in it and set them all present & "Ring All", then set the first group to overflow to that. After a couple of calls overflowing to the ring all group, the users should start managing their presence better.

8
What release did you upgrade from, and what integration type are you using? There's a known issue with indirect recording not working on MiVB 10.0 and up on the MiVCR/Oaisys platform. Mitel did not fix it due to MiVCR/Oaisys already being EOL & end of support by the time MiVB 10.0 was released.

According to the release notes, the indirect recording problem on MiVCR is fixed in MiVB 10.1.

9
Assuming you don't have USP integration set up already, go to edocs.mitel.com and get the MiCollab Installation and Maintenance Guide for MiVB for your release, and take a look at Appendix C, which walks you through the setup for an existing MiVB and MiCollab server. Then for setting up the users, you'll need to configure emails and login ID's for all the users (and optionally sync the users with AD if you want to save them from remembering another password). Also do the work of setting up your feature profiles and user profiles on the front end, it will save you headaches later. Also get your roles and templates set up to make adding new users easier.

As far as Teams integration, Mitel Assistant works, but doesn't really have any features to speak of. You can't even add a speed dial directly, it has to come from either the global address book or the user's Outlook contacts. It's been a couple years since I played around with Call2teams, but I remember that was pretty limited as well.

10
What release did you upgrade from, and what integration type are you using? There's a known issue with indirect recording not working on MiVB 10.0 and up on the MiVCR/Oaisys platform. Mitel did not fix it due to MiVCR/Oaisys already being EOL & end of support by the time MiVB 10.0 was released.

11
SIP On Mitel / Re: New SIP install with audio issues
« on: March 08, 2024, 01:21:42 PM »
In addition to ZuluAlphas comments, make sure SIP ALG is disabled on anything sitting between the MiVB, MBG, and your connection to the SIP carrier.

12
No. Mitel says they are working on improvements to Call History that will solve this, but no idea on when that will actually happen.

13
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.

Depending on the specific deployment configuration, I could see how that could happen, particularly with some DMZ deployments. In that same screen you could leave remote access enabled and then restrict it to specific netblocks.

14
Go to Remote Proxy -> Domain List, edit your domain. Towards the bottom of the settings, make sure the checkbox for "Do you wish to permit remote administrative access?" is unchecked to disable admin access from the WAN side.

15
You can force it on in the MiCollab Client Deployment Profile on the server side.

Pages: [1] 2 3 ... 77