1. InteroperabilityTechnology LeadershipReasonable Solutions Technical Training VON Europe

2. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Topics Logical structure (partitioning) of flash memory and firmware image location Firmware Update Methods Manual HTTP update TFTP update Automatic HTTP update

3. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Logical structure Partitioning of flash memory Boot loader „b“ BL ENV Settings Linux Kernel „l“ Root File System (Linux System Files) „r“ Application (JFFS2- File System) „j“ Ramdisk snom360- jffs2ToRamdisk- 3.31-br.bin JFFS2 snom3X0- ramdiskToJffs2-3.36- br.bin snom3x0 -3.25- l.bin snom3x0-X.X.X- SIP-j.bin

4. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Methods Firmware updates can be performed by the following distinct methods: Update Methods Manually via HTTP: Software Update via Web Interface Most common when already on V6 Manually via TFTP: TFTP Option via Phone GUI Exceptional situations Downgrade Automatically via HTTP PHP Script via snom´s provisioning server Automates manual steps Keeps the phone up-to- date Mass Deployment via own provisioning server Useful in big deployments for ITSP or distributors

5. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Manual HTTP Update Obtain the phone`s current FW version via Phone GUI

6. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Manual HTTP Update Or obtain the phone`s current FW version via Web Interface (System Information)

7. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Manual HTTP Update Copy the appropriate FW image link from the WIKI`s firmware update guide firmware update guide

8. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update : Manual HTTP Update Depending on the current FW version manual HTTP update requires up to 4 steps until V6: Version: 3.X/ 4.X 1: Application: 5.5a 2: Root FS: 3.36 3: Application: 6.X 4: Linux: 3.25

9. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update : Manual HTTP Update Go to the Web interface´s „Manual Software Update“ page and paste the link, press „Load“

10. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: TFTP Update Should ONLY be used in the following exceptional situations: -Malfunction of HTTP update although the correct image file was used (some rare 4.1 issues) -HTTP update (Erasing/ Writing application) was interrupted by power failure -Downgrade -NOTE: TFTP procedure will reset all settings to factory values Requirements: -PC (acting as TFTP Server) and phone should be preferrably connected peer to peer -ONLY application firmware images can be used -Images have to be downloaded to the PC acting as TFTP server in advance; the file name MUST be changed to snomXXX.bin

11. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: TFTP Update PC running TFTP Server: -Check of PC`s network settings (10.0.0.2) -TFTP Server installation on 10.0.0.2 and configuration

12. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: TFTP Update PC running TFTP Server: -Download of the appropriate application image file from snom`s Website, rename file and place it into TFTP servers download directory

13. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: TFTP Update Snom phone: -Rebooting the phoneRebooting the phone -TFTP boot up procedure:TFTP boot up procedure: -Pressing of any key during TFTP input challenge -Entering the phone´s temporary IP address (in the same subnet as TFTP server) -Entering the TFTP servers IP address -Phone starts loading *.bin File from TFTP server -Phone deletes flash partition and writes the new application image -Phone reboots with new application loaded

14. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: TFTP Update TFTP Server: Showing the progress of the file upload

15. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Automatic HTTP Update (via snom`s provisioning server) Assignment of one of the following provisioning URLs (manually or via DHCP): -h-http://provisioning.snom.com/release/update_once.php -h-http://provisioning.snom.com/release/update.php -h-http://provisioning.snom.com/beta/update.php Reboot (manually or via SIP NOTIFY) Phone contacts snom`s provisioning server and the choosen script updates automatically any previous firmware version to latest version

