MX-ONE "Weak Diffie-Hellman key"

This occurs with the self-generated SSL certificate on the Mitel MX-ONE v5.0. To access with Firefox:

Workaround for Firefox 39 and above:
1) In FireFox, enter "about:config" in the URL field and press enter.
2) Accept the "This might void your warranty!" warning :)
3) In the search field at the top, enter "security.ssl3.dhe_rsa_aes"
4) Double click each result (128 and 256) to toggle the Value to "false"

Now retry your site - it should work now. Remember to change these settings back when you're done.

Re-blogged from https://support.mozilla.org/en-US/questions/1066238

MX-ONE and DBC 4224 not coming out of Night Mode

Had a recent problem with an MX-ONE using a DBC 4224 as an operator (a dated method, but the client's choice). The system was equipped with ELU33 and MGU2. Once programmed, the phone started fine and showed "Night Service".

Pressing on/off did not change the status though! Problem?

TMU resources on the MGU are not sufficient. A TMU card (e.g. TMU/2) is needed for a DBC4224 to work on an MX-ONE.

Teamviewer via 3G and LAN access

Normally, when a Teamviewer connection is established via 3G (or similar), it uses that as the default network route. So reaching anything via the LAN port seems impossible.

However, all that needs to be added is a default route for that specific destination.

Example: Wanting to reach host 192.168.2.10.

Run ipconfig in command prompt. Find your "Local Area Connection" default gateway (e.g. 192.168.4.1).

 route add 192.168.2.0 mask 255.255.255.0 192.168.4.1

Teamviewer 11 and openSUSE 42.1 (LEAP)

Reference URL: http://www.2daygeek.com/install-teamviewer-in-linux/#

Only step missing was adding the key. Therefore:

1. wget http://download.teamviewer.com/download/teamviewer.i686.rpm
2. Download the public key: http://www.teamviewer.com/link/?url=354858
3. rpm --import TeamViewer_Linux_PubKey.asc
4. zypper install teamviewer.i686.rpm

Note: My system already runs Wine. It too may be needed, but zypper should add it and other dependencies automatically.

Polycom IP 7000 on Mitel 470 (A470)

First off, default password is "456" for Admin.

Note that you should configure either via Web or via Local Menu. To ensure no clashing config exists:

Menu button -> Settings -> Advanced -> Admin settings -> (5) Reset to default:
Choose (1) Local config and (2) Device setting.

After reboot:

Menu button -> Advanced -> Admin settings -> (2) SIP Config:

(This could be "(2) Line Configuration" on some software versions)
Server:
Address = PBX IP
Port = 5060
Transport = TCP Preferred
Register = Yes

Outbound Proxy:
Address = PBX IP
Port = 5060
Transport = TCP Preferred

(This could be "(3) SIP Server Configuration" on some software versions)
Line:
Display name = Boardroom (your choice)
Address = SIP Auth name
Label = Extension number
Type = Private
Third party name = SIP Auth name
Auth user ID = SIP Auth name
Auth password = 1234 (password for that SIP user on the PBX)

(!For simplicity, I changed the SIP Auth name to equal the extension number. And simplified the password)

After reboot, the top left "Polycom star" will be solid if registered and outlined if not registered.

Traceroute from Mitel MVO 400 (Aastra A470)

The MVO 400 allows one to ping from a telnet login, but no traceroute is provided. Fortunately, you can create a "manual" traceroute:

By starting the TTL at a low value and slowly incrementing, the respective gateways reply that the host is unreachable. It is exactly what the utility traceroute does - only slower and more resource intensive.

ping host-ip -t x

e.g.

ping 12.34.56.78 -t 1
ping 12.34.56.78 -t 2
...
ping 12.34.56.78 -t 10

Repeat until reply is that the host is reachable.
Compare https://nmap.org/book/nping-man-probe-modes.html

SNOM TAPI with xtelsio and Mitel 470 pin code

This is regarding the MiVoice Office 470, but can apply to others:

Using xtelsio, it is possible to have a TAPI interface for the SNOM phone direct. However, if the user is locked for pin usage it may be difficult to call out. Set the following:

1. Xtelsio for SNOM Configuration -> Settings Tab -> Format Phone Number -> Prefix 0 Replace with 622001234  -> OK
[Where 6 is speed dial for #46, 2200 is the extension, 1234 is the pin]
Remember that #46 adds the 0 automatically.

2. Reset...

3. Use LW64.exe to test the TAPI interface. (http://www.tapimaster.eu/en/Download/64Bit/Tools/LW64.EXE)
Enter 00812345678 and select "make call". Will show the 6220012340812345678 number being dialed.