Messages

886

Mitel MiVoice Business/MCD/3300 / "People" key on 5360 handsets

« on: February 23, 2016, 06:57:34 PM »

We've upgraded some phone users to use 5360 phones. They've discovered a key called "People" on their new handsets and discovered it has nothing in it.
We read the manual and told them it says they have to manually go into the key and add people if they want this button to do something useful.
 
They were a bit taken aback and told us they had already populated extensive Contacts lists in the corporate telephone directory on the MCD, via AD, as well as additional personal contacts in the MiCollab application, and are we seriously telling them to manually create a list that already exists in MiCollab?
 
Is there any way the "People" button can draw its information from information that already exists?

887

Mitel MiVoice Business/MCD/3300 / Multicall Line on PA phones that are in Pickup Groups

« on: February 23, 2016, 06:51:08 PM »

I have a bit of an issue which I would like to put out to the brains trust.
I'm fairly new to telephony, so there could be something very obvious that I am overlooking.
 
So we have a boss and her PA.
The PA want to monitor the boss phone and answer her calls on behalf of the boss. Seems like an obvious requirement.
The Mitel doco says use a DSS key, so we gave the PA a DSS key to monitor her boss.
Then we discover that the DSS key only allows the PA to answer the boss's calls if the boss is not on the phone. If the boss is on the phone, calls to the boss go straight to VM, the PA doesn't get them. This is obviously not at all how a PA wants to work, so we realise DSS keys just aren't fit for purpose.
To make boss calls available to the PA we changed the key to a Multicall key, and configure it to ring.
Now, whether the boss is on the phone or not on it, the Multicall key on the PA phone rings and she can take the call.
Then we discover the Multicall key doesn't show if the boss is on the phone or not - if the PA takes a call, she has to put the phone down, then walk to the boss's office to see if she's available before going back to her desk. This setup is obviously just as rubbish as the DSS key.
So....we give the PA 2 keys - a DSS key so she can see if her boss is on the phone, and a Multicall key so calls to the Boss, when the boss is on the phone, don't go straight to VM.
This works, although they think it's a bodge because we're using 2 keys for what they consider should be a very basic requirement built into one key.
 
OK, so now we have a pool of PAs, each responsible for her own boss.
The PAs are in a pickup group, because they want to be able to field each others' calls for non-boss-related work. They don't want to be picking up the Multicall key, only the other PAs' main extension.
However, when any PA's handset rings, the other PAs have no way to tell whether it's a call for the PA, or a call for her boss.
(For Example, a PA might be tasked with answering calls *only* if her boss is on the phone. The other PAs have no way of knowing if this is the case or not).
So the PAs are constantly using Call Pickup only to discover they have taken a call they shouldn't have and having to put it through to the other PA's boss anyway. That Boss gets cranky that she's had her phone ring twice for that call.
 
Ideally, the way to fix this would be to have Multicall keys use a different ringtone. This doesn't appear to be an option.
 
Have I missed something obvious here?

888

Mitel MiVoice Business/MCD/3300 / Re: MXE III Question

« on: February 22, 2016, 12:15:42 AM »

Change the Putty "Connection type" to "serial".

889

Mitel MiVoice Business/MCD/3300 / Re: DHCP Help

« on: January 14, 2016, 07:36:38 PM »

You're probably much better off having a separate subnet per campus (small sites), per building (small buildings) or per floor.
 
The best design uses the following concept as a rule of thumb: the fewest numbers of subnets per switch, and the fewest switches per subnet.
 
This greatly facilitates operational management, change management and has the additional benefit of protecting different geographical areas from each other in case of network issues occurring at one site.
 
