Messages

1

SIP On Mitel / Re: Mitel 5634 WiFi Phone Issue

« on: September 26, 2022, 05:27:25 AM »

Hi drwats

Nope, never got to the bottom of it. Ended up going back to good old 5624's!

Cheers

2

SIP On Mitel / Re: Mitel 5634 WiFi Phone Issue

« on: April 20, 2022, 06:05:58 AM »

On site today doing further troubleshooting. As an update, I have a 5624 with me, connected to the network with the exact same settings and works absolutely fine. When I switch back to the 5634 I just get no access again... Bizzare.

Got to be something different about this newer model..

3

Mitel MiVoice Business/MCD/3300 / Re: Mitel 5634 WIFI phone

« on: April 13, 2022, 05:39:30 AM »

You need a MiAccess account. If you have one of these, login and navigate to the Software Downloads section. In here search by catagory and go to WiFi appliances, you will find the WinPDM application for download and also the definition files you need to configure the WiFi phones.

4

SIP On Mitel / Mitel 5634 WiFi Phone Issue

« on: April 13, 2022, 05:35:25 AM »

Bit of a general query here but just wanted to see if this rang any bells for anyone.

Currently having a bit of an issue with setting up 5634 WiFi phones on a corporate WiFi network to connect to an external MBG. Basically the phone connects absolutely fine to the WiFi, picks up a DHCP lease absolutely no issues there but just wont connect to the MBG, screen showing "no access"

This would normally point to something blocking the traffic, but there is absolutely nothing that I can find thats restricting it. Running the teleworker network analyser from the WiFi subnet against the MBG returns that all required ports are open, including SIP UDP 5060, audio ports etc..

Taking this phone away from the corporate network, either on a hotspot or a home connection, the phone will work fine, which proves that there are no credential issues. Also if you setup a 5624 with exactly the same settings, this will connect fine on that WiFi network, it only seems to affect 5634's.

I guess my question is, does anyone know of any 'gotchas' with the newer 5634s or any settings on the device itself which may help the scernario when a 5624 with exactly the same settings would work? It almost suggests something NAT related but still need to look into that further

5

Mitel Software Applications / Re: NuPoint Supervised Transfer Query

« on: July 19, 2021, 09:07:59 AM »

Apologies mate I cant remember if I ever got to the bottom of it or not. Let me know if you do, will be useful to know!

6

Mitel Software Applications / Re: ACD silent monitor - MiCollab softphone

« on: March 22, 2021, 11:54:00 AM »

This didn't work for me. Dialing My FAC+agent ID from MiCollab gives me an error: "Call failed - The number was not recognised.". FAC is *321, agent ID for my test case is 1599. I can do it from a desk phone using the same login (Supervisor is also an agent).

Just remember, that any digits dialed greater than the extension value in micollab for the pbx node will insert the dial out value digit(s)

Ah yes, the old extension length gotcha. That did the trick, Gold star for you sir!

Thanks a bunch all whos posted here. Tried the workaround from Mitel along with changing the extension length in MiCollab to compensate for the FAC in the dial string and its worked a treat!

7

Mitel Software Applications / Re: ACD silent monitor - MiCollab softphone

« on: March 11, 2021, 12:40:52 PM »

Thought as much, thanks for the reply. They use ASC based call recording at the moment so I'll see if this is something we can implement.

8

Mitel Software Applications / ACD silent monitor - MiCollab softphone

« on: March 09, 2021, 09:49:28 AM »

Hi all,

Does anyone have any detail around ACD silent monitoring when it comes to contact centre setups where all ACD based agents are using MiCollab softphone and Ignite rather than Minet based deskphones? I have tested monitoring from softphone to softphone and it just doesnt work..

I have found some information which says its not supported however don't know if anyone else knows if there is a workaround or if this is a feature in development?

Thanks

9

Mitel Software Applications / Re: Micollab 9.2.104 CONNECT to WebRTC Gateway Failed

« on: December 17, 2020, 10:14:01 AM »