16. InteroperabilityTechnology LeadershipReasonable Solutions Firmware Update: Automatic HTTP Update (via snom`s provisioning server) Example php scripts -E-E.g. http://provisioning.snom.com/release/update_once.php $agent = $HTTP_SERVER_VARS['HTTP_USER_AGENT']; $info = explode(';', $agent); $phone_type = "snom"; if (strpos($agent, "snom300") > 0){ $phone_type = "snom300"; } else if (strpos($agent, "snom320") > 0){ $phone_type = "snom320"; } else if (strpos($agent, "snom360") > 0){ $phone_type = "snom360"; } if (strcmp($agent, "Mozilla/4.0 (compatible; ".$phone_type."-SIP 6.2.3; ".$phone_type." jffs2 v3.36; ".$phone_type." linux 3.25)") != 0) { $firmware_status="http://provisioning.snom.com/release/firmware.php"; echo(" \n"); echo("update_policy: auto_update\n"); echo("firmware_status: ".$firmware_status."\n"); echo(" \n"); } else { echo(" \n"); echo("update_policy$: settings_only\n"); echo("setting_server$: http://provisioning.snom.com/".$phone_type."/".$phone_type.".php?mac={mac}\n"); echo(" \n"); }

17. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment Overview Methods for distinct phone environments Usage in LANs w/ DHCP -Prerequisites -Setting file structure -Hints for setting files -Firmware Update requirements -Boot up process diagramm Demonstration -Factory reset -Boot up process -Analysis: Ethereal/ Setting page Setting Server Redirection PnP – new ways of mass provisioning

18. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Overview Mass Deployment is a function which permits the phone to retrieve its settings from a remote server (TFTP/ HTTP(S)) Mass Deployment is very useful for larger phone installations Mass Deployment can not only be used to provide general settings (e.g. language, timezone, tone scheme etc.) or phone specific settings (e.g. SIP identity settings) but also initiate firmware updates/ downgrades

19. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Methods Phone environment Local Area Network e.g. managed company/SOHO LAN LAN using DHCP Requirements: DHCP Server TFTP or HTTP(S) server for phone settings HTTP(S) server for FW update LAN using fix IP addresses Requirements: TFTP or HTTP(S) server for phone settings HTTP(S) server for FW update Randomly distributed e.g. distributor or ITSP network Requirements: Redirection of default provisioning server Phone MAC address management via snom`s provisioning console Public HTTP(S) server PHP knowledge Mass Deployment implementation may vary depending on the phone environment:

20. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Prerequisites 1: Running TFTP/ HTTP(S) Server and setting file (HTML or script) -E.g. http://prov.company.com/settings/snom3xx.htm -E.g. http://prov.company.com/settings/snom.php -E.g. tftp://prov.company.com/settings/snom.cfg 2: Configuration of option 66/67 on DHCP server -Option 66/sname: HTTP/HTTPS/TFTP setting server, e.g. http://prov.company.com -Option 67/file: Path to HTML/script setting file, e.g. settings/snom3xx.htm 3: Factory resetted snomXXX -Setting Server URL should not have been changed manually before -> Reset to factory values

21. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Setting Files Setting file structure: -ASCII-based files -lines may end with newline or carriage return/newline pairs -Comments start with a # or a < character -The characters allow easy integration of html tags -Names may consist of the characters a-z, A-Z, 0-9 and _. -Basically all available settings available on the Web Interfaces setting page may be used

22. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Setting Files Use ONLY as little settings as necessary: -General settings e.g: -language$, timezone$, -Account specific settings: -user_pname1$, user_name1$, user_realname1$, user_host1, user_srtp1$ etc. -Firmware Update related settings -firmware_status, update_policy, firmware_interval Use ONLY „$“ flags at the beginning -! = Setting may not be overwritten when it was changed by the user before -& or no flag will definitely overwrite existing setting and mark it „read-only“

23. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Setting Files Do NOT use: -Network settings: -dhcp, gateway, dns_server1 etc. -Setting server URL: -unless you want to redirect the phone to a different setting server -Firmware setting: -firmware/ bootloader -use ONLY "firmware_status" instead -Other internal settings: -update_server, update_filename, update_host_b, update_host_f, sip_port, reset_settings, reboot_after_nr, watch_arp_cache etc.

24. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Firmware Update A firmware configuration file must be located on the TFTP/ HTTP(s) server -E.g. http://prov.mycompany.com/settings/firmware.htm -ASCII-based file -must ONLY use „firmware“ setting w/o flags: -firmware: http://.../snom3xx-X.X.bin The setting file „snom3xx.htm“ links to „firmware.htm“ via firmware_status: -firmware_status: http://prov.company.com/settings/firmware.htm

25. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Boot- up- process 1)Loading settings from the flash memory if DHCP is enabled it will send an DHCP discover 1)DHCP offer: phone receives its network settings (IP address, net mask, gateway, DNS server, NTP server etc.) setting server URL [- > update_server]/ setting file path [-> update_filename] 1)No MAC parameter specified & HTML e.g. http://.../snom3xx.htm 1)Request of general settings file Receiving of settings Writing settings to flash memory 1)Request of the setting file appended by the phone´s MAC address e.g. http://.../ snom- 000413XXXXX.htm Receiving of phone specific settings Writing settings to flash memory 1)Activating new settings 1)MAC parameter specified & Script e.g. http://.../snom.php?mac= {mac} 1)Request of the resulting setting file Receiving of both general and phone specific settings at once Writing settings to flash memory 1)Activating new settings Part1: Setting provisioning :

26. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Boot- up- process 1)Firmware Update Check phone checks the setting „firmware_status“ 1)firmware_status: URL e.g. http://.../snom3xx-firmware.htm 1)Request of the firmware configuration file Receiving of the setting „firmware“ Comparision of the FW image URL and the last one stored on the phone 1)FW image URL`s different FW update will be performed Provisioning & FW Update finished 1)FW image URL`s equal FW update will NOT be performed Provisioning finished 1)firmware_status: Provisioning finished Part2: FW update

27. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Web (HTTP) Server installed on 10.0.0.2:

28. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment : Example using HTTP & DHCP Web (HTTP) Server provides: -General settings file http://10.0.0.2/snom360.htm -Specific setting file http://10.0.0.2/snom360-0004132314A4.htm -Firmware configuration file http://10.0.0.2/snom360-firmware.htm -Firmware image file http://10.0.0.2/snom360-6.5.1-SIP-j.bin

29. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Content of setting files: -snom360.htm -snom360-0004132314A4.htm

30. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Content of firmware configuration files: -snom360-firmware.htm

31. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP DHCP Server on 10.0.0.2: -Option 66: http://10.0.0.2 -Option 67: snom360.htm

32. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Snom360: -O-Out of the box (factory values)/ Factory value reset -P-Power up/ Reboot via SIP NOTIFY -B-Boot Up Process

33. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Ethereal analysis -DHCP Discover/ Offer

34. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Ethereal analysis: Plug And Play (PnP) default delay

35. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Ethereal analysis: HTTP Setting File request

36. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Snom360: Settings page check Snom360.htm Snom360-firmware.htm DHCP: 67 Snom360.htm Factory Value DHCP: 66 Factory Value

37. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Example using HTTP & DHCP Snom360: Settings page check Snom360-0004132414A4.htm

38. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Setting Server Redirection Snom phones contact snom provisioning server first (hardcoded in FW): -http://provisioning.snom.com/snom3x0/snom3x0.php?mac= {mac} -Settings script doesn´t deliver any settings back to the phone Distributors may ask for redirection ssh accounts to redirect the setting server URL to their own (public) HTTP setting servers Redirection is based on MAC address registration Registered MAC addresses will be redirected

39. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: Setting Server Redirection Snom provisioning snom.com Firewall NAT solved Phone Registered Phone MACxx1 Domain1 config Domain 1 FW ATA FAXCordless LAN ProvDB Domain1 Domain2 Domain3 Domain1 MACxx1 MACxx2 MACxx3 Welcome, arcor190! Type help for help. ==> help Welcome to the snom configuration tool. You may use the following commands: SHOW : Show the status of a phone. REGISTER : Register a phone. REG : Same as REGISTER. DEREGISTER : Deregister a phone. LIST : List all phones assigned. BYE : Leave this tool. A MAC address may be entered as 3 to 6 digit hexadecimal number, case does not matter (e.g. 2e4 --> 0004132202E4) ==> list 000413101214 00041310123C LAN Customer ssh account

