Call Transfer

Download Report

Transcript Call Transfer

Interoperability Technology Leadership Reasonable Solutions

Technical Training VON Europe

Interoperability

Firmware Update: Topics

Technology Leadership Reasonable Solutions

Logical structure (partitioning) of flash memory and firmware image location Firmware Update Methods Manual HTTP update TFTP update Automatic HTTP update

Firmware Update: Logical structure Interoperability Technology Leadership Partitioning of flash memory Reasonable Solutions

Boot loader

„b“

Linux Kernel

„l“

Root File System (Linux System Files)

„r“

snom3x0 -3.25 l.bin

Ramdisk

snom360 jffs2ToRamdisk 3.31-br.bin

JFFS2

snom3X0 ramdiskToJffs2-3.36 br.bin

Application (JFFS2- File System)

„j“

snom3x0-X.X.X SIP-j.bin

Interoperability

Firmware Update: Methods

Technology Leadership Reasonable Solutions Firmware updates can be performed by the following distinct methods: Update Methods Manually via HTTP:

Software Update via Web Interface

Manually via TFTP:

TFTP Option via Phone GUI

Automatically via HTTP

•Most common when already on V6 •Exceptional situations •Downgrade

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

Interoperability Firmware Update: Manual HTTP Update Technology Leadership Reasonable Solutions Obtain the phone`s current FW version via Phone GUI

Interoperability Firmware Update: Manual HTTP Update Technology Leadership Reasonable Solutions Or obtain the phone`s current FW version via Web Interface (System Information)

Interoperability Firmware Update: Manual HTTP Update Technology Leadership Reasonable Solutions Copy the appropriate FW image link from the WIKI`s firmware update guide

Interoperability Firmware Update : Manual HTTP Update Technology Leadership Reasonable Solutions 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

Interoperability Firmware Update : Manual HTTP Update Technology Leadership Reasonable Solutions Go to the Web interface´s „Manual Software Update“ page and paste the link, press „Load“

Interoperability

Firmware Update: TFTP Update

Technology Leadership Reasonable Solutions 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

Interoperability

Firmware Update: TFTP Update

Technology Leadership Reasonable Solutions PC running TFTP Server:

- Check of PC`s network settings (10.0.0.2) - TFTP Server installation on 10.0.0.2 and configuration

Interoperability

Firmware Update: TFTP Update

Technology Leadership Reasonable Solutions 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

Interoperability

Firmware Update: TFTP Update

Technology Leadership Reasonable Solutions Snom phone:

Rebooting the phone 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

Interoperability

Firmware Update: TFTP Update

Technology Leadership Reasonable Solutions TFTP Server: Showing the progress of the file upload

Interoperability Firmware Update: Automatic HTTP Update (via snom`s provisioning server) Technology Leadership Reasonable Solutions Assignment of one of the following provisioning URLs (manually or via DHCP):

- http://provisioning.snom.com/release/update_once.php - http://provisioning.snom.com/release/update.php - 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

Interoperability Firmware Update: Automatic HTTP Update (via snom`s provisioning server) Technology Leadership Reasonable Solutions Example php scripts

- 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("

\n"); echo("update_policy: auto_update\n"); echo("firmware_status: ".$firmware_status."\n"); echo("
\n"); echo("\n"); } else { echo("\n"); 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"); echo("\n");

Interoperability

Mass Deployment

Technology Leadership Reasonable Solutions 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

Interoperability

Mass Deployment: Overview

Technology Leadership Reasonable Solutions

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 specific settings (e.g. language, timezone, tone scheme etc.) or phone (e.g. SIP identity settings) but also initiate firmware updates / downgrades

Interoperability

Mass Deployment: Methods

Technology Leadership Reasonable Solutions Mass Deployment implementation may vary depending on the phone environment: Phone environment Local Area Network

e.g. managed company/SOHO LAN •LAN using DHCP •LAN using fix IP

addresses Requirements:

•DHCP Server •TFTP or HTTP(S) server for phone settings •HTTP(S) server for FW update

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: Prerequisites Interoperability Technology Leadership Reasonable Solutions 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

Interoperability

Mass Deployment: Setting Files

Technology Leadership Reasonable Solutions Setting file structure:

- ASCII-based files - lines may end with newline or carriage return/newline pairs - Comments start with a # or a < character - The < and > 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

Interoperability

Mass Deployment: Setting Files

Technology Leadership Reasonable Solutions 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“

Interoperability

Mass Deployment: Setting Files

Technology Leadership Reasonable Solutions 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.

Mass Deployment: Firmware Update Interoperability Technology Leadership Reasonable Solutions 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

Interoperability Mass Deployment: Boot- up- process Technology Leadership Reasonable Solutions

•

Part1: Setting provisioning :

•

1) Loading settings from the flash memory

if DHCP is enabled it will send an DHCP discover