Ive never managed to get WebRTC working properly with MiCollab softphone yet. If anyone has some useful tips or links to helpful documentation that would be great.

Mitel's documentation on WebRTC is somewhat lacklustre

10

Mitel MiVoice Business/MCD/3300 / Re: mitel 6900 branding

« on: August 19, 2020, 09:44:44 AM »

Its all in the help files on the MiVB. Search for "Phone Applications Update"

Martin

11

Mitel Software Applications / Re: MiCollab NextGen on PC Softphone

« on: July 29, 2020, 09:56:27 AM »

If you are wanting users to have both a deskphone and a MiCollab softphone, with full functionality, status and call control etc then you will need UCC licencing. However if this is an on-premise deployment you will only need a UCC Entry license rather than a UCC Standard license as you wont require the teleworker licenses that the standard includes.

Relatively cheap if you are just doing this for a select few users as you just need to purchase UCC Basic to UCC Entry uplift licencing. A normal full user licenses these are classed as a UCC basic user from a license perspective.

If you want to work around it you can set the second device up with a full user license and then use a personal ring group, but I dont believe you will get the same sort of functionality as a multi-device group. I know you have the endpoints setup on the MiCollab server but are you not using the MBG at all? Is the MiCollab for internal use only?

I don't believe this to be a true statement. I have full functionality and am not using UCC licenses as they are less limited on calling a group member direct

Fair point, I know you can use MiCollab etc with full I just wasn't aware you could get the same functionality as a PRG through MiCollab rather than using a multi-device user group. Or as cost effective due to the fact that he isnt using multi-device licenses this will be consuming 2 full licenses for the deskphone and softphone devices rather than having 1 multi-device user license using UCC. Anyway if it works the same its good to know!

12

Mitel Software Applications / Re: MiCollab NextGen on PC Softphone

« on: July 15, 2020, 09:13:23 AM »

If you are wanting users to have both a deskphone and a MiCollab softphone, with full functionality, status and call control etc then you will need UCC licencing. However if this is an on-premise deployment you will only need a UCC Entry license rather than a UCC Standard license as you wont require the teleworker licenses that the standard includes.

Relatively cheap if you are just doing this for a select few users as you just need to purchase UCC Basic to UCC Entry uplift licencing. A normal full user licenses these are classed as a UCC basic user from a license perspective.

If you want to work around it you can set the second device up with a full user license and then use a personal ring group, but I dont believe you will get the same sort of functionality as a multi-device group. I know you have the endpoints setup on the MiCollab server but are you not using the MBG at all? Is the MiCollab for internal use only?

13

Mitel Software Applications / Re: MiCollab Chat Sync

« on: June 17, 2020, 04:11:04 AM »

Ideally you want to get your MiCollab environment updated to the latest release (9.1) which will allow you to connect with the Mitel cloudlink service. This is a free service which will be enabled for all your MiCollab users when configured.

Once done it will use cloudlink as the chat provider and means that all messages and chats will be synced and available across all MiCollab devices and makes for a more seamless experience.

Another benefit of v9 is that there is more resilience if your MiCollab server fails. MiCollab client can still get past the initial loading page now if the server connection is unavailable and register the SIP device for call functionality if the MBG/MiVB is still available. Cloudlink chat will also still be available if there are MiCollab issues.

14

Mitel Software Applications / Re: MiCollab Mobile Client

« on: May 11, 2020, 06:31:26 AM »

The mobile app is built so that even if the app is closed down in the background it will still work. If you want to stop calls coming through to your MiCollab client you need to do this within the app rather than just closing it down. You can do this through the call flow settings in the status or just switch your softphone off from within the app.

You can control how MiCollab behaves with native calls on your mobile phone by going to settings > call settings. This should show you some native call settings.

Martin

15

Mitel Software Applications / Re: MiCollab Calendar Integration w/Exchange 2016

« on: May 04, 2020, 02:43:44 PM »

I believe the calendar integration also relies on what type of authentication you use on the exchange server. Do you know what you have configured?

Some exchange deployments dont support one of the older protocols MiCollab uses.