40. InteroperabilityTechnology LeadershipReasonable Solutions Mass Deployment: PnP configuration PnP Config: -"ON" (by default) the phone sends a SUBSCRIBE message to a multicast address (224.0.1.75) -All setting servers which have membership to the group can respond to the SUBSCRIBE and send NOTIFY messages with the setting server HTTP URL in the body. -The phone then retrieves its settings from the link specified. -This is particularly useful for out of the box setup of devices and mass deployment.

41. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer Overview Terminology Blind Transfer -Usage -Demonstration Attended Transfer -Default method -Call Join On Xfer -Transfer On On- Hook Analyzing „Attended Transfer“ on SIP level

42. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Overview Call Transfer feature of classic PBX provides different methods to transfer an incoming call to another extension can be distinguished by the way the call is treated after initiating the transfer Blind Transfer the outcome of the call is NOT determined (used in most voice mail applications) Direct Transfer (= Redirection)Standard Blind Transfer Attended Transfer call progress results are used in order to proceed (for example if the transferred party has answered, was busy etc.) Transfer On Onhook Joints 2 calls on onhook Call Join On Transfer Attended Transfer (> 2 calls) Call Join On Transfer: OFF Attended Transfer (2 calls) Call Join On Transfer: ON

43. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Terminology Phone B (extension performing the transfer) Phone A (calling party to be transferred) Phone C (extension of the transfer destination)

44. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Blind Transfer A calls B, B answers B places A on „Hold“ B presses „Transfer“ B dials C B hangs up B presses A establishes C call C terminates B call B terminates A call A C B B calls C B hangs up

45. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Blind Transfer Blind Transfer demonstration

46. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Attended Transfer (n calls) Advanced Page: Call Join On Transfer: OFF

47. InteroperabilityTechnology LeadershipReasonable Solutions B presses Call Transfer: Attended Transfer A calls B, B answers B places A on „Hold“ B dials C C answers B presses „Transfer“ and hangs up B presses A C B A establishes C call C terminates B call B terminates A call B selects A(n) from held call list B confirms B calls C C answers

48. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Attended Transfer (n calls) Attended Transfer demonstration

49. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Attended Transfer SIP Call Flow (1) A initiates call to B B is ringing B answers the call A acknowledges A talks to B B places A on hold A accepts hold B acknowledges

50. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Attended Transfer SIP Call Flow (2) B initiates call to C C is ringing C answers the call B acknowledges B talks to C (announces transfer) B presses „Transfer“ which places C automatically on hold C accepts hold B acknowledges

51. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Attended Transfer SIP Call Flow (3) B chooses A from held call list and confirms A accepts the transfer destination to be C A initiates call to C C accepts call from A C terminates call to B B accepts A notifies B to terminate call A acknowledges A talks to C B accepts notification B terminates A call A accepts

52. InteroperabilityTechnology LeadershipReasonable Solutions Call Transfer: Attended Transfer (2 calls) Advanced Page: Call Join On Transfer: ON

53. InteroperabilityTechnology LeadershipReasonable Solutions B presses Call Transfer : Attended Transfer (2 calls) A calls B, B answers B places A on „Hold“ B dials C C answers B presses „Transfer“ and hangs up B presses A C B A establishes C call C terminates B call B terminates A call B confirms B calls C C answers

54. InteroperabilityTechnology LeadershipReasonable Solutions Busy Lamp Field (BLF) Function Overview Configuration Usage

55. InteroperabilityTechnology LeadershipReasonable Solutions Busy Lamp Field (BLF) Function: Overview Overview -BLF function allows to show the status (idle, ringing, busy) of a distinct phone extension on your phone B A

56. InteroperabilityTechnology LeadershipReasonable Solutions Busy Lamp Field (BLF) Function: Configuration Configuration -Via Web Interface´s Function Key page

