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

Pages: 1 2 [3] 4 5 ... 60
31
Hi,
Mitel 3300 has a VRS and all calls to the pilot number  are routed to VRS. once it will ask to dial the required extension number , i am dialing to Grandstream extension number . it will ring once to Grandstream and the call will return to Mitel.
thanks,
satheesh

Sounds like the number isn't being delivered in the required format.
Did you SIP trace the call to see what number you are sending? Does it match the right number in the Grandstream directory?
Have you investigated various non-numeral characters that can modify the number, eg # at the end?

32
You need to add them to MiCollab.
I think with the latest version of MiCollab they get added from the Controller automatically, as long as they have a Username.

33
You can also use Business Schedules to create different Re-Routing destinations for differernt times of day.
 
As Ralph says, you should always use a Speed Dial, not put the real number in there.

34
Where should external calls be routed? Are you routing them there?
 
What digit mod do you have on this route? Does it deliver the number dialled in the correct format?

35
Or you could fix your routing so redirects aren't being sent.

36
They should Disable the AD accounts for a period.
Once disabled, the next LDAP sync from the MiCollab and the user will appear in the IDS detained list as a "D" record which you select and save which de-provisions them from the phone system.

37
The 3300 is programmed to auto-reboot when the CPU reaches threshold.
If somebody set this threshold too low, or if the CPU is going nuts for some reason, that might explain why it reboots.
 
We've had this with the root cause being faulty memory. The faulty memory was creating database corruption and the database corruption was causing high CPU.
 
I'd be worried that Mitel are suggesting "ping tests". Sounds like they have a long way to go before they reach the meat of the issue.
Depending on how many users are on the box, a few tens of thousands of SDS errors would cause this.

38
The out-of-the-box reliability of the 6930 is about 10x better than the 6920, and they only cost a tiny bit more.

39
Mitel MiVoice Business/MCD/3300 / Re: Web interface not accessable 3300
« on: October 24, 2019, 07:34:12 PM »
...except the phones are registered and working.
 
Check the phones to see what their IP address is and what the IP address of the controller is that they are registered to.
 
Then check your network to see how to get connectivity to that IP address.
 

40
Get a 6930 with a Bluetooth handset.
Minimum 3300 v8 to support 69xx phones.
 
Get a Mitel 112 DECT phone.

41
The new MiCollab Client seems to be pretty much aimed at the mobile phone app market. You wouldn't want multiple popups on your mobile I think.
Not sure what they think corporate users of MiCollab are supposed to think - maybe Mitel are writing off that market to Teams? That's a shame really, because MiCollab Client 7.3 was a *lot* better than Skype.

43
With that change of CoS option, there should never be any ringing from a second call.

44
Mitel MiVoice Business/MCD/3300 / Re: MXeII emergency replacement with MXe?
« on: September 22, 2019, 11:49:21 PM »
Could be a good opportunity to move away from hardware and build it as a virtual server instead?

45
Mitel MiVoice Business/MCD/3300 / Re: ASU used to replace Peripheral Nodes!
« on: September 19, 2019, 01:22:09 AM »
ASU provides 24 ports that act as analog ports just like the 4 in-built ones on the MXe.
 
It consists of a 1 RU 24-port patch panel, connected to a 2-RU ASU which connects to a CIM port on the MXe.

Pages: 1 2 [3] 4 5 ... 60