Page 1 November 2011 Deploying the snom ONE IP Telephone System Technical Manual Kevin Moroz and Robyn Wright Version 1.1 Printed by Puritan Press, Inc. Hollis, New Hampshire, USA...
Page 2 Copyright © 2011 snom technology, Inc. All rights reserved. snom® is a registered trademark of snom technology AG and its affiliates in the Euro- pean 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.
Page 3 Europe, where he was responsible for the entire operations for Europe, Middle East, and Africa. Jonathan is now Managing Director of snom UK Ltd and is also Product Manager for snom ONE.
Page 5: Table Of Contents
BRIEF CONTENTS Part I—Getting Started Getting Started ......................1 Part II—Administering the System System Settings ......................29 Administering the Domain ..................83 Trunks ........................113 Dial Plans ......................... 147 Extensions ........................ 161 Park Orbits ....................... 177 Service Flags ......................181 Auto Attendant ......................193 Hunt Groups ......................
Page 6 Deploying the snom ONE IP Telephone System Part III—The User Interface Web Interface ......................399 Star Codes ......................425 Voicemail ........................447 Cell Phones ......................459 Appendix A. Working with CSV Files ............475 Appendix B. SIP Overview ................499 Appendix C.
Page 7: Getting Started
............... About snom ONE .
Page 8: Administering The Domain
Deploying the snom ONE IP Telephone System viii Directory Tree ..............
Page 9 Contents Creating New Domains ............Configuring the Domain .
Page 10: Park Orbits
Deploying the snom ONE IP Telephone System Building a Dial Plan ............. . .
Page 11: Auto Attendant
Contents Service Flags and Buttons ............Using a Button to Activate a Service Flag .
Page 12: Paging
Deploying the snom ONE IP Telephone System Night Service ..............
Page 13: Calling Card Account
Contents xiii Calling Card Account ............. Setting up a Calling Card Account .
Page 14: Buttons
Deploying the snom ONE IP Telephone System Audio Prompts ..............
Page 15: Music On Hold
Contents Music on Hold ..............Setting up Music on Hold .
Page 16 Deploying the snom ONE IP Telephone System Redial a Number (*66) ........... . .
Page 17 Contents xvii Record a Personal Welcome Message ........Accessing the Voicemail System .
Page 18 Deploying the snom ONE IP Telephone System xviii Parameters ............... .
Page 19: Part I-Getting Started
Part I Getting Started...
Page 20 Part I—Getting Started...
Page 21: Getting Started
VoIP system can be a daunting task for administrators unfamiliar with VoIP. This guide is designed to help you plan and configure snom ONE Voice over IP (VoIP) deploy- ments ranging in complexity from a small office using the Internet for SIP trunks to a large, multi-national conglomerate of snom ONE systems.
Page 22: Memory/Hardware Requirements
Memory/Hardware Requirements The snom ONE system consumes only a small amount of memory. In the image shown below, a snom ONE system uses under 50 MB of RAM, which is not unusual for a lightly loaded system.
Page 23 Chapter 1: Getting Started For a heavily loaded system, we recommend 2 GB of RAM. However, the system can run on machines with far less RAM, but this will depend on your operating system. Factors influencing memory requirements include the number of voice mails that ac- cumulate, how much logging information is stored on the system, and the number of CDRs you store.
Page 24: Usb Device
Deploying the snom ONE IP Telephone System USB Device The snom ONE software has been loaded onto the 1 GB USB drive that was shipped with this book. This section contains information about the USB drive. Warnings The USB drive is for indoor use or storage with a temperature range between +0°C and +70°C.
Page 25: Installing The Software
Chapter 1: Getting Started Installing the Software The snom ONE software has been loaded onto the USB drive that was shipped with your order. Follow the instructions below to complete the installation. Note: If you purchased this book without the software, you may download snom ONE free at http://www.snom.com/products/ip-pbx/snom-one...
Page 26 Deploying the snom ONE IP Telephone System 6. Choose an installation location or accept the default, then click Next. Note: If you are installing the software on a 64-bit system, the default directory path will be as follows: 7. Click Next to start the installation.
Page 27: Mac Os Installations
Chapter 1: Getting Started Click Close when the installation is complete. MAC OS Installations This section explains how to install snom ONE for Mac OS (tested on Darwin). Cur- rently, we support only Intel-based hardware. Navigate to http://wiki.snomone.com , and click Downloads at the left.
Page 28 Deploying the snom ONE IP Telephone System Click Mac - Installer - New Installations Only. Download the installation package. Unzip the zip file by double-clicking it. Execute the installer contained in the zip file. At the Welcome screen, click Continue.
Page 29 Chapter 1: Getting Started To continue the installation, click Agree. 10. To install snom ONE to the default directory, click Install. To install it to a new location, click Change Install Location and select a location. 11. At the password screen, enter your password and click OK.
Page 30: Linux Installations
Deploying the snom ONE IP Telephone System 12. Click Close when the installation is complete. To log into snom ONE, enter http://localhost into a web browser. If you are using a different HTTP port, then enter localhost:<port> (e.g., localhost:80 Linux Installations Debian 1.
Page 31 Right-click Linux - Debian and copy the link location. Download the file onto your Linux box using the following command: wget <linklocation><previously saved> For example: wget http://downloads.snom.net/snomONE/debian/ snomone-debian4-2011-4.2.0.3958.deb To install the software, execute the following command with root privileges: dpkg -i snomone-debian4-2011-4.2.0.3958.deb...
Page 32 Deploying the snom ONE IP Telephone System The installed files are located in /usr/local/snomONE as shown below: If you need to uninstall snom ONE, execute the following command: apt-get remove snomone Cent OS 1. Go to www.wiki.snomone.com, and click Downloads at the left.
Page 33 Right-click Linux - CentOS and copy the link location. Download the file onto your Linux box using the following command: wget <linklocation><previously saved> For example:: wget http://downloads.snom.net/snomONE/centos32/ snomone-CentOS5-2011-4.2.0.3958.bin To make the file executable once the download is complete, enter the following command: chmod +x snomone-CentOS5-2011-4.2.0.3958.bin...
Page 34: Logging In
To uninstall the software, execute the following command: ./snomone-CentOS5-2011-4.2.0.3958.bin uninstall Logging In Once the software has been installed, the snom ONE will run as a service. To access it, bring up a browser from the machine on which the software has been installed and enter...
Page 35: Login Levels
Figure 1-2. Login Levels Login Levels snom ONE includes three main login levels—administrator, domain administrator, and user— that provide access to different web interfaces. The login levels are shown in Figure 1-2, and the web interfaces for each login type are shown in Figure 1-3:...
Page 36 Deploying the snom ONE IP Telephone System The Automatic login type will default to the highest login level of the person logging in. Administrators and domain administrators who want to log in as a user must enter their extension number and choose User Login from the dropdown. Instructions for each login type are detailed below.
Page 37: Activating Your License
Chapter 1: Getting Started Activating Your License Your snom ONE license will need to be activated before you can register extensions to the system. The activation code is located on the back cover of this book near the Product key barcode. To activate your license, complete the following steps: Click Admin.
Page 38: Manual Software Upgrades (Windows)
Deploying the snom ONE IP Telephone System the upgrade. The Maximum Number of Calls setting can also be used see restrict call activity (see page 49). Configure this setting to so that no new calls can be estab- lished on the system. To check the status of the system, navigate to Admin > Status >...
Page 39: Mac Os Upgrades
Keep the file in the directory so that you can later determine which software version is associated with which file. This step can be done while the system is running. 3. Go to wiki.snom.com and download the new executable (click the Existing Installations Only link). Place the file into the snomONE working directory.
Page 40: Linux Upgrades
Deploying the snom ONE IP Telephone System 1. Stop the PBX using the following command: sudo /Library/StartupItems/PBX/PBX stop 2. Remove the old link to pbxctrl-darwin9.0 by entering the following com- mand: rm pbxctrl-darwin9.0- < old file > 3. Recreate the link using the following command: ln -s <new file>...
Page 41: Restarting From Windows (Service Control Manager)
Chapter 1: Getting Started Restarting From Windows (Service Control Manager) Right-click My Computer. Click Manage. Click Service Applications, then click Services. From the right-hand pane, click snomONE PBX Click Restart.
Page 42: Restarting From A Command Line
Restarting From Mac OS The simplest way to restart snom ONE from a Mac is to restart the Mac, but this may not be desirable in many cases. In such cases, you can start and stop snom ONE from the command line: •...
Page 43: When The System Fails To Restart
A way around this issue is to rely on the file. This file is lo- snom/snomONE cated in the folder and indicates why the system either crashed or did not come up the last time an attempt was made. Following is a sample error message:...
Page 44: Technical Support
Technical support for snom ONE is available through the wiki, the online help system, and the forum. If you cannot find an answer to your question through these sources, you can also open a ticket with snom ONE support. Each support option is detailed below.
Page 45 To access online help, click the Help link at the top of each page. Forums To join the forum, go to forum.snom.com. Submit a Ticket To submit a ticket or view existing tickets, go to support.snom.com, and log in or regis- ter a new account:...
Page 46: Documentation
Deploying the snom ONE IP Telephone System Documentation The following typographic and usage conventions occur in this book: Typeface Description Example Names of tabs, settings, Navigate to Admin > Settings > Log- Bold and buttons ging. monospace • File and directory names, The default recording name is $r/$d/$t-$i-$u-$n.wav...
Page 47: Part Ii-Administering The System
Part II Administering the System...
Page 48 Part II—Administering the System...
Page 49: System Settings
This chapter discusses administrator-level settings only. Configurations that can be made by the domain administrator are discussed in Chapter 3. Admin Admin Domain User Settings Settings Settings Domain Admin Domain User Settings Settings User User Settings Figure 2-1. snom ONE Web Interfaces (Admin, Domain Admin, and User)
Page 50 Deploying the snom ONE IP Telephone System To access the administrator settings: 1. Log in as admin. The following screen will be displayed. 2. Click Admin. The new screen includes the four tabs shown below. These tabs can be seen only by administrators.
Page 51 Chapter 2: System Settings The settings associated with the administrator tabs are briefly outlined in Figure 2-2 and are described in more detail in Table 2-1. Settings Domains Email Web Page Control Status • G e ne ra l • p b x . c o m p a nya .c o m •...
Page 52 From this page, you can provide parameters to change the gen- eration of plug and play files. Access You can control which IP addresses may access the snom ONE service here. Domains From the Domains tab, the administrator can view and edit the domain.
Page 53: Directory Structure
All files related to the system are located in C:\Program Files\snom\snomONE which is the system’s default working directory. The main program that runs the pbxctrl.exe...
Page 54: Global Configuration File
Changes to this file must be made through either the XML file or by handcrafting a URL that contains the change. With either method, the three important components are the address of the snom ONE system, the name of the setting, and the value. In the sample URL shown below, the address is...
Page 55: Folder Overview
25m,$2o,$20F,$20T,$20R,$20r,$15c,$20f,$15v ). Be careful when choosing a delimiter. If the names or URIs contain those characters, there will be a conflict. Folder Overview Table 2-2 lists the folders that are located in snom/snomONE Table 2-2. Folder Details Folder Name Contents...
Page 56 Deploying the snom ONE IP Telephone System Folder Name Contents certificates Certificates being used by the system. colines Central office lines on the trunk conferences Account information about conference accounts dial_plan Dial plans that are on the domain dial_plan_entry Individual pattern and replacement values for each dial plan...
Page 57: Folder Details
• accesslist —The accesslist folder contains IP addresses that have been blocked from accessing the snom ONE service. IP addresses can be blocked/unblocked by the administrator in Admin > Settings > Access List. • acds —The acds folder contains an XML file for each agent group.
Page 58 Deploying the snom ONE IP Telephone System • attendants attendants —The folder contains an XML file for each auto attendant. Each file includes the possible parameters for the account and any values assigned to those parameters. • audio_* —The audio_* directory contains audio prompts that are used by the auto attendant and IVR node.
Page 59 Chapter 2: System Settings • callingcards callingcard —The folder contains an XML file for each calling card account. Each file includes the possible parameters for the ac- count and any values assigned to those parameters. • —The folder contains the CSV CDRs, if there are any. •...
Page 60 Deploying the snom ONE IP Telephone System • cdrt —The cdrt folder contains CDRs that hold trunk-related information. A CDR is generated for each call. • colines —The colines folder contains information about co-lines that are created on the system.
Page 61 . You can download these files from html wiki.snomone.com and then place them into the folder. Once the snom ONE is restarted, the new configurations will take effect. • hunts hunts —The folder contains an XML file for each hunt group. Each file includes the possible parameters for the account and any values assigned to those parameters.
Page 62: Configuring System Settings
Deploying the snom ONE IP Telephone System • tftp —The tftp folder can be used for customizing plug and play. For example, placing the snom_320_custom.xml file into the tftp folder will provide new settings for the phone. • trunks trunks —The...
Page 63 Chapter 2: System Settings The next four settings pertain to language and time zone. The settings made here by the administrator can be overridden by the domain administrator. • Default IVR Language: This setting represents the language that is used for voicemail and IVR prompts.
Page 64: Administrator Login
Deploying the snom ONE IP Telephone System Administrator Login The system administrator’s login must be protected at all times, so it is imperative that a high-security password be used (see the Password Strength setting on page 45). The password is stored in a hashed format and cannot be read from the global configuration file.
Page 65: Appearance
Chapter 2: System Settings Search for the <pw_pass> element tag. Delete the password. (If no text appears between the element tags, then the password field is empty.) Save the file. Restart the system. Set a new password through the web interface (Admin > Settings > General). Appearance •...
Page 66 — Medium Security: The score must be 120 or higher (see Table 2-3). — High Security: The score must be 200 or higher (see Table 2-3). Note: Beginning with Release 1.1, snom ONE replaces weak passwords with random passwords. The administrator can check the...
Page 67 Chapter 2: System Settings — Days: Enter a after the number (e.g., for 7 days) • SOAP Trusted IP: SOAP (Simple Object Access Protocol) is an XML message-based protocol specification that is used to allow computers to talk to each other over a network such as the Internet, typically as part of a Web service.
Page 68: Performance
Deploying the snom ONE IP Telephone System string used in this field. For more information about recording calls and how to create a string for the Record Location field, see page 315294. • Compress Recording: The system will compress recordings when this setting is enabled.
Page 69 Chapter 2: System Settings • Maximum Number of Calls: This setting defines the number of simultane- ous calls allowed by the system. Because every call requires a certain portion of the available CPU, allowing too many calls will affect the quality of all ongoing calls.
Page 70 Deploying the snom ONE IP Telephone System • Max. number of concurrent registrations per extension: This setting con- trols how many user agents (i.e., phones) can be registered against an exten- sion. This feature is useful if you want to restrict the number of phones that can be registered to an extension.
Page 71: Sip Settings
Chapter 2: System Settings SIP Settings This section defines SIP-related settings. • From Use Short SIP Headers: Some SIP headers have a short form (e.g., the header gets shortened to , the header becomes , and becomes Short headers have the advantage of saving space in the messages, reducing overall probability of running into problems with maximum message size in UDP.
Page 72 Therefore, the system must detect such a loop. In environments where an external SIP proxy routes the call from one snom ONE domain to another, a simple loopback detection that is based on the call-ID is too pessimistic.
Page 73: Ports
* Changes to HTTP and SIP settings require a system restart. HTTP Ports The HTTP and HTTPS ports are used to communicate between the built-in web server and the web browser (snom ONE does not rely on IIS or Apache for its web...
Page 74: Sip Ports
SIP signalling packets much like HTTPS encrypts HTTP traffic. The default SIP port per RFC 3261 is 5060 for SIP and 5061 for SIPS. The snom ONE software is listening for and transmitting SIP requests and responses on these ports.
Page 75 Chapter 2: System Settings • SIP TLS Ports: If you are using SIP over TLS (Transport Layer Security - Se- curity over TCP), you need to set this field. The default port for TLS is 5061 • Maximum number of SIP connections per second: This setting specifies the number of SIP conversations the system will respond to in 1 second.
Page 76: Rtp Ports
Deploying the snom ONE IP Telephone System be consulted by the system before consulting/using the operating system). Whenever the system wants to find the IP address that is being used when sending a SIP packet, it steps through the list and looks for a match (using the netmask mask) to a destination address (DAdr).
Page 77 Chapter 2: System Settings • Follow RTP: Some user agents use different ports for sending and receiv- ing. Although they will not be able to operate behind NAT, they are within the scope of the IETF standards. With this setting, these devices can be made compatible.
Page 78: Snmp
Deploying the snom ONE IP Telephone System • Bind to specific IP address (IPv4): The system listens to SIP requests that are sent by the user agent from this IP address only. This is useful if you have a dual NIC machine and want to listen to SIP requests only on one interface. If this is left blank, then the system will listen to SIP requests on all interfaces it sees in the machine.
Page 79: Tftp
Chapter 2: System Settings Description Absolute Unit 1.3.6.1.4.1.25060.1.3 Messages Minutes 1.3.6.1.4.1.25060.1.4 Call attempts Calls 1.3.6.1.4.1.25060.1.5 Successful calls Calls 1.3.6.1.4.1.25060.1.6 Media CPU load Value 0..100 1.3.6.1.4.1.25060.1.7 Successful emails Emails 1.3.6.1.4.1.25060.1.8 Unsuccessful emails Emails 1.3.6.1.4.1.25060.1.9 Email alert flag Value 0..1 1.3.6.1.4.1.25060.1.10 SIP received packets Packets 1.3.6.1.4.1.25060.1.11 SIP sent packets...
Page 80: Ldap
LDAP LDAP (Lightweight Directory Access Protocol) is an Internet protocol used to ac- cess directory type of information, such as address books. All snom phones support LDAP, so users can query phone numbers by pressing the directory button of the phone.
Page 81: General Logging
Chapter 2: System Settings General Logging • Log Level (0-9): This field determines which log messages are included in the log. The range is between 0 and 9. Level 0 will show you only critical messag- es, while level 9 will show you every available log messages of the system. Log level 9 should be used only for troubleshooting, as it creates additional load for the system and may generate extremely large log files.
Page 82: Specific Events
Deploying the snom ONE IP Telephone System the year, is the month, and is the date. If you have multiple drives, it is D:\logs good practice to write the logs there (e.g., Warning: Please note that using a log file without a dollar sign as part of the name is a ticking time bomb.
Page 83: Sip Logging
Chapter 2: System Settings • Log SOAP events: This subsystem deals with SOAP input and output. • Log TFTP and PnP events: This module includes events related to the built-in TFTP server. It also includes information related to plug and play. •...
Page 84 Deploying the snom ONE IP Telephone System When the system receives or sends a SIP packet, it determines whether the packet will be logged and which log level the event will have. • Log REGISTER: REGISTER packets deal with the registration of extensions or trunks, which can generate a lot of traffic.
Page 85 Chapter 2: System Settings Retrieving SIP logging The SIP log is the most common logging that is requested. Use the following steps to turn on SIP logging: Navigate to Admin > Settings > Logging. Set Log Level to 3. Set Log Length to Under “Specific Events,”...
Page 86: Configuration
Deploying the snom ONE IP Telephone System Configuration This section shows you how to save and restore the system configuration, as well as load the configuration XML files. This will generate a complete backup of your system, including all temporary files, recordings, TFTP server files, etc. You can even schedule this task nightly so that you automatically have a fresh backup for disaster recovery.
Page 87: Request Configuration
Chapter 2: System Settings To restore the backup To restore a configuration, the file must be loaded through the web interface. As with saving the configuration, this may be time-intensive, so be sure to do this when no calls are on the system. The system restoral will first erase your existing configuration, so exercise caution with this step.
Page 88: Schedule A Reboot
Deploying the snom ONE IP Telephone System The files are detailed below: • ringtones.xml Alert-Info : This file is used to describe the available Call-Info Alert-Info header that should be sent in the different head- ers. Some phone vendors handle these headers differently, and this file can be used to address that.
Page 89: Certificates
Chapter 2: System Settings Certificates Digital certificates are electronic documents that are used to verify that the system you are interacting with is legitimate. The PBX uses them in multiple ways: • For securing the traffic between the web browser and the web interface of the system when HTTPS is used.
Page 90 Deploying the snom ONE IP Telephone System When using certificates on snom ONE, you can choose from the following four types: Domain certificate chain + private key: While “Server certificate chain + private key” is the default for the whole server (see below), the PBX can also present domain-specific certificates that require that the client, at the beginning of the session setup, tell the server which domains it wants to connect to.
Page 91 Chapter 2: System Settings them there. You will need to load the root certificate into the clients that should talk to the snom ONE system. There are various other sites available which provide a similar service. You may also download the openSSL toolkit and compile your own certificate generator and set up your own trusted network.
Page 92: Access List
Deploying the snom ONE IP Telephone System Access List If your system is under a denial of service attack, the system will automatically block the IP address that is attacking the system. You can also add IP addresses to the Ac- cess page and place a Block on them so that they will be unable to access the system.
Page 93 Chapter 2: System Settings The motivation for the list is to provide the firewall type of functionality within the system application and reduce the chance of unauthorized access to the system. The access control is not limited to SIP only, but it also applies to all other protocols on the system, including HTTP, TFTP, and SNMP.
Page 94 Deploying the snom ONE IP Telephone System The behavior of the access list is similar to a firewall. However, especially for TCP, a firewall will keep the traffic completely out. Someone testing the system will not get a response for a TCP request if the source IP address is not listed.
Page 95: Web Page Control
Chapter 2: System Settings Web Page Control Templates This page allows you to change the look and feel of the PBX web pages. It also allows you to change the various email templates, phone configuration templates, style sheets, etc.
Page 96 Deploying the snom ONE IP Telephone System To customize the templates, a familiarity with HTML is required. Navigate to Admin > Web Page Control > Templates. From the dropdown, make a selection. The HTML will be displayed: Embedded between the standard HTML tags (e.g., <title></title>...
Page 97: Translation
FAMILY: Verdana </style> </head> <body bgcolor=”#f0f0f0” leftmargin=”0” topmargin=”0” margin- height=”0” marginwidth=”0”> <p class=”normalText>Hello new user. You have been added to the snom ONE telephone system. This email is sent automati- cally. Do not reply. </p> </body> </html> Translation Although we try to provide good translations, it’s not an easy task for every language.
Page 98: User Page Control
Deploying the snom ONE IP Telephone System User Page Control The User Page Control tab allows the administrator to control which fields are dis- played on the user pages. Figure 2-4 shows the general settings that can be hidden from the user.
Page 99 WAC. Not all users will need access at this level. • Phone address book preference: This setting is applicable to the address book of the snom phone. It allows the user to upload the address book from the system to the snom phone directory.
Page 100: Redirection Control
Deploying the snom ONE IP Telephone System Redirection Control The Redirection Control settings allow you to prevent the user from viewing certain redirection settings. Figure 2-5 highlights these settings (details are provided below the image). Figure 2-5. Blockable User Settings (Settings > Redirection) •...
Page 101 Chapter 2: System Settings Figure 2-6. Blockable User Settings (Settings > Mailbox) • Mailbox enabled field: This setting allows users to enable their voicemail. In situations where voicemail is not used, such as call centers, this setting is not needed. •...
Page 102 Deploying the snom ONE IP Telephone System Email Control The Email Control settings allow you to prevent the user from viewing various email settings. Figure 2-7 highlights these settings (details are provided below the image). Figure 2-7. Blockable User Settings (Settings > Email) •...
Page 103: Administering The Domain
They can also access the same address book and share features, such as call monitoring and call park/pickup. A snom ONE domain name should be fully qualified and configured in the DNS server so that traffic can be routed to the proper IP address of the PBX. If this is not possible, then you can set the outbound proxy field in the system.
Page 104: Naming The Domain
Deploying the snom ONE IP Telephone System Naming the Domain pbx.company.com local- By default, the system installation creates and associates host as alias to it. Default Domain Alias pbx.company.com localhost localhost domain will match all requests that cannot be matched to a domain name within the domain list.
Page 105: Assigning A Domain Administrator
Chapter 3: Administering the Domain Replace pbx.company.com with your own domain name. Enter an alias if desired. Click Save. Click List to view the domain. The new domain will be displayed. Note: Setting up a domain on the system does not imply that the necessary DNS records have automatically been set up.
Page 106 Deploying the snom ONE IP Telephone System The permission to manage the domain should be given only to those who are allowed to change passwords, create or delete accounts, change dial plans and rates, and so forth. Permission is given from the Permission tab in the user’s extension account:...
Page 107 Chapter 3: Administering the Domain The settings associated with the domain tabs are briefly outlined in Figure 3-1 and are described in more detail in Table 3-1. Settings Accounts Trunks Dial-Plans Status Admin • D omain Setting s • Ex tensi on •...
Page 108 Deploying the snom ONE IP Telephone System Web Interface Description Buttons This page provides a list of all the button profiles that are avail- able on the domain. From this page, you can create additional button profiles. Accounts This tab provides a listing of the accounts that have been created on the domain.
Page 109: Domains-Default And New
Chapter 3: Administering the Domain Domains—Default and New Default Domain The system comes with a preconfigured domain that includes ten 2-digit extensions and numerous domain accounts (Figure 3-1). To view the accounts, click Accounts > List. Figure 3-1. Default Accounts Note: A yellow triangle symbol indicates that the account is missing either the SIP pass- word or the web password.
Page 110: Creating New Domains
With snom ONE, information such as account information, trunks, dial plans, and system settings will be retained.
Page 111 Chapter 3: Administering the Domain Click the link at the bottom of the page to save the domain. Click Save File. Browse to the location where the file will be saved:...
Page 112 Deploying the snom ONE IP Telephone System Click Create as shown below: Using the Primary Name field, name the domain. Click Browse (shown above) and navigate to the tar file. Click Create. 10. Once the page has finished loading, click List. The new domain will be listed:...
Page 113: Configuring The Domain
Chapter 3: Administering the Domain Configuring the Domain From the Settings tab, you can configure many domain settings: • Name of the Domain: This field allows you to give the domain a descrip- tive name. The name can contain special characters and spaces and may include upper and lowercase characters.
Page 114 Deploying the snom ONE IP Telephone System The name of the time zones is reflected in the lang_xx.xml file, where xx is replaced by the respective language (see Table 18-5 for a list of language code identifiers). • Country Code: The country code plays a major role in interpreting tele- phone numbers.
Page 115 Chapter 3: Administering the Domain The Country Code setting corresponds to the Rewrite global numbers set- ting (page 140): • Area Code: This is the telephone area code for the domain. This is generally NPA in the NPA-NXX-XXXX number (e.g., , etc.).
Page 116 Deploying the snom ONE IP Telephone System • Delete all aliases when deleting the primary account: Aliases will be de- leted when primary accounts are deleted. From/To Headers • From header when switching the domain: This setting allows you to set a From header.
Page 117 Chapter 3: Administering the Domain device in an operator environment, you may want to make sure that the sys- tem does not change headers. In such cases, this setting should be set to Yes. CDR Settings • CDR URL: This setting allows you to configure where and how the CDRs are written for a specific domain.
Page 118 Deploying the snom ONE IP Telephone System • Billing Tones: This field allows you to configure whether domain users will hear a beep during the call when using the pre-pay feature of the system (pre-pay is discussed in Chapter 16).
Page 119 Chapter 3: Administering the Domain • Maximum Voicemail Duration: This setting specifies the length of a mailbox message. Typically, a mailbox message should be no longer than 2 minutes. If this setting is left blank, the length of any one message can be unlimited. Table 3-4.
Page 120 Deploying the snom ONE IP Telephone System • Calling own extension number goes to mailbox: By default, the system will send a user to the voice mailbox if he dials his own extension. However, in some situations it is useful to have the system call the registered extension.
Page 121: Accounts Page Display
Chapter 3: Administering the Domain • Call forward on no answer timeout: This setting establishes the number of seconds that the system will wait before performing a timeout action. It is ad- visable that this setting be less than the voicemail timeout; otherwise, the call will not be forwarded and will instead go to voicemail.
Page 122 Deploying the snom ONE IP Telephone System After (set to Yes): • Display hyperlink for the disabled accounts in the accounts page: When this setting is set to Yes, disabled accounts will be hyperlinked to the actual account: Before (set to No):...
Page 123 Chapter 3: Administering the Domain obtaining MAC addresses, a question mark or asterisk will appear in the MAC address field. • Display Email address for the account in the accounts page: When this set- ting is activated, the email address for each account (if one is available) will be displayed: •...
Page 124: Recording Defaults
Deploying the snom ONE IP Telephone System Recording Defaults This section allows you to define domain-level call recording settings. Recorded calls will be saved in the recordings directory (see also Chapter 18). • Record incoming calls from hunt group: This setting controls the recording on an extension (applies to calls coming from the hunt group for the entire domain).
Page 125: Midnight Events
Chapter 3: Administering the Domain (these settings can also be made by the administrator by going to Admin > Email). If the administrator has opted to use the same email settings across all domains, the email settings shown below will not be displayed at the domain level (see page 297). Midnight Events At midnight, the system can perform several maintenance tasks, including the genera- tion and sending of CDR reports.
Page 126: Provisioning Parameters
Deploying the snom ONE IP Telephone System Figure 3-2. Sample CDR Report • Reset DND Flags: DND is a major problem if users forget that they’ve set their extensions to DND and then open a trouble ticket next morning because they’ve stopped receiving calls! This setting can prevent that.
Page 127 Chapter 3: Administering the Domain • Default PnP Dialplan Scheme: This setting allows you to set auto-dial and configure timeout-based dialing. These settings are used by the phone and not the system (see Chapter 5 for the dial plan that is used by the system). The PnP Dialplan Scheme setting allows you to tell the system how many numbers your extensions contain (either 2, 3, or 4 digits).
Page 128: Domain Address Book
Note: If you want to create a customized dial plan, you can do this from either the snom phone or through the binary files of the system. In the case of the latter, you will need to request the appropriate file from snom and place it into...
Page 129: Creating A Domain Address Book
Chapter 3: Administering the Domain their IP phones. From the address book, contacts can be whitelisted or blacklisted and CMC codes can be added to a contact’s information. Creating a Domain Address Book Adding Contacts Manually Enter the contact’s information into the Create New Entry form shown below: •...
Page 130 Deploying the snom ONE IP Telephone System Once contacts have been added to the domain address book, their information will be displayed to the person they are trying to reach. Adding Contacts Using CSV Files Domain address books can also be compiled through CSV files (see Appendix A).
Page 131: Searching For Contacts
Chapter 3: Administering the Domain Searching for Contacts Web Interface Users can search for contacts by entering the contact’s first or last name into the search box:...
Page 132 Deploying the snom ONE IP Telephone System Phone Display If the administrator has enabled the User can select the address book setting (Admin > Web Page Control > User Page Control), users can also search through the domain address book from their IP phones:...
Page 133: Trunks
Chapter TRUNKS Trunks are used to route calls in and out of the system. When the system receives a call from an extension, it checks to see if another account is being called. It does this by looking at the field of the SIP packet.
Page 134: Trunk Types
Figure 4-2. Using SIP Trunks for Communicating with External Networks The snom ONE telephone system has three types of trunks: SIP registrations, SIP gate- way, and SIP proxy. All act as an entry and exit point to an external network. The type of network you are connecting to will determine which type of trunk you will need.
Page 135 Although service providers often assume that a trunk registration involves an IP phone or an ATA rather than a trunk, many phones can sit behind the snom ONE telephone system and share the resources of the trunk (Figure 4-3). However, most service pro- viders limit the number of calls that can be made over a SIP trunk and use a charging method that simulates the charges accumulated by a physical legacy TDM trunk (i.e.,...
Page 136: Sip Gateway
Deploying the snom ONE IP Telephone System A SIP registration trunk can also be used to connect two or more snom ONE systems together, as in a branch/head office configuration (see “Connecting Branch Offices Together” on page 142). SIP Gateway The gateway trunk is typically used to talk to a PSTN or cellular gateway, which could authenticate the call leg on the IP address in the system.
Page 137: Inbounds Calls
Chapter 4: Trunks proxy represents its own domain. As the name suggests, the proxy model assumes that you are talking to a SIP proxy or session border controller, while the gateway model assumes you are talking to a SIP user agent. However, the two models are quite similar. As a general rule, use the gateway trunk first, and if you have an issue, try changing the trunk type.
Page 138 Deploying the snom ONE IP Telephone System Figure 4-7. Line Parameter in 200 Ok of SIP Trace Figure 4-8. Line Parameter in INVITE of SIP Trace For gateways and proxies, this method is not possible, so if the line parameter isn’t there to give clues on how to route the call, the system must continue searching the trunk.
Page 139: How The System Routes A Call To The Proper Extension
Chapter 4: Trunks A match is based on the following priority: Trunk Settings Proxy address of trunk DID number in domain of trunk Proxy address of trunk Account name of trunk 75.150.87.9:5060 Domain name of trunk Proxy address of trunk Username of trunk Proxy address of trunk Port of proxy address of trunk...
Page 140 Deploying the snom ONE IP Telephone System If the setting includes regular expressions, the system will route the call accord- ingly (see “When Regular Expressions are Involved” on page 121). When using regular expressions in the Send call to extension field, it is important...
Page 141: When Regular Expressions Are Involved
Chapter 4: Trunks If the trunk’s Send call to extension field is empty and the system finds an extension that is associated with the number that was called, the called number will be reflected in the user portion of the Request-URI is 8124351234 (Figure 4-11): Figure 4-11.
Page 142 Deploying the snom ONE IP Telephone System • Replacement: The replacement field tells the system which expression to use when dialing. In our example, expression 2 has been defined (as is indicated ), so if 9781234567 had been the incoming number, would be dialed.
Page 143 Chapter 4: Trunks This expression allows the trunk to find the correct extension when lots of DIDs are used on the system. As a safety net, you can also direct the trunk to send the call to a default extension in the event the replacement pattern does not produce an existing extension.
Page 144: Regular Expressions And Direct Inward Dialing (Did)
Deploying the snom ONE IP Telephone System Samples of regular expressions are shown in Table 4-2. Table 4-2. Examples of Regular Expressions ![0-9]{7}([0-9]*)!\1!t!100 Example 1 This example is common in Europe. It is used to strip the main number of the system so that the remaining numbers can be used to identify the extension.
Page 145 Chapter 4: Trunks Though easy to use, this method is cumbersome to employ for a large number of DIDs, so you will need to use an alternate method. The method chosen will depend on the numbering scheme of the DID numbers themselves. When the ending digits of the DIDs form a definite pattern that can lend itself to correlate with extension numbers, you simply need to enter a single string into the trunk’s Send call to extension field.
Page 146 Deploying the snom ONE IP Telephone System Using the example shown below, the system will use either the last 3 or 4 digits of the 10-digit number, depending upon which string is used. (If the system cannot find a matching DID, the call will be sent to extension 777.)
Page 147: Outbound Calls
Chapter 4: Trunks Enter a regular expression into the Send call to extension setting, telling the system to replace the 10-digit DID with the alias number that is associated with the extension account. Outbound Calls Caller-ID The caller-ID is shown in the called party’s telephone display and is also used by the From carrier for billing purposes.
Page 148: Generating The Ani
Deploying the snom ONE IP Telephone System Generating the ANI An ANI is an administrative number provided by the system to identify the caller to the receiver and is not necessarily the originating number. Before the system can generate an outbound call on a trunk, it must have an ANI. To get the ANI, the system first...
Page 149: Representing The Source
Chapter 4: Trunks 3. Trunk (Prefix setting): If the trunk’s ANI has not been set, the system will check to see whether a prefix has been set in the trunk. When this is the case, the system will add the fixed number to the front of all calls leaving the trunk. In many cases when you have an ITSP, you may want a prefix number to be appended to the front of all calls.
Page 150: Creating Trunks
Deploying the snom ONE IP Telephone System Over the last few years, providers have developed different methods of representing these two numbers: • RFC 3325 describes a way to represent these two numbers. In most cases, it makes sense to use the P-Asserted-Identity header.
Page 151: Configuring Trunks
Chapter 4: Trunks From the dropdown list, choose a trunk type. (For a description on each trunk type, see “Trunk Types” on page 114.) Click Create. The following section shows you how to configure the trunk settings. Configuring Trunks General Settings Trunks have a large number of settings.
Page 152 Deploying the snom ONE IP Telephone System 1. Name: This setting allows you to name the trunk (the name and type of trunk can be changed at any time). 2. Type: See “Trunk Types” on page 114. 3. Direction: Traffic can be limited to either inbound traffic or outbound traffic.
Page 153 12. CO (central office) Lines: CO-lines can serve multiple purposes on the sys- tem. They allow you to channelize a trunk and can be used in a way similar to the CO-lines of traditional TDM-based PBX systems. Although snom ONE runs calls through SIP trunks over computer networks instead of connecting to...
Page 154 Deploying the snom ONE IP Telephone System public telephone lines (at least directly), CO-lines are still useful for determin- ing which calls are active between the system and the outside world. To begin with, each trunk may have several CO-lines, and because users can subscribe to the state of CO-lines, each CO-line name must be unique within a domain.
Page 155 Chapter 4: Trunks Phone CO lines Buttons Figure 4-16. CO-Lines Linked to Phone Buttons From a system point of view, the status of a CO-line is similar to the status of an extension: It may be idle, connected, ringing, or on hold. It also might be holding a parked call.
Page 156 (Some user agents are not capable of chang- ing the media once the conversation begins. ) When this setting is used, snom ONE transcodes the stream so that changes made to the codec by the other side go unnoticed by the user agent.
Page 157 Chapter 4: Trunks Because some providers will accept the proposed duration without bothering to refresh the NAT binding, you need to force the system to renew the registration in a shorter period of time and ignore the service provider’s registration. This is done through the Keepalive Time setting below.
Page 158 Deploying the snom ONE IP Telephone System not determine whether these redirects introduce additional costs (redirection to expensive numbers). Therefore, enable this setting only if you are sure that your service provider or SIP gateway does not abuse this feature. This flag is especially important when you use the system with Microsoft Exchange or other Microsoft products, such as the speech server.
Page 159: Outbound Settings
Chapter 4: Trunks Outbound Settings 26. Prefix: This setting is used as a representation of the system when making out- bound calls. The system will add the prefix to the front of all calls leaving the trunk. (See also “Generating the ANI” on page 128.) 27.
Page 160 Deploying the snom ONE IP Telephone System 30. Rewrite global numbers: When you are using a trunk, you may have to rep- resent the telephone number in a specific format. For example, in the NANPA area, you might want to use 10 or 11 digits to represent a national number.
Page 161: Inbound Settings
For example, when the trunk goes to a local PSTN gateway, you might decide to treat this call as a secure call. Incoming calls with the SIPS scheme will ask the snom ONE system to ensure that the call be kept secure end-to-end.
Page 162: Connecting Branch Offices Together
(which is default) and asking the operator to fix the problems with early media. Connecting Branch Offices Together This section describes how to connect two snom ONE systems together so that calls between the two locations will be routed through VoIP rather than through the local PSTN.
Page 163 Chapter 4: Trunks Extensions Extensions Site 1 Site 2 209.251.11.111 151.195.11.111 Public IPs Figure 4-17. Connecting Branch Offices Using a Gateway Trunk Create a trunk for each branch office, using the instructions that are shown below. Branch Office 1 From the Type dropdown, select SIP Gateway. Enter the IP address into the Domain field: Branch Office 2 From the Type dropdown, select SIP Gateway.
Page 164: Using A Sip Registrations Trunk (Sip Tie Line)
Deploying the snom ONE IP Telephone System Using a SIP Registrations Trunk (SIP Tie Line) The SIP registration trunk can be used to connect two branch offices when one of the offices has a private IP address. For example, a corporate head office has a pubic IP ad-...
Page 165 Chapter 4: Trunks Create a SIP registrations trunk for the branch office, entering the extension that will be used to route the calls (e.g., Once the offices have been connected, the headquarters will need to dial the extension that the trunk is routed to. Once the call hits the branch office, it will be sent to the auto attendant so that the headquarters can dial the remote extensions.
Page 166 Deploying the snom ONE IP Telephone System will need to register the trunk to the system at the headquarters, the same way an ITSP would need to be registered. Then anyone in the world can dial the DID, much like...
Page 167: Dial Plans
Chapter DIAL PLANS When an extension dials a number that is not available on the local snom ONE tele- phone system, the system must search for a trunk on which to route the call. To do this, it consults the dial plan. The job of the dial plan is to use pattern and replacement strings to route calls out different trunks.
Page 168: Parts Of A Dial Plan
Deploying the snom ONE IP Telephone System Parts of a Dial Plan Key Components A dial plan consists of the following key components: Preference: The preference number is used to establish the preference order • that will be used by the system when searching for a trunk on which to route a call.
Page 169 Chapter 5: Dial Plans routed through the same trunk. To indicate that a prefix is being using, an asterisk must be entered after the prefix (e.g., 9011* — Fixed patterns: If you use an in a pattern, the system will treat it as a wildcard for 0-9.
Page 170: User Agent Clients
Appendix B: SIP Overview • User Agent Server (UAS): The UAS receives the methods, processes them, and generates responses (e.g., it sends a 200 Ok response to indicate a success- ful session). The UAS may issue multiple responses to the UAC. User Agent Clients The UAC is often associated with the end user, since applications running on systems are used by people.
Page 171: Wildcard Patterns
Deploying the snom ONE IP Telephone System do not register cannot be called and SIP devices that do not successfully authenticate cannot make outbound calls. A media server is a device that handles any kind of media or RT, such as a voicemail server, a conference server, an IVR server, and a music on hold server.
Page 172: Regular Expression Matching
Appendix B: SIP Overview SIP Language Similarities with HTML and SMTP SIP shares some common characteristics with HTTP and SMTP. Like the latter two, SIP is an ASCII text-based protocol which makes it easy to read and troubleshoot. The text below is a SIP trace that shows a user inviting another use to a session. Users are identified by a SIP address, known as a Uniform Resource Identifier (URI).
Page 173 Deploying the snom ONE IP Telephone System Table B-2 Non-RFC 3261 Methods SIP Method Description PRACK Provisional acknowledgement 3262 SUBSCRIBE Subscribes for an Event of Notification from the notifier 3265 NOTIFY Notifies the subscriber of a new event 3265 PUBLISH...
Page 174: Content Of Messages
Appendix B: SIP Overview Common response codes are shown below (for a complete list, see Table B-8). Table B-4 Common Responses Code Definition Occurrence Trying When the other side is trying to process the request Ringing When the other side is ringing Session progress When the event is successful Moved temporarily When forwarding has been activated on the phone...
Page 175 Deploying the snom ONE IP Telephone System • Message body: SIP requests and responses can both contain message bodies. The content of the message body is usually a session description and contains syntax as shown in the message below. SIP URI INVITE sip:513@192.168.1.119:1036;transport=tls;line=islsi...
Page 176: Describing The Sip Session
Appendix B: SIP Overview SIP Header Description Path taken by the request so far Call ID A unique number used to identify the call CSeq Used for keeping track of the conversation number Contact Used for identifying the user agent and the version of software used by the user agent Describing the SIP Session Besides methods and responses, SIP messages can also carry session descriptions in the...
Page 177 Deploying the snom ONE IP Telephone System In the example shown above, the session-level section consists of five lines of text (al- ways beginning with , which indicates the version number of SDP), and the media- level section consists of one audio stream. The...
Page 178: Session Establishment
Appendix B: SIP Overview SIP Call Process Session Establishment INVITE 100 Trying 180 Ringing 200 OK Call Flow 41@pbx.company.com The UAC sends an INVITE message to (UAS). The UAS receives the request and responds with a 100 Trying. 3. The UAS sends a 180 Ringing response to the UAC when the phone begins ringing.
Page 179 Deploying the snom ONE IP Telephone System To: <sip:41@pbx.company.com;user=phone> Call-ID: 3c2812339279-zvojwzvof6we CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:40@192.168.0.32:2061;transport=tls;line=i339wes g>;reg-id=1 P-Key-Flags: resolution=”31x13”, keys=”4” User-Agent: snom360/7.3.14 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUB- SCRIBE, PRACK, MESSAGE, INFO Content-Length: 452 SIP/2.0 100 Trying Via: SIP/2.0/TLS 192.168.0.32:2061;branch=z9hG4bK-...
Page 180: Session Termination
Appendix B: SIP Overview From: “Roland Wright” <sip:40@pbx.company.com>;tag=1521860827 To: “Rachel Reed” <sip:41@pbx.company.com>;tag=ozac09qwnh Call-ID: f6f17567@pbx CSeq: 28593 PRACK Contact: <sip:41@192.168.0.31:1037;transport=tls;line=zs4m8le i>;reg-id=1 Content-Length: 0 ACK sip:41@192.168.0.31:1037;transport=tls;line=zs4m8lei SIP/2.0 Via: SIP/2.0/TLS 192.168.0.34:5061;branch=z9hG4bK- 6dcf1018159b8e96b7b6d62a758d77fd;rport From: “Roland Wright” <sip:40@pbx.company.com>;tag=1521860827 To: “Rachel Reed” <sip:41@pbx.company.com>;tag=ozac09qwnh Call-ID: f6f17567@pbx CSeq: 28592 ACK Max-Forwards: 70 Contact: <sip:41@192.168.0.34:5061;transport=tls>...
Page 181: Register Request
Deploying the snom ONE IP Telephone System Via: SIP/2.0/TLS 192.168.0.34:5061;branch=z9hG4bK- eec7092e42e0694ecd8be3d3e9400816;rport From: <sip:41@pbx.company.com;user=phone>;tag=eed7a3b4e0 To: “Roland Wright” <sip:40@pbx.company.com>;tag=g5ua0i7fz6 Call-ID: 3c2812339279-zvojwzvof6we CSeq: 23626 BYE Max-Forwards: 70 Contact: <sip:40@192.168.0.34:5061;transport=tls> RTP-RxStat: Dur=20,Pkt=970,Oct=170720,Underun=0 RTP-TxStat: Dur=18,Pkt=975,Oct=171600 Content-Length: 0 [7] 2010/04/14 16:10:50: SIP Rx tls:192.168.0.32:2061: SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.0.34:5061;branch=z9hG4bK-...
Page 182 The UAC tries to register the user’s SIP address. The address is located, so a 200 OK response is sent to the UAC. Scenario 1 REGISTER sip:cs410.snom.com SIP/2.0 Via: SIP/2.0/TLS 192.168.1.103:2077;branch=z9hG4bK- rib4emgq;rport From: “Hanna Flanders” <sip:520@cs410.snom. com>;tag=fwxg2s0u4i To: “Hanna Flanders” <sip:520@cs410.snom.com> Call-ID: 3c267028e8ad-q7dwiql86rvc CSeq: 6134 REGISTER Max-Forwards: 70 Contact: <sip:520@192.168.1.103:2077;transport=tls;line=ibey...
Page 183 Deploying the snom ONE IP Telephone System Scenario 2 REGISTER 407 Proxy Authenication Required REGISTER 200 OK Call Flow The UAC tries to register the user’s SIP address. The Web server (running the Web site) thinks that the HTTP data stream sent from the UAC was correct,...
Page 184: Cancel Request
Via: SIP/2.0/UDP 75.150.83.2:5060;branch=z9hG4bK- a071e61e35d725f2c9a17c9bf2edb7f7;rport From: “itsp” <sip:17772830314@itsp.com>;tag=45682 To: “itsp” <sip:17772830314@itsp.com> Call-ID: niyrncl8@pbx CSeq: 8043 REGISTER Max-Forwards: 70 Contact: <sip:17772830314@75.150.83.2:5060;transport=udp;line =19ca14e7>;+sip.instance=”<urn:uuid:7e96105b-8c8b-440e-a0aa- 07add8c80727>” User-Agent: snom-PBX/4.0.1.3453 Supported: outbound Proxy-Authorization: Digest realm=”itsp.com”,nonce=”ab45 353d389d01ba2086232c09417752”,response=”664617e317a5c34 448f276db3932be2f”,username=”17772830314”,uri=”sip:itsp. com”,algorithm=MD5 Expires: 3600 Content-Length: 0 SIP/2.0 200 Ok CANCEL Request The CANCEL request cancels pending transactions and generates an error response to the pending request.
Page 185 Deploying the snom ONE IP Telephone System cease ringing and then respond to the INVITE with a specific error response (a 487, as shown below). CANCEL 200 OK 487 Request Terminated Figure B-4. CANCEL Request—INVITE Response 487 Request Terminated Call Flow A user makes a call, but after a few rings decides to hang up, so a CANCEL request for the previous INVITE is sent by the client to the server.
Page 186 Via: SIP/2.0/UDP 192.168.0.32:2048;branch=z9hG4bK- lg7xoa360cuh;rport=2048 From: “PC PBX 51” <sip:51@localhost>;tag=u58kfgll03 To: <sip:50@localhost;user=phone>;tag=4de5095638 Call-ID: 3c2c575f0429-38s24k0wrdrx CSeq: 2 CANCEL Contact: <sip:51@192.168.0.33:5060> User-Agent: snom-PBX/4.0.1.3475 Content-Length: 0 [7] 2010/04/28 11:21:27: SIP Tx udp:192.168.0.32:2048: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP 192.168.0.32:2048;branch=z9hG4bK- lg7xoa360cuh;rport=2048 From: “PC PBX 51” <sip:51@localhost>;tag=u58kfgll03 To: <sip:50@localhost;user=phone>;tag=4de5095638...
Page 187 Deploying the snom ONE IP Telephone System SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.0.33:5060;branch=z9hG4bK- 9611418f8bbb34f24b5482fb86159ddd;rport=5060 From: “Fifty One” <sip:51@pbx.company.com>;tag=33392 To: “Robyn Wright” <sip:50@pbx.company.com>;tag=55ay4g1375 Call-ID: a8c5d213@pbx CSeq: 21261 CANCEL Content-Length: 0 [7] 2010/04/28 11:21:27: Call a8c5d213@pbx#33392: Clear last request [7] 2010/04/28 11:21:27: SIP Rx udp:192.168.0.31:1024:...
Page 188: Snom One Settings And Sip Traces
CSeq: 2 ACK Max-Forwards: 70 Contact: <sip:51@192.168.0.32:2048;line=o4a1zo97>;reg-id=1 Content-Length: 0 snom ONE Settings and SIP Traces Viewing SIP Traces This section shows you how to turn SIP logging on and view SIP traces. Navigate to Admin > Settings > Logging. Under General Logging, set the log level to 7.
Page 189: Logfile Syntax
Deploying the snom ONE IP Telephone System Logfile Syntax Figure B-6 shows a sample logfile and the syntax that typically appears in one. Date and time Transport layer Transmit Log level [7] 2010/04/07 14:27:31: SIP Tx tls:187.147.41.75:2137: SIP/2.0 200 Ok Protocol Via: SIP/2.0/TLS 192.168.1.131:2137;branch=z9hG4bK-tbn06xq6tjgv;rport=2137;received=187.147.41.75...
Page 190: Troubleshooting With Logfiles
SIP INVITE. “Domain” (Trunk setting) IP address of PBX 1. INVITE sip:509@itsp.com;user=phone SIP/2.0 2. Via: SIP/2.0/UDP 192.168.0.34:5060;branch=z9hG4bK-6574779d5edc4d91e2f dc47a8fba26ec;rport 3. From: “snom ONE” <sip:17772022934@itsp.com>;tag=677614076 4. To: <sip:509@itsp.com;user=phone> 5. Call-ID: 317ab0eb@pbx “Account” (Trunk setting) 6. CSeq: 23418 INVITE 7. Max-Forwards: 70 8.
Page 191 Deploying the snom ONE IP Telephone System Figure B-6. Trunk Settings Supporting Tables Table B-7 SIP Headers Header Abbrev. Header Abbrev. Accept Organization Accept-Contact P-Access-Network-Info Accept-Encoding P-Answer-State Accept-Language P-Asserted-Identity Accept-Resource-Priority P-Associated-URI Alert-Info P-Called-Party-ID...
Page 192 Appendix B: SIP Overview Header Abbrev. Header Abbrev. Allow P-Charging-Function- Addresses Allow-Events P-Charging-Vector Answer-Mode P-DCS-Billing-Info Authentication-Info P-DCS-LAES Authorization P-DCS-OSPS Call-ID P-DCS-Redirect Call-Info P-DCS-Trace-Party-ID Contact P-Early-Media Content-Disposition P-Media-Authorization Content-Encoding P-Preferred-Identity Content-Language P-Profile-Key Content-Length P-Refused-URI-List Content-Type P-Served-User CSeq P-User-Database Date P-Visited-Network-ID Encryption Dep.* Path Error-Info...
Page 193 Deploying the snom ONE IP Telephone System Header Abbrev. Header Abbrev. Min-Expires Resource-Priority Min-SE Response-Key Dep.* Retry-After Target-Dialog Route Timestamp RSeq Security-Client Trigger-Consent Unsupported SIP-If-Match User-Agent Subject Subscription-State Warning Supported WWW-Authenticate Suppress-If-Match * These headers have been deprecated. Table B-8 SIP Response Codes 1xx—Informational Responses...
Page 194 Appendix B: SIP Overview Alternative Service Busy Here 4xx—Client Failure Responses Request Terminated Bad Request Not Acceptable Here Unauthorized Bad Event Payment Required Request Pending Forbidden Undecipherable Not Found (User not found) Security Agreement Required Method Not Allowed 5xx—Server Failure Responses Not Acceptable Server Internal Error Proxy Authentication Required...
Page 195 Deploying the snom ONE IP Telephone System...
Page 196: Configuring Exchange For Snom One
This appendix shows you how to set up Microsoft Exchange 2007/2010 UM with your snom ONE software. Although this setup provides basic functionality to get you started, keep in mind that both Exchange 2007/2010 UM and snom ONE can be customized extensively, which allows for more complex configurations than what is shown here.
Page 197 Deploying the snom ONE IP Telephone System Create a New Unified Messaging Dial Plan 1. Using the Exchange management console, select Organization Configuration/ Unified Messaging. 2. Under Actions, select New UM Dial Plan. 3. Name the dial plan snomone , and set the number of digits in extension num- bers to 4.
Page 198 Appendix C: snom ONE and Exchange Select IP Address and enter the IP address of your snom ONE server. snomone Click the Browse button, and select the dial plan you created. Click New, then click Finish. Associate the Dial Plan with the Unified Messaging Server Using the Exchange management console, select Server Configuration/Unified Messaging.
Page 199 Deploying the snom ONE IP Telephone System Enable Mailbox Recipients for Unified Messaging Using the Exchange management console, select Recipient Configuration/ Mailbox. Select the mailbox you wish to enable and then under Actions, click Enable Unified Messaging. Next to Unified Messaging Mailbox Policy, click the Browse button and then select snomONE Default Policy.
Page 200: Configuring The Snom One Server
Appendix C: snom ONE and Exchange Configuring the snom ONE Server Create a new trunk to connect to Exchange: Click the Trunks tab. MS-Exchange Name the new trunk or any suitable name. Set its type to SIP Gateway. Click the Create button.
Page 201 Deploying the snom ONE IP Telephone System Figure C-1. Trunk Settings for Configuration with Exchange 2007/2010 UM...
Page 202 Click Save. Set the snom ONE External Voicemail System The redirection target should be a telephone number, rather than a SIP URI, and it must be possible to dial that number through the dial plan (the extension must have the permission to do that).
Page 203 Deploying the snom ONE IP Telephone System 2. Set the External Voicemail System field as explained in the previous section. 3. Set Offer Camp On to No. 4. Click Save.
Page 204 GLOSSARY SIP (Session Initiation Protocol) Address mask A bit mask used to identify which bits in an IP address correspond to the network portion of the Internet address and which ones correspond to the subnet portions of the address. The address mask is often referred to as the subnet mask because the network portion of the address can be determined by the class inherent in an IP address.
Page 205 ONE • Administrator Guide, Release 5 Bandwidth The range from highest to lowest frequencies transmitted on a network. Band- width measures network capacity. BLF (Busy Lamp Field) A collection of lights or indicators on a phone that allows users to monitor the dialog state of another phone/user extension.
Page 206 CDR (Call Detail Report) A record produced by the system which contains the details of a call that has terminated on the system. CDRs include the date and time the call started, the number making the call, the number receiving the call, and the call duration. Client/server A network architecture whereby a machine is designated to serve the needs of client machines.
Page 207 ONE • Administrator Guide, Release 5 DHCP (Dynamic Host Configuration Protocol) The TCP/IP protocol for allocating IP addresses dynamically when they are needed. Devices running DHCP do not need a pre-configured IP address to join an IP-based network. As devices join the network, IP addresses are given, and as devices exit the network, IP addresses are released.
Page 208 DND (Do Not Disturb) A feature that prevents an extension from ringing. DND functionality allows users to silence their phones for all incoming calls, even calls made to a hunt group or an agent group, and takes precedence over call forwarding. DND can be configured with an override permission that allows a designated extension to call an extension that has been placed into DND.
Page 209 ONE • Administrator Guide, Release 5 E1 (or E-1) Similar to the North American T-1, E1 is the European format for digital trans- mission. E1 carries signals at 2 Mbps (32 channels at 64 kbps, with 2 channels reserved for signaling and controlling), and the T1 carries signals at 1.544 Mbps (24 channels at 64 kbps).
Page 210 by the Internet’s DNS system like traditional Web site domains. The goal of the ENUM standard is to provide a single number to replace the multiple numbers and addresses for an individual’s home phone, business phone, fax, cell phone, and e-mail. FTP (File Transfer Protocol) A standard Internet protocol used to upload and download files between com- puters that are connected to the Internet.
Page 211 ONE • Administrator Guide, Release 5 H.323 A carrier-grade communication protocol that has been approved by the world governments as the international standard for voice, video, and data conferenc- ing. It defines an entire, unified system for performing these functions and leverages the strengths of the IETF and ITU-T protocols.
Page 212 ISDN (Integrated Services Digital Network) An international communications standards for simultaneous digital transmission of voice, video, data, and other network services over the traditional circuits of the public switched telephone network. ISDN supports data transfer rates of 64 Kbps (64,000 bits per second). BRI (basic rate interface) and PRI (primary rate interface) are the two types of ISDNs.
Page 213 ONE • Administrator Guide, Release 5 packets are played out as they arrive, the output will produce jitter and will be of poor quality. Jitter buffers can be used to change the variable delays into constant delays. LAN (Local Area Network) A computer network covering a small physical area, like a home, office, or small group of buildings, such as a school, or an office park.
Page 214 generated voices are also used). The listeners individually grade the test sentences using a scale that ranges from 1 to 5 (“bad” to “excellent”) and the mean score is taken. Anything below a 3 generally indicates issues with the signal processing or the bandwidth applied to the signal.
Page 215 ONE • Administrator Guide, Release 5 NTP (Network Time Protocol) [RFC 958] A protocol for synchronizing the clocks of computer systems using a set of dis- tributed clients and servers. NTP uses UDP on port 123 as its transport layer and uses a jitter buffer to resist the effects of variable latency.
Page 216 PSTN (Public Switched Telephone Network) The network of the world’s public circuit-switched telephone networks. Origi- nally a network of fixed-line analog telephone systems, the PSTN is now almost entirely digital in its core and includes mobile as well as fixed (plain old telephone service, POTS) telephones.
Page 217 ONE • Administrator Guide, Release 5 by the computer’s processor. RAM is quickly readable and writeable compared to other kinds of computer storage (e.g., the hard disk, floppy disk, and CD-ROM); however, data in RAM remains only as long as the computer is running. Once the computer has been turned off, RAM loses its data.
Page 218 put the RTP packets in order once they are received. The timestamps are used to restore the original timing relationship of the data. SBC (session border controller) A device used in Voice over Internet Protocol (VoIP) networks to control the sig- naling (and even the media streams) involved in initiating, conducting, and ter- minating telephone calls or other interactive media communications.
Page 219 ONE • Administrator Guide, Release 5 measure, justify, and even compare the services with those of outsourcing net- work providers. SNMP (Simple Network Management Protocol) [RFC 1157] A UDP-based network protocol used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention.
Page 220 a variety of NATs and application programs. However, STUN does not allow incoming UDP packets through symmetric NATs and cannot be used to obtain an Internet Protocol address (IP address) to communicate with a peer behind the same NAT. Switch A small device for connecting one or more computers to other computers, networked devices, or to other networks.
Page 221 ONE • Administrator Guide, Release 5 TLS (Transport Layer Security) [RFC 4346, 5246] A protocol that ensures privacy between a client and a server. TLS authenticates both the client and the server and creates an encrypted connection between the two. TLS provides protection against eavesdropping by a third party and protec- tion against tampering with a message.
Page 222 VLAN (Virtual Local Area Network) A software concept whereby a group of hosts with a common set of requirements communicate as if they were attached to the same broadcast domain, regardless of their physical location. A VLAN has the same characteristics as a physical LAN, but end stations in a VLAN can be grouped together even if they are not located on the same network switch.
Page 224 Index INDEx feature overview 225–226 logging in and out 244–245, 441 message-music cycle 228–229 monitoring 237 Symbols naming the agent group 230 911 95 night service 242–243 queueing 227 queue manager 236 recording agent group greetings 242 access list blocking IP addresses 72 ringback in the queue 239–240 setting up an agent group 229–243 address book...
Page 225 Deploying the snom ONE IP Telephone System welcome greetings 209–213 DISA 283 welcome message 193 pre-pay 284 read out balance 287 setting up the account 284–287 black list calling features auto attendant 198 add to white list 444 classify a contact 444...
Page 226 Index call pickup 431 buying 70 gmail SMTP server 298 call recordings making your own 70 system performance 49 size and format 71 call return 427 system certificate 68 call teach 174 clean up extension 444 call teach mode 442 clean up extension permission 175 CMC 97 CDR URL setting 47...
Page 227 Deploying the snom ONE IP Telephone System CSV files 475–494 sample dial plans 155–158 button profiles 334–335 wildcard patterns 151–152 CDR to CSV 391–392 DID. dialing converting Excel to CSV 482–488 direct destinations 205–206 domain address book 489–496 disk space.
Page 228 322 MoH/paging application 381 file system 33–42. configuration See also ringtone config. file 324 files snom ONE software 19 directory tree 33 DTMF folder overview 35, 37–41 inband 52 generated folder 365 global configuration file 34 of greetings 310 email 295–306...
Page 229 Deploying the snom ONE IP Telephone System fresh installation 5 Linux 10 greetings 309–314 Mac 7 agent group greetings 313–315 Windows 5 auto attendant greetings 311–312 instant messaging 414 personal greetings 309–310 intercom 174, 427 recording permission 201 record new greetings 452 IP addresses blocking access 72–75...
Page 230 Index leaving a voicemail message 451 paging 251–258 configuring paging/MoH 381–387 Microsoft Exchange multicast 252 basic setup for Exchange Server multicast IP addresses 256–257 2007/2010 527–533 setting up an account 253–256 midnight events 105 unicast 251 reset block CID 106 parameters reset DND flags 106 max_tcp_length 67...
Page 231 Deploying the snom ONE IP Telephone System default dial plan scheme 107 ptimes DHCP 343, 344, 352–353 multicast IP addresses 57 dial plan scheme 107 PVA. Personal Virtual Assistant. generated directory 36 generated files 365–370 logging PnP events 63 record calls 445 manual setup 344, 345, 355–357...
Page 232 191–192 SOAP settings trusted IP 47 changing hidden settings 34 star codes snom ONE star codes 426 From header 96 logging SIP events 62 star codes (by number) multicast 51 *00 (call cell phone of extension) 469...
Page 233 Deploying the snom ONE IP Telephone System *61 (show account balance) 442 *98 (record new greetings) 452 *62 (wakeup call) 443 *99 (clear message indicator) 458 *63 (request call details) 443 support *64/*65 (login/logout) 441 online help 25 *66 (redial) 427...
Page 234 Index ports 59 Linux 20 tftp directory 42 Mac 19 tftp folder 36, 371 Windows 18 time zone setting local time zone 43 voicemail To header accessing 449 setting a new To header for the domain add a comment to a message 449 calling own extension 100 transferring calls change your PIN 448, 449...
Page 235 ring my cell phone when voicemail arrives 466 skip a message 449 transfer call to another’s voicemail transfer call to your voicemail 428 voicemail prompts 38 voicemail settings blocking from user interface 80 wakeup call using star feature codes 443 WAV files MoH 379–380 web interface...
Page 236 How to Find Us Berlin snom technology AG Leeds LS12NL Charlottenstr. 68-71 United Kingdom 10117 Berlin Tel: +441133503111 info@snom.com Fax: +441133503110 The entrance is at Charlottenstraße/ Boston corner of Krausenstrasse. Next subway station: snom technology Inc. Stadtmitte (lines U2, U6).
Page 237 Taipei R803,5F,No.285,Sec 4, Zhongxiao E. Rd., Taipei city, Taiwan ,10692 Tel: +886-2-6639-8031 Fax: +886-2-6639-8039 infoASIA@snom.com...

Snom ONE IP Technical Manual

Quick Links

Related Manuals for Snom ONE IP

Summary of Contents for Snom ONE IP

Table of Contents