Although Aastra phones are not supported by 3CX, it is still possible to have them register remotely with the 3CX via a tunnel. To do so you will need the Session Border Controller Software (if using 3CX v12) or SIP Proxy Manager (if using 3CX v11 or lower). Once the tunnel between Session Border Controller or SIP Proxy Manager and the 3CX has been has been established, you will need to configure your Aastra phone to register with the 3CX via the tunnel.
To do so go to Advanced Settings and select a line to configure (Line 1 – Line 9). In this example I am configuring Line 5.
Under ‘Basic SIP Authentication Settings’ section enter the extension’s credentials as they have been setup in the 3CX.
- The Phone Number is the extension number in the 3CX
- The Authentication Name is the 3CX authentication ID
- The Password is the 3CX authentication password
If you are unsure of these details please check them in the 3CX to ensure you enter the correct details.
In the ‘Basic SIP Network Settings’ section enter details of the Session Border Controller (SBC) or the SIP Proxy Manager (SPM).
- The Proxy Server is the IP address of the SBC or SPM device
- The Proxy Port is 5060 by default. Please use 5060 unless you have specified a different setting in the SBC or SPM.
- The Outbound Proxy Server is the IP address of the SBC or SPM device
- The Outbound Proxy Port is 5060 by default. Please use 5060 unless you have specified a different setting in the SBC or SPM.
- The Registrar Server is the IP address of the SBC or SPM device
- The Registrar Port is 5060 by default. Please use 5060 unless you have specified a different setting in the SBC or SPM.
Once you have entered the above information and saved your changes, your phone should now be registered via the Tunnel.
If you are having issues and the phone is not registering you can restart the 3CX Phone System SIP/RTP Tunneling Proxy Service on the 3CX itself. Then if necessary you can restart the service in SBC or SPM and finally restart the Aastra phone. Your phone should now be registered via the tunnel.
I have tested this with the Aastra 6757i, 6757i CT and 6753i models on both 3CX v11 (SPM) and 3CX v12 (SBC). All models I’ve tested seem to work without any issues on 3CX v11 (SPM).
I have noticed a few issues in 3CX v12 (SBC)..
ISSUE: The first, with registrations being lost when 3CX services are restarted in the management console.
FIX: Rebooting the phones after services have completely restarted seems to overcome this issue.
ISSUE: The second issue, with registrations being lost randomly throughout the day. You can try to overcome this by enabling keep alives in the 3CX Management Console > Settings > General Settings > Global Options but it doesn’t always work. I am still trying to find a resolution to this issue. It not only occurs on Aastra handsets. I have the same issue on the Cisco 509G. It seems to be a global issue rather than an issue solely related to Aastra handsets. I will keep you posted.
FIX: Since updating to 3CX v12 SP6. This issue no longer exists
ISSUE: The third issue, with one way audio on the 6757i and 6757iCT. Calling party has audio but called party does not.
FIX: I found that this issue was particularly related to the 3.2.x Aastra Firmware. I downgraded the firmware version on both models to 2.6.x and it resolved my audio issues. Note the following comments from a community forum (http://pbxinaflash.com/community/index.php?threads/how-do-i-downgrade-aastra-firmware.11551/)
”the 3.2.x is still buggy enough that the 2.6.x series is preferable”, Oct, 2011
Even in 2014, this 3.2.x firmware remains buggy.