Howto:Mitel 6940 - Mitel - 3rd Party Product
Product name
Mitel 6940
Disclaimer
This document describes results of interoperability tests performed by innovaphone as of October 2026.
The information shared below exclusively refer to the specified model 6940.
All results and configuration steps refer to below given firmware versions.
Tests were performed one-time by use of a rental device. No regression testing is done.
Compatibility with other models or versions is not guaranteed.
No warranty is given regarding the accuracy or completeness of the information.
No technical support for setup, configuration or troubleshooting is provided.
Category
SIP hardware and software endpoints
Version
Product versions used for interop testing:
Mitel 6940
- Firmware Version: 6.3.0.2043 and 6.4.0.2009
- Firmware Release Code : SIP -> Basic requirement is that the Mitel 6940 runs the SIP firmware!
- Boot Version: Boot2 2.1.0.2 May 21 2020 01:06
- Platform: 6940 , Rev: 08000FC1D968
innovaphone PBX
- innovaphone IP3011
- Firmware Version: 16r1sr5 (16.1.1009)
- Bootcode: 1610393
- Hardware: 200
Note:
Mitel devices do not use the reverse negotiation mechanism, and some RFCs are not implemented in the phone.
Use of functionalities such as queue calls, blind transfer from/to the Mitel device require at least PBX firmware version 16r1sr4.
Functions
Registration
Global SIP Settings
- The Mitel 6940 can be registered using the following Global SIP settings:

- The Mitel 6940 cannot be used in combination with SIP TLS with reverse proxy. See #Known Issues.

- The Mitel 6940 can be used ONLY with SRTP SDES or unencrypted voice. DTLS is NOT supported by the Mitel 6940 .
Line Settings
- The following settings must be configured for Line 1:
- Phone Number (the user's number in the PBX)
- Authentication Name (the user's Hardware ID in the PBX)
- Password (the user's password in the PBX) -> Alternatively, the PBX password can be used here; in that case, PBX PWD must be checked at the Hardware ID in the user object
- Proxy Server + Port (5060) -> either the system name or the IP address of the PBX
- Outbound Proxy Server + Port (5060) -> DNS name or IP address of the PBX
- Registrar Server + Port (5060) -> DNS name or IP address of the PBX

- The Mitel 6940 supports the SIP Digest Replay Check mechanism. However, if registration does not work, it may be worth checking this. A successful registration should look like this in the PBX logs:

- The SIP Digest Replay Check mechanism can be disabled. However, this is NOT recommended!
innovaphone User Settings
- The user in the PBX must have the following attributes:
- Long Name
- Name
- Number
- Password
- Hardware ID (identical to the Name field)

BLF / Busy Lamp Field
- BLF is configured according to the mechanism described and works out of the box
- On the phone, create a softkey of type "BLF"
- Enter the number of the user to be monitored as the value. Label and line can be chosen freely

- If everything is configured correctly, it looks like this on the phone:

Call Pickup
- Call pickup must be implemented using DTMF feature codes within the PBX
- To do this, create a DTMF Features object in the PBX. You can either change the feature code for "Directed" or leave it as is (the default code is *0*$# )
- "Autocomplete #" MUST be enabled here! The Mitel 6940 removes a # at the end of a number when dialing, so the feature code could never be triggered by key press otherwise.

- When a call comes in for a partner, it can be picked up with a speed dial softkey. Its value must be set to " *0*partner's extension ":

- Ideally, use one softkey for BLF to see whether a partner is being called and one softkey to pick up that call
- For pickup via DTMF features to work, the users must be active members of the same group

3-Party Conference
- Works natively without issues (regardless of whether an innovaphone phone or the Mitel 6940 initiates the 3-party conference)
- The Mitel 6940 has a "Conference" button to start a conference once you are connected to two parties

Hold & Retrieve / MOH
- By default, no MOH is played when the Mitel 6940 puts a call on hold.
- This must be adjusted in the PBX so that MOH is no longer sent by the device but directly by the PBX
- The relevant parameter is: /take-sendonly-as-inactive on
- It is written to the config with the following command (depending on the registration protocol used):
- !config add TSIP /take-sendonly-as-inactive
- !config add SIP /take-sendonly-as-inactive
- !config add SIPS /take-sendonly-as-inactive
- With this, MOH works when a Mitel 6940 puts a party on hold
Call Transfer
- Works without further configuration
- Blind transfer works as of 16r1 SR4
Call Forwarding
- Setting it on the Mitel 6940 works without issues
- Call forwarding is only set locally and is not written to the PBX, i.e. there is no global call forwarding for all devices.
Call Waiting
- Works without further configuration
Voicemail
- Works without further configuration
Known Issues
- For registration of Mitel 6940 SIP/TCP only was used. In principle, TLS support is given but requires upload of custom certificates or a trust list.
During internal testing, we did not find any further information on how handle certificates and also do not have any knowledge on this.
- The Mitel 6940 can be used ONLY with SRTP SDES or unencrypted voice. DTLS is NOT supported by the Mitel 6940 .
- SIP TLS registration via a reverse proxy is not supported