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.