Thursday, May 26, 2016

Aastra BusinessPhone Management Suite (BMS) on Internet Explorer 11

One cannot go back to Internet Explorer 10 on Windows 8.1. Internet Explorer 11 is the default web browser for Windows 8.1. However, it is possible to use Internet Explorer developer tool and use Internet Explorer 10 on Internet Explorer 11 by following these steps:

1.       Open Internet Explorer 11
2.       Press F12 on the keyboard
3.       Click Emulation button or press Ctrl + 8.
4.       Under Mode change “User agent string” to Internet Explorer 10.
5.       You can use IE11 as IE10.

BMS will still give runtime issues so just add the site 127.0.0.1/smt to the compatibility list:
http://windows.microsoft.com/en-in/internet-explorer/use-compatibility-view#ie=ie-11

Contributed by Burkhard Conrad

Setting compatibility:
Whilst still in emulation menu, enable top left icon "persist emulation settings".
IE settings -> Compatibilty -> Add 127.0.0.1 

Sunday, May 15, 2016

Polycom SoundStation IP 5000 on Mitel MX-ONE 6.1

On Polycom:
To ensure there is no conflicting existing config:
Menu -> Settings -> (Password = 456) -> Admin Settings -> Reset to Defaults -> Reset Local Configuration
Menu -> Settings -> (Password = 456) -> Admin Settings -> Reset to Defaults -> Reset Device Settings

Whilst booting, select "Setup" key:
Password = 456
DHCP Menu -> Boot Server = Static
DHCP Menu -> Boot Server = FTP
DHCP Menu -> Server Address = 0.0.0.0
Save and reboot 

On Polycom:
Menu -> Settings -> (Password = 456) -> Admin Settings :-

CALL SERVER CONFIGURATION
Server 1:
  • Address = MX-ONE Server IP addres
  • Port = 5060 (or SIP signalling port)
  • Register = Yes

Server 2: Unchanged

Outbound Proxy:
  • Address = MX-ONE Server IP addres
  • Port = 5060 (or SIP signalling port)

Save changes

LINE CONFIGURATION
Line:
  • Display Name = Boardroom (or any other preferred arbitrary string)
  • Address = 4583 [Auth user name (usually extension number)]
  • Label = 4583 [Extension number]
  • Line Type = Private
  • Third Party Name =  4583 [Auth user name (usually extension number)]
  • Line keys = unchanged
  • Server1 = unchanged
  • Server2 = unchanged
  • Authorization:
    • UserID =>  4583 [Auth user name (usually extension number)]
    • Password = blank (unless set)
Save changes

Mitel MiVoice MX-ONE Programming:
extension -c -d 4583 --third-party-sip-client yes

Wednesday, April 27, 2016

IPLU telnet

As found at http://www.tek-tips.com/viewthread.cfm?qid=1603923

root / root123

Wednesday, April 13, 2016

Exit remote desktop (RDP) without leaving local PC locked

From command prompt:
query session
Exit command prompt

Use the Session ID (in the example below, ID = 2), and in Windows Run:
tscon.exe 2 /dest:console

!Update: A neat script to automate this is found at https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/keeping-computer-unlocked.html

Thursday, February 11, 2016

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

Thursday, January 28, 2016

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.

Monday, January 11, 2016

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