2) 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]

3) No MAC parameter specified & HTML

e.g. http://.../snom3xx.htm

4) Request of general settings file

• Receiving of settings • Writing settings to flash memory

5) 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

6) Activating new settings 3) MAC parameter specified & Script

e.g. http://.../snom.php?mac= {mac}

•

4) Request of the resulting setting file

Receiving of both general and phone specific settings at once • Writing settings to flash memory

5) Activating new settings

Interoperability Mass Deployment: Boot- up- process Technology Leadership Part2: FW update Reasonable Solutions

•

6) Firmware Update Check

phone checks the setting „firmware_status“

7) firmware_status: URL

e.g. http://.../snom3xx-firmware.htm

7) firmware_status:

•

8) 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

9) FW image URL`s

•

different

FW update will be performed

Provisioning & FW Update finished

•

9) FW image URL`s equal

FW update will NOT be performed

Provisioning finished Provisioning finished

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Web (HTTP) Server installed on 10.0.0.2: Reasonable Solutions

Interoperability Mass Deployment : Example using HTTP & DHCP Technology Leadership Reasonable Solutions 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

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Content of setting files:

- snom360.htm

- snom360-0004132314A4 .htm

Reasonable Solutions

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Content of firmware configuration files:

- snom360-firmware.htm

Reasonable Solutions

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership DHCP Server on 10.0.0.2:

- Option 66: http://10.0.0.2

- Option 67: snom360.htm

Reasonable Solutions

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Reasonable Solutions Snom360:

Out of the box (factory values)/ Factory value reset - Power up/ Reboot via SIP NOTIFY Boot Up Process

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Ethereal analysis

- DHCP Discover/ Offer

Reasonable Solutions

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Reasonable Solutions Ethereal analysis: Plug And Play (PnP) default delay

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Reasonable Solutions Ethereal analysis: HTTP Setting File request

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Snom360: Settings page check Reasonable Solutions Snom360.htm

Snom360.htm

Snom360-firmware.htm

DHCP: 67 Snom360.htm

Factory Value DHCP: 66 Factory Value

Interoperability Mass Deployment: Example using HTTP & DHCP Technology Leadership Snom360: Settings page check Snom360-0004132414A4.htm

Reasonable Solutions Snom360-0004132414A4.htm

Snom360-0004132414A4.htm

Interoperability Mass Deployment: Setting Server Redirection Technology Leadership Reasonable Solutions 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

Mass Deployment: Setting Server Redirection Interoperability

Snom provisioning

snom.com

ProvDB

Domain1

Domain2 Domain3 LAN Firewall NAT solved

Technology Leadership

LAN Domain1

MACxx1

MACxx2 MACxx3

Reasonable Solutions Customer ssh account

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

Registered Phone

MACxx1 Domain1 config Domain 1 FW Phone Phone Phone FAX ATA Cordless

Mass Deployment: PnP configuration Interoperability Technology Leadership Reasonable Solutions 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.

Interoperability

Call Transfer

Technology Leadership Reasonable Solutions

Overview Terminology Blind Transfer

- Usage - Demonstration

Attended Transfer

- Default method - Call Join On Xfer - Transfer On On- Hook

Analyzing „Attended Transfer“ on SIP level

Interoperability

Call Transfer: Overview

Technology Leadership Reasonable Solutions 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

Interoperability

Call Transfer: Terminology

Technology Leadership Reasonable Solutions

Phone A (calling party to be transferred) Phone B (extension performing the transfer) Phone C (extension of the transfer destination)

Interoperability

Call Transfer: Blind Transfer

Technology Leadership Reasonable Solutions B

A calls B, B answers B places A on „Hold“ B presses „Transfer“ B presses B dials C B hangs up B calls C B hangs up A establishes C call C terminates B call B terminates A call

A C

Interoperability

Call Transfer: Blind Transfer

Technology Leadership

Blind Transfer demonstration

Reasonable Solutions

Interoperability Call Transfer: Attended Transfer (n calls) Technology Leadership Reasonable Solutions Advanced Page: Call Join On Transfer: OFF

Interoperability Call Transfer: Attended Transfer Technology Leadership Reasonable Solutions B

A calls B, B answers B places A on „Hold“ B presses

B dials C C answers B presses „Transfer“ and hangs up

B calls C C answers B presses B selects A(n) from held call list B confirms A establishes C call C terminates B call B terminates A call

A C

Interoperability Call Transfer: Attended Transfer (n calls) Technology Leadership Reasonable Solutions

Attended Transfer demonstration

Interoperability Call Transfer: Attended Transfer Technology Leadership Reasonable Solutions 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

Interoperability Call Transfer: Attended Transfer Technology Leadership Reasonable Solutions 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

Interoperability Call Transfer: Attended Transfer Technology Leadership Reasonable Solutions 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

