Download Print this page

Snom ONE Technical Manual

Ip telephone system

Hide thumbs Also See for ONE:

User manual (27 pages)

Table Of Contents

Table of Contents

Advertisement

Quick Links

See also: User Manual

Deploying the

snom ONE IP Telephone System

Technical Manual

Table of Contents

Advertisement

Table of Contents

Troubleshooting

Need help?

Need help?

Do you have a question about the ONE and is the answer not in the manual?

Questions and answers

Summary of Contents for Snom ONE

Page 1 Deploying the snom ONE IP Telephone System Technical Manual...
Page 2 Copyright © 2010 snom technology, Inc. All rights reserved. snom® is a registered trademark of snom technology AG and its affiliates in the European Union, USA, Japan, South Africa, Australia, China, and certain other countries and regions. Unless specified otherwise, all trademarks, in particular product names, are legally protected trademarks of snom technology AG.
Page 3 Web Interface ........................261 Star Codes ........................279 Voicemail .......................... 295 Cell Phones ........................303 Appendix A. Working with CSV Files ................. 315 Appendix B. SIP Overview ....................331 Appendix C. snom ONE and Exchange ................351 Glossary ............................357 Index 369...
Page 5: Table Of Contents
Getting Started About snom ONE .................
Page 6 Deploying the snom ONE IP Telephone System General Logging ................
Page 7 Contents Inbound Settings ................Connecting Branch Offices Together .
Page 8 Deploying the snom ONE IP Telephone System viii Ringing an Extension ..............
Page 9 Contents Scheduled Conferences ..............Creating a Scheduled Conference Account .
Page 10 Deploying the snom ONE IP Telephone System Blacklist Activity to Email ..............
Page 11 Contents Changing Default Settings Using a Customized XML File ....Troubleshooting ................Music on Hold Setting up Music on Hold .
Page 12 Deploying the snom ONE IP Telephone System Transfer Calls ................
Page 13 Contents xiii Via Email ................. . Via Cell Phone .
Page 14 Deploying the snom ONE IP Telephone System User Agent Clients ..............
Page 15: Part I-Getting Started
Part I Getting Started...
Page 16 Part I—Getting Started...
Page 17: Getting Started
VoIP. This guide is designed to help you plan and configure snom ONE Voice over IP (VoIP) deployments ranging in complexity from a small office using the Internet for SIP trunks to a large, multi-national conglomerate of snom ONE systems.
Page 18: Memory/Hardware Requirements
Additional languages, recorded calls, and log files can fill the disk quickly. 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 19: Disposal
European Union should be done in line with local regulations. Please con- tact local authorities for further information. 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. Windows Installations 1.
Page 20 Deploying the snom ONE IP Telephone System 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. The installation will take a minute to install.
Page 21: Logging In
Chapter 1: Getting Started 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 http://localhost...
Page 22 Deploying the snom ONE IP Telephone System System Administrator Domain Administrator User Figure 1-3. snom ONE Web Interfaces 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.
Page 23: Activating Your License
Activating Your License Your snom ONE license will need to be activated before you can register extensions to the system. The acti- vation 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 24: Manual Software Upgrades
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). 4. Put the file into the snomONE working directory.
Page 25: Restarting From A Command Line
Chapter 1: Getting Started 2. Click Manage. 3. Click Service Applications, then click Services. 4. From the right-hand pane, click snomONE PBX 5. Click Restart. Restarting From a Command Line The system can be stopped and restarted from the command line: net stop snomone ■...
Page 26: When The System Fails To Restart
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.
Page 27: Documentation
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 register a new account: Documentation The following typographic and usage conventions occur in this book:...
Page 28 Deploying the snom ONE IP Telephone System...
Page 29: Part Ii-Administering The System
Part II Administering the System...
Page 30 Part II—Administering the System...
Page 31: System Settings
SYSTEM SETTINGS The snom ONE telephone system encompasses three different accesss levels—administrator, domain admin- istrator, and user—each providing a different web interface (depicted earlier on page 6). The system ad- ministrator has control of the entire system, while the domain administrator has control of only the domain.
Page 32 From this page, you can provide parameters to change the generation of plug and play files. Access You can control which IP addresses may access the snom ONE service here. User Page This page lets you control which settings will be displayed on the user’s web inter- Control face.
Page 33: Directory Structure
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...
Page 34: Folder Overview
Deploying the snom ONE IP Telephone System ONE system, the name of the setting, and the value. In the URL example shown below, the address is the setting is setting , and the value is being changed to Important: Always make a backup before modifying the file! http://pbx/reg_status.htm?save=save&setting=123...
Page 35: Folder Details
Chapter 2: System Settings Folder Name Contents extensions Information about each extension (name, number, MAC, etc.) generated** Files that are generated from templates that exist within the system binary hoots Multicast paging information html Customized HTML files hunts Account information about hunt group accounts ivrnodes Information about each IVR node account messages...
Page 36 —The accesslist folder contains IP addresses that have been blocked from ac- ■ cessing 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. Each file includes the pos- ■...
Page 37 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 account and any values assigned to those param- eters. —The folder contains the CSV CDRs, if there are any. ■...
Page 38 Deploying the snom ONE IP Telephone System colines —The colines folder contains information about co-lines that are created on the sys- ■ tem. conferences —The conferences folder contains an XML file for each conference account. ■ Each file includes the possible parameters for the account and any values assigned to those param- eters.
Page 39: Configuring System Settings
Chapter 2: System Settings pnp_parms pnp_parms —The folder contains all configuration files that are involved in plug and ■ play. recordings recordings —The folder contains a WAV file for all greetings and recordings, ■ whether created for personal or system use (e.g., auto attendants, agent groups, and hunt groups). Chapter 17 for more information on recordings.
Page 40: Administrator Login
Password: This field sets the password for the user name from the previous setting. By default, ■ there is no password, but be sure to set one. The administrator’s password can be reset in the event it gets lost (see instructions below).
Page 41: Appearance
Chapter 2: System Settings 2. Search for the <pw_pass> element tag. 3. Delete the password. (If no text appears between the element tags, then the password field is empty.) 4. Save the file. 5. Restart the system. 6. Set a new password through the web interface (Admin > Settings > General). Appearance Web Session Timeout (s): This field determines how long a web session will stay active before it ■...
Page 42 Deploying the snom ONE IP Telephone System — 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). Table 2-3. Password Scoring Method Character Type...
Page 43 Chapter 2: System Settings Format CDR URL Syntax Description of Syntax file:disk Disk can be any name, as it is not used by the program anyway. mailto:name@company.com Email Record Location: This field determines where system-initiated recordings will be stored on the ■...
Page 44: Performance
CPU should play out media, it will come across as stuttering and be perceived as jitter coming from the system. In order to avoid this problem, bind the pbxctrl to one fixed CPU. Depending on the operating system, you can do this manually or you can ask the system...
Page 45: Sip Settings
2 hours (7200 seconds), but you can increase this setting if you lean toward longer phone calls. This setting is crucial for keeping your call list clean; for example, if one mailbox talks to another mailbox or if a call does not drop properly, the system can automatically clean this up.
Page 46 Therefore, the system must detect such a loop. In environments where an external SIP proxy routes the call from one snom ONE do- main to another, a simple loopback detection that is based on the call-ID is too pessimistic. There-...
Page 47: Ports
. In general, you may bind to more than one socket; just separate the addresses by spaces. If you do not want to use the service, leave the field empty. If you change a port binding, you will need to restart the snom ONE service. We sup- port the default SIP port.
Page 48 Deploying the snom ONE IP Telephone System * Changes to HTTP and SIP settings require a system restart. SIP UDP Ports: If you are using SIP over UDP, you need to set this field. The default port for ■ UDP is 5060 .
Page 49: Rtp Ports
Chapter 2: System Settings IP Routing List: The IP Routing List setting is used to override the operating system IP routing ■ table and is linked to the routing table (this setting will be consulted by the system before consult- ing/using the operating system).
Page 50: Snmp
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 the interfaces it sees in the machine.
Page 51: Tftp
Chapter 2: System Settings Table 2-5. Available SMNP Sensors Description Absolute Unit 1.3.6.1.4.1.25060.1.1 Call legs Calls 1.3.6.1.4.1.25060.1.2 Registrations Registrations 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...
Page 52: Logging
One of the first log messages that you will see is the working directory. If the Log Filename set- ting does not contain a path, the system will write the log file to that directory. You can specify the directory during the installation process.
Page 53: Specific Events
Log SIP events: Events in this module relate to the SIP traffic of the system. ■ Log media events: The system reports events about media processing, for example, a one-way ■ audio RTP timeout. Log IVR events: This module logs events related to processing user input (e.g., all DTMF events, ■...
Page 54: Sip Logging
INVITE, CANCEL, ACK, BYE). When you enable the logging for one of the previous categories, the SIP packets will be logged on log level 7. If your log level is below 7, the packets won’t show up in your log.
Page 55: Configuration
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 4.
Page 56: Save/Restore A Backup
Click Browse to find the file to be restored (the full path of the file is required). This file is the one you backed up in the previous section.
Page 57: Reload Configuration Files
Chapter 2: System Settings Reload Configuration Files Configuration files ringtones.xml pnp.xml can be customized for your system. These files can be downloaded from wiki.snomone.com and uploaded through the Browse option shown below. You can also place the files into the html folder and restart the system (downloads are available at wiki.snomone.com).
Page 58 Buying a Certificate When you buy a certificate, it must be known that you are really the one who is operating a server. Although the mechanisms for this process differ, all services require that you pay for the service and that your web browser is already set up to trust the certificate authority.
Page 59: Access List
Chapter 2: System Settings In order to provide the key, just enter the ASCII string that you received from the trusted party, copy it into the text field, and press Save. The system will then present this certificate to HTTP and SIP connections that require secure communications.
Page 60 Deploying the snom ONE IP Telephone System Limiting the service to authorized addresses: You might also want to limit the service to specific IP ■ addresses only. For example, while you might allow users to register their IP phones in the office, you might allow only selected users with their associated IP addresses to register their phones from home.
Page 61: Controlling User Page Appearance
Chapter 2: System Settings Address Net Mask Type Description of Result 127.0.0.1 255.255.255.255 First Allow This will ensure that entry you can always access the HTTP interface from the local com- puter. 192.168.0.0 255.255.0.0 Next Allow This will ensure that entry everyone in the LAN can access the system.
Page 62: General Control
User can select the address book: 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. Figure 2-4. Blockable User Settings (Settings > General)
Page 63: Redirection Control
Chapter 2: System Settings Redirection Control The Redirection Control settings allow you to prevent the user from viewing the redirection settings: Incoming anonymous calls: This setting allows users to control the treatment of anonymous ■ callers (reject them, pretend to be busy, ask for name, etc.). In some situations, administrators may prefer to determine how anonymous callers are handled.
Page 64: Email Control
Deploying the snom ONE IP Telephone System Figure 2-6. Blockable User Settings (Settings > Mailbox) Email Control The Email Control settings allow you to prevent the user from viewing the following email-related settings: Send a mailbox message by email: This setting allows users to send voicemail messages to their ■...
Page 65: Administering The Domain
ADMINISTERING THE DOMAIN The snom ONE uses the notion of a domain since all IP systems are based on domains. A domain is essen- tially a logical group of users on the same network or computer that is linked to the Internet (the name must be a resolvable entity on the Internet via DNS so that it can get its IP address).
Page 66: Changing The Name Of The Domain
Deploying the snom ONE IP Telephone System Changing the Name of the Domain To change the name of the default domain so that it reflects your company domain: Navigate to Domains and click the Edit icon. pbx.company.com 2. Replace with your own domain name.
Page 67 Chapter 3: Administering the Domain To log in to the domain, users will need to log in as Domain Administrator (with their extension credentials) as shown below: Once logged in, domain administrators will be able to access to the domain settings shown below. These settings are detailed in Table 3-1.
Page 68: Default Domain
Deploying the snom ONE IP Telephone System Web Interface Description Buttons This page provides a list of all the button profiles that are available 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. This includes extensions, hunt groups, agent groups, service flags, paging accounts, and any other account that exists on the domain.
Page 69: Configuring The Domain
Chapter 3: Administering the Domain Note: A yellow triangle symbol indicates that the account is missing either the SIP password or the web password. Configuring the Domain From the Settings tab, you can configure many of the domain’s settings: Name of the Domain: This field allows you to give the domain a descriptive name. The name can ■...
Page 70 Emergency Numbers: You can specify special destination numbers when an extension dials an ■ emergency number. The number(s) that trigger the mechanism must be listed in this setting. If you have more than one emergency number, use a space between the numbers (e.g., 911 199 ). By...
Page 71 Chapter 3: Administering the Domain Use last 7 digits when cellphone matching: If this is checked, the system will use the last 7 digits ■ to match cell phone numbers. This is useful in places where only 7 digits are used in the caller-ID. Send welcome email when an extension is created: If this setting is checked, new users will auto- ■...
Page 72 Deploying the snom ONE IP Telephone System <pbx install dir>/cdr into the directory in XML format (see the CDR URL setting on page 26). Billing Settings CMC authentication for outbound calls: This setting works in ■ tandem with the “C” checkbox in the dialplan (page 91).
Page 73 Voicemail PIN Digits: This setting specifies the number of digits that will be ■ required for the voicemail PIN. Although any number larger than one digit is ac- ceptable, we recommend you require four or five digits. See also the PIN setting in...
Page 74: Accounts Page Display
Accounts Page Display Accounts page size: This setting determines how many accounts appear on one page. The options ■ range from 25–1000 accounts (all accounts can also be viewed).
Page 75 Display MAC address for the accounts in the accounts page: When this setting is activated, ■ the MAC address for each account (if one is available) will be displayed. When the permanent or temporary assignment mode is used for obtaining MAC addresses, a question mark or asterisk will appear in the MAC address field.
Page 76: Recording Defaults
Deploying the snom ONE IP Telephone System All three fields can be displayed at the same time: Recording Defaults This section allows you to define domain-level call recording settings. Recorded calls will be saved in the cordings directory (see also Chapter 17).
Page 77: Midnight Events
Chapter 3: Administering the Domain Midnight Events At midnight, the system can perform several maintenance tasks, including the generation and sending of CDR reports. Send daily CDR report to: The system sends daily CDR reports (sample shown in Figure 3-2) to ■...
Page 78: Provisioning Parameters
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 ap-...
Page 79: Domain Address Book
Chapter 3: Administering the Domain Authentication User/Password: This setting makes it easier to carry out domain level settings of ■ phones. Using this setting, the administrator can create identical usernames and passwords for all devices in a domain. This password will bypass users’ passwords. However, an extension@domain is admin password still required.
Page 80 Deploying the snom ONE IP Telephone System the CDR report. The CMC can also be entered directly into the display of the phone (by pressing the CMC soft key) if the person is calling from a number other than the number that is in the ad- dress book.
Page 81: 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: Phone Display If the administrator has enabled the User can select the address book setting (Admin > Settings > User Page-Control), users can also search through the domain address book from their IP phones:...
Page 82 Deploying the snom ONE IP Telephone System...
Page 83: Trunks
In the example shown below, a telephone switch is connected to a corporate private branch exchange (PBX) through one physical T1 line. A separate line (or channel) is needed for each of the 23 calls that are on the PBX.
Page 84: Trunk Types
Figure 4-2. Using SIP Trunks for Communicating with External Networks There are three types of trunks with the snom ONE telephone system: SIP registrations, SIP gateway, 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 85: Sip Gateway
ITSP 6031234577 6031234588 Figure 4-3. SIP Trunks 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 86). 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 86: Inbounds Calls
Deploying the snom ONE IP Telephone System nection to the network and is similar to the gateway model. The difference is in the way anonymous calls are made and in how the 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.
Page 87 Chapter 4: Trunks line For gateways and proxies, this method is not possible, so if the parameter isn’t there to give clues on how to route the call, the system must continue searching the trunk. This is done by a recursive DNS-resolu- tion of the outbound proxy of the trunk.
Page 88: How The System Routes A Call To The Proper Extension
Deploying the snom ONE IP Telephone System How the System Routes a Call to the Proper Extension Basic Routing Once the trunk has been identified and the inbound call is trusted, the system must determine where in the system to send the call. Two possibilities are available for this: The system first looks at the trunk’s Send call to extension setting.
Page 89: When Regular Expressions Are Involved
Chapter 4: Trunks Figure 4-11. SIP INVITE Reflecting DID Routing When Regular Expressions are Involved Regular expressions can be used for numerous call routing purposes, but they are especially helpful when you have a large number of DIDs. When you have a few DIDs, you can simply enter the DID number into the Account Number(s) setting in the extension that the DID is assigned to.
Page 90 Deploying the snom ONE IP Telephone System Important: The example shown in Figure 4-12 simply shows that numerous expressions can be used in one string; however, a single expression in many cases would be sufficient. For example, to specify that only the...
Page 91: Regular Expressions And Direct Inward Dialing (Did)
Chapter 4: Trunks 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. If the extension is not found, the call will be sent to the auto attendant.
Page 92 Deploying the snom ONE IP Telephone System DIDs and 3-Digit Extensions DIDs and 4-Digit Extensions 978 521-1402 978 521-4102 978 521-1403 978 521-4103 978 521-1404 978 521-4104 978 521-1405 978 521-4105 Follow the steps below: 1. Create the regular expression.
Page 93: Outbound Calls
Chapter 4: Trunks 2. Enter the aliases into the corresponding extension accounts: 3. 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 carrier for billing pur-...
Page 94: Representing The Source
4. Trunk (Trunk ANI setting). As a last resort, the system uses the DID number of the trunk, when there is one. This is a typical scenario in the NANPA area, where a trunk has a primary number associated with it. When someone calls the number, the caller will typically reach an auto attendant that processes the DID number.
Page 95: Creating Trunks
Chapter 4: Trunks P-Preferred-Identity representation can be done with the header. The system changes only the name of the header from P-Asserted-Identity P-Preferred-Identity . The rest remains the same, as in the first method. No Indication: This method just discards the display number and uses only the network number ■...
Page 96: Configuring Trunks
Deploying the snom ONE IP Telephone System Configuring Trunks General Settings Trunks have a large number of settings. For an explanation of each setting, match the numbers in the image with the numbers below the image. 1. Name: Once a trunk has been created, the name and type of the trunk can be changed at any time.
Page 97 ). If a fourth simultaneous call attempt is made, the system will play a fast busy signal. If you have more than one trunk, you can set up a failover behavior so that the system will try to use a different trunk for the call once the first trunk has all CO-lines in use.
Page 98 Up and Down buttons. 15. Lock codec during conversation: This prevents the end point from engaging a conversation on one codec and then requesting a codec change later. For example, if a carrier wants the G.729 codec to be...
Page 99 16. Proposed Duration (s): Use this setting to specify the registration duration. Although the registrar typically defines the duration of the registration (according to the IETF standards), some providers follow the proposed duration of the trunk. The values range from 20 to 3600 seconds. One hour (3600 seconds) is a reasonable value.
Page 100: Outbound Settings
Enable this setting also when you have a trunk that comes from another system; this will make it possible to call from one system to another. 23. Interpret SIP URI always as telephone number: When a call comes into the system, the system needs to know how to interpret the number.
Page 101 PSTN gateways are available for terminating the call and one gateway does not accept any more calls. Another example is when you first try to route the call via a peer-to-peer call using ENUM or other location methods and only if such resolution does not result in a connection fallback to a PSTN call.
Page 102: 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 103: Using A Gateway Trunk
Using a Gateway Trunk SIP gateway trunks are the best method for connecting two snom ONE telephone systems, as long as both systems either have public routable IP addresses or are on a private network with no issues with NAT. Likely candidates for this configuration are the classroom environment and organizations with a large private net- work (as long as the system has an interface directly on a public IP address).
Page 104: Using A Sip Registrations Trunk (Sip Tie Line)
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 address, and a remote branch office has only one public IP address and requires that the system be on a private address but still wants to have connectivity back to corporate (Figure 4-18).
Page 105 Chapter 4: Trunks 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 headquar- ters can dial the remote extensions.
Page 106 Deploying the snom ONE IP Telephone System...
Page 107: Dial Plans
Since extensions map to dial plans, dial plans should be set up before extensions; however, if only one dial plan will be used and it will be the default dial plan, then this is not as important.
Page 108 Deploying the snom ONE IP Telephone System This can be used to prevent unauthorized callers from making international calls. The C and P set- ting works in tandem with the CMC authentication for outbound calls domain setting (see page 56). The CMC code can also be set from the domain address book or the personal address book.
Page 109 Chapter 5: Dial Plans Following is a sample dial plan. The trunks are listed in the order in which the system will look at each trunk. The notes that follow the dial plan describe the effect of the pattern and replacement fields. Notes A.
Page 110: Wildcard Patterns
4* to allow all extensions that start with a 4. To grant permission to only one extension, place a single extension in the field. In the Permissions to monitor this account field: This field is included in all account types (ex- ■...
Page 111: Building A Dial Plan
Chapter 5: Dial Plans number (starting with 1). Additionally, the matching string may be used to insert the registrar name. For examples of algorithms, see “Sample Dial Plans” on page Building a Dial Plan Creating a Dial Plan Every domain has its own dial plans, and any number of dial plans is allowed on a domain. The number of entries allowed on a dial plan is also unlimited.
Page 112 In multi-domain ■ environments, this mode is used to send a call from one domain to another domain (on the same system) without using an external SIP proxy. In this mode, the system will first check to see whether there is a match of the pattern and then calculate the destination using the replace- ment pattern.
Page 113: Sample Dial Plans
, the system will automatically convert that into a 12121234567 A North American Dial Plan If you use the snom ONE telephone system in the fixed-length dial plan of North America, you may use a dial plan similar to the one that follows: 9[911|411] —The first pattern matches the emergency number and the service number explicitly...
Page 114: Sending Star Codes On A Trunk
Deploying the snom ONE IP Telephone System Sending Star Codes on a Trunk Extended regular expressions can also be used when sending star codes on a trunk. \*67 When passing a star (*) to the carrier, a backslash is required before the star (e.g., );...
Page 115: Inter-Domain Dialing
Chapter 5: Dial Plans Inter-Domain Dialing Domains with Non-Overlapping Extensions If you have domains with non-overlapping extensions, use the following instructions to configure your inter- domain dialing. (DIDs, by nature, are non-overlapping.) For each domain, create a dial plan entry with Try Loopback in the Trunk field. Enter * for both pattern and replacement.
Page 116 Deploying the snom ONE IP Telephone System...
Page 117: Extensions
This section guides you through both. Working with the Default Extensions The snom ONE telephone system comes with ten preconfigured, two-digit extensions. To modify these extensions, use the following procedure:...
Page 118 Deploying the snom ONE IP Telephone System 1. Click the Domains tab. 2. Select the domain and click Accounts. The accounts list will be displayed as shown below: Figure 6-2. Default Accounts 3. Replace the First name and Last name fields with the user’s name.
Page 119: Importing Multiple Extensions (Bulk)
Chapter 6: Extensions Note: After changing the number of digits of the extensions, the PnP Dialplan Scheme setting will need to be reset so that the phone will allow the user to enter the necessary digits before it begins processing the call (this setting is detailed on page 62).
Page 120 PIN field empty and opt to have users set up their own PINs. Once a PIN has been set up, no one other than a user who registers with the extension credentials will be able to go to the mailbox. For optimum security, we recommend at least five-digit PINs (see...
Page 121 Chapter 6: Extensions 4. Click Create. 5. To open the account, click List then click the account or use the search box at the top of the screen The following screen will be displayed: Figure 6-3. General User Settings (as seen by the admin) Once the account has been created, the administrator, registration, and permission settings will need to be configured.
Page 122: Before Registering The Extension
Registration Settings The registration page is used to control the registrations for the account. You may register one or more de- vices for one extension. When an extension is called, the system will call all registered extensions in parallel.
Page 123 This is useful for service providers or enterprises that want to ensure only one phone is registered per extension. Credit for outbound calls: This setting allows you to place a limit on outbound calling for the ■...
Page 124 Deploying the snom ONE IP Telephone System tion problems easier. You can also decide who should receive an email when the registration status does change—the administrator, the user, or both. Current Registrations Displayed at the bottom of the Registrations page are the current registrations (if any exist) for the account.
Page 125: Permission Settings
Teaching (whisper mode) for the following extensions: Call Teach mode allows a third party on ■ a line with only one of the parties knowing. This is typically useful in a call center when a trainer wants to offer tips to a new agent without the customer knowing. Once permission has been set,...
Page 126 DND which has been set on the system. The permission to override DND is useful for extensions being used by assistants who are responsible for screening calls. Intercom to the following extensions: This feature is used for communicating with one other ■...
Page 127: Service Flags
hapter SERVICE FLAGS Service flags give companies professional methods for handling callers who call after normal business hours. These options include (1) night service, which redirects callers to the extension or phone number of the person covering the business during closed hours, (2) voicemail, which allows the customer to leave a mes- sage and the company to respond as necessary, and (3) a recording of important information (e.g., hours of operation, directions, contact information).
Page 128: Setting Up A Service Flag Account
Deploying the snom ONE IP Telephone System 1 12 Feature Functionality Benefit Auto attendant Auto attendants are used to answer incom- Use several auto attendants to reduce control ing calls and direct them to other destina- the risk of losing business. Create tions.
Page 129 Chapter 7: Service Flags 1 13 3. Click Create. When the page reloads, click List and open the account. 4. Use the following information to complete the service flag configuration: Account Number: This field takes an extension number and/or DID number(s). The number ■...
Page 130: Linking A Service Flag To An Account
24-hour format (e.g., 21:00 for 9:00 p.m.) ■ English AM/PM style (e.g., 9:00P for 9:00 p.m.) ■ Multiple time To specify more than one time segment, use a space between the two segments: segments 9:00-12:00 1:00P-7:00P ■ Holidays To specify the days on which you do not want the schedule to be activated, such as a holiday or any other day, use the holiday field: To specify one day, use the MM/DD format (e.g., 11/24 for November 24).
Page 131: Method 1: Night Service
Chapter 7: Service Flags 1 15 Method 1: Night Service The Night Service setting allows you to provide service to callers during after-hours. Callers will be forward- ed to the new number based on the service flag schedule. In our example, when service flag 600 is active, auto attendant 500 (an auto attendant with a day message) will forward calls to extension 501.
Page 132: Method 2: Message-Only And Voicemail Options
Deploying the snom ONE IP Telephone System 1 16 5. From the day auto attendant account, link the service flags to the other accounts. Method 2: Message-Only and Voicemail Options If you don’t want to provide service to callers during after-hours, use the IVR link from the auto attendant account.
Page 133: Setting/Clearing A Service Flag
The Set/Clear status of a service flag can be seen from the Accounts tab: Automatic service flags will become activated according to a schedule that you create. Manual service flags, on the other hand, need to be manually activated using one of the following methods.
Page 134: Setting A Manual Service Flag From The Phone
Deploying the snom ONE IP Telephone System 1 18 Setting a Manual Service Flag from the Phone Call the service flag extension each time you want to change its state. The confirmation tone that is played is based on the Confirmation tone setting: Setting a Manual Service Flag from the Web Interface A manual service flag can also be set by using the Current State setting in the service flag account.
Page 135 Chapter 7: Service Flags 1 19 7. Click Buttons. 8. From the Configuration Profile dropdown, assign the profile to the extension. 9. From the phone, press the button configured as Service flag. It will toggle between Set and Clear. The values assigned to the buttons correspond with the locations shown below:...
Page 136 Deploying the snom ONE IP Telephone System...
Page 137: Auto Attendant
hapter AUTO ATTENDANT The auto attendant functions like a virtual receptionist, connecting incoming calls to extensions and other devices that have been configured to the system. The auto attendant often announces a company’s name, followed by a selection of dialing options. A typical welcome message might be “Thank you for calling Company ABC, “for Sales, press 1,”...
Page 138: How An Auto Attendant Works
Welcome Message When someone calls into the auto attendant, the auto attendant plays a welcome message. The welcome message can be a standard message or one that varies according to time of day or week (see “Multiple Mes- sages—Time-Based Configuration” on page 124).
Page 139: Processing User Input
Once the auto attendant has processed the user’s input, the auto attendant calls the extension. If the exten- sion is not available and the user has only one line (see user’s Registrations tab), the caller will be sent di- rectly to the extension’s voicemail. If more than one line has been designated to the extension, the caller will hear ringback and the user will hear a beeping noise (call waiting).
Page 140: Blacklisted Callers And Anonymous Calls
If a user has programmed a redirection from an extension and does not pick up the call from that phone, the auto attendant will handle the call in one of two ways: If the call comes from an outside user, the caller will be sent to the extension’s voicemail after the ■...
Page 141: Auto Attendant Behavior
Name: This field allows you to create an alias so that you can quickly identify the auto attendant ■ Day Auto Attendant among other auto attendants. For example, you might use the names Night Auto Attendant to distinguish them from one another.
Page 142 ■ dant. The report is sent nightly at midnight to the email address listed in this field (e.g., voicemail@ snom.com). Only one email address is allowed in this field. Set Language: The auto attendant supports multiple-language environments. You may explicitly ■...
Page 143: Timeout Handling
Chapter 17 more information on audio prompts and languages that can be downloaded. Permissions to monitor this account: By default, the snom ONE telephone system allows ■ any phone within the domain to monitor an auto attendant account. The account is monitored through the busy lamp field (BLF).
Page 144: Night Service
Note: You may specify more than one night service flag (separated by a space). The first service flag account will correspond to the first night service number, and the second service flag account will correspond to the second night service number, etc.
Page 145: Direct Destinations
3-second delay ensures that the caller’s complete input (e.g., 101) will be processed rather than just the first digit. Input number: This number can be one or multiple digits; however, the system dials direct des- ■ tinations immediately after a user has provided keypad input, so overlapping between a direct destination and an extension number can be a problem.
Page 146: Nesting Auto Attendants
8-5 depicts three auto attendants nested within the main auto attendant. This model could be developed even further to include nine additional auto attendants, one for each of the boxes shown to the right (i.e., an auto attendant could be created for product A that would include prompts that are specific to that product).
Page 147: Welcome Greetings
Chapter 8: Auto Attendant For product A, press 1. For Sales, press 1. For product B, press 2. For product C, press 3. To make a payment, press 1. For Accounting, press 2. To hear your balance, press 2. To speak to an agent, press 3. To reset password, press 1.
Page 148: Recording The Greeting
Deploying the snom ONE IP Telephone System 2. Enter your greeting into the system either by recording the message using the star code (*98) or by uploading it as a WAV file. See the next section, “Recording the Greeting.” Recording the Greeting Before an extension can record a greeting for an auto attendant account, the extension must have permission to do so.
Page 149: Filing System And Naming Conventions
1. Using a recording device, record the greeting (use an 8 kHz mono, 16 bit file). 2. Go to the auto attendant’s IVR tab and click Browse. 3. Select the recorded file. snom/snomONE/recordings 4. Click Save. The file will be placed into the directory.
Page 150 Deploying the snom ONE IP Telephone System Note 2: Numbers in blue indicate account numbers. Greetings can be viewed from either the Windows environment (Figure 8-8) or the command prompt (Fig- ure 8-9). Figure 8-8. Viewing Greetings from the Windows Environment...
Page 151: Hunt Groups
hapter HUNT GROUPS A hunt group is a set of extension numbers that are embedded inside a single virtual extension. Incoming calls are rotated through the pool of extensions until someone answers and the caller is connected. (Cell phones can also be configured to be included in calls made to a hunt group.) Final stage Figure 9-1.
Page 152: How The Hunt Group Works
Once a caller has reached a hunt group, the system begins searching for an extension that will answer the call. Hunt groups can be configured with one to three stages of extensions, and each stage can consist of any number of extensions. When looking for an extension, the system begins with stage 1. Once the ring stage...
Page 153: Setting Up A Hunt Group
Group name (calling party) option in the header to en- sure that it will fit into the display of the phone. This field also distinguishes one hunt group from another hunt group on the Accounts page.
Page 154: Ring Stages
Behavior settings allow you to control numerous account behaviors. You can choose a ring melody, a display header, and music on hold source. You can also enter a safety net phone number that will be used if no one picks up a call. Other settings are here as well.
Page 155 — Group name (calling party): This mode displays both the group name and the calling party. — Calling party (CMC): The calling party’s client matter code will appear in the display, if one is available. The CMC identifies the customer and is used to expedite billing in offices that bill their clients for phone calls.
Page 156: Night Service
Internal extensions and external numbers are acceptable. Note: You may specify more than one night service flag (separated by a space). The first service flag account will correspond to the first night service number, and the second service flag account will correspond to the second night service number, etc.
Page 157: Agent Groups
hapter AGENT GROUPS An agent group, also known as automatic call distribution, is a system that routes incoming calls to a specific group of agents. Before connecting to an agent, callers are placed inside a queue, allowing agents to deal with incoming calls without losing other callers to busy signals or unanswered phones.
Page 158: How The Agent Group Works
How the Agent Group Works A caller reaches an agent group in one of two ways: either by calling the agent group directly or by calling a company’s auto attendant. When agent groups branch off the auto attendant, callers must press the number that corresponds with their choice.
Page 159: The Message-Music Cycle
Once an agent is available, the system automatically takes the next call out of the queue, rings the agents, and puts the call into ringback state. Within any one agent group, only one call at a time can be in ringback state, regardless of the number of agents that are available.
Page 160: Setting Up An Agent Group Account
Choose a short name if you plan to use the Group name (calling party) option in the From header to ensure that it will fit into the display of the phone. This field also distinguishes one agent group from another agent group on the Accounts page.
Page 161: Behavior
For small agent groups, a value of is recom- mended. Ring Melody: It is important to set the ring melody so that the phone knows which one to play ■ and so that agents will be able to distinguish regular calls from agent group calls.
Page 162 Deploying the snom ONE IP Telephone System Add to the address book and keep it for . . . : Automatically adding a caller’s phone number into ■ the address book allows the caller, when calling again, to be routed to the same agent.
Page 163 Fred Feuerstein <ff@domain.com> this field (e.g., ). Only one email address is allowed. It you want to send the CDR email immediately, click the Try button, rather than waiting until midnight. Keep in mind that this is just a link, and you may have to save your list before clicking the link.
Page 164 Deploying the snom ONE IP Telephone System time the caller spent talking. Information about the agents is also shown in the report (e.g., agents in the queue and number of calls handled by each agent). The queue manager can access the infor- mation from the Status tab (user account).
Page 165: Connecting Caller To Agent
145). The agent listed first will be tried first. If that agent is busy, then the system will jump to the second one and so Ring stage duration (secs): At regular intervals, the system checks agent availability and de- ■...
Page 166: Preventing Lengthy Periods In Ringback Or Queue
Deploying the snom ONE IP Telephone System Preventing Lengthy Periods in Ringback or Queue Calls That Approach the Head of the Queue This section allows you to establish timeout settings that will determine the length of time a call is kept in queue or ringback state in a given situation.
Page 167 The system will not do this automatically. The place to do this is through the greetings that are delivered by the system (using the *98 star code feature). One greeting or several greetings can be used to inform the caller that this additional option is available. In...
Page 168: Night Service
The SOAP interface allows you to use external logic to control the queue behavior. See Chapter 13 for a sample SOAP message. http://www.snom.com/soap/pbx/queuestatus Queue Status URL: ■ Logging In and Out Agent group members can use one of two methods (buttons or star codes) when logging in and out of agent groups.
Page 169: Method 1: Buttons
Log out Agents who are members of numerous agent groups and who need to log out of one agent group before log- ging into another can do so by entering the agent group number after the star code. Using the sample shown below, the agent will be logged out of agent group 666 and will retain logged-in status for all other agent groups.
Page 170: Monitoring Agent Groups
Deploying the snom ONE IP Telephone System Note: Agent group calls can be forwarded to an agent’s cell phone. See When calling the extension in an agent group on page 307. Monitoring Agent Groups Agent groups can be monitored from the web interface through the buttons on the phone and from the WAC (Web-based Attendant Console).
Page 171 Chapter 10: Agent Groups 3. Click Agents to view agent-related information. 4. Click Call Log to view the call history of the agent group. 5. Click Email to send an email to a connected agent.
Page 172: Monitoring Using Buttons On Phone
Deploying the snom ONE IP Telephone System Monitoring Using Buttons on Phone An agent group can be monitored through LEDs on the phone. To do this, create a button profile with Agent Group as the button type and the agent group number as the parameter. To monitor numerous agent groups from the phone, assign numerous buttons as Agent Group and enter the appropriate agent group into the corresponding parameter fields.
Page 173: Paging
Advanced IP phone systems allow even small offices to have a fully functioning paging system without using a standalone system. Paging can be thought of as a one-way audio session, as opposed to intercom’s two-way audio. Paging allows a single extension to communicate with a few people (unicast paging) or a potentially large group of people (multicast paging).
Page 174: Multicast Paging
A multicast page is essentially a predefined broadcast address that phones or SIP user agents are programmed to listen to. Each phone can be configured to listen to as many as 10 different multicast IP addresses. The advantage of a multicast page is that only one SIP session is established between the originator and the system (Figure 11-2).
Page 175 Chapter 11: Paging 2. In the Account Name field, enter an extension number and/or alias, i.e., a DID number. When entering an alias in addition to an extension number, use the following syntax: 515/9781234567 515 9781234567 Note: If you use a space instead of a slash ( ), you will create two separate accounts that will be unrelated to each other.
Page 176 Deploying the snom ONE IP Telephone System all devices configured to listen on the same multicast IP address will go into paging mode as soon as they receive RTP traffic on that port. Not all phones support multicast paging. Phones that do have this support must be config- ured through the phone’s web interface before they can be part of a multicast paging group...
Page 177: Assigning Multicast Ip Addresses To Ip Phones
Assigning Multicast IP Addresses to IP Phones Before a phone can be part of a multicast paging group, a phone must have a multicast IP address that matches the snom ONE multicast IP address. This requires configuring the multicast settings for each phone.
Page 178 Deploying the snom ONE IP Telephone System...
Page 179: Conferencing
A conference room or conference server is normally an expensive add-on with traditional phone systems. With the snom ONE telephone system, you can have your own conference rooms within your own system. Several types of conferencing can be used on the system: scheduled and ad hoc. The scheduled conference allows users to plan in advance for the conference and the ad hoc conference, as its name suggests, allows us- ers to pull together a conference at a moment’s notice.
Page 180: Scheduled Conferences
The access code ensures that no unauthorized users can join the conference. Before users can schedule conferences, the administrator must set up at least one confer- ence account. After the account has been created, users can schedule conferences by going to Lists > Confer- ences (available only from the user login).
Page 181 Choose a name that will help users differentiate one conference room from the next: The conference name will also be displayed next to the account number on the Accounts page: Mode: Be sure to choose Scheduled conference.
Page 182: Scheduling A New Conference
Deploying the snom ONE IP Telephone System Scheduling a New Conference Once a conference account has been created, users can create conferences from their own accounts: Click Conferences from the Lists tab, as shown below: 2. Populate the form using the following information: Name: This field allows participants to know the subject of the conference.
Page 183: Modifying Scheduled Conferences
(*8). Exiting conference ■ — Continue the conference: Participants will be able to communicate with one another after the moderator has exited the conference. (The conference will not be deleted until after 24 hours.) —...
Page 184: Ad Hoc Conferences
Deploying the snom ONE IP Telephone System Table 12-2. Conference Star Codes Star Code Description Send participant list Mute your device Unmute your device Mute other participants Unmute other participants Hang up the conference 1. Requires moderator privilege. Note: As with the other conference star codes, *0 (send participant list) must be executed during the con- ference.
Page 185: Calling Into An Ad Hoc Conference
If the designated extension is 665, then all parties who enter 665 from their extension phones will be joined to the same call. Participants will be required to enter an access code if one has been set; oth- erwise, they will be joined directly into the conference room. Any number of participants can join the call.
Page 186 Deploying the snom ONE IP Telephone System...
Page 187: Ivr Node
hapter IVR NODE At the most basic level, the interactive voice response (IVR) system allows callers to reach their destina- tion by making touch-tone entries through the phone keypad, rather than going through the operator. An IVR node can also be configured for complex tasks so that callers can enter account numbers and pay bills through an external application server.
Page 188: How The Ivr Node Works
Deploying the snom ONE IP Telephone System Feature Functionality Benefit Announcement The system greets every caller with Information can be delivered before the caller is before ringing a uniform message prior to con- connected. This prepares the caller, expedites call necting the call: flow, and makes your initial greeting count.
Page 189: Setting Up An Ivr Node Account
An IVR node can also be used to define dialog that will be used to process calls. In this case, each node plays one prompt and asks a specific question to the caller. The first prompt may ask the caller what language is preferred and then dispatch the caller into two different node systems for two different languages.
Page 190: Identity
Deploying the snom ONE IP Telephone System Identity Account Number(s): This field takes an extension number(s) and/or DID number(s). The number ■ of DIDs that can be entered into this field is unlimited. Name: This field allows you to create an alias so that you can quickly distinguish the IVR nodes ■...
Page 191: Recording Messages
From-based routing match list: This field requires syntax similar to the DTMF field. ■ To-based routing match list: This field is used when the snom ONE opens the IVR node. Use the ■ same format as in DTMF Match List above. If there is a match with the...
Page 192: Upload A Wav File
Deploying the snom ONE IP Telephone System Upload a WAV File WAV files allow you to record and edit your message before loading it into the system. They also allow you to use professional IVR dialogs. From the IVR Node settings: Click the Browse button and upload the file (WAV files should be 8 kHz Mono, 16 bit).
Page 193 Chapter 13: IVR Node xmlns:sns=” http://www.snomone.com/soap/pbx”> <env:Body> <sns:IVRInput> <CallID>3525234@snomone.com</CallID> <Output>123</Output> <From>Fred Feuerstein <sip:ff@test.com></From> <To>Tom Test <sip:tt@test.com></To> </sns:IVRInput> </env:Body> </env:Envelope> In the snomone namespace, the record CDR indicates that a CDR shall be transmitted. The CDR may have the following attributes: CallID : This attribute contains the call-ID of the call and makes it possible to put the IVR input ■...
Page 194 Deploying the snom ONE IP Telephone System function start_element($parser, $name, $attrs) { global $elem; $elem=$name; function end_element($parser, $name) { function xml_data($parser, $data) { global $elem, $from_user, $to_user, $from, $to, $duration, $start, $callid, $output; if($elem==”CALLID”) $callid .= $data; else if($elem==”OUTPUT”) $output .= $data;...
Page 195: Calling Card Account
PIN code. The call will reflect the of- fice’s caller-ID and will appear in the user’s call log. snom ONE ext 231 The calling card account can be used in three different modes: DISA —The user calls into the account and authenticates himself by entering his extension number...
Page 196: Setting Up A Calling Card Account
Deploying the snom ONE IP Telephone System Setting up a Calling Card Account This section provides instructions for creating and configuring a calling card account: From the Accounts tab, click Create and select Calling Card: 2. In the Account Name field, enter an extension number and/or alias, i.e., a DID number. When...
Page 197: Identity
Important: Before users can use the calling card in pre-paid mode, Callback must be set to off...
Page 198 Deploying the snom ONE IP Telephone System — System dials automatically (ROW): The system will interpret numbers according to a “rest of world” scheme, which means that international numbers start with 00 and national numbers start with 0 (see Table 3-2 for more information on ROW).
Page 199: Pre-Pay Feature
hapter PRE-PAY FEATURE The pre-pay feature allows the administrator to create customized rate tables for multiple pricing strategies. Calls are calculated based on call duration, destination, and the rates provided in the tables. The pre-pay fea- ture can be configured so that users can access it using the extension account, the Personal Virtual Assistant (available from the cell phone), or the calling card account (PIN access).
Page 200 Deploying the snom ONE IP Telephone System 2. Click List to view a list of the trunks 3. Click the Edit icon for the trunk you just created: 4. Click Rates. A sample rates table is displayed: The rates table follows standard CSV format. All fields are separated by commas: Greece,01130,0.10...
Page 201: Assigning A Dollar Amount To An Extension
Chapter 15: Pre-Pay Feature 5. Enter your own calling rates in the space under the sample rates table. Important: In the event a blank field sits between two other fields (e.g., you’re requiring a connec- tion fee but will not be changing the Duration of Unit default, as shown in the table below), you will need to make provision for this empty space in your CSV syntax.
Page 202: Personal Virtual Assistant
Deploying the snom ONE IP Telephone System Personal Virtual Assistant With this method, users can call into the Personal Virtual Assistant from their cell phone to access their pre- paid account (the cell phone must be configured to the user’s account). Instructions are as follows: Call into the main number from the cell phone.
Page 203: Email
If you already have an SMTP server set up, you can configure it to the system using the following instructions. If you do not have one set up, you can set one up through Gmail for free or ask your email administrator.
Page 204: Domain-Specific Smtp Settings
Deploying the snom ONE IP Telephone System 2. Populate the form using the following information: From Address: This field will be used by the system when it sends emails (it is the From ■ voicemail@your-company.com pbxautomailer@ dress). You can use names like your-company.com...
Page 205 Chapter 16: Email Note: Figure 16-1 shows the standard email settings that are available to the user, but administrators can prevent the user from seeing the Send a mailbox message and After sending a message settings (see the email control settings on page 48).
Page 206 Deploying the snom ONE IP Telephone System Send email at the end of every call: When this setting is activated, the system sends the user an ■ email for all calls (see below). This feature is useful for keeping track of a group sales extension, a telemarketing campaign, or calls made to a new employee’s extension.
Page 207: Receiving Email Notifications From The System
Chapter 16: Email Receiving Email Notifications from the System Types of Email Notifications The system can be configured to notify a list of administrator accounts when an important system event occurs. The types of email notifications are presented in Figure 16-2 and are located in Admin >...
Page 208: Cdrs To Email
All types of CDRs can be exported to email. Depending upon which type of information you would like to receive, you will need to configure the respective setting on the snom ONE. Important: Before you can receive any type of CDR, the SMTP server settings must be configured (go to...
Page 209: Cdrs For Trunk Activity
Chapter 16: Email CDRs for Trunk Activity If you want to receive a nightly email report on trunk activity, add your email address to the Midnight Events setting. Navigate to Domain. Click the domain. Click Settings. Scroll down to Midnight Events and enter your email address into the Send daily CDR report to setting.
Page 210: Cdrs For All Extensions On Your Domain
Depending upon which phone model is being used, the Record button may be located in different places on the phone. On the snom 360, the Record button has a white circle on it. When the button is pressed, the...
Page 211: Blacklist Activity To Email
Chapter 16: Email phone display will show a solid black circle to indicate that the call is being recorded. The recorded call will be displayed in the extension user’s log under List > Mailbox. The user can click the audio icon to play the recording as shown below: Blacklist Activity to Email System-Initiated...
Page 212 Deploying the snom ONE IP Telephone System...
Page 213: Audio And Greetings
hapter AUDIO AND GREETINGS Greetings Greetings are prerecorded, customized messages that can be used with numerous account types. Users can create greetings for their personal voicemail account, and administrators can create greetings for auto atten- dant, agent group, and IVR node accounts. Greetings are created with the Record New Greeting (*98) star recordings code and are stored in the folder.
Page 214: Auto Attendant Greetings
Deploying the snom ONE IP Telephone System Activating a Personal Greeting Administrators: Once greetings have been recorded for an extension, administrators have the option to up- load them from the Mailbox tab of the user’s account. Users: Once greetings have been recorded, a user can activate a greeting by using the following steps: Enter extension number to access voice mailbox.
Page 215 Chapter 17: Audio and Greetings Naming Conventions Auto attendant greetings (when created with *98) are named according to the system’s syntax rules. Its nam- ing system is based on the greeting number that was recorded and the account type (personal, auto atten- dant, agent group, etc.) for which the greeting was recorded.
Page 216: Agent Group Greetings
Deploying the snom ONE IP Telephone System To delete auto attendant greetings, navigate to the location where the greetings are stored on the system, and delete them. Agent Group Greetings Agent group greetings can be used to provide callers with information about a company or to provide ad- ditional options for the caller (see “Mapping Telephone Keypad Numbers with Extensions”...
Page 217: Recorded Phone Calls
User-Initiated Recordings User-initiated recordings are generated when the user either presses the Record button on an IP phone (e.g., snom 320 and 360) or dials the Record (*93) star code. The recordings will be placed into the record-...
Page 218: System-Initiated Recordings
Deploying the snom ONE IP Telephone System ings folder. Anyone with access to the computer running snom ONE can listen to, copy, save, and forward the conversations. The recordings will be sent to the user’s email address. Users can listen to them by clicking the paper clip.
Page 219 Chapter 17: Audio and Greetings snomONE/re- Using the string shown above (which is the system default), the directory location would be cordings/pbx.company.com/73 , and the file name could be 20100907-165929-i-50.wav There’s a lot of flexibility with regard to where the system can place recordings and the file names that it as- signs.
Page 220: Notes
Audio Prompts The voicemail and IVR systems of the snom ONE rely on audio prompts for their menu prompts. By de- fault, these prompts are in U.S.-English and are located in the audio_ * directory.
Page 221: Uploading New Languages
Default IVR Language and Default Tone Language dropdown lists: Uploading New Languages Audio prompts in many languages can be downloaded from snom ONE’s web site. Following is a list of available languages: Table 17-5. Country Identifier Codes...
Page 222: Customized Ringtones
Ring Melody dropdown in the hunt group and agent group ac- count. To create custom ringtones, you will need to come up with your own ringtones and link them to the snom ONE by modifying the ringtones.xml...
Page 223 <vendor type=”alert-info”><http://127.0.0.1/Bellcore-dr4></ven- dor> 4. To create a custom ringtone for the snom ONE, create a new vendor element using one of the other vendor elements (copy and paste it).
Page 224 Deploying the snom ONE IP Telephone System 8. Restart the system. 9. The new tone will be listed in the Ring Melody dropdown:...
Page 225: Buttons
hapter BUTTONS Buttons simplify the workflow in almost any environment and are ideal for all types of users. Once a button has been configured to the user’s extension, the user can press the button to execute whatever function has been configured to it. Button functionality includes many helpful options, including agent log in/log out and queue monitoring.
Page 226 If the agent needs to log in and out of all agent groups at the same time ■ (or if the agent belongs to only one agent group), use a single Agent If you enter a spe- login/logout button and do not specify a parameter (leave it blank).
Page 227: Creating A Button Profile
In this case, a group mailbox must be cre- ated, and the phones must subscribe to MWI for the extension of the group- mail account.
Page 228 . If is used for one of the buttons (for a phone that does not have a DND button), replace the numerical reference with The values assigned to the buttons correspond with the positioning shown below: Figure 18-1.
Page 229: Csv Method
“Point-and-Click” method (previous pages). The result will be one button profile with only one button set. 2. Click the here link as shown above to switch to a text-based editing window. A text-based editing window with one button record will be displayed: 3.
Page 230: Assigning Button Profiles To Users
Deploying the snom ONE IP Telephone System Button Type CSV Syntax park Park orbit Do not disturb login Agent login/logout redirect Redirect Busy lamp field (BLF) queue Agent group 4. When finished, click Save. Assigning Button Profiles to Users A button profile can be assigned to a single user or to multiple users. The following procedures outline both scenarios.
Page 231: Massive Update Of Profiles
The buttons feature can be used to emulate a key system when combined with a snom phone. Although there are no physical cables to connect the snom ONE telephone system with the outside world, as with a TDM-based PBX, it is still possible to emulate the behavior of TDM-based PBXs and still have “CO-lines.”...
Page 232: Setting Up A Key System
Deploying the snom ONE IP Telephone System CO-lines are associated with trunks, and each trunk may have several. CO-lines are listed in the account list because they share the same namespace. Once configured, the buttons will have the following behavior: When a corresponding extension receives a call, the button will blink (by pressing the button, the ■...
Page 233: Multiple Identities And Button Profiles
Multiple identities on a single phone (shown below) can be problematic with button profiles because a phone can utilize only one button profile at a time. When multiple identities are involved, the tendency is to configure a button profile that includes a private line for each user, which is okay to do. The problem occurs...
Page 234 Deploying the snom ONE IP Telephone System when a new button profile gets uploaded after the first one and overrides the private line settings. In these cases, it may be wiser to manually configure a button profile on the handset instead of using plug and play.
Page 235: Plug And Play
PLUG AND PLAY The goal of plug and play is for the phone to be able to find the snom ONE and download its configura- tion settings with little or no configuration. In many cases, this can be done without actually touching the phone.
Page 236: Plug And Play Checklist
Deploying the snom ONE IP Telephone System snom ONE looks in its ARP cache and is 100% sure who it is talking to, so users on the LAN will not be required to authenticate.) Instructions using this method begin on page 224.
Page 237: Configuring The Domain Settings
Chapter 19: Plug and Play 4. If you have snom 300 phones and would like to customize them, you have the option to statically configure buttons 3 through 6 (see Figure 19-2). 5. For firmware, select the version you would like to have in the phone. If the firmware in the phone is newer than what is shown on the screen, you will need to get a matching version of software from snom’s website;...
Page 238: Creating An Authentication Password
Once you have made the necessary changes, place the modified version into the html direc- tory. When snom ONE looks for the file, it will look in that directory before looking on the server. Creating an Authentication Password The authentication password setting allows administrators to provision phones and log into a phone’s web interface remotely.
Page 239: Setting Up The Domain Address Book
WAN-based extensions for plug and play, you can skip this section. The MAC address is the phone’s unique hardware number and is used to identify the phone to snom ONE. It is a 12-digit hexadecimal number located on the back of the phone and is written in the following format:...
Page 240: Performing Plug And Play
This method can be used only if you have a DHCP server that supports option 66. You do not need to rely on multicast. Once you have set option 66 with the IP address of snom ONE, the DHCP server will be able to tell the phone where snom ONE is.
Page 241: Sip Subscribe (Multicast)
SIP SUBSCRIBE (Multicast) This method is limited to environments with a single snom ONE. It is generally used in LANs, as multicast typically does not traverse routers. It requires configuration on the phone and is not supported if the phone is connected remotely (over the public Internet).
Page 242: Mass Deployment
Mass deployment (also known as “redirection service”) allows for touch-free, WAN-based plug and play and is ideal for a large deployment of phones. To use this service, you will need to contact snom and have the MAC addresses of your phones provisioned to a setting URL that reflects your snom ONE.
Page 243 1. Power up the phone. 2. Log in to the web interface of the snom phone by entering the phone’s IP address into a web brows- 3. Click Advanced from the left-hand section of the screen. 4. Click the QoS/Security tab.
Page 244 14. Reboot the phone when prompted. 15. Click Yes to confirm that you want to reboot. During the reboot process, the phone will contact the snom ONE and request the snom820.htm file with the authentication information that was set during Steps 6 and 7. The system will verify the authentication information and, if valid, will generate and send the requested file.
Page 245: Resetting The Phone
1. Go to Settings > Maintenance > Reset Values. Click the confirm button. 0000 2. Enter the password (snom’s default password is 3. Press the confirm button to reboot the phone. (The phone will update its default configuration.) Using the Phone From the phone, enter **#*.
Page 246: Registering Numerous Extensions To One Phone
Deploying the snom ONE IP Telephone System 4. Click Reboot. Registering Numerous Extensions to One Phone Registering multiple identities to a single phone can be useful in cases when the phone is being used to answer calls for numerous companies. Each identity has its own extension, and the extension can be config- ured to a system that is either local or remote.
Page 247: Overriding Plug And Play Defaults
This section shows you how to manually change plug and play settings using the Admin > PnP tab. The only changes that you can make using this method are the transport layer, the password of the snom phone, some of the buttons on the snom 300 phone, and the firmware versions. Once the changes have been made and the phone has been rebooted, the phone will request the configuration files from the server and the changes will take effect.
Page 248 To make any of the custom settings shown in Figure 19-5(A), use the following steps: Go to Admin > Settings > PnP and scroll down to the snom settings. 2. Make the necessary configurations. (The button settings are for snom 300 phones only.) 3. Click Save.
Page 249: Changing Default Settings Using A Customized Xml File
Figure 19-6. Directory Structure of Extensions on Domain The files are generated from templates that exist in the binary of snom ONE and are inaccessible. When the phone boots up, it looks at the files in the generated directory and will take on the settings that are repre- sented by those files.
Page 250 (Step 4 below), the phone will request its configuration files. At this point, snom ONE will process the plug and play settings and compile them into generated files, which are received by the phone once it reboots. Extensions 1.
Page 251 Figure 19-8 shows one of the template files ( ) that the system uses to create one of the generated files. Though you cannot access this file, it is important to notice the structural syntax that is used in the file because the customized file will need to follow a similar structure.
Page 252 Deploying the snom ONE IP Telephone System snom_3xx_phone.xml Figure 19-9 shows an example of the generated version of Figure 19-9. Sample of a Generated File (snom_3xx_phone.xml)
Page 253 Before you can create a customized file, you need to know the XML element tags that have been reserved for each setting, as well as the parameters that can be used. You can find this information on the snom web site (Figure 19-10).
Page 254 Deploying the snom ONE IP Telephone System When the settings are viewed in XML, the following document tree is displayed: Figure 19-11. Document Tree of snom Phone Settings Creating a Customized File 1. Create a directory named tftp on the system:...
Page 255: Troubleshooting
Turn off the SIP awareness SIP-aware routers are altering the mes- on the routers or replace the sages. routers. Multiple snom ONE instances are run- This could inadvertently affect Verify who is responding ning on the same network. the multicast SUBSCRIBE- to the phone’s requests by...
Page 256 ONE. 2. Modify the PnP tab of the snom ONE with the firm- ware version that was downloaded. 3. Rename it snomxxx.bin 4. Reboot the phone.
Page 257: Music On Hold
RTP stream. These sources serve different purposes and are detailed below. The sources can be used in parallel in different locations on the same system. Files: The system can use one or more files for MoH. These files are read by the system on demand ■...
Page 258: Setting Up Music On Hold
Deploying the snom ONE IP Telephone System Setting up Music on Hold MoH sources are available to all domains on the system, so setup is done from the administrator level. Navigate to Admin > Settings > MoH. 2. Populate the fields using the following information: Name: Assign a name to the MoH source (this name will appear in the Available Sources list at ■...
Page 259: Editing Moh Sources
Chapter 20: Music on Hold 4. To verify that the source has been added on the domain level, navigate to Domain > Settings. You should see the newly added source in the Music on Hold Source dropdown: Once MoH has been created, it can be selected for use on a domain level within both the agent group and hunt group accounts.
Page 260 Deploying the snom ONE IP Telephone System 4. Click File > Load Audio CD Track(s). 5. Select the track you want to use and click Load. The following screen will be displayed while the track is loading: When the file has finished loading, you will see the following screen:...
Page 261: Configuring Paging/Music On Hold
Configuring Paging/Music on Hold The snom ONE Paging/Music on Hold application allows you to use a PC to stream audio from a music on hold input and play back audio on a paging output. This section details the installation and basic configura- tion of the application.
Page 262: Setting Up Paging
Deploying the snom ONE IP Telephone System Setting up Paging Creating a Multicast Paging Account This section provides instructions for creating a multicast paging account on the system. From the Accounts tab, click Create and select Paging from the dropdown.
Page 263 Assigning Multicast IP Addresses to IP Phones To be part of a multicast paging group, a phone must have a multicast IP address that matches the snom ONE multicast IP address. To do this, you will need to configure the multicast settings for each phone.
Page 264: Configuring Music On Hold
Deploying the snom ONE IP Telephone System The phone can now pick up the RTP stream and begin playing it. Configuring Music on Hold This section shows you how to create the new RTP stream-based MoH source. From the domain, click Admin > Settings > MoH, as shown below.
Page 265: Xml Configuration File
Chapter 20: Music on Hold XML Configuration File The configuration options in the XML file are set in the parameter:value format. Available parameters and sample values are shown below: pagmoh.xml Table 20-1. Available Options in Parameter Function Example 5000 page Defines the port where to listen for RTP traffic.
Page 266 Deploying the snom ONE IP Telephone System...
Page 267: Call Detail Records (Cdrs)
26). The storage duration can be expressed in seconds, minutes, hours, or days. The CDR listing size setting dictates how many CDRs are permitted on the page (default is 30). This field is used to prevent a user from getting too many CDRs displayed at any one time.
Page 268: Extension" Cdrs
Deploying the snom ONE IP Telephone System “Extension” CDRs CDRs that are placed into the cdre directory contain extension-related information, such as caller-ID, From headers, and details as to whether the call was a missed call. All possible fields are listed in the...
Page 269: Trunk" Cdrs
Chapter 21: Call Detail Records (CDRs) XML Tag Definition Extension account that connected (e.g., Agent) Descriptive From header Descriptive header Domain in which the call took place Language of the call Time when call started Duration that the call waited Duration of ringing Duration of two-way audio Duration of hold period...
Page 270: Cdrs For Third-Party Software Vendors
Deploying the snom ONE IP Telephone System Figure 21-3 shows trunk-related information wrapped inside XML start and end tags. These tags correspond to the XML tags in the above table. Figure 21-3. XML Output for CDRs—Trunk CDRs for Third-Party Software Vendors CDRs can be exported to third-party software vendors for a wide range of purposes.
Page 271: Cdr To Csv
Chapter 21: Call Detail Records (CDRs) Field Values TrunkName PSTNGateway TrunkID Domain company.com LocalTime 20100310105708 Start 20100310095708 Connect 20100310095710 DurationHHMMSS 0:00:10 DurationSec 20100310095720 IPAdr udp:192.168.0.248:5060 Record_Location Indicates the location of the file CDR to CSV To generate CDR files on the local disk in CSV format, use file:disk in the CDR URL setting and specify a string that will be representative of both the filename and the contents of the CDR.
Page 272: Cdr To Email
Several commercial tools are available for collecting CDR information through simple TCP-based commu- nication. Each CDR is sent in one line of ASCII text terminated by a CRLF pair over a TCP-based commu- nication link. To differentiate the destination from a SOAP CDR, use in the CDR URL setting in front of the IP address and the port (the fields are separated by a colon).
Page 273 For example, if you want to change the CDR format of a system running on a localhost, you would enter something like this (replace localhost with your snom ONE address): http://localhost/reg_status.htm?save=save&cdr_format=$w$5d$25m$2o$20F$20T$ 20R$20r$15c$20f$15v You can also use the web interface to make changes to the...
Page 274: Cdr To Soap/Xml
Deploying the snom ONE IP Telephone System CDR to SOAP/XML The CDR SOAP mechanism can communicate with an external web server. The system starts a SOAP call to a URL specified in the system each time a call is completed. The third-party web script which receives the SOAP call will then parse the XML packet and file the data in the required place.
Page 275: Part Iii-The User Interface
Part III The User Interface...
Page 276 Part III—The User Interface...
Page 277: Web Interface
WEB INTERFACE The web interface is one of the most important differences when comparing modern-day VoIP systems with legacy IP-based systems. The web interface allows users to integrate their cell phone and configure other set- tings related to their account. Before users can access the web interface, they will need the URL of the system and a user name and password.
Page 278: Extension Settings
Deploying the snom ONE IP Telephone System These tabs are detailed below: The Settings tab allows users to change their password, set up redirection, and control their mail- ■ box. Voicemail, buttons, and instant message settings are also located here.
Page 279 Users should not change this password, as it will interfere with access to other registered SIP devices (e.g., soft phone). Web Password: This password is used to access the snom ONE web interface. ■ Note: Use a combination of letters and digits and even a symbol to ensure password security. After you’ve entered a new password, the current HTTP session will stay valid until your next login.
Page 280 ■ they would like to monitor from the WAC. When using the WAC, this setting enables users to join a conference room (the conference room must be included as one of the extensions that will be monitored). Permissions to monitor the account: This setting allows users to specify the extensions that are ■...
Page 281: Address Book
Chapter 22: Web Interface extensions have been grouped with certain agent groups and hunt groups, as it will prevent the wrong calls from being picked up. If a star (*) is entered into this field, the system will have no preference list to draw from and will require a park orbit number after the *87 (see page 283 more information on Call Pickup).
Page 282 Deploying the snom ONE IP Telephone System Do not disturb: This setting allows users to tell the system to leave their phone silent for all calls, ■ both internal and external, and even calls from the hunt group. Only extensions with permission to override DND will be able to call the extension.
Page 283: Mailbox Settings
Maximum number of messages: This setting allows the user to specify the maximum number of ■ voicemail messages that should be stored at any one time. If the maximum has been reached and a caller wants to leave a new voicemail message, the system will attempt to delete a saved message. If space is still unavailable, the system will inform the caller that the mailbox is full.
Page 284: Email Settings
Deploying the snom ONE IP Telephone System own phone (see page 297 for instructions on accessing voicemail from an outside phone). Dialing directly into the shared mailbox allows users to hear messages that were called into the shared exten- sion only (i.e., the messages will not be mixed with the user’s own voicemail messages). Users will need the PIN of the shared mailbox when accessing it directly.
Page 285 Chapter 22: Web Interface The following information details the settings that can be set from the user’s Email link: Email Address (e.g. abc@company.com): This feature allows users to integrate their email ac- ■ count with their extension account. Voicemail messages will be sent to the user’s email account according to the settings chosen below (a semicolon is required when entering multiple email ad- dresses into this field).
Page 286: Instant Message
DND status, changing the registration status, etc.). Instant Message The Instant Message feature allows users to display an instant message (IM) on the screen of snom phones. Although snom phones cannot generate IMs, they can display them. This feature comes in handy when users need to pass information along to someone during a conference call, for example.
Page 287: Call Lists
Chapter 22: Web Interface 1. Enter the extension numbers into the Destination field. 2. Enter your message into the Message field. 3. Click Create. 4. Note: When multiple destinations are used, a space should be used as a separator (e.g., 102 103 ).
Page 288: Call Log
Deploying the snom ONE IP Telephone System The following icons are associated with the Missed Calls page: One-click dialing: Click to initiate a callback to the party who called you. The call will be charged to the user's extension. Address book: Click to save the contact in the personal address book.
Page 289: Contacts
Chapter 22: Web Interface Address book: Allows users to add contacts to the personal address book: Contacts Address books allow users to see who’s calling. They can also be used to expedite billing (when a CMC is used) and to speed-dial contacts. The system offers two types of address books: a personal address book, which is private for the extension, and a domain address book.
Page 290 3. If you add a contact whose information is incomplete, click the account number and populate the necessary fields: First Name: Enter the first name of the contact if one was not available. ■ Last Name: Enter the last name of the contact if one was not available.
Page 291: Domain Address Book
Chapter 22: Web Interface block that call. Otherwise, the system will ask the person to leave his name before calling your extension. Black list contacts are not allowed to camp on an extension. 4. Enter comments that are relevant to the contact. Click Create.
Page 292: Upload Domain Address Book To Phone
Deploying the snom ONE IP Telephone System The address book can also be used to indicate which DID number has been dialed. If the user adds an ad- dress book entry that matches a specific DID, the system will add the display name to the caller-ID and the phone can then display the text associated with the caller-ID.
Page 293 Chapter 22: Web Interface Hot Desking at: If the extension has redirected all calls (including calls from hunt groups and ■ agent groups) to another location, the destination is shown in this line. Call forward all destination: If the Call forward all calls setting has been set, the destination is ■...
Page 294 Deploying the snom ONE IP Telephone System...
Page 295: Star Codes
Star codes are two-digit numbers prefixed with a star (*) and are used to instruct the system. Each star code maps directly to an action of the system, allowing users to quickly access snom ONE features, such as Do Not Disturb (DND), call forwarding, and a host of other features. All users across the domain have access to the same set of star codes and can access the list by logging into their account and going to Lists >...
Page 296: Basic Star Codes
4. These codes are used during a conversation; the tones are audible and can be heard by the connected party. 5. These star codes must be identical to one another (e.g. *64/*64 and *86/*86) when conﬁgurated as a toggle button.
Page 297: Call Return (*69)
272) can also be used to dial the last number received. Intercom (*90) The Intercom feature mimics the old secretary-boss intercom systems and can be thought of as a one-part page with two-way audio. Intercom is used to communicate with one other person. The other party must have a separate extension number, as the Intercom feature will not work between two phones that are regis- tered to the same extension.
Page 298: Transfer A Call Directly To Someone's Voicemail
Press the Transfer button on your phone, or press Hold and dial *77. Enter the extension number (or phone number) of the recipient. A blind transfer offers no confirmation of call connectivity. If the number is busy or does not exist or no one picks up, the user will not be notified.
Page 299: Call Park (*85) And Call Park Retrieve (*86)
Chapter 23: Star Codes Call Park (*85) and Call Park Retrieve (*86) Call Park allows the user to send a caller to someone whose whereabouts (within paging proximity) are not known. The receiving party uses Call Park Retrieve (*86) to retrieve the call. Scenario: A call comes in for Diane, but you do not know where she it, so you put the customer on hold, dial , and press the confirm button.
Page 300: Conferencing
Deploying the snom ONE IP Telephone System Note: When compared to Call Park Retrieve, Call Pickup is associated with a sense of urgency (i.e., the user must pick up the ringing phone before the call goes to voicemail.) With Call Park Retrieve, the caller is already in the system, so there is no hurry.
Page 301: Conference (*53)
It also prevents called parties from looking the user up in an address book and initiating a callback. Calls from one extension to another extension will not be affected by *67. These calls will always reflect the caller- Dial *67 and press the confirm button on the telephone keypad.
Page 302: Reject Anonymous Calls (*88)
Deploying the snom ONE IP Telephone System Reject Anonymous Calls (*88) Users can reject anonymous calls by dialing *88 and pressing the confirm button. To re-allow anonymous calls, users must dial *89 and press the confirm button. Note: If a user has set Call Forward to busy condition...
Page 303: Call Forward All Calls (*71/*72)
Chapter 23: Star Codes The system will acknowledge that the Hot Desking feature is in service. Note: The system will automatically log a user out of a hot desk each night. Also, after activating the hot desk feature, users will be notified via email that a status change has been initiated on their extension.
Page 304: Call Forward On No Answer (*75/*76)
Deploying the snom ONE IP Telephone System The system will repeat the number and then hang up. If you want to change the forwarding number, just call *73 again. To deactivate, dial *74. The announcement will indicate that call forwarding has been turned off.
Page 305: Set Night Mode For Domain Accounts (*80)
Chapter 23: Star Codes DND takes precedence over Call Forwarding, as the latter cannot prevent hunt group calls from reaching the user’s extension. Set Night Mode for Domain Accounts (*80) This feature allows users to forward domain accounts (e.g., auto attendant, hunt group, etc.) to their own extension.
Page 306: Agent Log In/Log Out (*64/*65)
Call Teach Mode (*82) Call Teach mode allows a third party to call into an existing call and communicate with one of the partici- pants without the other person knowing. This is typically useful in a call center when a trainer wants to offer tips to a new agent without the customer knowing.
Page 307: Listen In (*83)
Chapter 23: Star Codes Listen In (*83) Listen In mode allows a third party to listen in without being detected. The two parties speaking to each other are not notified about the listen-in and have no idea that a third party is on the phone. Users cannot activate Listen In unless permission has been given by the domain administrator (page 109).
Page 308: Clean Up An Extension (*84)
Deploying the snom ONE IP Telephone System Clean up an Extension (*84) This feature allows users to quickly clean up an extension. This makes it ideal in hospitality environments, as it can be used to clear an extension of its messages after guests have checked out and before new ones arrive.
Page 309 Chapter 23: Star Codes...
Page 310 Deploying the snom ONE IP Telephone System...
Page 311: Voicemail
Setting up the Voicemail Account Changing the PIN Users will need a voicemail PIN in several areas of snom ONE (e.g., when accessing their voicemail from an outside phone, when using the calling card feature, and when hot desking). Domain administrators can set a...
Page 312: Record Your Name
Deploying the snom ONE IP Telephone System Record Your Name This recording will be used in announcements to all callers. Users can choose not to record their name. The system will recite the extension number instead. The user’s name can be recorded as follows: Dial your extension number (if messages are waiting, press * to skip to the main menu).
Page 313: Forwarding A Message
Chapter 24: Voicemail Users can access the voicemail system using any of the following methods: Listen to the messages from your main phone: Dial *97 and press the confirm button on the telephone keypad. (Another way to listen to your messages from your phone is by dialing your extension number.) Listen to the messages from your cell phone: Dial into the main number and press 3 once you hear the auto attendant.
Page 314: Composing A New Message
Select an action: Press 1 to move the message to a single mailbox. ■ Press 2 to copy the message to one or more mailboxes. Use a # sign to separate multiple mail- ■ boxes. Press 3 to mark as urgent.
Page 315: Hearing Your Personal Greetings
The system administrator must enable a direct dial number before users can “blindly” transfer a call to some- one else’s voicemail. The default for direct dial is “8.” Put the call on hold using the Hold button on your telephone keypad.
Page 316: Listen To Voicemail On Cell Phone
Deploying the snom ONE IP Telephone System The caller will be transferred to the extension’s voicemail. Because the caller will bypass the voicemail time- out, the caller will not hear any ringing. This method does not need to involve an outside caller. If you want to call a person’s mailbox directly, you can dial 8123 followed by the confirm button.
Page 317: Send Voicemail To Email Account (*95/*96)
Chapter 24: Voicemail Send Voicemail to Email Account (*95/*96) Users that have an email account on the system can have their voicemail forwarded to their email account. To activate this feature: Dial *95 and press the confirm button on the telephone keypad. Activate Deactivate Users can ask someone to leave a voicemail message to ensure that the forwarding works (the email is...
Page 318: Clear Message Waiting Indicator (*99)
Deploying the snom ONE IP Telephone System Users can listen to groupmail messages from their main phone by dialing *97 and pressing the confirm but- ton on the telephone keypad. Users can also listen to groupmail messages from an outside phone: Dial into the main number.
Page 319: Cell Phones
Note: Cell phone integration is different from having two phones registered to the same extension. Register- ing two phones to the same extension allows users to merely receive calls at one of two locations, while cell phone integration allows users to receive calls at any location, as well as be reached at numerous phone num- bers.
Page 320: Cost Savings
Deploying the snom ONE IP Telephone System Figure 25-1 illustrates the role that the cell phone plays in handling an incoming call. First, the cell phone must be configured to be included in all calls. Next, the call rings both phones. In the event the user decides not to answer the call, the caller can leave a message.
Page 321: Calling Card Account
Chapter 25: Cell Phones This feature is designed for users making calls from international destinations back to their home country. Neither the user nor the party receiving the call will be charged for the call. The call will be charged to the user’s extension.
Page 322: Configuring The Cell Phone
Deploying the snom ONE IP Telephone System Once the user’s cell phone has been configured to the extension, the user can use the calling card to make these calls from the cell phone. Although calls made using the calling card still consume the user’s cell phone minutes, the rates are less expensive than calling directly.
Page 323 When this setting is set to on, the system will call both the extension and the user’s cell phone. After one of the phones is answered, the PBX dials the contact. This setting is useful if the user is traveling and does not have access to the office phone.
Page 324: Safeguard Against Loss-Of-Signal Events
Deploying the snom ONE IP Telephone System Figure 25-3. Cell Phone Calling Schedule When this cell phone calls the PBX: The Personal Virtual Assistant provides special prompts to ■ users who call into the system from their cell phone. This setting allows you to turn this feature off.
Page 325: Feature Codes
Chapter 25: Cell Phones 2. Tell the system not to include your cell phone in any incoming calls. To do this, modify your cell phone redirection settings, as shown below: Note: Putting your phone into DND mode (using *78) will prevent incoming calls from ringing your cell phone;...
Page 326: Move Current Call To Cell Phone (*52)
Deploying the snom ONE IP Telephone System Move Current Call to Cell Phone (*52) This feature allows users to move a current call from the extension phone to the cell phone. (Note: The user’s cell phone must be configured to the extension before this feature can be used.) Scenario: You’re on your extension in the middle of a conversation and need to leave the office.
Page 327 # key. Receive a Callback When the system rings your phone: Use feature codes from your cell phone. 1. Answer the phone. snom ONE Star Codes 2. Enter the outbound number and press the # key. Making Calls Call Forwarding...
Page 328 Deploying the snom ONE IP Telephone System...
Page 329 Appendices...
Page 331: Appendix A. Working With Csv Files
CSV files need to follow to the structural requirements that have been set by snom. For example, if you are preparing a file for an address book import, it cannot include fields that are not part of snom ONE’s address book structure.
Page 332: Parameters
Deploying the snom ONE IP Telephone System The following four lines meet the criteria stated above. Records are on separate lines, semicolons act as field separators, and embedded quotes have been addressed. Cynthia Smith;102 Tremont Street;Bradford;MA;01834;9781234567 Bob Pine;22 King Street;Boston;MA;02134;6171234567 Cathy Chere;13 Tremont Street;Bradford;MA;01834;9781234567...
Page 333: Agent Groups
Appendix A: Working with CSV Files extensions;650;9786501234;1234;1234;Fred;Feuerstein;1234;ff@abc. com;000BBBCCCDDDD extensions;651;9786511234;1234;1234;Carl;Clever;1234;cc@abc. com;000BBBCCCDDDE Agent Groups The possible parameters for the agent group are listed in Table A-2 (not all are required). Table A-2 Agent Group Parameters Parameter Definition Value acds type Account type alias Extension number of the agent group 41 42 43...
Page 334: Conference Account
Deploying the snom ONE IP Telephone System Conference Account The possible parameters for the conference account are listed in Table A-4 (not all are required). Table A-4 Conference Account Parameters Parameter Definition Value conferences type Account type alias Extension number of the account...
Page 335: Converting An Excel File To Csv
Appendix A: Working with CSV Files Table A-6 Service Flag Parameters Parameter Definition Value hoots type Account type alias Extension number of the account srv_658 display Display name for the account mode clock Determines whether this service flag will be automatic ( clock ) or manual...
Page 336 Deploying the snom ONE IP Telephone System type;alias;ani;password;web_pass;first_name;display_name;mb_pin;email_ address;mac Note: Your file cannot contain columns that do not conform to these parameters. In the exercise sample shown in Step 1 above, columns C, D, E, and F contain nonconforming material and will not be needed for the CSV conversion.
Page 337 Appendix A: Working with CSV Files 7. Populate the empty fields. Begin by populating the fields that will have identical information, such as type password web_pass , and mb_pin . Type only the first entry as shown below: These parameters are outlined as follows: ■...
Page 338 Deploying the snom ONE IP Telephone System ■ Enter the first extension, as shown below: ■ Click the bottom right-hand corner, then while holding down the Ctrl key, drag the double plus sign to the end of the column. The numbers will appear in sequential order, as shown below: 10.
Page 339: Changing The Field Separator And Validating The File
3. Change the comma to a semicolon by clicking Edit > Replace. The final file is shown below. The file is now ready to be used for the address book upload. 4. To import the CSV file into snom ONE, see “Importing the CSV File” on page 327.
Page 340: Creating A Domain Address Book
Address Book Parameters When creating CSV files for a domain address book, be sure your data conforms to the structure of snom ONE’s address book. Depending upon the particular file you will be converting to CSV, this may mean that you will need to remove information that does not conform to this layout.
Page 341 Appendix A: Working with CSV Files display_number;domain;first;name;number;speed;type Keep in mind that your file cannot contain columns that stray from these parameters. In the sample shown in Step 1, columns C, D, E, and F contain nonconforming material. Delete the nonconforming columns (Edit > Delete). The material that remains must correlate with the allowable parameters, as shown below: 4.
Page 342: Changing The Field Separator And Validating The File
3. Change the comma to a semicolon by clicking Edit > Replace. The final file is shown below. The file is now ready to be used for the address book upload. 4. To import the CSV file into snom ONE, proceed to the next section, “Importing the CSV File.”...
Page 343: Importing The Csv File
Importing the CSV File Importing a CSV File for the Extension Account This section shows you how to import the CSV files for the extension account into snom ONE (the same procedure can be used for all account types). Open the CSV file in a text editor (for example, Notepad).
Page 344: Importing Csv Files For Domain Address Books
Importing CSV Files for Domain Address Books This section explains how to import a CSV file that will be used as a domain address book. Use the follow- ing instructions from the snom ONE home page: From the domain, click the Settings tab, then choose Address-Book: 2.
Page 345: Troubleshooting
Accounts page, portion out of the CSV file and import it again. but internally, (Aliases will need to be entered manually using there will be only this method of CSV import.) one extension. This is not a problem.
Page 346 Deploying the snom ONE IP Telephone System...
Page 347: Appendix B. Sip Overview
ppendix SIP OVERVIEW SIP (Session Initiation Protocol) is a signaling protocol that is used to control multimedia communication sessions, such as voice and video calls, over Internet Protocol (IP). SIP is analogous to HTTP for voice and is essentially the glue that ties communications systems together, much like HTTP ties clients and serv- ers together for worldwide communication.
Page 348: User Agent Clients
Note: Non-IP devices like dumb phones can also be turned into SIP UAs by using an inexpensive analog telephone adapter (ATA) to make them SIP-aware. An ATA is a box with one or two analog ports with RJ11 jacks used for connecting regular analog phones to the VoIP network. Popular ones include the SIPura or Linksys PAP2.
Page 349: Back-To-Back User Agent (B2Bua)
A B2BAU establishes a two-legged call, keeping the SIP server in the middle of the call to orchestrate the details. One side of the session acts as the SIP UA server that receives the calls; the other side acts as the SIP UA client that establishes the other leg of the call.
Page 350: Types Of Messages
Deploying the snom ONE IP Telephone System Types of Messages SIP communication consists of two types of SIP messages—methods and responses. Methods are sent from the client to the server and are used to indicate the purpose of the request. The following six methods are part of RFC 3261.
Page 351: Content Of Messages
When a phone number cannot be located Unsupported When the SDP contains no common codecs (this can happen media type if one side supports only G.729 and the PBX has no G.729 license defined) Server internal error When the SIP server is out of resources...
Page 352: Describing The Sip Session
In the example shown above, the session-level section consists of five lines of text (always beginning with , which indicates the version number of SDP), and the media-level section consists of one audio stream. a=rtpmap lines convey information about the media format used.
Page 353: Sip Call Proces
Appendix B: SIP Overview Type Description Owner/creator and session identifier (optional) Time zone adjustments Session name (optional) Encryption key (optional) General information about the session (optional) Session attribute (optional) URI containing a description of the session (optional) Time the session is active (optional) Email address of the contact person (optional) Times when the session will be repeated Phone number to obtain information about the session (optional)
Page 354 Deploying the snom ONE IP Telephone System Via: SIP/2.0/TLS 192.168.0.32:2061;branch=z9hG4bK-9gg3wzak;rport From: “Roland Wright” <sip:40@pbx.company.com>;tag=g5ua0i7fz6 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=i339wesg>;reg-id=1 P-Key-Flags: resolution=”31x13”, keys=”4” User-Agent: snom360/7.3.14 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK,...
Page 355: Session Termination
Appendix B: SIP Overview Session Termination 200 OK Call Flow Once the caller hangs up, a BYE is sent to the UAS. The UAS receives the request and responds with a 200 Ok. BYE sip:40@192.168.0.32:2061;transport=tls;line=i339wesg SIP/2.0 Via: SIP/2.0/TLS 192.168.0.34:5061;branch=z9hG4bK-eec7092e42e0694ecd8be3d3e94 00816;rport From: <sip:41@pbx.company.com;user=phone>;tag=eed7a3b4e0 To: “Roland Wright”...
Page 356 Deploying the snom ONE IP Telephone System Scenario 1 Registrar REGISTER 200 OK Call Flow 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...
Page 357: Cancel Request
Via: SIP/2.0/UDP 75.150.83.2:5060;branch=z9hG4bK-a071e61e35d725f2c9a17c9bf2ed b7f7;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=”ab45353d389d01ba2086232c0 9417752”,response=”664617e317a5c34448f276db3932be2f”,username=”17772830314”,u ri=”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 358 Deploying the snom ONE IP Telephone System 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 359 User-Agent: snom-PBX/4.0.1.3475 Content-Length: 0 [7] 2010/04/28 11:21:27: SIP Tx udp:192.168.0.31:1024: CANCEL sip:50@192.168.0.31:1025;line=npbudr1b SIP/2.0 Via: SIP/2.0/UDP 192.168.0.33:5060;branch=z9hG4bK-9611418f8bbb34f24b5482fb861 59ddd;rport From: “Fifty One” <sip:51@pbx.company.com>;tag=33392 To: “Robyn Wright” <sip:50@pbx.company.com> Call-ID: a8c5d213@pbx CSeq: 21261 CANCEL Max-Forwards: 70 Content-Length: 0 [7] 2010/04/28 11:21:27: SIP Rx udp:192.168.0.31:1024: SIP/2.0 200 OK...
Page 360: Snom One Settings And Sip Traces
3. Under Specific Events, set Log SIP Events to yes. 4. Click Save. To view the SIP trace, navigate to Status > Call Log. Logfile Syntax Figure B-6 shows a sample logfile and the syntax that typically appears in one.
Page 361: Troubleshooting With Logfiles
Receive layer Packet [7] 2010/04/07 14:27:31: SIP Rx udp:76.127.234.149:5060: type REGISTER sip:cs410.snom.com SIP/2.0 Via: SIP/2.0/UDP 76.127.234.149:5060;branch=z9hG4bKb9f8adb39884fe0e3fd1996e7b97bfd3.0 Via: SIP/2.0/UDP 76.127.234.149:1030;rport=1030;branch=z9hG4bK-a8ru3e03jsdp.om8vRLKP6dg__ From: "Jane Smith" <sip:509@cs410.snom.com>;tag=lcnnszda0o To: "Jane Smith" <sip:509@cs410.snom.com> User Call-ID: 3c267027d74e-hmz8xouk5s3x agent CSeq: 177 REGISTER Max-Forwards: 69 Contact: <sip:509@76.127.234.149>;expires=3600;reg-id=1;q=1.0;+sip.instance="<urn:uuid:2 User-Agent: snom370/7.3.14...
Page 362 Deploying the snom ONE IP Telephone System “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.
Page 363 Appendix B: SIP Overview 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 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...
Page 364 Deploying the snom ONE IP Telephone System Header Abbrev. Header Abbrev. 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 Interval Too Brief...
Page 365 Appendix B: SIP Overview Unsupported Media Type 6xx—Global Failure Responses Unsupported URI Scheme Busy Everywhere Unknown Resource-Priority Decline Bad Extension Does Not Exist Anywhere Extension Required Not Acceptable Session Interval Too Small...
Page 366 Deploying the snom ONE IP Telephone System...
Page 367: Configuring Exchange For Snom One
When using snom ONE with Exchange, you can redirect calls, voicemail, and email to the mailbox of the Exchange server. You can also use the calendar and the address book. Exchange’s address book allows you to initiate outbound calls and perform voice-activated dialing for internal or external calls.
Page 368: Associate The Dial Plan With The Unified Messaging Server
5. Create a new unified messaging IP gateway. Under Actions, select New UM IP Gateway. Name the gateway snomONE 6. Select IP Address and enter the IP address of your snom ONE server. 7. Click the Browse button, and select the snomone dial plan you created.
Page 369: Enable Mailbox Recipients For Unified Messaging
3. Next to Unified Messaging Mailbox Policy, click the Browse button and then select snomONE Default Policy. 4. Enter a mailbox extension for this user that matches the user’s extension number on the snom ONE server. 5. Enable Manually specify PIN.
Page 370: Add The Exchange Gateway To Your Current Dial Plan
Deploying the snom ONE IP Telephone System exchange. 6. In the Domain field, enter the FQDN or IP address of your Exchange Server (i.e., company.com sip:exchange.company.com:5060;transport=tcp 7. In the Proxy Address field, enter , but replace exchange.company.com with the FQDN or IP address of your Exchange Server. The 100.200.100.200...
Page 371: Set The Snom One External Voicemail System
4. 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). The replacement fields known from the caller-ID representation in the trunks can be used (e.g., in the image shown below,...
Page 372 Deploying the snom ONE IP Telephone System...
Page 373: Glossary
ARP returns the layer 2 address for a layer 3 address. ATA (Analog Telephony Adapter) A device used to connect one or more standard analog telephones to a digital and/or non-standard telephone system such as a Voice Over IP based network. Bandwidth The range from highest to lowest frequencies transmitted on a network.
Page 374 Deploying the snom ONE IP Telephone System CAlEA (Communications Assistance for law Enforcement Act) A U. S. wiretapping law passed in 1994 to protect public safety and ensure national security. Its objec- tive is to preserve law enforcement’s ability to conduct lawfully-authorized electronic surveillance while preserving public safety, the public’s right to privacy, and the telecommunications industry’s competi-...
Page 375 A feature offered by telephone companies for use with their customers’ private branch exchange (PBX) systems. In DID service, the telephone company provides one or more trunk lines to the customer for connection to the customer’s PBX and allocates a range of telephone numbers to this line (or group of lines) and forwards all calls to such numbers via the trunk.
Page 376 “Touchtone,” DTMF has essentially replaced pulse dialling. When a user presses touch keys, two tones of specific frequencies are generated (one from a high-frequency group and the other from a low- frequency group), so it’s impossible for the voice to imitate the tones.
Page 377 IETF and ITU-T protocols. A device for connecting one or more computers to other computers, networked devices, or to other networks. Compared to routers and switches (which are also connecting types of devices), a hub is the least complicated way to get the job done.
Page 378 Jitter The statistical variance of the inter-arrival times of RTP data packets. If a VoIP device sends out one RTP packet every 20 milliseconds for an audio stream, the packets will not necessarily arrive precisely every 20 milliseconds, so if the packets are played out as they arrive, the output will produce jitter and will be of poor quality.
Page 379 PBX (Private Branch eXchange) A telephone exchange that serves a particular business or office, as opposed to one that is owned by a common carrier or telephone company and is used by many businesses or the general public. Users of...
Page 380 Deploying the snom ONE IP Telephone System have evolved over time, beginning as a manual switchboard or attendant console that was operated by a telephone operator (circuit switching) to the modern IP PBX. See also “IP PBX.” PCM (pulse code modulation) A sampling technique that converts analog signals to digital form.
Page 381 IETF adopts some of the proposals published as RFCs as Internet standards. Router A device for connecting one or more computers to other computers, networked devices, or to other networks. Compared to hubs and switches (which are also connecting types of devices), a router is the smartest and most complicated of the three.
Page 382 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. Compared to a hub (which is also a connecting type of device), the switch is more...
Page 383 In this way, it sends traffic only where it needs to go rather than to every port, making the network significantly faster. Switches work at the data link layer (layer 2) of the OSI model. T1 (also called channelized T1) A digital carrier modulation method in which a T1 line is divided into 24 channels, each having a maximum data speed of 64 thousand bits per second (Kbps), and each capable of supporting a unique application that can run concurrently with, but independently of, other applications on different...
Page 384 Deploying the snom ONE IP Telephone System URI (Uniform Resource Identifier) [RFC 2396] A string of characters for identifying all types of names and addresses on the Internet (e.g., a page of text, a video, a program, a SIP proxy). It enables devices the ability to interact with the resource over a network (typically the Internet) using specific protocols.
Page 385: Index
Index INDEX blocking your caller-ID rejecting using *88 attended transfer Symbols audio audio__* folder audio prompts busy.wav codec preference access list customized ringtones 206–208 blocking IP addresses installing new languages 204–206 address book IVR language add agent group callers to ringback.wav and anonymous calls tone language...
Page 386 Deploying the snom ONE IP Telephone System unblocking CDR (Call Detail Record) midnight events calling card pre-pay 179–182 See also account balance CDRs 251–258 callback automatically generated 251–253 credit for outbound calls cdre, cdri, and cdrt folders dialing interpretation global configuration file...
Page 387 CMC web language configuring a PIN voicemail/mailbox settings preferencing regular expression matching domain address book replacement string 92–95 create one with CSV file sample dial plans 97–100 downloads wildcard patterns 93–94 audio prompts DID. dialing MoH/paging application ringtone config.
Page 388 Deploying the snom ONE IP Telephone System email auto attendant greetings 187–196 198–199 add email accounts personal greetings 197–198 blacklist activity recording permission blocking user interface settings record new greetings CDRs to email group mail customizing email notifications 191–192 Exchange 2007/2010 UM...
Page 389 233–238 blocking monitoring settings logging PnP events manual setup 226–228 multicast mass deployment IP addresses multiple extensions on one phone 230–232 sip.mcast.net overriding PnP defaults 231–234 music on hold. MoH PnP methods 219–221 MWI (message waiting indicator)
Page 390 Deploying the snom ONE IP Telephone System credit for outbound calls ptime parameter pre-pay feature calling card 183–186 See also access from extension security access from PVA blocking the access of IP addresses dollar amount on extension service flags 1 1 1–120...
Page 391 Index star codes midnight events snom ONE star codes system performance. CPU See also star codes (by number) binding pbxctrl to fixed CPU *00 (call cell phone of extension) call duration *51 (retrieve call from cell phone) call recordings *52 (move call to cell phone)
Page 392 Deploying the snom ONE IP Telephone System outbound calls web interface 77–80 purpose of customizing the accounts page 67–68 58–60 regular expressions 73–76 white list routing calls to extensions 72–79 add a contact SIP trunks 68–71 voicemail accessing add a comment to a message...
Page 393 How to Find Us Berlin Boston snom technology AG snom technology Inc. Charlottenstr. 68-71 18 Commerce Way, Suite 6000 10117 Berlin Woburn, MA 01801 info@snom.com +1 (781) 569-2044 The entrance is at Charlottenstraße/corner of +1 (781) 569-2045 Krausenstrasse. infoUSA@snom.com Next subway station: Stadtmitte (lines U2, U6).