Search results for query: *

Yes, the solution is to make sure the Online URLs form does NOT have the avatar link (from he MiCollab) applied. If it's there, the phones apparently have an issue with delayed performance dealing with the avatars. If you don't have avatars set, then don't worry about it. Supposedly there's...

Anyone experience this issue where then you dial a number, whether extension or phone number, the DTMF digits outpulsed by the phone over the speaker are out of sync with the physical key presses? Worse, they seem to stop and then burst out in batches instead of steadily sounding out the...

@richgraham I populated the Online Service URL avatar field with same URL from the Enterprise tab on MiCollab and it worked. Maybe check your IP routing to make sure the phones can see the MiCollab server without any problems.

That's a good point and the funny thing is, another user here on AT&T Wireless is able to get extension info, but not the Verizon user.

We've had this issue for some time and still not sure of the cause. We're on MiVB 8.0. The issue is related to Dynamic Extension, whereas when an internal call is made to the DE extension in question via its extension #, the cell phone gets "Restricted" as the Caller-ID even though the COS has...

We've got both on a Windows 2012R2 server and the phones only came up after adding Option 43. Are you using the controller's DHCP? Because that works fine with Option 125.

OK, figured it out! YOU MUST USE OPTION 43 I added Option 43 to our MS Server 2012R2 scope and bingo, phones came up. Nothing that I could find in the documentation specified that you can't use option 125 for the new 6900 series phones.

Yeah it's driving us nuts. The phone gets DHCP, hangs at Contacting RCS, then blows through saying TFTP error and then Contacting Server 0.0.0.0 No static options are assigned but if we do assign the controller's IP as TFTP and Call Server, phone works just fine. Our DHCP works for all other...

I have a 6940 at my desk ready to be deployed but despite upgrading to MiVB 8.0 I'm getting a failure of the phone to get its firmware from the controller. Are there special settings in DHCP that are required for these new phones that are different from the usual 53xx?

Yes, we have a problem right now with Windows 10 and a specific Windows update that kills the ability to log in to MiCollab. The 'fix' is with a custom registry entry but would be fixed if we got the MiCollab Client upgraded. We're hoping that happens by the end of the week to see if this...

That's the plan, soon. However, this started happening some time after we were on this version. I'm guessing it has more to do with the LG in this case.

Using an LG G3 on Android 6.0 with MiCollab Client connected to a dedicated MiCollab server running 6.0.505.24722 for Android to a MiVoice Business 7.2 SP1 PR1. Problem is within the MiCollab app, everything works fine except for the real time status of users. Can't see online/offline...

We're running MiCollab with Voice virtual (7.0 SP2) with MiCCM (7.1.2) and agents are running the Salesforce Connector and using the MiCollab Client as their softphone/audio device (with Jabra Pro USB headsets). Issue we're having is after a call is completed and the agent is in wrap up mode...

The only post I found was this: http://www.tek-tips.com/viewthread.cfm?qid=1386078 But it's related to changing out from Spectralink files...

OK thanks. I'm trying to avoid having to connect a laptop to a phone to playback the greeting file for best audio... If you find those instructions let me know and I can poke around.

Is it possible to upload the company's main auto attendant greeting (EMEM) via FTP once it's been converted to the right WAV format? Thanks!

OK thank you. Our application is a bit different in that during the day, calls should ring multiple phones and only in Night should they hit the auto attendant night greeting. However, sometimes they want to throw the system in Night but play a "day" greeting that doesn't specify that they are...

Thanks all. I verified that the station timer is shorter than the VM ports timer, so it looks like kwbMitel may be correct. *501 is a Name Tag Hunt Group that points to 600 which is the VM hunt group to end up in mailbox 501. It's not an MLAA however. From there dialing the extension number...

We're having an issue where when the system (MCD 5.0 SP2 R1) is in night mode, calls (enter extension #) transferred from the auto attendant (EMEM) ring the station but then return to the auto attendant and never hit the user's mailbox. The system says it's transferring, plays the name, rings...

Does anyone know if there's a way to have CPN Substitution with a PRI connected to the Mitel 5000? Thanks!