Snom M700 Admin And Installation Manual
Hide thumbs
Also See for M700:
- Admin and installation manual (58 pages) ,
- Provisioning manual (38 pages) ,
- Deployment manual (16 pages)
Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Snom M700
Summary of Contents for Snom M700
- Page 1 Admin and Installation Guide v1.1 snom M700, snom M300 Base stations...
-
Page 2: Table Of Contents
M300 and M700 administration and installation guide Contents Contents ................................ 2 Document History .............................. 3 Introduction ............................... 4 Intended Audience ............................. 4 Abbreviations .............................. 4 Preinstallation information .......................... 5 Environmental considerations ....................... 5 Wall/ceiling mounting ........................... 5 Operating controls and LED’s ........................ 5 Reset switch ............................ 5 Network and power connection ...................... 5 General software considerations and requirements ................ 6 First setup ................................ 6 Identifying base IP‐address and first login ..................... 6 ... -
Page 3: Document History
Document History Revision Author Issue Date Comments 0.1 Tim Koehler 05‐Sep‐2014 Initial Version 1.0 Benajmin Ziebarh 01‐Oct‐2014 Initial Release 1.1 Benjamin Ziebarth 9 Dec 2014 Added: Handset update info Version 1.1 Page | 3 ... -
Page 4: Introduction
Introduction This document shall help to install and administrate the snom Mobile base stations M300 and M700. This document does NOT cover the installation of a multicell DECT system, in this case please refer to the snom multicell deployment guide for further guidance. Intended Audience The target audience for this document includes network administrators. Abbreviations For the purpose of this document, the following abbreviations hold: DHCP: Dynamic Host Configuration Protocol (T)FTP: (Trivial) File Transfer Protocol IOS: Internetworking Operating System NAT: Network Address Translator PCMA: A‐law Pulse Code Modulation PCMU: mu‐law Pulse Code Modulation RSSI: Received signal strength indication RTP: Real‐time Transport Protocol RPORT: Response Port (Refer to RFC3581 for details) SIP: Session Initiation Protocol SME: Small and Medium scale Enterprise SRTP: ... -
Page 5: Preinstallation Information
Pre-Installation information Environmental considerations Please install the M300/M700 base station only in dry locations which are not potentially explosive atmosphere. Don’t install the base near air conditions, radiators, in direct sun exposure, very dusty places or where it could be exposed to water and/or chemical splashes. The base stations are shall only be used indoor. Environmental temperature: ‐10°C to +50°C (14°F to 122°F) Humidity: max 70% (noncondensing) It is recommended to not install the base station directly on metal surfaces and to maintain a minimum distance of 20cm (8 inches) from current lines or water pipes; otherwise the reception might be degraded. Wall/ceiling mounting The snom M300/M700 can be wall mounted. On the M700 please remove the foot stand prior mounting. The M700 can also be mounted on the ceiling with the optionally available “snom A700 ceiling mount” with the product number 00003933. Please do not try to install the base stations on the ceiling without this mount, as the base station may fall down. Operating controls and LED’s The base stations have a multicolour LED for status signalling. Status LED System state Solid green base is operational blinking orange base is booting blinking red network or registration failure off base is inactive ... -
Page 6: General Software Considerations And Requirements
Both base stations have a 10/100 Mbit autosensing network port. General software considerations and requirements The snom M‐Series base stations follow most snom specific snom configuration and management schemes. It is recommended to have a local HTTP/HTTPS server for firmware updates and central configuration management. The HTTP‐Server will host firmware files for base stations, handsets and repeaters. The handsets and repeaters can be updated over the air by the base station. First setup The first setup will guide through the process of identifying the base stations IP‐address, to login and to setup the first handset and SIP‐registration. This guide will NOT describe how to setup M700 in a multicell configuration. Note: The screenshots are taken from an M700 base station and an M65 handset. Where applicable individual screenshots are taken. Identifying base IP-address and first login Once you connected the base station to power and network as described before, take a snom M65/M25 handset and press the “Menu” key and enter “*47*”. This will show the base stations IP‐ addresses in range: Please enter the IP‐address of the base to configure into your webbrowser. The standard Administration credentials are: ... -
Page 7: Setting Up Accounts And Handsets
Note: After the first login, please go to the security tab and change the admin login password immediately to prevent that third parties have access to the installation. Setting up accounts and handsets Three steps are required to make the first phone call: 1. Setup a SIP‐server Please start to setup a SIP‐server, by clicking on Servers. Version 1.1 Page | 7 ... -
Page 8: Create An User Account
The server page lets you configure server specific settings, such as Codec priorities, RTP settings, encryption, etc. 2. Create an user account Now click on Extensions to create user accounts (consider creating all required user accounts at this stage, they will be associated with the handsets in the next step): Version 1.1 Page | 8 ... - Page 9 Then click on “Add extension”: Version 1.1 Page | 9 ...
-
Page 10: Register Handset
3. Register Handset Back at the extension page, you will notice, that the newly created account is associated with a handset which has the IPEI FFFFFFFFFF, this means that no handset has been associated with this SIP extension. Select the “unregistered” extension by setting the check‐mark and click on “Register Handset(s)”. Now take your handset, press Menu and select “Connectivity”: Version 1.1 Page | 10 ... - Page 11 Press OK, The M65 can register to up 10 different base station, for now select the first entry (M25 only supports one registration and won’t show this screen). Select Register, Version 1.1 Page | 11 ...
-
Page 12: Firmware Update
Enter the network code – by default “0000” Firmware Update When first installing a system, snom recommends updating to the latest version. Factory installed version might be outdated and a newer version with fixes and new functionality might be available. Please go to the snom Website (www.snom.com) to download the latest version. Firmware Files: Depending on the devices in use you might need different firmware files: M700 base station update file M300 base station update file M65 handset update file M25 handset update file M5 repeater update file Before continuing, please make sure, that you downloaded all required files. The file naming is PRODUCTNAME_VERSION.fwu, please do NOT rename the files as the base station will look for filenames in exactly this scheme. For example: M700_v0320.fwu would be the update file for M700 with the version 320. Folder Structure: It is recommended to have a subfolder for the snom Mobile products, in these folder folders for each product is required. Note: Linux/Unix based HTTP servers are case sensitive, so please ensure that the folders are created with capital letters. M700 = OK, m700 will not work. The files need to be sorted in folders by product name: Version 1.1 Page | 12 ... -
Page 13: Wireless Device Firmware Upgrade
In the product folders multiple firmware files can be present (example for M700): Wireless device firmware upgrade: To perform an update to connected wireless devices (handsets/repeaters), you must provide corresponding update files to the base station and the desired firmware version needs to be defined. This chapter assumes you have deployed the firmware files according to the previous chapter. Snom recommends performing wireless updates when the whole system is in idle. In case the update is performs on an active live system, snom cannot guarantee uninterrupted functionality While it is possible to update the system in production, snom recommends not to do this. Manual Update (via Webserver): To manually trigger the update, please go to the web interface of the base station, and then go to the menu “Firmware Update”. Now enter next to the desired device the desired firmware version, which has to correspond with the firmware file name. Version 1.1 Page | 13 ... - Page 14 Once you press “Save/Start Update”, the base station will start the transfer to the endpoints. NOTE: Handsets will be updated the next time they are placed in the charger. Version 1.1 Page | 14 ...
- Page 15 Automatic Update (via provisioning): If remote provisioning is configured, the firmware update files to be used can be defined in the configuration file of the base station. The firmware relevant settings need to be in the <phone‐ settings> section. <phone-settings> <firmware-settings> <firmware>http://server/path</firmware> <fp_fwu_sw_version>318</fp_fwu_sw_version> BASE STATION FIRMWARE <pp_fwu_sw_version type=M65>318</pp_fwu_sw_version> DEVICE FIRMWARE M65 </firmware-settings> </phone-settings> Description of the settings: <firmware‐settings> This is the settings container for the individual firmware related settings. <Fp_squ_sw_version> defines the base station firmware version, this needs to be a decimal value (for example 318) <Pp_fwu_sw_verion> defines the firmware version for the attached devices (handsets and repeaters). It has the type parameter to define the version for each device. The value is decimal. Note: Up to Version 3.18 Build 9 the handset type needs to be entered as HEX‐value. The values are: 0x0D9A0079 = M65 0x0D9A007F = M5 0x0D9A008D = M25 The easier way would be to first update the base station to 3.18 Build 10, which directly supports the usage of the product names (M65, M25, M5). The wireless updates process: When a wireless device (handset or repeater) firmware update has been provided, there is a three step process for the update: ...
- Page 16 a. Handsets perform the firmware update as soon as they are put in the charger. The actual update takes ~1 Min. b. Repeaters will execute the updates as soon as there are no active calls. The device remains operational during firmware transfer, the DECT installation however might not operate at full capacity. The progress of the handset firmware upgrade can be monitored under Extensions. Note: The handset update process is visualized by the LED on the base station blinking red. After the update the successful transfer is verified. When the update has been successfully verified, the handset waits to be put in the charger to perform the actual update. Once the handset has been put in the charger, it will turn off; the LED will flash green rapidly and then flash red rapidly. When the update was successful it will turn on again. The current firmware and the status of the update will be shown: Considerations: The update transfer to a device takes on average ~10‐15 min. Depending on traffic conditions (Voice traffic is with priority); under certain conditions it might take up to 60 min. Using the device will pause the transfer process. It will continue once the handset is back in idle mode. Once the firmware has been transferred, the actual update takes ~1 min. Version 1.1 Page | 16 ...
-
Page 17: Wording
The M700 can update up to 10 devices, the M300 up to 5 devices at the same time. If more devices are registered with the base, they will be updated once another handset successfully received the firmware update. A repeater will start the update automatically once there are no calls. This leads to a short service interruption (~1 min), while the repeater is updating the firmware. The base station randomly selects the devices for firmware transfer. It is not possible to priorize certain devices. Multicell considerations: A M700 will update all handsets in range; also devices “homed” on a different cell. If the user moves from one cell to another, the update will continue (as long as sufficient update capacity is available). In case a cell is fully busy with firmware transfer, handover/roaming will fail (an active call might be lost). If a wireless device update is triggered on one base station all base stations will perform an update. Wording Master base station The base station in an installation, which will organize the topology and share the topology information with the entire installation. Version 1.1 Page | 17 ...
Need help?
Do you have a question about the M700 and is the answer not in the manual?
Questions and answers