MBU 400 TM Administrator Guide Release 1.
Aastra Telecom will not accept liability for any damages and/or long distance charges, which result from unauthorized and/or unlawful use. While every effort has been made to ensure accuracy, Aastra Telecom will not be liable for technical or editorial errors or omissions contained within this documentation. The information contained in this documentation is subject to change without notice. Copyright 2008 Aastra Telecom. www.aastratelecom.com All Rights Reserved.
Table of Contents Important Safety Instructions...................................................................................................... 5 Importantes mesures de sécurité ................................................................................................................................ 5 Software License Agreement........................................................................................................ 6 FCC Information................................................
Important Safety Instructions When using your telephone equipment, basic safety precautions should always be followed to reduce the risk of fire, electric shock and injury to persons, including the following: 1. Do not use this product near water, for example, near a bath tub, wash bowl, kitchen sink or laundry tub, in a wet basement or near a swimming pool. 2. Avoid using a telephone (other than a cordless type) during an electrical storm. There may be a remote risk of electric shock from lightning. 3.
Software License Agreement Software License Agreement Aastra Telecom Inc., hereinafter known as "Seller", grants to Customer a personal, worldwide, non-transferable, non-sublicenseable and non-exclusive, restricted use license to use Software in object form solely with the Equipment for which the Software was intended. This Product may integrate programs, licensed to Aastra by third party Suppliers, for distribution under the terms of this agreement.
FCC Information Contact your System Administrator or Technical Support for any questions regarding your MBU 400. Have your serial number and MAC address ready when contacting support. You can locate the serial number and MAC address on the bottom of the MBU. For inquiries concerning telephony services, contact your Internet Telephony Service Provider.
FCC Information US Service Center: Aastra Telecom US - Service Center 900 Technology Park Drive Billerica, MA, 01821, USA Phone (978) 262-3200 For Industry Canada: "This product meets the applicable Industry Canada technical specifications." Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection.
The REN is used to determine the number of devices that may be connected to a telephone line. Excessive RENs on a telephone line may result in the devices not ringing in response to an incoming call. In most but not all areas, the sum of RENs should not exceed five (5.0). To be certain of the number of devices that may be connected to a line, as determined by the total RENs, contact the local telephone company.
Safety Information Safety Information Important Safety Information Charge the battery or handset only in combination with 420d Charger and the SALOM SSW-1444 adapter that comes with the product. Plug the SALOM SSW1444 AC/DC adaptor in a wall outlet socket near the equipment for easy access/ removal of the AC/DC adaptor. Important Battery Information This product uses rechargeable Lithium-ion batteries 3.7V, 650mAh.
For countries outside the European Union Disposal of electrical and electronic products in countries outside the European Union should be done in line with the local regulations. If no arrangement has been made with Aastra or your supplier, please contact the local authorities for further information. Battery Disposal Information Defect or exhausted batteries should never be disposed of as municipal waste.
About This Guide This Administrator Guide provides the information required to use and configure the MBU 400 on your business or home network. It includes advanced configuration instructions for features and functions of the MBU and the Aastra 420d Handset. This Administrator Guide is intended for the System Administrator only. Documentation The following documentation can be found on the Aastra Telecom website at www.aastratelecom.
Introduction Introduction The MBU 400 consists of a Mobility Base Unit (MBU) and the Aastra Digital Enhanced Cordless Telephone handset (420d) that provide telephony service over the Internet and over the Public Service Telephone Network (PSTN) or landlines. You can install the MBU on a desktop or on a wall, while the 420d handset sits in its charging cradle on a desktop. You can register up to 8 handsets with the MBU. The MBU supports up to 3 SIP calls and 1 PSTN call simultaneously.
Other MBU Features • System Administrator Web Interface Support (in English only) • SIP accounts configured via WebUI, TFTP, or from the handset. • Quality of Service • Type of Service (ToS) • CODECs • Pulse Code Modulation A-law (PCMA) (G.711, 64 kbps) • Pulse Code Modulation u-law (PCMU) (G.711, 64 kbps) • iLBC (20 ms) • G.
Introduction Call and Telephony Features • 12 numerical keys, 5 navigation keys, 2 function keys • Auto answer (when handset is lifted from the charger) • Key lock option • Call forward - all, busy, no answer • Call timer • Call transfer and call hold (for internal calls) • Call waiting indication • Caller ID with name from phone book • Distinctive ringing • Call log of incoming/outgoing/missed calls • Call return (from call log) • Customizable phone settings • Intercom (handset to handset through MBU) • C
Requirements Before using the MBU 400 on your network, the following may be required depending on your network connection: • Broadband Internet connection – cable, DSL, or equivalent • Internet Telephony Service Provider subscription – to make voice calls over your Internet connection • Analog telephone line subscription – to make ordinary phone calls (and emergency calls) over the LINE port on the MBU (optional) • In addition, before you start the installation process, the following may be required: — (opt
Getting Started Getting Started This section describes the first steps in configuring the administrator settings on your MBU 400 system. Administrator configuration settings are accessed through three interfaces. • The handset VoIP Settings and Internet Settings menus provide limited configuration access. See the Aastra MBU 400 User Guide for more information on the handset interface. • The Web UI provides access to most configuration settings.
2. Scroll down to see the IP address and other status information about the MBU. System Status --Network-MAC Address 00-08-7g-98-45-cf IP address 192.345.43.54 (D) Boot Status Failed MAC Address IP Address --Gateway-Version Sw: 01:08 Hw: 1 Serial no.
Getting Started To open the Aastra Web UI for your MBU 400 system do the following. 1. Open your web browser and enter the MBU’s IP address (in dotted decimal format) into the address field, then press Enter. For example, an address of http://10.30.123.1 opens the following page. The Login window displays. 2. Enter your user name and password and click OK. Note: For an administrator, the default user name is “admin” and the password is “22222”.
The MBU 400 Welcome screen displays, showing a summary of your system and account information. 3. To logout at any time, close the browser window. Web UI Menu Administrator configuration options can be accessed using the Aastra Web UI. The exact menu appearing in the Web UI can be set through the configuration files, and may differ from the default menu described here. The following categories appear in the side menu of the MBU Web UI by default.
Getting Started Menu Item Description (Continued) Telephony Settings Destination of incoming calls and display name for each handset. See Customizing Your SIP Accounts on page 34. Time Settings Current time and date configuration. See Changing Time Settings on page 36. Debug Debug trees for advanced troubleshooting. SIP Trace Details of SIP protocol messages sent and received by the MBU 400 system. Settings Configuration file (details of configuration parameters).
2. Click to return all settings to the default values. All settings on this page are reset to default values. The MBU 400 then saves the settings and resets automatically. Note: All account settings will be lost and need to be re-entered before VoIP calls can be made. The handset access codes will not be reset, and need to be changed to match the default gateway access code of "0000".
Using the Web UI Using the Web UI Administrator configuration settings can be accessed through the Aastra Web UI using a web browser and the IP address of your Aastra MBU 400 system. For more information on finding the Aastra MBU 400 IP address and opening the Aastra Web UI see Getting Started on page 18. Some administrator settings can be reached through the MBU 400 handset using the handset menus. For more information see the Aastra MBU 400 User Guide.
To register an SIP account with the MBU 400 do the following. 1. In the MBU Web User Interface, click VoIP Account 1 (or VoIP Account 2 for the second SIP account, and so on). The VoIP page opens. Field Description Server is Local Allows you to select a local or remote sever. An external sevice provider VoIP account indicates a remote server in most cases. Default setting is No. Display Name For reference purposes only. This name will not appear on the handset display.
Using the Web UI Field (Continued) Description (Continued) Registrar SIP registrar/proxy address Outbound Proxy SIP outbound proxy or SBC address Authentication Username SIP authentication username Server Port SIP registrar/proxy port Outbound Proxy Port SIP outbound proxy port or SBC port Re-registration Time SIP registration period 3. Click 4. Click to save the configuration. to reset the MBU 400 so the new settings take effect.
If you want to return to the default settings for configuration and upgrade paths without factory defaulting the MBU 400 do the following. 1. In the MBU Web User Interface, click Management Settings on the left menu. The Management Settings page opens. 2. Click to return all settings to the default values. All settings on this page are reset to default values. The MBU 400 saves the settings and resets automatically.
Using the Web UI The following firmware settings are available on the Management Settings page, and can be changed by entering new values or selecting from the drop-down menus. Field Description Firmware update server address The IP address or domain name of the server containing firmware update files. Default value is Mbuupdates.Aastra.com. Firmware path The firmware update server path in which to look for firmware update files. Must start with a slash (/).
Changing NAT/RTP Settings For details of the advanced administrator configuration settings available through the NAT/RTP page in the Aastra Web UI, see STUN, RPORT, SIP port settings on page 45 in the configuration files chapter. Configuring IP Settings Aastra MBU 400 Administrator Guide 29 Using the Web UI The Aastra MBU 400 gateway can be configured to obtain its IP address via DHCP or to use a static IP address. The default setting is for DHCP.
Using the Web UI To change the IP setting of your MBU 400 do the following. 1. In the MBU Web UI, open the IP Settings page (click IP Settings on the side menu). The IP Settings page opens. 2. Select DHCP or Static in the drop-down menu. 3. If you have selected Static, enter IP addresses or domain names in the appropriate fields. 4. Click 5. Click to save your new IP settings. to reset the MBU and apply the new settings.
2. Click Pincode Settings on the left menu. The pincode settings window opens. Setting a PIN code Within the Pincode Settings window of the MBU 400 Web UI, you have the option of changing the VoIP pincode. This 4-digit number corresponds to the PIN code found in the 420d handset Settings>VoIP Settings menu. If your system has an active pincode, several handset menus will require you to enter the correct pincode before allowing access. The default pincode used by Aastra Telecom is "2222".
Using the Web UI 4. Click to reset the MBU 400 and apply the new pincode to the system. Activating the pincode The pincode can only be activated or deactivated through the configuration file. See Protecting Handset Menus on page 52 for details. Setting an Access Code Setting an access code on your gateway ensures only handsets with the same access code are able to connect to the gateway. The access code can be set through the handset (see the Aastra MBU 400 User Guide for details) or through the Web UI.
5. Click to reset the MBU 400 and apply the new username and password. Use the new username and password the next time you logon to the Web UI. Changing PSTN Settings Using the PSTN Settings page in the Aastra Web UI, the landline can be disabled. In this instance incoming calls on the landline (if one is connected to the MBU 400) are ignored, and references to the landline are removed from the handset UI.
Using the Web UI To change the PSTN settings for your Aastra MBU 400 system do the following. 1. In the MBU Web UI, open the PSTN Settings page (click PSTN Settings on the side menu). The PSTN Settings page opens. 2. Change the PSTN settings as required. (See the proceeding table for details of the PSTN fields.) 3. Click 4. Click to save the new settings. to reset the MBU 400 and apply the settings to the system.
To customize the account settings for MBU 400 handsets do the following. 1. In the MBU Web UI, open the Telephony Settings page (click Telephony Settings on the side menu). The Telephony Settings page opens. For example, checking PSTN only for handsets 2 and 3 will result in all incoming landline (PSTN) calls ringing handset 2 and handset 3. Other handsets will not be able to answer landline calls. 3.
Using the Web UI — If you have selected VoIP calls, choose the number of the registered SIP account to use when dialing out. • Fill the parameter Handset name with the name and number you want displayed on the 420d screen. If nothing is entered, the default "Handset 1" for account 1, "Handset 2" for account 2, and so on will be used. • Enable the Match IPEI to Handset parameter to activate IPEI matching and fill in the IPEI For Handset for each handset.
To change the time settings for MBU 400 handsets do the following. 1. In the MBU Web UI, open the Time Settings menu (click Time Settings on the side menu). The Time Settings page opens. 2. In the Time Server field, enter the IP address or domain name of a time server. Using the Web UI 3. In the Time server refresh interval field enter the length of time in seconds between time server refreshes. 4. In the Timezone field, enter your local timezone in GMT format.
Using the Web UI Time Zone Location (Continued) GMT+8 Australian Western Standard Time (AWST) China Coast Time (CCT) Perth; Beijing GMT+3 Bagdad Time (BT) Moscow GMT+2 Eastern European Time (EET) Cairo GMT+1 Central European Time (CET) Paris; Stockholm; Vienna GMT Greenwich Mean Time (GMT) London GMT-4 Atlantic Standard Time (AST) GMT-5 Eastern Standard Time (EST) New York; Washington DC; Ottawa; Toronto GMT-6 Central Standard Time (CST) Mexico City GMT-7 Mountain Standard Time (MST) Den
Using Configuration Files This chapter describes the configuration options available when using configuration file transfers to setup the MBU 400 system. By customizing configuration files you can configure all parameters accessed through the MBU handset menus and the Aastra Web UI, as well as some advanced features such as PIN code security activation for handset menus. Note: When the gateway is reset, it attempts to reload a configuration file.
Using Configuration Files To view the configuration file from the Aastra Web UI do the following. 1. Open your web browser and enter the MBU’s IP address (in dotted decimal format) into the address field, and press Enter. The Login window displays. 2. Enter your user name and password and click OK. Note: For an administrator, the default user name is “admin” and the password is “22222”. The username and password can be changed through the configuration file parameters. 3. Click Settings on the left menu.
The Settings Page opens, showing the complete configuration parameter settings. Use the scroll bars to view the file. 4. To logout at any time, close the browser window. IP configuration The Aastra MBU 400 gateway can be configured to obtain its IP address via DHCP or to use a static IP address.
Using Configuration Files Parameter (Continued) Values (Continued) Description (Continued) NETWORK_WAN_SETTINGS_DNS1 0.0.0.
Parameter (Continued) Possible values Description (Continued) NETWORK_DHCP_CLIENT_BOOT_ 0-1 SERVER_OPTION_DATATYPE 0: IP Address 1:String(default) NETWORK_DHCP_CLIENT_TIMEO UT Wait time when requesting a DHCP address from the DHCP server. 3 (default) VLAN tagging By specifying a VLAN ID, frames are confined to that virtual network. VLAN tagging is disabled by setting the ID to zero.
Using Configuration Files Configuration file example: %SRV_0_SIP_UA_DATA_DOMAIN%:"proxy.goip.dk" %SRV_0_SIP_UA_DATA_PROXY_ADDR%:"proxy.goip.
Parameter (Continued) Values (Continued) Description (Continued) SUBSCR_0_SIP_UA_DATA_VOICE_MAIL String (max 22 characters) BOX_NUMBER Voice Mailbox number Sip address/ phone number used when listening to messages CODEC_SILENCE_SUPRESSION Landline silence supression for G729 CODECs. (default=1) 0,1 [Disable,Enable] Configuration file example: %SRV_0_SIP_UA_DATA_DOMAIN%:"proxy.goip.
Using Configuration Files Parameter (Continued) Values (Continued) Description (Continued) SIP_STUN_BINDTIME_DETERMINE 1 (default) If stun is enabled and SIP_STUN_BINDTIME_GUARD is defined setting this parameter to TRUE forces the system to automatically determine the duration of NAT bindings in the system. In this case the SIP_STUN_BINDTIME_GUARD parameter defines the initial test duration.
Updating Firmware The firmware update process can be initiated from the handset, by sending a SIP notify with a check-sync event to the gateway, or by scheduling a firmware update. Handset initiated firmware updates A firmware update can be initiated from the handset using Settings >System settings>Firmware update. In the firmware update menu select the desired firmware version and language. Use the right and left navigation keys to switch between the Simple and Advanced pages.
Using Configuration Files The following configuration parameters are used for scheduled firmware updates. Parameter Possible values Description FWU_POLLING_ENABLE 0,1 [DISABLE, ENABLE] Enables or disables scheduled of firmware update. FWU_POLLING_MODE 0,1 [ABS, REL] 0 (ABS) means that firmware update uses the absolute time, 1 (REL) means that firmware update uses a relative time. FWU_POLLING_PERIOD Unit is in sec Used in REL mode.
Error Code (Continued) Description (Continued) Code 11: Server name lookup failed Indicates the DNS server cannot determine the IP address for the provided firmware update server. Code 12: Authentication failed Indicates the HTTP request for the DirFile or firmware files failed with a HTTP/1.1 401 response code. This indicates that either the username or password is incorrect.
Using Configuration Files Handset Configuration Handsets can be customized with options such as the display name and do not disturb setting. The phonebooks used by all handsets (the Call Log and Contacts List) can be set as private, or shared between all handsets registered to the same MBU.. Parameter Values Description COMMON_PHONEBOOK 0,1 [Private, Common] Makes the Call Log and Contacts List private for each handset, or sharded vetween all handsets.
Parameter (Continued) Values (Continued) Description (Continued) FWD_ON_BUSY_DEACT_PSTN FWD_ON_BUSY_DEACT_0 ... FWD_ON_BUSY_DEACT_7 "" (default is blank) Deactivates call forwarding when the line is busy for PSTN, SIP Account 1,...SIP Account 8. FWD_ON_NO_ANSWER_ACT_PSTN FWD_ON_NO_ANSWER_ACT_0 ... FWD_ON_NO_ANSWER_ACT_7 "" (default is blank) Activates call forwarding when there is no answer for PSTN, SIP Account 1,...SIP Account 8.
Using Configuration Files four-digit access code is formatted as two hexadecimal numbers, separated by a comma. The first two digits correspond to the first number, and the last two digits to the second number. Some examples of AC_CODE values follow.
Bit Setting (Continued) 6 Reserved 7 (MSB) Reserved Pincode protection is enabled by writing 1 and is disabled by writing 0 in the corresponding bit field. The values in the three most significant bits are reserved for future use (currently these values are ignored). The default value is 0x00, disabling pincode protection on all settings. Note: The popup in idle mode announcing new firmware will not be displayed when the System settings menu is pincode protected.
Using Configuration Files Aastra Web UI customization The Aastra Web UI can be customized using configuration parameters associated with the title or login credentials. Subpages may be individually disabled, resulting in a modified Web UI menu.
LOCAL_HTTP_SERVER_ACCESS The configuration parameter LOCAL_HTTP_SERVER_ACCESS is a bit-field describing which pages (from 1-16) are visible on the Aastra Web UI. The least significant bit configures the first link (VoIP Account 1). An illustrated example follows. The time settings configuration options allow the Aastra MBU 400 system time to be set by an external time server, with a set refresh rate and local timezone.
Using Configuration Files Parameter (Continued) Possible values Description (Continued) NETWORK_SNTP_SERVER "" (default is blank) The IP address or domain name of a time server. NETWORK_SNTP_SERVER_UPDATE_TIME 15 (default value) Time interval in seconds between updates from time server. The configuration parameter GMT_TIME_ZONE allows you to select your local timezone from the following options..
GMT_TIME_ZONE Value Time Zone (Continued) 8 GMT-4:30 7 GMT-5 Eastern Standard Time (EST) New York; Washington DC; Ottawa; Toronto 6 GMT-6 Central Standard Time (CST) Mexico City 5 GMT-7 Mountain Standard Time (MST) Denver; Phoenix 4 GMT-8 Pacific Standard Time (PST) Los Angeles; Vancouver 3 GMT-9 2 GMT-10 1 GMT-11 0 GMT-12 Location (Continued) Adjusting DST (Daylight Saving Time) DST adjustments can be handled manually or automatically.
Using Configuration Files Parameter (Continued) Possible values (Continued) Description (Continued) DST_STOP_DATE 1..31 DST start date. Not used if FixedDayEnable is set to FALSE (default=1) DST_STOP_TIME 0…23 DST start time. (Default=2) DST_STOP_DAY_OF_WEEK 1..7 (1=Sunday) (Default = 1) DST_STOP_WDAY_LAST_IN_MONTH 0,1,2,3 0: Stop day of week first in month. 1: Stop day of week last in month 2: Start day of week second first in month. 3: Start day of week second last in month.
Possible values for VOIP_LOG_AUTO_UPLOAD are given in the following table. VOIP_LOG_AUTO_UPLOAD Description 0 Automatic upload is disabled. (default) 1 Only upload the boot log 2 Continuously upload log files.
Sample Configuration File Sample Configuration File The following configuration file is an example of a fully functional configuration for the MBU 400, including the registration of multiple handsets. //-----------Network Settings-----------%SIP_RPORT_ENABLE%:1 //A way around NAT %SIP_STUN_ENABLE%:0 //0-disable, 1-enable stun services %NETWORK_STUN_SERVER%:"stun01.sipphone.
// ------------- Registration 1 ------------------%SUBSCR_0_SIP_UA_DATA_SIP_NAME%:"36976091" // insert SIP username here.
Sample Configuration File // ------------- Registration 5 ------------------%SUBSCR_4_SIP_UA_DATA_SIP_NAME%:"" //SIP address %SUBSCR_4_SIP_UA_DATA_VOICE_MAILBOX_NUMBER%:"" //Mailbox number %SUBSCR_4_UA_DATA_DISP_NAME%:"" //Display name for Caller ID %SUBSCR_4_UA_DATA_AUTH_NAME%:"" //Auth User ID %SUBSCR_4_UA_DATA_AUTH_PASS%:"" //Auth password %SUBSCR_4_SIP_UA_DATA_SIP_NAME_ALIAS%:"" //Alias name for Phone UI %SUBSCR_4_SIP_UA_DATA_VOICE_MAILBOX_NAME%:"" // ------------- Registration 6 ---------
// ----------Emergency Primary Line---------------%EMERGENCY_PRIMARY_PORT%:1 //0-PST, 1-VOIP1....
Troubleshooting Troubleshooting The following is a list of solutions to the most common issues that you may experience when you install and use the MBU 400. Most of the problems you can easily solve yourself, whereas others require that you contact your service provider. To view the most recently updated troubleshooting information, go to www.aastratelecom.com. Issue Causes Solution The handset keeps repeating the checking step of the handset update.
Issue (Continued) Causes (Continued) The I-NET indicator on the MBU is The Ethernet cable is not not lit. connected. Solution (Continued) Check that the Ethernet cable between the WAN port on the MBU and the LAN port on your modem or router is connected properly. The router or modem is not powered. Turn on the power to the modem or router. The MBU cannot retrieve an IP address. In Internet settings, check that the IP mode corresponds to the IP mode of your Internet connection.
Troubleshooting Issue (Continued) Causes (Continued) Solution (Continued) I cannot make Internet calls, but it The MBU is not logged in at the Check that all cables are connected worked yesterday. Internet Telephony Service Provider. properly, and check that power is turned on, and then reset the MBU. How do I determine the software version of my Handset? 66 The router is turned off. Turn on the router. The SIP server is down. Contact your Internet Telephony Service Provider.
Limited Warranty Aastra Telecom warrants this product against defects and malfunctions during a one (1) year period from the date of original purchase. If there is a defect or malfunction, Aastra Telecom shall, at its option, and as the exclusive remedy, either repair or replace the MBU 400 at no charge, if returned within the warranty period. If replacement parts are used in making repairs, these parts may be refurbished, or may contain refurbished materials.
Index A D Aastra 420d handset, features 15 daylight savings time automated 57 manual 57 Aastra MBU 400 Administrator Guide, about 13 Aastra MBU 400 Installation Guide, about 13 Daylight Savings Time (DST) 38 Aastra MBU 400 User Guide, about 13 Debug Page 22 Aastra Telecom website 13 DECT_SUBS_1 53 about this guide 13 DECT_SUBS_MATCH_IPEI 53 AC_CODE 51, 52 default access code 32 Access Code 52 default password 31 access code factory default 23 setting 32 default pincode 31 default Web UI pass
Index F I Factory defaulting 22 Important Safety Instructions 5, 10 FCC Information 7 Importantes mesures de sécurité 5 features, MBU and 420d handset 14 installation and setup 18 firmware path 28 update error codes 48 update server address 28 Introduction 67 IP address, finding 18 IP Settings Page 21, 30 IPEI 19, 36, 53 Frequency for relative searching 28 IPEI matching 36 FWD_ON_BUSY_ACT_0 50 FWD_ON_BUSY_ACT_PSTN 50 FWD_ON_BUSY_DEACT_0 51 J FWD_ON_BUSY_DEACT_PSTN 51 Join Calls 36 FWD_ON_NO_
N P NAT/RTP Settings Page 21 password Web UI 30 NETWORK_DHCP_CLIENT_BOOT_SERVER 42 password, SIP authentication 25 NETWORK_DHCP_CLIENT_BOOT_SERVER_OPTI ON 42 NETWORK_DHCP_CLIENT_BOOT_SERVER_OPTI ON_DATATYPE 43 phonebook private 36 shared 36 NETWORK_DHCP_CLIENT_TIMEOUT 43 Phonebook Selected 36 NETWORK_FWU_SERVER 47 PIN code See pincode.
Index S U Safety Information 10 Upgrading Firmware 27 Scheduled Firmware Update 28 USER_PRIMARY_LINE_PP1 50 security settings 30 USER_VOIP_LINE_PP1 50 Sensitive Electronic Environment 10 username and password factory default values 23 Server Port 26 Settings Page 22 shared phonebook 36 V SIP Trace Page 22 VoIP Account 25 SIP_RPORT_ENABLE 45 VOIP Account 1 through 8 Pages 21 SIP_RTP_PORT 46 VOIP_LOG_AUTO_UPLOAD 58, 59 SIP_RTP_PORT_RANGE 46 VOIP_SETTINGS_PIN_CODE 52 SIP_RTP_PRIORITY 46 SIP
Aastra Telecom will not accept liability for any damages and/or long distance charges, which result from unauthorized and/or unlawful use. While every effort has been made to ensure accuracy, Aastra Telecom will not be liable for technical or editorial errors or omissions contained within this documentation. The information contained in this documentation is subject to change without notice. Copyright 2008 Aastra Telecom. www.aastra.com All Rights Reserved.