57. InteroperabilityTechnology LeadershipReasonable Solutions Busy Lamp Field (BLF) Function: Configuration Configuration 1.Select any available Function key and choose key type „Extension“from the drop down list 2.The remote phone extension has to be configured as „number“ using the extension number or SIP URI format: extension@SIPdomain 3.„Context“ can be assigned to any local SIP identity (account, registration, line) which had successfully registered at the same SIP domain before

58. InteroperabilityTechnology LeadershipReasonable Solutions Computer Telephony Integration (CTI) Overview Syntax Command Set Dialling complete numbers Usage

59. InteroperabilityTechnology LeadershipReasonable Solutions Computer Telephony Integration (CTI) Method used to use CTI with snom phones -HTTP requests Syntax -http://phoneIP/command.htm?key={KEYEVENT} -phoneIP = address of snom phone -'command.htm' = HTML page where the post value „key“ can be evaluated Command Set -KEYEVENT: CANCEL, CLEAR, ENTER, OFFHOOK, ONHOOK, RIGHT, LEFT, FUNCTION, MENU, REDIAL, F1, F2, F3, F4, SPEAKER, DISCONNECT, RECALL, BREAK, 0-9, *, #, P1- Px, EK1- EK42

60. InteroperabilityTechnology LeadershipReasonable Solutions Computer Telephony Integration (CTI) Dialling complete numbers: -http://phoneIP/command.htm?number=12345678&outgoing _uri=account@registrar -Instead of command.htm -> index.htm can be used

61. InteroperabilityTechnology LeadershipReasonable Solutions Computer Telephony Integration (CTI) Usage -Simplest usage is pasting the URL into any Web Browsers address line and press „Enter“ -More sophisticated CTI applications are easy to implement by using the complete command set -Phone may interact with the CTI application by using Action URLs

62. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs Definition -Action URL settings page -Action URL Key Event on Function Key page Syntax -Example -Debugging Usage

63. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Overview Action URLs HTTP GET Requests allow the phone to interact with internal/external Web Server Automatically Via Web Interface´s „Action URL Settings“ page Predefined Events: DND on/off - Redirection on/off Incoming call/Outgoing call - Setup finished On offhook/onhook - Missed call On Connected/Disconnected Static phone settings See Settings page Runtime status $local, $remote and $call-id Manually Via Web Interface´s „Function Key“ page -> Key Type „Action URL“ Established by pressing the correspondend function key Start internal/external Minibrowser application (currently only snom360) Send static status information to external Web Server (example)

64. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Setting Page Predefined Events Action URLs: Static phone settings Runtime status

65. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Setting Page Action URL Setting page -Predefined events -DND On/Off -Redirection On/Off -Incoming/ Outgoing Call -Setup finished -Off- / On- hook -Missed Call -On connected/ disconnected -Static phone settings -Run- time status

66. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Syntax/ Example Syntax -normal HTTP- URL: http://server/path/app -Parameter list separated by „&“ -Static settings: e.g. weblang=$language -Runtime status: dialled=$remote Example -Action URL page -> Outgoing Call: -http://test/test.php?weblang=$language&dialled=$re mote

67. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Example/ Debugging Example -Dialling from Web Interface´s Home page Debugging -Log page, Log Level 2

68. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Example (1) Example (1) -Hotline Functionality: the phone dials a predefined number automatically on handset pickup (off-hook) -May be desired in hotel lobbies, hospitals or other public areas -Action URL page -> On Offhook: -http://127.0.0.1/index.htm?number=486&outgoing_uri=48 4@intern.snom.de

69. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Function Key Page Action URL Key Type on Function Key page -Choose Key Type „Action URL“ from the Drop Down List -Type the Action URL into the „number field“

70. InteroperabilityTechnology LeadershipReasonable Solutions Action URLs: Example (2) Example (2) -Call Center with several agents -Call distributor should be updated which agent (extension) is available -Solution: function key with key type „Action URL“ may be configured this way -http://server/free.php?number=$user_name1

