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.

BusinessPhone IPU repair

Recently I had an IPU that would not read from the Compact Flash.

Symptoms:

• "Voice Channel Licensing" and "Board Configuration" did not show.
• Boot and Application image were R3A
• Telnet into IPU and cannot change to "/cf0"

The problem is that the cards are old stock and the default Boot Image (R3A) does not read from 1GB Compact Flash cards.

Solution:

• Any 32MB Compact Flash can be loaded with IPU Boot and Application Images. (Even an old MFU CF can be used. No need to remove the existing structure / .ULK files unless space is needed. This way the card can be reused for MFU again)
• Insert IPU into system with CPU-D5
• Cold start system
• Once started, remove cold start strap and program an IP on the IPU.
• Shut down and restart the IPU.
• Once started up, telnet into the IPU
• Upgrade the IPU Boot Image.
• Restart the IPU and confirm the Boot Image has been upgraded
• Switch off system, insert original (1GB) CF
• Cold start system
• Export license

MiVoice 400 SIP trunking one-way audio

In this scenario we connected an NEC SL1000 to a Mitel MiVoice 400 (A470) via SIP trunks. In the office environment it worked well.

On site we could establish calls from both directions, however there was one-way audio when placing a call from the NEC to the Mitel.

After much troubleshooting, it appears to have been the Fortinet Firewall, even though it appeared to have the SIP Helper disabled.

Below is the procedure to deactivate it (kindly provided by a support technician):

--Via CLI interface

config system settings
 set sip-helper disable
 set sip-nat-trace disable
end
--Reboot the fortigate device

--Remove the default-kernel helper entry for SIP

config system session-helper
 show           {//locate the SIP entry, usually 12 or 13, but can vary}
 delete [identified ID] {//the number that you identified from the previous command}
end
--Disable RTP processing as follows:

config voip profile
 edit default
 config sip
 set rtp disable
end--This should disable SIP Helper on most Fortigates, dependant on FortiOS version.

Ericsson BFYBS 10101/1 Door Interface Unit

To connect to an Intercom (e.g. and Aiphone IE-JA):
-Disconnect loudspeaker from the circuit board and connect direct to the Door Interface Unit (DIU) LS connector. There does not seem to be a polarity for the speaker.
-Disconnect the Switch from the circuit board and connect direct to the BELL connector on the DIU.
-Leave microphone connected to circuit board and connect the input of the intercom (back panel of intercom) to the MIC connector of the DIU. This allows the built in audio transformer of the intercom to be used by the microphone.
-Connect the extension to Ext A, program as a hotline and test.

Opensuse 13.2 and fatal error: Python.h: No such file or directory

When trying to install cx_Freeze with pip (pip install cx_Freeze) I got the above error.

Python-devel is installed and yet the error occurred!

Solution? zypper in python3-devel

612d Survey Mode and Factory Reset

Menu -> Settings -> General -> Administration -> Diagnostics

BusinessPhone to MX-ONE TSW via H.323

Should you be linking a MX-ONE TSW (may even apply to the TSE) to a BusinessPhone via IP, note the following:

BusinessPhone needs a "Own Location Code". e.g. 6504

On MX-ONE, you create:
RODDI:DEST=6504,ROU=xy,....;

The BusinessPhone needs it's own location code to be sent to it, so no truncation in the above example.

Note that the following will not work:
RODDI:DEST=2015,ROU=xy,TRC=4,PRE=6504,.....;

Even though the correct digits are being sent, the BusinessPhone rejects the call for some reason. Thus the DEST must equal the Own Location Code.

MiVoice 400 DoS Blacklist

Asstra 67xxi phones ceased to function for a while and then resumed working. Under Event Logs it showed the phone was Blacklisted (often repeatedly) for DoD reasons. The following seems to have fixed it:

Set the Keep Alive to 120 and registration timer to 3600. 

MiVoice 470 ISDN Dial up Access

1. Setup ISDN Modem
2. Mitel 400 -> Configuration -> Routing -> Select a DDI number

-> CDE = Remote management (SRM).

3. Create a user for Admin access or use existing user.

4. On Windows -> Create a VPN (Set up a connection -> Connect to a workplace)

-> Number = DDI number, user and password = as per that on the A470.

5. Connect. Use ipconfig /all to view assigned IP address.

6. Open a Web browser and enter the VPN IP of the PBX.

MX-ONE Number Presentation 2

On a client using a Primary Rate ISDN, the CLOP was incorrect because the circuit numbering "clashed" with the extension numbering:

- 3125xxx is the DID range.
- 5xxx is the extension range (thus no DID tables need to be setup)
- 31255xxx is the resulting displayed CLOP

number_conversion_initiate -conversiontype 1 -numbertype 10 -entry 5 -truncate 1

The above removed the extra 5 for each extension as they call out.

It is worth noting that:
1. I did not use RONDI.
2. I set the Public Exchange number (=312) and Common Public Directory Number (=312) in the Web GUI (MTS)