1
Mitel MiVoice Business/MCD/3300 / Re: guide:How to capture CCS trace to file
« on: Yesterday at 01:58:46 PM »
I wonder if there's a way to pipe it directly to a file on the MiVB?
News:
Welcome to Mitel Forums. The Mitel resource - by techies, for techies...
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.
2
Mitel Software Applications / Re: Nupoint
« on: April 16, 2024, 05:03:55 PM »
So there is. HO2683, and it's a slightly different method of creating the mailbox data report that I referenced in my method. You still have to generate a text file and search for the match within it.
3
Mitel Software Applications / Re: Nupoint
« on: April 16, 2024, 02:33:12 PM »
Easiest way I know is to capture a mailbox report and then search in the resulting text file.
What I mean by that is SSH into the NuPoint text console, select Reports. Run a Mailbox Data report to the console (screen), capture that output, then search for your DN's in the output.
What I mean by that is SSH into the NuPoint text console, select Reports. Run a Mailbox Data report to the console (screen), capture that output, then search for your DN's in the output.
4
Mitel MiVoice Business/MCD/3300 / Re: Embedded VM - no new messages in Operator mailbox
« on: April 16, 2024, 09:26:07 AM »
Forgot to mention, it's running MiVB 9.3, I've already tried a reboot and a DB backup/restore.
5
Mitel MiVoice Business/MCD/3300 / Embedded VM - no new messages in Operator mailbox
« on: April 16, 2024, 09:14:14 AM »
Got a small CX-II system with just a handful of mailboxes on embedded voice mail. After hours call comes in, hits the primary greeting, then the caller can leave a message that should go to the Operator mailbox and light an MWI. I see the message files in /vmail/d/vm/grp/0, but the mailbox doesn't see that there's a new unplayed message, either in ESM or by logging in via TUI. Normally I'd delete the mailbox and re-create it, but it's 0 so the system won't let me do that. Any ideas? Only other option I can think of is to dial in as admin and delete and recreate the entire EMEM system. No active SWA, so I can't raise a ticket.
6
Mitel MiVoice Business/MCD/3300 / Re: 5212 phones have an invalid DHCP option 124 - new Cisco gear incompatible
« on: April 16, 2024, 09:10:27 AM »Hello, I'm having the same issue with a client still using old phones (and in MCD 6.0).
He's asking if putting the phones in SIP mode could help, any ideas about that ? He's probably anticipating that Mitel will say it's fixed in 9.0 or 10.0 or whatever but doesn't have the budget to upgrade.
Sounds like it's a Cisco issue and not a Mitel issue, so I don't see how upgrading the Mitel will help.
7
Mitel Software Applications / Re: Micollab IDS Managed Client user information
« on: March 26, 2024, 05:52:46 PM »
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".
8
Mitel MiVoice Business/MCD/3300 / Re: Dialing issue with the 5304 IP phones
« on: March 26, 2024, 05:51:40 PM »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.
9
Mitel MiVoice Business/MCD/3300 / Re: Hotdesking on 6869i SIP phone on Mivoice Business
« on: March 25, 2024, 09:26:46 AM »
The MiVB does not support hot desking on SIP phones.
10
Mitel MiVoice Business/MCD/3300 / Re: 3300 CXII Voicemail to Email with Google Workspace
« on: March 22, 2024, 12:07:10 PM »
What release are you running? Looks like there was a known issue that was fixed in MiVB 10.1.0.27.
11
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.
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.
12
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.
13
Mitel MiVoice Business/MCD/3300 / Re: Ring group members present/absent
« on: March 19, 2024, 09:21:50 AM »
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.
14
Mitel Software Applications / Re: Upgraded to 10.1 on 3300 and Oaisys is no longer recording agent calls
« on: March 12, 2024, 07:59:14 PM »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.
15
Mitel Software Applications / Re: Best way to implement Micollab client to a existing not in use Micollab server.
« on: March 12, 2024, 09:19:11 AM »
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.
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.