71. InteroperabilityTechnology LeadershipReasonable Solutions Phonebook Support Overview -Internal/ External Address Book Internal address book -Features, Limits, Usage External phone book integration -MS Outlook Add- In -LDAP support -XML Phone Book Support Examples

72. InteroperabilityTechnology LeadershipReasonable Solutions Phonebook Support: Overview Phone Book Support Internal Address Book Access via Phone GUI/ Web Interface Features Up to 100 entries Update/ backup possibilities Contacts can be grouped R i n g t o n e s m a y b e a s s i g n e d t o g r o u p s Address Book names may be used to display incoming/ outgoing calls (instead of numbers) External Phone Book Integration MS Outlook Add In Access via MS Outlook Dialling via HTTP request LDAP Support Integrated LDAP client Access via Phone GUI Configuration via Web Interface XML Phone Book Access via Phone GUI Currently ONLY on snom360

73. InteroperabilityTechnology LeadershipReasonable Solutions Phonebook Support: Internal Address Book

74. InteroperabilityTechnology LeadershipReasonable Solutions Phonebook Support: Internal Address Book Internal Address Book -Features -Up to 100 entries -Update/ backup possibilities -via CSV file import/ export -MS Outlook ® import (by using snom´s MS Outlook ® Add- In) -via mass deployment -Contact grouping -None, Friends, Family, Colleagues, VIP, Deny List -Ringtones can be assigned to groups -Address Book names may be used to display incoming/ outgoing calls (instead of numbers) -Disadvantage -Limited to 100 entries -Central update/ backup cumbersomely

75. InteroperabilityTechnology LeadershipReasonable Solutions Phonebook Support: Outlook Add- In External Phone Book Integration (1) -MS Outlook ® Add- In

76. InteroperabilityTechnology LeadershipReasonable Solutions Phonebook Support: LDAP Support External Phone Book Integration (2) -S-Snom3xx phones have integrated LDAP clients (V2) -B-Basic LDAP support since FW V5.0 -E-Enhanced navigation since FW V6.3 -L-LDAP configuration via Web Interface: -S-Server Address: IP address of the LDAP server. -P-Port: The port on which the LDAP server is listening, e.g. 389 -B-Base: The root of the LDAP tree -U-Username: Your username to access the LDAP server. -P-Password: Your password to access the LDAP server. -M-Max. Hits: Specify the maximum number of entries an LDAP request will deliver back.

77. InteroperabilityTechnology LeadershipReasonable Solutions Phonebook Support: LDAP Support External Phone Book Integration (2) -Example of LDAP usage -LDAP Server: 152.1.226.117 -Base: ou=people,dc=ncsu,dc=edu

78. InteroperabilityTechnology LeadershipReasonable Solutions Desktop Messages: Prerequisites Prerequisites: -Snom3XX: -Identity: 493@192.168.7.24 -Support broken Registrar to "on„ -Filter Packets from Registrar to "off„ -Network identity (port): 5060 -> Reboot! -Preparations on PC (Linux/ Windows): -Install SIPSAK -Enter this command: -sipsak -i -M -B "Test" -s sip:493@phoneIP

79. InteroperabilityTechnology LeadershipReasonable Solutions Desktop Messages: SIP Trace

80. InteroperabilityTechnology LeadershipReasonable Solutions Desktop Messages: Phone Display Phone Display

81. InteroperabilityTechnology LeadershipReasonable Solutions © 2006 snom technology AG The author has made his best effort to prepare this document. The content is based upon latest information, whenever possible. The author makes no representation or warranties of any kind with regard to the completeness or accuracy of the contents herein and accepts no liability of any kind, including, but not limited to, performance, merchantability, fitness for any particular purpose, or any losses or damages of any kind caused or alleged to be caused directly or indirectly by this document. For more information, mail info@snom.com Gradestr. 46, 12347 Berlin, Germany.