Interoperability Call Transfer: Attended Transfer (2 calls) Technology Leadership Advanced Page: Call Join On Transfer: ON Reasonable Solutions

Interoperability Call Transfer : Attended Transfer (2 calls) Technology Leadership Reasonable Solutions B

A calls B, B answers B places A on „Hold“ B presses

B dials C C answers B presses „Transfer“ and hangs up

B calls C C answers B presses B confirms A establishes C call C terminates B call B terminates A call

A C

Interoperability Busy Lamp Field (BLF) Function Technology Leadership Reasonable Solutions

Overview Configuration Usage

Interoperability Busy Lamp Field (BLF) Function: Overview Technology Leadership Reasonable Solutions Overview

- BLF function allows to show the status (idle, ringing, busy) of a distinct phone extension on your phone

B A

Interoperability Busy Lamp Field (BLF) Function: Configuration Technology Leadership Configuration

- Via Web Interface´s Function Key page

Reasonable Solutions

Interoperability Busy Lamp Field (BLF) Function: Configuration Technology Leadership Reasonable Solutions 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

Interoperability Computer Telephony Integration (CTI) Technology Leadership Reasonable Solutions

Overview Syntax Command Set Dialling complete numbers Usage

Interoperability Computer Telephony Integration (CTI) Technology Leadership Reasonable Solutions 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

Interoperability Computer Telephony Integration (CTI) Technology Leadership Reasonable Solutions Dialling complete numbers:

- http://phoneIP/command.htm?number=12345678&outgoing _uri=account@registrar - Instead of command.htm -> index.htm can be used

Interoperability Computer Telephony Integration (CTI) Technology Leadership Reasonable Solutions 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

Interoperability Action URLs Technology Leadership Reasonable Solutions

Definition

- Action URL settings page - Action URL Key Event on Function Key page

Syntax

- Example - Debugging

Usage

Interoperability Action URLs: Overview Technology Leadership Reasonable Solutions 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)

Interoperability Action URLs: Setting Page Technology Leadership Reasonable Solutions Predefined Events Action URLs:

Static phone settings Runtime status

Interoperability Action URLs: Setting Page Technology Leadership 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

Reasonable Solutions

Interoperability Action URLs: Syntax/ Example Technology Leadership Reasonable Solutions 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

Action URLs: Example/ Debugging Interoperability Technology Leadership Example

- Dialling from Web Interface´s Home page

Reasonable Solutions Debugging

- Log page, Log Level 2

Action URLs: Example (1) Interoperability Technology Leadership Reasonable Solutions 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 [email protected]

Interoperability Action URLs: Function Key Page Technology Leadership Reasonable Solutions 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“

Action URLs: Example (2) Interoperability Technology Leadership Reasonable Solutions 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

Interoperability

Phonebook Support

Technology Leadership Reasonable Solutions

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

Interoperability

Phonebook Support: Overview

Technology Leadership Reasonable Solutions Phone Book Support Internal Address Book

Access via Phone GUI/ Web Interface

Features

Up to 100 entries Update/ backup possibilities Contacts can be grouped Ringtones may be assigned to groups 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

Interoperability Phonebook Support: Internal Address Book Technology Leadership Reasonable Solutions

Interoperability Phonebook Support: Internal Address Book Technology Leadership Reasonable Solutions 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

Interoperability Phonebook Support: Outlook Add- In Technology Leadership External Phone Book Integration (1)

- MS Outlook ® Add- In

Reasonable Solutions

Interoperability Phonebook Support: LDAP Support Technology Leadership Reasonable Solutions External Phone Book Integration (2)

- Snom3xx phones have integrated LDAP clients (V2) - Basic LDAP support since FW V5.0 - Enhanced navigation since FW V6.3 - LDAP configuration via Web Interface: - Server Address: IP address of the LDAP server. - Port: The port on which the LDAP server is listening, e.g. 389 - Base: The root of the LDAP tree - Username: Your username to access the LDAP server. - Password: Your password to access the LDAP server. - Max. Hits: Specify the maximum number of entries an LDAP request will deliver back.

Interoperability Phonebook Support: LDAP Support Technology Leadership External Phone Book Integration (2)

- Example of LDAP usage - LDAP Server: 152.1.226.117

- Base: ou=people,dc=ncsu,dc=edu

Reasonable Solutions

Desktop Messages: Prerequisites Interoperability Technology Leadership Reasonable Solutions Prerequisites:

- Snom3XX: - Identity: [email protected]

- 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

Interoperability

Desktop Messages: SIP Trace

Technology Leadership Reasonable Solutions

Interoperability Desktop Messages: Phone Display Technology Leadership Reasonable Solutions

Phone Display

Interoperability Technology Leadership Reasonable 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 [email protected]

Gradestr. 46, 12347 Berlin, Germany.