Page 10
Server Profiles The Motivation: To increase snom m9 product ease of use and integration with 3 party iPBXs To provide support for non-standard functionality of some of the most popular VoIP platforms in the market To limit tailored FW builds by providing a single FW...
Page 15
Action URLs are HTTP GET Requests allowing the phone to interact with web server applications for CTI and remote notification Action URLs can be triggered on the snom m9 by predefined events of each connected handset snom m9 Webinar (ST802)
Page 17
CTI with Action URLs Setup: Each SIP Identity on the snom m9 base station provides this sets of Action URLs These Action URLs are triggered whenever a handset assigned to that Identity performs a particular action These Action URLs can either be configured manually...
Page 20
Picture Caller-ID Overview: The caller picture feature allows the snom m9 Handset to display the picture of the calling party All photo pictures provided to the snom m9 Base Station must be in 40 × 50 Pixels JPEG format snom m9 Webinar (ST802)
Page 22
Picture Caller-ID VCARDs: The feature allows the snom m9 Handset to display the calling party picture via VCARDs In order to use this feature, the user need to create a 40x50 Pixel JPEG and assign it the contact’s VCARD The VCARD then needs to be uploaded to the snom m9 Base station The snom m9 Base station would then relay the...
Page 24
Picture Caller-ID Uploading the VCARD to snom m9: Select the Identity for which you want to add the VCARD Upload the VCARD through the “VCARD(s) Upload” section The newly added VCARD should be visible under “Contacts” The picture of “Contact” will be displayed on the associated handset whenever a call is received from the “Contact”...
Page 25
Picture Caller-ID SIP “Call-Info”: The snom m9 is also able to display the calling party picture on the handset, via HTTP links For this purpose, the snom m9 Base station support the “icon” parameter of the SIP “Call-Info” header HTTP(s) links received in the “icon” parameter are...
Page 26
The Calling-party provides his picture in the “Call-Info” header of the SIP INVITE The “icon” parameter is used to specify the picture URL The snom m9 downloads the picture from the link and displays it on the handset snom m9 Webinar (ST802)
Page 29
LDAP can be used to retrieve Caller-ID related information from an LDAP server for incoming calls LDAP may also be used to view corporate address book (s) on the snom m9 Handset, and subsequently calling the contacts from the LDAP address book snom m9 Webinar (ST802)
Page 30
LDAP Caller-ID lookup with LDAP: This feature allows the snom m9 base station to retrieve the calling-party name from the LDAP server when an incoming call is received If the server returns a valid name for the calling number, the snom m9 base relays the calling party...
Page 31
LDAP Address book searching: On the snom m9, LDAP can also be used to view the corporate address book and subsequently place telephone calls to the contacts The snom m9 handset further allows the user to search through the LDAP address book returned from...
Page 37
IPv6 on snom m9 Address assignment and auto configuration The snom m9 is able to automatically assign an IPv6 address to the device over DHCPv6 Further more, when connected to an IPv6 network, the snom m9 can configure itself automatically using Internet...
Page 43
“snom CA” as default These “Client Certificates” allow the SIP server or Configuration server to verify the snom m9 base as an authentic device on the network The m9 base station is also able to perform “Server Identity Verification” based on trusted X.509 chains when SSL/TLS is used...
Page 48
Custom Client Certificates The client certificate of the snom m9 can also be customized by loading custom client certificate/private key pairs to the device Embedded within an XML file with <cert> and <key> tags, the snom m9 can be auto...
Page 50
Server Identity Verification The snom m9 base station is able to perform “Server Identity Verification” based on trusted X.509 chains when SSL/TLS is used Servers which present certificates signed by CAs unknown to the base are rejected By default, the snom m9 is designed to...
Page 52
Custom CA Setup Trusted Root CAs can also be customized on the snom m9 to tailor “Server Identity Verification” With <certificates> as the top XML tag, each trusted root CA can be enclosed within a <ca> snom m9 Webinar (ST802)
Page 56
Auto Configuration To administer a large pool of snom m9 devices, the device provides the possibility to configure settings and upgrade device Firmware with zero- touch interaction from the user These mechanisms allow the administrator to manage and monitor all snom m9 devices in the...
Auto Configuration Automatic Setup The most convenient way of auto configuring a snom m9 is via DHCP options 66 and 67 DHCP option 66 and 67 provide an HTTP(S) or TFTP configuration server’s address and a boot file-name for download Upon receiving the said DHCP options, the...
Page 58
Firmware In case a new Firmware is provided in the configuration file, the snom m9 downloads the Firmware and performs an automatic reboot This automatic Firmware upgrade mechanism...
Page 68
Diagnostics To increase responsiveness toward customers and reduce customer support overhead, the snom m9 provides a number of mechanisms for device diagnostics Such tools allow snom’s to provide a solution to customer reported issues in an efficient manner, even in the absence of physical access to the...
Diagnostics Packet Capture: As a further diagnostics tool, the snom m9 provides an on-device packet capture tool “Network Analyzer” Such packet captures provide an efficient way for snom to analyze and respond to any customer reported device issues snom m9 Webinar (ST802)
Need help?
Do you have a question about the m9 and is the answer not in the manual?
Questions and answers