I always use 10. addresses to give myself maximum space. (I can't understand why anybody wants to use 192.168 or the 172.16 addresses).
 
I make the 2nd octet synonymous with a campus, then the 3rd octet synonymous with a building within that campus, or, for large buildings, a string of subnets running up the building.
For example, one hospital network I did had multiple 7--storey buildings on one campus, with 2 subnets per floor (East v. West)plus an old 1940s campus which was one huge sprawling single-storey building with about 32 subnets on it, one per wiring closet.
 
(I don't make the mistake of using the second octet to differentiate between services - that makes route summarisation impossible).
 
So I end up with a scheme like:
10.10.0.0/16 = Campus A
   10.10.10.0/24 = Building A, Ground, East
   10.10.11.0/24 = Building A, Ground, West
   10.10.12.0/24 = Building A, Lvl1, East
   .
   10.10.28.0/24 = Building B, Ground, East
   .
   10.10.45.0/24 = Building C, Ground
10.20.0.0/16 = Campus B
   10.20.10.0/24 = Porter
   10.20.11.0/24 = Store
   10.20.12.0/24 = Pathology
   10.20.13.0/24 = Renal
   10.20.14.0/24 = Oncology
   .
10.30.0.0/16 = Small Country Hospital A
   10.30.1.0/16 = Comms Room A
   10.30.2.0/16 = Comms Room B
10.40.0.0/16 = Clinic A
etc...
 
There really isn't any benefit to trying to cram as many geographically dispersed devices as possible onto the same subnet, and many drawbacks. There is no drawback to creating many multiple subnets each only using 20 devices.

890

Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 LAN Policy (QoS) question

« on: December 06, 2015, 10:31:32 PM »

Signaling doesn't matter so much - it's TCP and latency isn't very important.
The most important QoS is for the actual voice traffic. For internal calls, this is set by the phone on each voice packet it sends, and should be set as DSCP46. L2P should be set to match whatever the network uses - Mitel like to use 6, but a Cisco network will by default be setup for voice to use 5, whereas an HP network uses 6. This is set in the DHCP option.
The controller will have to be setting QoS for packets coming from the far end of an external call coming in off the PSTN. You set this on your LAN policy form. Set it the same as the QoS is set for the handsets.
Bear in mind some networks might ignore what the handsets and controller are setting and might have policies to re-mark all traffic.
 
It might be useful to find out what kind of calls were affected - Internal, or External, or both?

891

Mitel MiVoice Business/MCD/3300 / Re: UC360 Factory Reset

« on: November 24, 2015, 07:49:20 PM »

**UPDATE**
Ok so I reached out to Mitel and they said that no one has ever asked this question. Apparently I was the first. The Mitel guy asked his engineering group and they said to do this: (See Picture)



I have done this and it worked like a champ! Though one wonders why this is not in the manual.

Thanks,
-Iron

Awesome - and here was me foolishly going through the EG & and Admin & UG thinking RTFM would be the solution....
 
Thanks for this. My headache is gone.

892

Mitel MiVoice Business/MCD/3300 / Re: Help!3300 Failover

« on: October 08, 2015, 09:14:15 PM »

1-2 other things to check on the new switches - check for loops as well as pre-set the speed/duplex of the ports going to the 3300's. Sometimes they switches don't auto-detect properly and cause random issues.

This is definitely the troubleshooting path I would be thinking about - if the switchports are showing errors, and if the errors are indicative of a duplex mismatch, you should ask the network guys to change their end to auto/auto, and double-check all the Access ports that phones are on at the same time.
 
What can happen is that the switchports see lots of errors and occasionally reset themselves, giving you a brief outage.

893

Mitel MiVoice Business/MCD/3300 / Re: Help!3300 Failover

« on: September 30, 2015, 02:26:41 AM »

Ask them to check the switch logs and the switchport error counts for the switchports that controllers are attached to.

894

Mitel Software Applications / Re: UCA Client - Request Playback Call

« on: September 23, 2015, 02:29:17 AM »

Yes, but I had to go back after doing the dialler, and it works!
Summary:
-       Create 4 numbers on the controller
-   Create a Line Group “2” for “Outbound dialler” calling it “Message Playback”, save
-   Give Line Group “2” 4 ports linked to the controller numbers, save
-   Create a Dialler “0” called “Message Playback” with a blank access code, save
-   Back into Line Group “2”, “Dialler” tab and tick the “Message Playback” dialler just created, save
-   Commit then activate.

895

Mitel Software Applications / Re: UCA Client - Request Playback Call

« on: September 21, 2015, 07:36:22 PM »

I'm having the exact same issue.
(NuPoint with MiCollab)
I can't see any "Call me" phone number on the mailbox. In any case, with a few hundred mailboxes, I'm hoping for an answer that doesn't involve editing individual mailboxes...

896

Mitel Software Applications / Re: MiCollab Single Point Provisioning user roles/keys

« on: September 15, 2015, 10:38:38 PM »

My team recently tried this, by trying to match up the names as you refer to, but without luck.
 
We would love to know how to make single-point provisioning tie in to a defined handset template.

897

Mitel Software Applications / Leading "0" not being added in MiCollab client

« on: August 18, 2015, 04:58:32 AM »

OK, this is driving me crazy - I know it's here somewhere: where do I configure the MiCollab client to always use an extra "0" when dialling an external contact?
I've found it before but not anymore...

898

Mitel Software Applications / Firing up MiCollab chat session from a link in a web page

« on: August 02, 2015, 08:36:21 PM »

The following Microsoft Technet article describes how you can fire up a Lync chat session from an embedded link:
https://technet.microsoft.com/en-us/library/gg398376(v=ocs.15).aspx
 
example:
im:<sip:user1@host><sip:user2@host>

I'm wondering if anybody has found the best equivalent to do this with the MiCollab client?
 

899

Mitel MiVoice Business/MCD/3300 / Re: activate call waiting

« on: July 24, 2015, 12:56:24 AM »

"Automatic camp-on is only supported for phones without softkeys, ONS stations, and trunks."

Its not possible on sets with softkeys. That is from the help file.

Can I just get this clarified: does "automatic camp-on" mean the same thing as call waiting?
 
What I would normally expect is that an incoming call to a busy handset is alerted on the handset as a "call waiting" for a short period to give the handset user the opportunity to place his 1st call on hold and answer the 2nd call.
 
Are we saying this is not possible in an environment with 5300-series handsets using MiCollab?