SARK UCS/MVP Headers Panel

Overview

SARK UCS/MVP _ Headers Panel exposes the generated file headers of those _.conf files which SARK manages for you. In addition to the regular Asterisk .conf files, there are also two virtual .conf files; seldir.conf and selspeed.conf. Neither of these files exist in the asterisk directory proper but only as SARK/SAIL database tuples. Below we show screen shots of the modification panels for voicemail.conf, features.conf and sip.conf. You can freely modify the entries to suit your installation requirements.

Universal Directories

The virtual entries; seldir.conf and selspeed.conf allow you to create a central directory and speed-dial register for those phone types that support it. Currently the central directory is implemented for Snom and Aastra units, while the speed dial register is implemented for Snom units only. Others (in particular, Cisco/Linkys) will be included as required or requested by customers. First we show the central directory. You will notice that the tuples are free form and that you may annotate them freely.

Only the first two attributes (separated by a comma) are regarded as significant, all other data is treated as comments. Additionally, attribute two (telephone number), can be formed with any of the traditional seperator chracters; {().- or space} in order to make the entries more legible. You may also add any notational data (such as address etc) to the right of the two significant attributes (see the example above). Finally, you may include comment lines which begin with a hash (#). Entries do not have to be in any particular sequence, or order. This is important when you have mixed phone types in your estate where the types do not support the same cardinality of directory. For example, Aastra SIP units can support several hundred directory entries whereas Snoms can only handle 100. Absence of sequence allows you to specify the most significant 100 entries first. Thus both phone types will inherit the most significant entries but the Aastras (which can handle more entries) can have their own additional entries beginning at the 101st entry in your list.

selspeed.conf allows you to create a central speed-dial register for those phone types that support it. Currently the register is implemented only for Snom units since the Snom units can each handle 32 speed dials (Aastra units only support a very limited speed dial capability based upon the available programmable keys on the phone so they are not included). You will notice that the tuples are free form and that you may annotate them freely.

Only the first two attributes (separated by a comma) are regarded as significant, all other data is treated as comments. Additionally, attribute two (telephone number), can be formed with any of the traditional seperator chracters; {().- or space) in order to make the entries more legible. You may also add any notational data (such as address etc) to the right of the two significant attributes (see the example above). Finally, you may include comment lines which begin with a hash (#).

Once "committed", the central directory and speed dial register are synthesised into the correct format for each supported phone type and loaded to the tftp/http provisioning entries for each phone on the system. The next time a phone is rebooted, the directory and speed dial data will be automatically loaded.