Aastra 6700i Installation Instructions Manual
  1. Manuals
  2. Brands
  3. Aastra Manuals
  4. Touch terminals
  5. 6700i Series
  6. Installation instructions manual
Aastra 6700i Installation Instructions Manual

Aastra 6700i Installation Instructions Manual

Sip terminals for mx-one
Hide thumbs Also See for 6700i:
Table of Contents

Advertisement

Quick Links

Download this manual
INSTALLATION INSTRUCTIONS
26/1531-ANF 901 14
E10
2014
01
22
Aastra 6700i SIP Terminals for
MX-ONE
Amiler
Amiler
Arne Miler
amiler
INSTALLATION INSTRUCTIONS

Advertisement

Table of Contents
loading

Related Manuals for Aastra 6700i

Summary of Contents for Aastra 6700i

  • Page 1 INSTALLATION INSTRUCTIONS 26/1531-ANF 901 14 2014 Aastra 6700i SIP Terminals for MX-ONE Amiler Amiler Arne Miler amiler INSTALLATION INSTRUCTIONS...
  • Page 2 The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Aastra shall have no liability for any error or damage of any kind resulting from the use of this document.
  • Page 3 Some expressions in this document follows the expressions used in MX-ONE, which can differ from the expressions used in the Adminis- trator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones. Table 1 Expressions used in MX-ONE and in 6700i documents...

  • Page 4: Environmental Requirements

    6700 SIP T MX-ONE ASTRA ERMINALS FOR Environmental Requirements See Administrator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones. 26/1531-ANF 901 14 Uen E10 2014-01-22...
  • Page 5 ABLING Cabling See Administrator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones. 26/1531-ANF 901 14 Uen E10 2014-01-22...

  • Page 6: Power Equipment

    6700 SIP T MX-ONE ASTRA ERMINALS FOR Power Equipment These telephones can be powered from any of the following methods: • 6730i is powered from an AC adapter 5V. No PoE support. • 6731i, 6735i, 6737i, 6739i, 6753i, 6755i, 6757i are powered using PoE according to IEEE 802.3af or from an AC/DC adapter 48 V.
  • Page 7 ARTHING AND ROUNDING Earthing and Grounding See Administrator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones. 26/1531-ANF 901 14 Uen E10 2014-01-22...
  • Page 8 6700 SIP T MX-ONE ASTRA ERMINALS FOR Setting up the Software Server The software and the configuration files used by the IP phones shall be stored on a server where the IP phones can fetch them. The server is called IP Phone SW Server. Manager Telephony System Telephony Server...
  • Page 9 ETTING UP THE OFTWARE ERVER • Reconfigure Microsoft IIS web server, if it exists. • Creating a directory structure on the IP Phone SW Server. • Copy the IP phone application and language files to the IP Phone SW Server. The configuration files shall not be copied, these are created by MTS.
  • Page 10 6700 SIP T MX-ONE ASTRA ERMINALS FOR Click OK. The window Welcome to the IPPhone SW Server Setup Wizard is displayed. Click Next. The step Licence Agreement is displayed. Click Agree. The step Tomcat Port Number is displayed. Type the port number in the field, default port is 80. Click Next.
  • Page 11 ETTING UP THE OFTWARE ERVER The reason that you need to have the Tomcat web server running instead of just using the IIS web server is that the IP Phone SW Server Configuration Management Application is developed in Java and IIS can only host web applications developed in the Microsoft environment.
  • Page 12 6700 SIP T MX-ONE ASTRA ERMINALS FOR – Open C:\WINDOWS\system32\inetsrv\inetmgr.exe, navigate to Default Web Site. – Right click on Default Web Site and select New Virtual Direc- tory. A wizard will start. – Enter the directory name to where the telephone firmware shall be stored as Alias, example: aastra67xxi.
  • Page 13 ETTING UP THE OFTWARE ERVER Start of the Tomcat Web Server During the installation of IP Phone SW Server Configuration Manage- ment Application for Windows®, Tomcat will start automatically on port 80. In case Tomcat is not up and running, it can be started manually with Windows®...
  • Page 14 Manager Telephony System MX-ONE Manager Telephony System (MTS) shall be used when creating or changing the aastra.cfg and the model specific configuration files. The information regarding parameters is available in the online help for MX-ONE Manager Telephony System. The picture below shows an...

  • Page 15: Create A Configuration File

    Go to Telephony > IP Phone > Configuration file. Press Add new to open the new configuration file. Make sure that Aastra 67xxi family is selected and enter the data into the configuration file which is automatically stored under the correct directory in the IP Phone Software Server when pressing Apply.
  • Page 16 Scratch Pad when Creating the Configura- tion file If a new parameter has to be added into the aastra.cfg file but there is no support for this new parameter in Manager Telephone System, the scratch pad can be used. Another usage is if MTS creates a parameter value, but another value is requested.
  • Page 17 ANAGE THE ONFIGURATION ILES IN ANAGER ELEPHONY YSTEM Retrieve the Back-up Copy If any problem is discovered when a new configuration file has been loaded into the phones and there is a need to go back to the previous version, the following procedure shall be used: Log on to MX-ONE Manager Telephony System.
  • Page 18 6700 SIP T MX-ONE ASTRA ERMINALS FOR How to Start a New Phone The phone is delivered with default settings for an IP network. These settings must be adapted to the local network using phone configuration files. If Manager Telephony Server (MTS) is used and chapter 5.1 Install IP Phone SW Server on page 9 has been followed, the phone configuration files are generated and stored on the Software Web Server.

  • Page 19: Boot Flow Chart

    SW-server Reboot This file contains the encrypted site key. Use the anacrypt tool to create security.tuz security.tuz and encrypt the config files. File exists? aastra.cfg aastra.tuz Get model Get model specific.cfg specific.tuz MAC.cfg MAC.tuz Check MD5 check sum...

  • Page 20: Log On / Log Off

    Log on / Log off To get log on / log off working, the configuration file shall be created in MTS and if this is not possible it shall be based on the aastra.cfg template which is stored in MX-ONE under /etc/opt/eri_sn/aastraSIP- phones.
  • Page 21 The procedure for logging on to MX-ONE is described in the Quick Reference Guide for each telephone model. The necessary settings in the configuration files for this are created auto- matically when using MTS. In the configuration file aastra.cfg the following parameters must be enabled: dynamic sip:1 sip line1 user name: “Not configured”...
  • Page 22 6700 SIP T MX-ONE ASTRA ERMINALS FOR softkey5 states: idle softkey5 line: 1 7.3.2 Log on with procedure This method can be useful in a home office scenario when the registra- tion towards MX-ONE is done via a firewall that only allows SIP signaling but not http signaling.

  • Page 23: Message Waiting Indicator

    If the PIN code is changed in MX-ONE, it must also be manually changed in the <mac>.cfg file. Inactivate action uri startup (set in aastra.cfg) by setting it to an empty string (this will also inactivate Free Seating. The terminal will not be...
  • Page 24 MX-ONE under /etc/opt/eri_sn/aastraSIPphones/. aastra.tuz This is the encrypted aastra.cfg file. The phone uses http protocol to fetch this file. The configuration file has to be adapted for each installation and then it has to be encrypted, see section 19.1 Encrypted Configuration Files on page 77.

  • Page 25: Installing The Firmware / Configuration Files

    When this file is used, it is possible to get unique parameter settings per telephone. This file is optional and the file looks similar to the aastra.cfg file. <mac> represents the mac address of the phone. Example: 00085D1B5D8.cfg The settings in <mac>.cfg will override the settings in aastra.cfg and in <phone model>.cfg.

  • Page 26: Firmware Upgrade

    The phone will automatically look for firmware update and configu- ration files during the boot process. • Define in the configuration file aastra.cfg if and when phones shall check for new firmware and changed configuration file. Both regis- tered and not registered terminals will be updated. Example from the configuration file: auto resync mode: 3 #Check for new fw and configuration files every day.
  • Page 27 ESTART ESTORE Restart / Restore There are three options: • Restart the phone. Can be used when settings shall be applied. • Remove local configuration settings. The settings that are done from the phone UI and web UI are lost. •...

  • Page 28: Restore To Factory Default

    6700 SIP T MX-ONE ASTRA ERMINALS FOR extension_unregistration with parameter forced Restore to Factory Default Factory default reset will force the phone to go back to the initial setting. If configuration server is not set via dhcp options, you will need to set it again.

  • Page 29: Entering Administrator Mode

    NTERING DMINISTRATOR Entering Administrator Mode Phone UI • Press (options) key • Scroll down and select Admin Menu 6739i; select Advanced. • Enter the administrator password: 22222 (which is the default pass- word but can be changed) Web UI • Find the IP address of the telephone by selecting Options >...

  • Page 30: Configuring The Phone

    The necessary settings in the configuration file for getting the telephones to work in a correct way with MX-ONE are created automatically when using MTS. In the configuration file aastra.cfg the parameters must have the following values: ! sip aastra id: 1...
  • Page 31 EAP-MD5 and EAP-TLS protocols. Figure 3: Components in LAN access control Below is an example of the settings in the phone configuration file (aastra.cfg) when EAP-TLS shall be used: eap type: 2 identity: Phone_Floor1 802.1x root and intermediate certificates:aastra67xxi/Aastra_Client_ca.pem 802.1x local certificate:aastra67xxi/Aastra_Client_cert.pem...
  • Page 32 Phone_Floor1 will use VLAN 150. For more information about how to set up IEEE802.1x in the phones, see Administrator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones. 26/1531-ANF 901 14 Uen E10 2014-01-22...

  • Page 33: Enabling / Disabling Dhcp

    Previously, Aastra IP Phones had a 5 second timer for listening to LLDP-MED responses when the phone is booting up. If LLDP-MED responses are received after this initial listening period, the phone will not get access to the telephony VLAN.

  • Page 34: Setting The Phone's Ip Address

    6700 SIP T MX-ONE ASTRA ERMINALS FOR Options > Admin Menu[6739i; select Advanced] > Network Settings > DHCP Settings > DHCP 11.6 Setting the Phone's IP Address If DHCP is used, the phone's IP address is set automatically, using the DHCP server.

  • Page 35: Setting Time And Date

    The phone is configured with the IP address of the SIP proxy using one of the following methods: In the configuration file aastra.cfg in the parameter: sip proxy ip. The necessary settings in the configuration file for this are created automatically when using MTS.

  • Page 36: Configuring Language Settings

    MX-ONE ASTRA ERMINALS FOR The following configuration alternatives are available: • aastra.cfg file. • Phone UI. Options > Preferences > Time and Date • Web UI: Click on Preferences > Time and Date Settings It is possible to use LIM 1 in MX-ONE as a NTP server.

  • Page 37: Using Shortcut Keys

    1-4, system keys. For MX-ONE busy services (call back call pickup etc.) and for xml kit applications. These are predefined as key type XML in aastra.cfg and will get the actual key label and value when busy services is offered.
  • Page 38 6700 SIP T MX-ONE ASTRA ERMINALS FOR – Speed dial (TNS) key. Can also be programmed from a menu in the telephone or from the web interface in the phone. – Personal Number (PEN) key – Shared Call Appearance (SCA) key –...
  • Page 39 ONFIGURING THE HONE Expansion modules can be added to 6753i, 6735i/55i, 6737i/57i and 6739i. When adding an expansion module to the telephone, the keys for MNS, TNS (defined in the PBX), MCT and PEN are moved from the telephone to the expansion module. 11.13.2 Default key layout This chapter shows the default key layout per model.
  • Page 40 See also 8.2 Installing the Firmware / Configuration files on page 25. The default key layout for the different models is shown below. Services LocalDir CallList MsgWaiting Diversion More Logon /Log off CorpDir Figure 4: Aastra 6737i/57i 26/1531-ANF 901 14 Uen E10 2014-01-22...
  • Page 41 ONFIGURING THE HONE Services LocalDir CallList MsgWaiting Diversion Logon /Log off CorpDir Figure 5: Aastra 6735i/55i Save (directory) Delete (directory) Local directory Callers list Transfer Log on /off Figure 6: Aastra 6753i 26/1531-ANF 901 14 Uen E10 2014-01-22...
  • Page 42 Log on/off CorpDir Diversion MsgWaiting Callers list Services Figure 7: Aastra6739i Save contacts Log on / off Delete contacts MsgWaiting Diversion Directory (*) Services Callers list (*) Local or corporate Figure 8: Aastra 6730/31 26/1531-ANF 901 14 Uen E10 2014-01-22...
  • Page 43 ONFIGURING THE HONE 11.13.3 Flexible IP Function keys in MP For most telephone models, Manager Provisioning makes keys avail- able for individual programming based on the assumption that both ip_telephony.conf and the model specific configuration file has standard definitions. For the 6730i and 6731 models, Manager Provisioning analyzes the actual settings to determine which function keys are avail- able for individual programming.
  • Page 44 6700 SIP T MX-ONE ASTRA ERMINALS FOR Note: Each Telephony Server holds a copy of the ip_telephony.conf file. For consistency and simplicity, any change to it should be made consistently on all telephony servers. Settings apply to all tele- phones of the same model: In the example above, the logon/logoff key is disabled for all 6731i telephones, and all keys are open for programming since the offset value is zero.
  • Page 45 ONFIGURING THE HONE Figure 11:Configuration Server Settings Restart the phone. Open MP, and click Telephony tab. Add a SW server for your configuration files. Restart a unit SIPLP, to activate changes, use command restart -u SIPLP-lim x. Figure 12: SW Server Specify a IP Phone server and a domain folder, if used.
  • Page 46 6700 SIP T MX-ONE ASTRA ERMINALS FOR the phone). This is done in the Subsystem task by selecting the IP Phone Server in the dropdown list and selecting one of the avail- able folders in the Domain Folder dropdown list.The admin may also manually type in any IP Server address, at which the MP should read the model specific configuration files.
  • Page 47 ONFIGURING THE HONE Figure 14:MTS settings, in this example keys 2-8 are flexible as key 1 is locked. Note: If you want a different function keys layout on some special exten- sions even if they are using the same telephone model as the default extension, you can do this by: 1.
  • Page 48 MNS key and it is changed from the PBX or from Manager Provisioning. The default value is visual only. No settings for this can be done in the aastra.cfg file. It is also possible to set a pop-up option for monitoring keys. With this...

  • Page 49: Shared Call Appearance (Sca)

    The following terminal models can be initiated to have SCA lines: Aastra 6730i/31i, 6739i, 6735i/55i, 6737i/57i. The extension number for a SCA line can be represented on a number of terminals.

  • Page 50: Key Lock / Unlock

    1 #Delete prgkey6 locked:1 When viewing the locked key via the Aastra Web UI, the key is grayed out (disabled) and cannot be changed. It is also possible to lock parameters in the configuration files, by starting the line with an exclamation mark (!). Example:...
  • Page 51 Conference key The hard key for conference in A6730i/31i/39i is defined in the aastra.cfg template file, and of course when using MTS to create the configuration file, to send a DTMF digit to the exchange. The possibility to initiate a three part conference locally in the phone is disabled.
  • Page 52 More to the next page and 15,16,17,18,19 and 20 to the last page. 11.15 Dial Plan The dial plan is defined via the configuration file. In the aastra.cfg file the following parameters are set: !sip dial plan: "x+^|xx+*" !sip dial plan terminator: "1"...
  • Page 53 When entering a service code procedure containing an authorization and PIN code, it is possible to prevent the authorization or PIN code to be stored in the logs. The configuration for this is done in the aastra.cfg file. There are two options: •...
  • Page 54 From Manager Provisioning on page 54. The Diversion key is set from the PBX and cannot be changed. The phone internal Call Forward menu is disabled by default in the aastra.cfg file: call forward disabled: 1 11.18.1 Initiate the Divert Settings From Manager Provisioning In MX-ONE a default personal number list is used to create the divert function, see feature description for Personal Number.

  • Page 55: Do Not Disturb (Dnd)

    ONFIGURING THE HONE – Call List Deactivation Forbidden (which means that the user is not allowed to deactivate the personal number list) • MP: If a number of new extensions shall be created with default personal number list: – Create a new template for an extension with the CSP created above.
  • Page 56 6700 SIP T MX-ONE ASTRA ERMINALS FOR 11.20 Configuring Ring Signals The adaptation of the ring signals for the market is made from the config- uration file. The tables below shows values to be set for Europe / Stan- dard and for North America application systems. Table 4 Ring signal cadences for Europe / Standard Ring Parameter in...
  • Page 57 This feature can also be used when a local branch office sip proxy shall be used. DNS SRV records can be defined in the DNS server or in the aastra.cfg file.
  • Page 58 11.24 Central Storage of User Specific Data The data the that follows the user for the Aastra 6700i family when logging on to another phone is the data stored in MX-ONE, for example MNS, SCA keys and the speed dial keys initiated from MX-ONE. The data locally stored in the phone does not follow the user.
  • Page 59 11.27 Registration Distribution When the registration distribution feature is enabled in the system, the Aastra 6700i phones will be configured to register in the server with the generic extension data. In the MX-ONE concept called HLR (Home Location Register) server, the configuration is a part of the initial REGISTER procedure.
  • Page 60 Redundancy The primary proxy IP address shall be set according to 7.3.1 Log on with Soft key on page 21. It is also possible to define in the aastra.cfg file a redundant IP address with the parameters: sip backup proxy ip sip backup registrar ip The IP address to set shall be equal in both of these parameters.

  • Page 61: Corporate Directory

    This is done by pressing the Services key and select VoiceMail. In this case the phone will use the directory number to access the voice mail system. The settings for these options are defined in the aastra.cfg file. Below is an example: sip vmail:”*32#”...
  • Page 62 MX-ONE ASTRA ERMINALS FOR To be able to access the directory function some parameters in the aastra.cfg file of the phone have to be set, see the example below: softkey6 label: "Corp Dir" softkey6 type: xml softkey6 value: http://<CMG server>/xml/directory/CorpDir.php...

  • Page 63: Changing The Administrator Password

    12.1 Changing the Administrator Password The administrator password can be changed from the aastra.cfg file, see Administrator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones. The password can only consist of digits The user name is: admin The default password is 22222.
  • Page 64 6735i/37i, 6737/57i, 6739i and 6753i. To connect the phone to a DHSG compatible cordless headset, a special cable from Aastra must be used. The article number is: 62-001134-00. To enable the headset port via the phone UI: Options >...

  • Page 65: Expansion Modules

    XPANSION ODULES Expansion Modules There are two types of expansion modules; M670i and M675i. M670i is a key panel unit with 36 keys. Paper labels are used to label the keys. Maximum 3 modules can be connected to the telephone. The following models has support for the key panel unit: 6753i, 6735i/55i, 6737i/57i and 6739i.

  • Page 66: Emergency Calls

    6700 SIP T MX-ONE ASTRA ERMINALS FOR Emergency Calls Even if the telephone is not registered to the PBX, it is possible to make emergency calls. The sip proxy ip parameter in the configuration file, defines where the telephone sends the INVITE with the SOS number. No registrar is required for this.
  • Page 67 IP R ECORDING VoIP Recording It is possible to record voice calls to a central recording equipment. The phones that shall have recording are monitored via the CSTA interface and this means that an Application Link or an Open Application Server (OAS) must be used to provide the CTI interface to the recording system.
  • Page 68 6700 SIP T MX-ONE ASTRA ERMINALS FOR Below is an example how to set the parameters in the configuration file: recorder address1: 192.168.1.20 recorder address2: 192.168.1.21 #recording destination1: recording destination beep: 0 sip services transport protocol: 1 sip services port: 7300 Recorder addressN specifies the trusted IP addresses corresponding to the recording system.
  • Page 69 IP address and port number. • Stop recording: http://192.105.88.152:8080/XVOIPService?page=STOP&amp; OPN=$SIPUSERNAME$$ If the URL contains any characters considered as special by Aastra 6700i, they must be escape encoded, see table below. Table 7 Escape encoding Character Symbol Escape Sequence Ampersand &...

  • Page 70: Quality Of Service (Qos)

    6700 SIP T MX-ONE ASTRA ERMINALS FOR Quality of Service (QoS) It is not possible to view the QoS statistics via MX-ONE. 26/1531-ANF 901 14 Uen E10 2014-01-22...

  • Page 71: Dhcp Server

    DHCP SERVER DHCP server 18.1 Data from DHCP The phone has support for DHCP by which the following IP configuration data can be provided: • Own IP address, subnet mask and default gateway, received in the DHCP standard fields (1 and 3). •...
  • Page 72 00 00 00 64 in hex. For an example how to configure option 60 and 43 in a Linux environ- ment, see the Administrator Guide for Aastra IP SIP Phones Below is an example showing how to configure DHCP in a Windows environment.
  • Page 73 DHCP SERVER 18.3.1 Define Vendor Class Select Define Vendor Class in the drop down list. Figure 16:Define and add the vendor class To enter the Vendor Class ID, click on the right side below ASCII in the large form field. Enter the Identifier Value from table 7 above. Repeat this step for each phone model that should be served by this DHCP server.
  • Page 74 6700 SIP T MX-ONE ASTRA ERMINALS FOR 18.3.2 Set Predefined Options Select Set Predefined Options to get the menu to enter the option 43 data. Figure 17:Set Predefined Options Select appropriate option class from the drop down list and press the Add button.
  • Page 75 DHCP SERVER Figure 18:Predefined Options and Values The data in the Option Type menu has to be entered manually: Name: Configuration Server URL Data type: String Code: 02 Repeat this for each phone model that should be served by this DHCP server.
  • Page 76 6700 SIP T MX-ONE ASTRA ERMINALS FOR 18.3.3 Set Scope Options The last step is to set the URL string. Figure 19:Set Scope Options Select appropriate Vendor class and set the User class to Default User Class. Activate option 002 and enter the URL of the software server (configuration server) in the input field String value.
  • Page 77 The aasta.cfg, <model>.cfg and <MAC>.cfg files can be encrypted and downloaded to the phone from the software server with the http or https protocol. Aastra provides a tool for Windows and Linux to encrypt the configuration files. This tool is called anacrypt. Use the following procedure: Create the file security.tuz with the encrypted site key:...
  • Page 78 The IP Phones include support for Secure Real-time Transfer Protocol (SRTP), using Session Description Protocol Security (SDES) key nego- tiation, for encryption and authentication of RTP/RTCP messages sent and received by the Aastra IP phones on your network. The administrator can choose among the following options: •...
  • Page 79 MX-ONE: For certificate handling see operational directions Certif- icate Management (132/15431-ANF90114) in the CPI library. 6700i phones: The only certificate that is necessary is the root certificate. The key storage for MX-ONE certificates is /etc/opt/eri_sn/certs/. The root CA is called, CA.pem. Copy CA.pem to the configuration server, i.e.
  • Page 80 Aastra 6700i If Ingate is used as Session Border Controller (SBC), follow the Installa- tion Guide How to Install an Ingate Solution for Aastra Teleworker Solu- tions in Stand-alone mode or DMZ/LAN mode behind existing Firewall in the CPI library.
  • Page 81 The InOffice directory shall consist of model specific configuration files, aastra.cfg and the phone FW (see above). Note, that the root certificates are loaded but not used as the setting is TCP for SIP and RTP for media.
  • Page 82 Either the Logon keys are removed. Then you rely on that the users logon when prompted due to reboot (triggered by action uri startup in aastra.cfg), or the /Logon key value needs to be set to “https://193.10.10.10:22223/Logon?user=$$SIPUSERNAME$$”. If Corporate directory is to be used a TLS port relay can be config- ured in Ingate the same way as port 444 is setup towards the configuration server), Let’s say port 445 is set up then the Corpo-...
  • Page 83 ECURITY Ingate Relay setting for port 22223. However, if extension_registration_distribution is active the proxy, registrar will be set according to the extension’s Home Location Register (HLR) (see the lim setting in command extension -p) sip proxy ip: 0.0.0.0 sip proxy port: 0 sip registrar ip: 0.0.0.0 sip registrar port: 0 time server disabled:0 #0-NTP enabled...

  • Page 84: Troubleshooting

    6700 SIP T MX-ONE ASTRA ERMINALS FOR Troubleshooting 20.1 Capture logfiles via SYSLOG When log files for troubleshooting purpose shall be retrieved from the telephone, it is possible to use the external syslog feature in Linux for storing or the Kiwi Syslog Server. Setup the SYSLOGD server In the MX-ONE system: Uncomment the following line in /etc/syslog-ng/syslog-ng.conf.in...
  • Page 85 The following log files are available: local.cfg, server.cfg and crash.log. It is also possible to view the Task and Stack Status. For more information about troubleshooting, see Administrator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones. 20.2 Issues with DHCP Options...
  • Page 86 However if the simple TLS handshake used in ‘persistent TLS’ is used only the server is authenticated by its certificate (this is the method used in chapter 19.5 “How to enable security for home worker on Aastra 6700i”). In a client-authenticated TLS handshake (also referred to as mutual TLS), the server will request to authenticate the client based on its certificate as well.
  • Page 87 TLS cert request is created and then it is signed by the CA >openssl req -new -newkey rsa:1024 -out phone_csr.pem -nodes -keyout private/phonekey.pem -days 3650 [answer cert questions accordingly]CN: Aastra IP Phone >openssl x509 -req -in phone_csr.pem -out phonecert.pem -CA ca.pem -CAkeyprivate/cakey.pem -days 3650 -CAcreateserial -CAserial ca.seq...
  • Page 88 Copy the following certificate related files from the openssl (Enterprise CA) to the phones’ Configuration Management path (the same place as where the aastra.cfg is stored). When following chapter 19.5, the path would be to /atHome. ca.pem - public CA signing phonecert.pem phonecert.pem - signed client certificate...

Table of Contents