Domain settings
From Pbxnsip Wiki
You can view domain as a collection of users, attendants, hunt groups and service flags etc. Generally, in a small enterprise, you may have a singe domain.
Example: pbx.mycompany.com
But medium to large enterprises, you can have more than one domain.
Example: management.pbx.mycompany.com, engineering.pbx.mycompany.com, shipping.pbx.mycompany.com, datacenter1.mycompany.com etc
Note: If you do not find what you are looking for in this page, then please view the old pages regarding the domain settings here Domain Administrator
Contents |
Domain Settings
This section covers some of the basic domain level setting.
General Settings
Name of the Domain: You can give you domain a descriptive name. This name can contain special characters like spaces and you may use upper and lower case characters. This setting is used for example when the PBX sends an email with the call data records for the domain. This name is independent from the domain name (which is set by the system administrator).
Default Dial Plan: This is the dial plan that users in this domain can use. Note that each user (extension) can override this with their own dial plan based on the requirement. Most of the accounts in a domain will use the default dial plan.
If you don't set a default dial plan, you will likely have problems placing outbound calls. Therefore, it is strongly recommended to choose a default dial plan.
Default IVR Language: This is the domain level override for the IVR language selected and the system level(see Overall System Settings). This field is useful, if you have multiple domains and each wants have their own IVR language See Localization for more details on language support.
Tone Language: Similar to the IVR language.
Default Web Language: Again similar to the above two.
Music on Hold Source: You can select the source for the 'music on hold'. This source will be used when the call is put on hold. The party who is on hold hear the music selected here. See Music on Hold for more information.
Timezone: The PBX is able to deal with several time zones at a time. This makes it possible, that every user can select his home time zone, so that for example mailbox messages are read out with the time zone of the user. The PBX also uses the time zone information during the provisioning of the phones, so that the phone will also use the time zone of the user. See Localization for more details on time zones.
Country Code: The country code plays a major role in interpreting telephone numbers. There are essentially three modes:
- If you keep the country code setting empty, the PBX does not change telephone numbers. In this case you must make sure that users, PSTN gateways and service providers use the same way of representing a number (for example, 10 or 11 digits in USA). You should choose this mode when the other modes are causing problems.
- If you put a "1" there then the PBX will interpret telephone numbers according to the NANPA (North North American Numbering Plan Administration, see http://www.nanpa.com) scheme. That means that international numbers start with 011 and numbers that have 10 digits are written in the (xxx)xxx-xxxx scheme (JavaScript takes care about this in the web interface). This scheme also applies for other countries than USA, for example Canada. Apart from the readability of numbers, this scheme also has the benefit that different way of representing numbers (11-digit or 10-digit) are automatically converted by the PBX into a global format. The area code ust be three digits and it is used for numbers that have only 7 digits.
- If you put another country code there (for example, "33" for France), the PBX will interpret numbers according to the "Rest of World" scheme. That means that international numbers start with 00 and national numbers start with 0. The area code is used to determine if the short number format can be used (local call).
Area Code: This the telephone area code for the domain. This is generally NPA in the NPA-NXX-XXXX number. Ex: '978', '212', etc
Default ANI: You can configure each domain with a default ANI (Automatic Number Identification). ANI is a service that tells the recipient of a telephone call the telephone number of the person making the call. Mostly used for the billing purposes.
Voicemail Timeout: The "Voicemail Timeout" defines how long the PBX will wait until it redirects the call to a mailbox. You may override the setting in the settings for a specific extension.
If you plan to use cell phones with the PBX, then you should choose a long voicemail timeout (e.g. 30 seconds). Because the call setup time for a cell phone call is long and the user might have to search the cell phone, such a long value is reasonable. If you don't plan to use cell phones, you can choose a shorter time, for example 15 or 20 seconds.
Voicemail Size
The Voicemail Size determines how many messages can be stored in a voicemail box. Again, you can override this value per user, but it is good to have a reasonable default. "20" is a good default number.
Maximum Voicemail Duration
In addition to the maximum duration for a recording, you may specify how long a mailbox message may be. This setting makes it easier to plan memory size for mailbox messages. Typically, a mailbox message should not be longer than two minutes. The unit for the setting is seconds.
Voicemail PIN Digits
When you create an extension, you can leave the PIN field empty. Then nobody will be able to access the mailbox with a pin, only a user that registers with the extension credentials is able to go to the mailbox. However, if a user wants to set up the PIN, you must tell the PBX how many digits a PIN must have. Typically, a PIN consists of four or five digits, but you can pick any number larger than one.
Require Entering Mailbox PIN
Calling your mailbox should be simple. Depending on your office layout, it might be easy for coworkers to use a phone without authorization and listen to voicemail messages. Therefore, the administrator can decide if the mailbox should first ask for the PIN code before reading out messages.
Trust Caller-ID:
Billing Tones: This field lets to configure whether the domain users will hear a 'beep' during the call or not. Need More details, example
Calling own extension number goes to mailbox
When a user calls his own number, the PBX has to make a decision if the PBX should call the registered extensions or the call should straight go to voicemail. By default, the PBX would send the call to the mailbox. However in some situations it is useful to use the rules to call the extension.
Mailbox Escape Account
If the Mailbox Escape Account setting is set, a user who hits the mailbox may press the "0" key to get to the account that you specify here. The number may be an internal number or a external number.
Mailbox Direct Dial Prefix
If you want to call directly into a mailbox, you may put this direct dial prefix in front of the extension number. This is useful when calling from your cell phone into the auto attendant or when you want to leave a voicemail message for your coworker. Typically, this prefix is a "8".
External Voicemail System
Sometimes you don’t want to use the built-in mailbox. There are several specialized external voicemail systems available which accept calls from a SIP PBX and provide functions like voicemail to email, calendar functions and much more. For example, you can use Microsoft Exchange for this purpose.
The setting contains the telephone number that should be dialed. You can include replacement fields which are used in the Caller-ID representation for outbound calls (see Outbound Calls on Trunk). The dial plan for the called extension will decide which trunk will be used to initiate the call.
Emergency Numbers
You can specify special destination numbers when an extension dials an emergency number (see Emergency Calling). The number(s) that trigger the mechanism must be listed in the setting "Emergency Numbers". If you have more than one emergency number, use a space between the numbers (e.g. "110 112").
'Mailbox Explanation Prompt
If a user records a personalized message, the PBX may say after this prompt another message that explains that the caller may now leave a message. Some people like this and others don't, therefore we made the behavior of the PBX a setting. If you set the Mailbox Explanation Prompt, the mailbox will explain the caller's options after the playback of the personal recording. For the standard greetings, the PBX will always explain the options.
Offer Camp On: This setting lets you configure whether calling users can camp on when call goes to called person's voicemail. You have to turn this off if you are using external voicemail systems such as Microsoft Exchange.
Call Forward On No Answer Timeout
Sometimes the PBX has to redirect a call after a timeout. The setting "Call Forward On No Answer Timeout" tells the PBX how many seconds to wait before performing the timeout action. It is advisable to set this less than the Voicemail Timeout, otherwise call forward will not happen.
Park Reminder
It is easy to forget the parked call. Therefore, the PBX can call the extension that parked the call back after a certain time and reconnect the call. In this setting you can specify after what time the PBX should do this or if the PBX should not do this at all.
From header when switching the domain
This setting is used when the PBX switches the domain context for calling an extension. You can set the new 'From' header value in this field. See Inter-Domain Call for more information.
For example, the string “$d: $n” will produce an output like “Company A: John Smith” if the source domain name was set to “Company A” and the original content of the header was “John Smith”.
If the setting is empty, the PBX will not change the header.
To header when switching the domain
This setting is used when the PBX switches the domain context for calling an extension. You can set the new 'To' header value in this field. See Inter-Domain Call for more information.
Change names in To/From-headers
Usually it is okay if the PBX changes the names in the To/From headers in the SIP packets. For example, this makes sense when the address book matches the caller-ID and the PBX should present the address book entry.
However, if the PBX is used as a SIP device in operator environment, you may want to make sure that the PBX does not change headers. In this case, you can turn this flag on.
SOAP External Call
In this setting you can put the address of the application server that is used to determine if calls are allowed to go to an external number. This setting is only visible if your license key contains a SOAP key. See SOAP for more details.
CDR URL: You can configure where and how the CDRs are written for this specific domain. This setting will override what is configured at the system level for this domain. PBX supports several different types of CDR generation apart from writing them into the '<pbx install dir>/cdr' in the XML format. See Admin Level Settings
Recording Defaults for this domain
In this section you can define the domain level call recording settings. Most of the recordings settings are with respect to the extensions.
Record incoming calls from hunt group: This settings turns on or off the recording on an extension for the calls coming from the hunt group.
Record incoming calls from agent group: This settings turns on or off the recording on an extension for the calls coming from the agent group.
Record incoming calls from extension: This settings turns on or off the recording on an extension for the calls coming from another extension.
Record outgoing calls to internal numbers: This settings turns on or off the recording on an extension for the calls going to another extension.
Record outgoing calls to external numbers: This settings turns on or off the recording on an extension for the calls going to external numbers.
Record outgoing calls to emergency numbers: This settings turns on or off the recording on an extension for the calls going to emergency number.
Please refer Recording for the details and examples
Midnight Events
At midnight, the PBX can perform several maintenance tasks. This includes the generation of CDR reports and sending them by email.
Send daily CDR report to: PBX can send daily CDR reports to configured email addresses. This is really a useful feature for lot of the customers. You can specify a list of email recipients that will get a CDR email with the calls of the last day. This list must be seperated by semicolon, because email addresses may contain spaces. For example, you can use "Fred Feuerstein <ff@domain.com>; Carl Clements <cc@domain.com>".
It you want to send the CDR email immediately, you can click the "try" button. This is very useful because you don't have until midnight to try your settings. Keep in mind that this is just a link and you may have to save your list first before clicking on that link.
Reset DND Flags: DND is a major problem if users forget that they put their extensions and DND and open a trouble ticket next morning because they don't receive calls any more. Therefore you can check the "Reset DND Flag" setting. The PBX then will reset all DND flags of this domain during midnight.
Reset Hot Desking: Keeping the Hot Desking settings has a similar problem like DND Flags: Users go home and forget about it. Because of this the PBX offers also the possibility to reset the hot desking at midnight.
Reset Block CID: This is another case where you may need to reset during the midnight.
Provisioning Parameters
When the PBX automatically generates files for the configuration of extensions, it needs a few settings that depend on the domain.
Default PnP Dialplan Scheme:
The automatic provisioning is able to provision a dial plan for the domain users. The final decision for the used scheme is being made based on the dial plan of the extension. By default, there are several dial plan schemes available:
- When the "user must press enter" scheme is selected, the user of the extension must always press the "Enter" or "Ok" key on the phone. This is essentially like on a cell phone, where the user has to press the green check button on the device. This scheme avoids a lot of problems when it is very difficult to predict how many digits the phone has to collect in order to have complete number.
- When the user is located in the North America area (see http://www.nanpa.com), the length of the number is predictable for national calls and calls of other extensions in the domain. Calls to international destinations or star codes are still very difficult to predict, and users still have to press the check button on the phone to start the button.
- For other countries the "Europe" scheme might be appropriate. Like in the rest of the world outside of NANPA, the length of a telephone number is practically unpredictable and users have to press enter in order to start the call. The "Europe" scheme will dial automatically only if the destination is another destination.
Authentication User/Password: When the PBX tries to identify a device, it needs to verify that the client has the permission to download a configuration file. In order to make things easier for the administrator, the username/password can be the same for all devices in a domain. Please also refer to Prepare an Extension for Plug and Play for more information.
Feature Codes
Feature codes are traditionally used by users to control the PBX. When the first PBX was invented, there was nothing like a web interface where you could set up your preferences, so the designers decided to define a specific number space for controlling the behavior of the PBX. Traditionally, these codes start with a star symbol followed by one or two digits. The IP PBX emulates this behavior, so that users can use the IP phone just like a PBX extension phone.
The default mapping of feature codes can be found in the page Default Feature Codes.
Call Treatment
Call Park
Extensions may hold or park a call. When a call is hold, only the extension can pick the call up again; when the call is parked other extensions may pick up the call as well. Holding is done by pushing the hold button on the extension, most SIP user agents support this feature with a special key or a soft key. Parking a call will redirect the call to a park orbit. Even if you disconnect the extension the call will stay there until someone picks the call up or the caller disconnects.
Every hunt group and extension has its own park orbit. The name of the orbit is the same as the name of the account.
Usually user agents don't have a special key for parking a call. If they have, this key will essentially redirect the call to the park orbit with a blind transfer. Therefore, extension may generally park a call by a blind transfer to the park orbit. However, PBX users are used to star codes that perform the transfer to the park orbit.
In SIP, a user agent will first put the call on hold before it can send a star code. Sending the star code is executed in a new call that has the destination of the star code (e.g. <sip:*85@test.com>). When the PBX receives such a call, it will search the last call that this extension received or initiated and will perform the blind transfer of that call to a matching park orbit. It will then play an announcement that the call has been parked and hang up.
If the extension subscribes for the LED status information, it will light up the respective LED after the call has been parked on the park orbit.
Call Park Retrieve
After a call has been parked, there must be a way to retrieve the call from the park orbit. The retrieve code will go through the list of park orbits of the user and pick up the first park orbit where a call has been parked.
Note that park orbits may have more than one call parked. In this case the park orbit acts as waiting queue. The call park retrieve will pick the first call in the orbit, so that the callers will leave the queue after the first-in-first-out principle.
See Park and Pickup for more information.
Call Pickup
Call pickup searches for unconnected calls and redirects them to the extension. The other extension that might be ringing will be canceled. The typical case for call pickup is when a colleague is temporarily not available, but you want to take the call.
The PBX searches first the hunt groups where the extension is a member for a call that can be picked up. If no call was found, it tries the extension's park orbit. If the user specifies the park orbit after the pickup code, the PBX will search only the indicated park orbit. However, the extension must be member of a hunt group, where the pickup destination is also a group member. This is necessary to protect unauthorized call pickups.
More information on parking and pickup can be found in Park and Pickup.
Call Return
Call Return will dial the last number that has been missed. This function is useful for SIP devices that don't keep a lit of missed calls (e.g. ATA). Most SIP devices with a display have this function built-in, and the user may see the caller-ID in the screen before returning the call.
The call return function stores only one number. When the extension makes a call that gets connected, the call return number is cleared. This makes sure that a number is called only once, and users can dial the call return code without talking to the same number again.
Redial
The Redial is similar to call return, but it does not call the last incoming number, it calls the last dialed number again. The redial number is never deleted, users can redial numbers even if the call established. The redial number and the call return numbers are stored independently.
Transfer
Some devices do not have a transfer button. For examples, when using ATA there is usually no way to initiate a transfer except dialing a special code. The transfer code initiates a blind transfer of the last call on hold to the provided destination. The destination must be entered directly behind the star code.
Call Forwarding
There are six star codes to handle the call forwarding other than hot desking. Three codes are used to enable the call forwarding condition. If the user dials this star code, the PBX will prompt the user for the redirection number.
The other codes are used for turning the redirections off. When the user dials these star codes, the user will hear a prompt that the feature has been deactivated.
Hot Desking: "Hot Desking" (see for example http://en.wikipedia.org/wiki/Hot_desking) makes it possible that employees temporarily or permanently change the routing of all their calls to a specific physical device. Then all calls to that extension, also as part of the hunt group or agent group, get routed to that extension.
Hot Desking describes feature in detail in a seperate page.
Call Forward All(Activate/Deactivate): All means that the call is forwarded always, independently of an event.
Call Forward Busy(Activate/Deactivate): Busy means that a call is forwarded if the extension is busy. The busy condition must be returned by the device, the PBX does not check the internal state for the busy condition. This makes it possible to handle the busy condition if several devices register for the same extension number. When several extensions are used, the busy condition checks if all devices are busy.
Call Forward No Answer(Activate/Deactivate): No Answer means that no device picked up after a certain timeout. The timeout is a domain setting that can be overwritten by an extension setting.
Anonymous Calls
Block CID(Activate/Deactivate)
By default, the PBX will try to present the caller-ID on outgoing calls. Sometimes, users don't want to show the extension number. By using the block CID code the PBX will try to hide the CID on all subsequent calls until the user deactivates the blocking.
Calls from one extension to another extension will always show the caller-ID.
Block Anonymous Calls(Activate/Deactivate)
When the PBX receives a call where the caller-ID is neither an extension number nor consists of a valid caller-ID, it will assume that this is an anonymous caller ID. A call-ID is treated as valid when it consists only of the characters 0-9. It may have a '+' character in the beginning.
By default, the PBX will allow anonymous calls. However, some users don't like to receive such calls. When the feature is enabled, those calls are rejected with a IVR prompt which explains that the caller-ID could not be identified and the user accepts only calls with a valid caller-ID.
DND(Activate/Deactivate)
Do Not Disturb (DND) is used to temporarily reject all incoming calls for all devices registered with this extension. The two star codes are used to turn DND on and off.
DND also applies to hunt groups. If a member of a hunt group has set its extension number to DND, the hunt group will skip that extension. This is a different to redirect all, which will not redirect calls from a hunt group.
Many SIP devices have a dedicated DND button. Most implementation handle DND locally on the device. However, when this function is used, the DND applies only to the specific device and not to the extension and it usually does not survive reboot cycles.
If the codes for DND on and off are the same, the PBX toggles between the two states. This is useful if you have a phone that just has DND programmed as a speed dial button.
Agent Login and Logout
Extensions may be part of agent groups. These agent groups serialize incoming calls and distribute them to one or more extensions (see Agent Group).
By default, an agent group will consider the extension online at all times. However, by dialing special star codes an agent can control if an agent group will route calls to the extension. This is in addition to the DND status, which does not only block calls from agent groups, but all calls (except for call that come from extensions that have the permission to override DND). That means, an agent group may route a call to a specific extension, if that extension is on the list of agents or the list of escalation agents ("include the following additional agents"), and that extension has at least one registration, is logged in and that extension is not on DND.
If the agent dials the agent login/logout code without a specific agent group behind the code (e.g. *64 or *65), than the PBX will set the login or logout status of the extension. This status flag can be seen in the web interface as "Agent Logged In". The login status is also visible in the agent group web interface in the agent overview. This status flag affects all agent groups; it does not change the list of agents of a group. A typical usage of this code is when an agent starts working in the morning or goes home in the evening.
If the codes for Agent Login and Logout are the same, the PBX toggles between the two states. This is useful if you have a phone that just has login and logout programmed as a speed dial button.
Sometimes it makes sense to let agents dynamically put themselves on an agent group or take themselves out of an agent group. If an agent has domain administration permission, he can easily do that by putting him on the list of agents in the web interface. However, most agents do not have domain administrator rights, therefore the PBX provides a star code that performs the same task without having to log into the web interface. In order to allow this, the setting "Extensions that may jump in or out" must list the extension or use a wildcard in the settings of the agent group. When an extension dials the login or logout code with an agent group name behind the code (e.g. *64701 for logging into agent group 701), then the PBX adds that agent at the end of the list of agents for that group, or takes the agent from the list, respectively (*65701). Dialing this code does not affect the general login status of that extension. That means if an agent adds himself to an agent group but is not logged in, he will not receive calls (he need to log in by dialing the login code).
Miscellaneous
Go To Voicemail
This star code is just a quick way to get to the mailbox.
Intercom
By using the Intercom prefix, you can directly call another extension. The other phone is asked to pick up immediately and to establish a two-way audio conversation.
Intercom is different from Paging in the way that Intercom is two-way, one-to-one communications while paging is one-way, one-to-many communications.
Call Extension Cell Phone
This is like a speed dial code that you don't have to set up. By putting the code for calling the cell phone in front of the extension number, you can directly call that extension's cell phone (e.g. *00123 for dialling the cell phone associated with extension 123). The caller will not see the cell phone number, so that the extension's privacy is kept regarding handing out cell phone numbers.
Record
If you want to record the prompt for an auto attendant, an agent group or an IVR node, you can use the Record star code. The PBX differentiates three cases:
- Attendant: The digits behind the code identify the auto attendant and will record the announcement for the account (e.g. dial *98123 to record the announcement for auto attendant 123).
- IVR Node: The digits behind the code identify the IVR Node and will record the announcement for the account.
- Agent Group: The code needs two arguments. The first argument identifies the queue, and the second argument the prompt. The arguments are separated with a star symbol. The first prompt with index 0 is the welcome prompt; it will not be repeated and it will be played for all callers, no matter if they have to wait or not. The other prompts with the index 1-9 will be repeated in a loop and are only played while the caller has to wait in the loop.
If you require that the user has to enter the PIN code before going to the mailbox, then the PBX will also ask the user for the PIN code before the PBX allows to record a message. If the user has no PIN code, then the PBX does not permit recording.
Clear Voice Message Indicator
When the user dials this star code, the PBX will delete the Message Waiting Indicator (MWI) on the extensions. Usually it should not be possible to clear the MWI indicator manually, but if the extension just does not want to listen to the mailbox and keep the MWI indication silent, this star code will turn the indicator off.
Send Voicemails((Activate/Deactivate)
When the PBX records a mailbox message, it may store it locally or it may send it via email to the user. Please note that sending a voicemail message per email requires that you have properly set up the email address of the user and of the domain. With the activation and deactivation of this feature you toggle between the methods.
Customer Originated Trace
This useful feature sends the call details of the last calls to the email account of the extension. Instead of writing down the number on a notepad, the user can instead send him an email that contains all the information.
The PBX will include a link to the last number. If you click on this link, the PBX will prompt you for your username and password. Please enter your username in the form "user@domain". If your browser supports saving the login information, the next time when you click on such a link to dial a number you will immediately initiate the call to that destination.
This feature works only with user agents that support the REFER mechanism outside of existing dialogs. Check out your phone if it is able to support this feature. On some phones, you have to press "Ok" or lift up the handset in order to acknowledge the dialing of the number. The remote initiation of a call is a security-sensitive topic, as it might turn your phone into a microphone. Therefore, you must authenticate yourself during the initiation of the call and you may have to acknowledge the initiation of the call.
Add White List, Add Black List
These codes are used to store the last caller in the "white" or "black" list. It is a convenient way of keeping the address book updated with useful information for further communications. See Black List and White List for more details.
Wakeup Call
This code is used to program the wakeup call for this extension, see Wakeup Call.
Show account balance: By dialing this star code user can find the balance on their account.
Call Intrusion
One of the benefits of the PBX architecture is that existing calls can be interrupted and monitored.
All three modes, and especially the listen in mode, are severely affecting the privacy of the calls on the PBX. Therefore, those modes are only available to extensions that are specifically allowed to use those features. In the permissions tab of the respective extension, the domain or system administrator has to enable the features. Please consult corporation and government regulations if turning these features is allowed in your environment. Illegal listening to phone calls is a severe crime, and system administrators must be aware about that.
To see which calls are active, you can monitor the extension's state of the state of a CO-line. For example, you can do this by using the LED key of a SIP phone with the associated display.
Call Barge-In
In call barge in, two persons that are talking to each other are put into a kind of conference with a third person. Typically, this third person is a secretary reminding ("saving") the boss about another appointment. Both parties will hear the third person come into the call ("knock knock") and both parties will be able to hear what the third person has to say. The existence of the barge in call depends on the existence of the underlying conversation.
In order to barge into a call, dial *81 followed by the extension number that you would like to interrupt, then press dial.
Call Teach-Mode
In teach mode, only one side of the call can hear the third party. This is typically useful in a call center when a trainer wants to give tips to a new agent, so that the customer does not know about the teacher in the background. This mode is also sometimes called whisper mode, because the agent's phone must have a real good echo cancellation so that the customer does not hear some background echo.
In order to start the teach mode, dial *82 followed by the extension number that should hear your voice, and then press dial.
Call Listen-In
The listen mode is similar, but completely stealth mode. The two persons talking to each other are not notified about the listen in and cannot hear what the third person says on the phone (e.g. breathing).
In order to start listening to calls, dial *83 followed by the extension number that you would like to monitor.
In-Call Codes
Record On Key: This setting lets the administrator to configure a code so that the user can initiate a call recording in the middle of call by pressing this star code.
Record Off Key: This setting lets the administrator to configure a code so that the user can stop a call recording in the middle of call by pressing this star code.
Address Book
The domain address book entries are visible to all members of the domain. That means they can search the domain address book and calls coming to that domain will automatically see the name of the calling party.
All names in a domain are automatically included in names searches in the domain.
You can also use the address book to indicate which DID number has been dialed. If you add an address book entry that matches the specific DID, the PBX will add the display name to the caller-ID, and the phone then can display the text associated with the caller-ID.
First Name: The first name of the contact.
Last Name: The last name of the contact.
Number: The telephone number of the contact. This is not SIP URI.
Speed Dial: This is a 2 digit star code that can be associated with this contact. Note that these star codes should not overlap with any of the feature codes.
CMC:
Contact Type: Whether this contact is black listed or not.
You can also load a CSV file to create the address book as explained in the picture above.
For further details on the address book refer Address Book.
Buttons
This document addresses this requirement in the scope of devices that use the session initiation protocol (SIP, see RFC 3261). It introduces a new document type that contains the necessary information and that can be exchanged between the endpoint and the SIP-enabled PBX.
Please refer Buttons for the details on the buttons
