25
ENTERPRISE-GRADE DEPLOYMENT WITH SNOM UC EDITION A guide to 1
| Date post: | 01-Jun-2015 |
| Category: |
Technology |
| Upload: | snom-technology |
| View: | 942 times |
| Download: | 5 times |
ENTERPRISE-GRADE DEPLOYMENTWITH SNOM UC EDITION
A guide to
1
Challenges from the market
Easy installation of phones
Easy configuration of installed phones
Management of thousands of phones
All without additional investment and hassle for the user / admin
2
snom‘s evolution in Lync
3
Native Lync Software Update + PIN/Ext Sign-in
Native Lync Device Management
Push-Pull CPE Maintenance
Number of devices installed
Level of M
anagem
ent
1000+
OUT-OF-THE-BOX INSTALLATIONSince 8.8.1.x / 8.8.2.x (Apollo)
4
Out-of-the-box Installation
5
Automatic FW Update 1
User Registration 2
InbandProvisioning 3
• Already provides the snom unique “ZERO Touch First Time Setup”:
• SIP firmware equipped devices in cardboard box support Lync Update Service
• Devices perform a user interaction free update to snom UC edition firmware
• Ready for Ext. & PIN sign in or NTLM sign in directly after the update
Out-of-the-box Installation
6
Lync Server
(IIS)
DNSDNS lookup request
FW request
UC edition FW file
Server URL1
2
3
4
Initial Lync in-band Provisioning
locationPolicy
mediaPolicy (e.g. bypass enabled)
serverConfiguration (e.g. enforce PIN lock, VM URI)
ucPolicy
userSetting (ucUserLocationProfile)
Enhanced Privacy
7
But there is no „one fits all“
8
Time zone
Language
Corporate design
Menu structure
User/-group defined
keypad lock policies
Phone hardening
(Common Area)
User specific fkey assignment
• Boss / Admin
• Contact/Presence
• Intercom
Music on Hold
Ring Tones
NATIVE DEVICE MANAGEMENTNEW!
9
Device Management approaches
10
Other Vendors
• Additional layer of complexity
• Investment in hardware, software, training and
maintenance increase total cost of ownership
• Limited to internal corporate networks
Native Lync device management
11
snom UC edition
• Leveraging the Lync admin’s daily interface: PowerShell!
• No DHCP server options or 3rd party equipment required!
• Not limited to internal corporate networks!
Lync device management workflowStep Description Example
1. Define your scenario based on
relevant snom settings in a .txt-file
File scenario_no_keypad_lock.txt contains:
server_enforced_kb_lock: off
enable_keyboard_lock: off
keyboard_lock: off
2. Create a new scenario-policy by
running Matt’s Lync PowerShell
script
Open the script in an editor and customize accordingly:
$pathandfile = "c:\snom-settings\scenario_no_keypad_lock.txt"
$policyname = "Test_No_Keypad_Lock".
Save the script and execute it.
3. Grant the policy to either a single
user or mass audience based on e.g.
Site, Pool, AD-Filters, Groups, Users.
Get-CsUser -LdapFilter "Title=*manager*" | Grant-CsClientPolicy -
PolicyName Test_No_Keypad_Lock
12
Matt Landis‘ blog post: http://bit.ly/1o2jCwC
Example: No Keypad Lock
13
1
2
3
Defining scenario
Creating policy
Granting policy
Note:
Using Matt’s Landis Lync PowerShell script is
not mandatory, but it greatly makes creating or
editing of management policies easier.
Example: BusyOnBusy & CallBack On Busy
14
1
2
3
Defining scenario
Creating policy
Granting policy
Note:
Using Matt’s Landis Lync PowerShell script is
not mandatory, but it greatly makes creating or
editing of management policies easier.
Native Lync Device Management
15
Automatic FW Update 1
User Registration 2
Managed Device 3
Native Lync Device Management
16
Lync Pool
SIP Registration/re-registration
UC edition FW file
1
2
Lync + snom settings
• Settings submission secured by SIP/TLS as default in Lync deployments
• Location & Topology independent (corporate & remote / home office users)
• Like Lync Client settings, snom specific settings roam with the user
• Already works with published snom UC edition FW 8.8.1.x and 8.8.2.x
Overview of settings
17
wiki.snom.comphoneIP.settings.htm
Side note
Changes will be pulled from the Lync server with each registration and re-registration of the device
Re-registration can be triggered by the user via the phone interface Reregister User(Menu -> 3 -> 2 -> 1)
18
PUSH-PULL MAINTENANCETR-069
19
Push-Pull Maintenance
20
ACS
Server
Retrieve ACS URL
FW & setting requests
UC edition FW & TR-069 configuration
1
2
3
Remote management established4
Auto-Configuration
Monitoring
Remote Reboot
Customization
XML notifications
FW updates
Seamless transition to an TR-069 system
Discovery and access information to the ACS (TR-069) system is typically provided via out-of-band provisioning
By using snom specific Lync native device management such information can be submitted SIP/TLS secured and without the need to touch each phone.
With seamless handover to optional full PUSH-PULL Maintenance can easily grow with the customer and its device management needs
21
Use cases for push-pull maintenance
Enterprise grade push-pull CPE maintenance
Recommended for 1000+ seats
remote view, reboot, firmware enrollment
device inventory
802.1x secure staging
Recommended in Service Level Agreements
Most enterprise switches, routers etc. already supportmanagemtent via TR-069
22
Summary
snom is the only vendor to support:
Out-of-the box zero touch installations
Native device management with Lync server
No additional Hardware or Software needed
Not limited to internal corporate networks
No vendor-specific DHCP options to be set
Push-pull maintenance for enterprise-grade installations
23
For more information…
24
Devices Services
Downloads Features
snom.com/lyncVisit
Contact
25
Copyright © 2000 – 2012 snom technology AG. All rights reserved. snom® is a registered trademark of snom technology AG and its affiliates in the European Union, USA, Japan, South Africa, Australia, China and certain other countries and regions. Unless specified otherwise, all trademarks, in particular product names, are legally protected trademarks of snom technology AG. Other mentioned trademarks or registered trademarks are the property of their respective manufacturers or owners. Product specifications are subject to change without notice. snom.com
Additional pictures by Svilen Milev, Craig Parylo and Ove Tøpfer
Mark Wiegleb
+49 30 39833-114
