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 4 ... 78
16
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.

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

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

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

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

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

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

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

24
All they should have to do is disconnect, the remaining parties should stay connected. So if I'm on a 5320 on a 3 party call, I just hit the Cancel key, the other 2 parties stay connected, and I have dialtone to make my next call or I can press a ringing line key to answer.

25
No, Call History only shows calls to/from the prime line (key 1) of the phone.

26
Using a MiCollab account for that would be the cleanest. You'd burn a Standard UCC license, but then you can have either 8 or 16 EHDU extensions assigned and the on-call staff can log in via the web client and switch the device. Set up an availability status for each on call member, and they just need to log in via the web client and change the status. They could even update the EHDU number there if there was a staffing change or someone had to send calls to an alternate number on the fly.

An uglier solution would be to set up a DISA number (with an account code on it) and then dial speed call DN's that in turn dial the forwarding FAC and associated numbers.

27
Update:
I've verified that everything in the CESID assignment form has a number.
No change.
I found that by turning off Automatic updating the alarm goes away.
That's bumming me out a bit.

Ralph

The issue there is your CESID's will no longer update when a phone moves. I've only used the automatic updating a handful of times, and generally it was not worth the extra work to track down all of the changes and clear the alarms.

28
You'd want to program a "Group Park" key against the DN. This lets you park and pick up a parked call by just pressing the Group Park key, and also gives you an indication that a call is parked.

29
Mitel MiVoice Business/MCD/3300 / Re: Call Routing question
« on: February 16, 2024, 12:57:13 PM »
Frankly that's the nature of how key system lines work, they're occupied as long as a call is up on one. The alternate would be to set up group park keys:
  • Create a DN (single line, ring group, doesn't really matter. I've used ring groups in the past for this).
  • Create Group Park keys against that DN on the phones that need to be able to park and pick up parked calls. The line will only be busy while a call is waiting to be picked up from the park key.

30
Mitel MiVoice Business/MCD/3300 / Re: Random ip6920 handset reboots
« on: February 05, 2024, 09:36:20 AM »
What is this and could it be related?

      FLOOD_MONITOR
Description      TCP SYN Flood or Redundant Failover Activity. Dropping TCP SYN pkts. Last pkt dropped:MAC s=00:18:0a:4f:01:48 d=08:00:0f:b7:56:** IP len=44 s=10.151.*.* d=192.168.1.2 TCP sport=40408 dport=8290 For info use Sniffer & RTC cmd FloodShow. WD was tickled.

That's certainly possible. I'm assuming MAC 08:00:0f:b7:56:**/IP 192.168.1.2 is the controller? What's the source device from that log message?

Pages: 1 [2] 3 4 ... 78