In order to configure the WARP Pager the administrator will be required to create two files. One file will contain SIP User Agent account credentials needed to register with the host service provider. The other is made up of a list of phones designated as Page targets identified by the phones MAC address, registered directory number or extension and Page group designations.
If you intend for the Pager to retrieve its configuration via (T)FTP then the files are named using the following format < WARP Pager MAC Address >.. The MAC Address is used so the the Pager is able to locate configuration files specific to it on a shared server.
eg. '001e840006d9.cfg' and '001e840006d9.phones'
The other format is used when provisioning by USB key. The naming convention for this process is simply config.cfg and config.phones.
The config.cfg or < WARP Pager MAC Address >.cfg is comprised of the following parameters and their respective comma delimited values:
The following are a list of mandatory parameters:
username - The directory or extension number assigned by the host ed PBX service provider.
auth_username - The authentication name provided by the host service provider used for registration challenges.
auth_username - The authentication password provided by the host service provider used for registration challenges.
domain - The domain used for registration with your host service provider. This can be either be an FQDN or IP address. An example would be 5544@192.168.1.1 or 5544@sip.pika.net where 192.168.1.1 and sip.pika.net represent the domain.
domain_proxy - The IP address or FQDN used to proxy all SIP signaling. If this value is different that the domain then all SIP messaging will be sent to the 'domain_proxy' address. If no proxy is required then use the same address provided in the 'domain' parameter.
The remaining parameters are optional:
callerid_name - The value associated with this parameter overwrites the the caller-id provided by the service provider and instead delivers this value to each of the Page targets.
answer_string - This parameter defines the payload for the 'Alert-Info ' SIP header sent in the INVITE request to each Pager Target. Some phone specifically Polycom utilizes this parameter for Page activation and the payload is customizable by the phone administrator. The default value for this parameter is 'Ring Answer'. If you use this parameter take note that '#' character will signify white space. For instance, 'Ring Answer' would be defined as 'Ring#Answer'.
expiration - This parameter the means to manually configure the registration refresh interval of the WARP Pager SIP User Agent. The value is represented in seconds default value is 30.
dtmfmode - The mode used to receive DTMF digits from the external SIP server. This parameter is used only for the WARP Pager 30SZ. The parameter settings are:
auto - combination of RFC2833 and In-band.
rfc2833
inband
info
The config.phones or < WARP Pager MAC Address >.phones is comprised of the following comma delimited parameters that identify each Pager Target. These targets are identified by their MAC addresses, directory or extension numbers followed by the Page Groups or Zones they are members of. The example below illustrates this format .
00:04:f2:28:5f:e6,6135551234,0,1,3
00:04:f2:27:82:84,6135554321,0,2,3
There are 10 available Page Group definitions 0-9. Groups 0 and 1 will include the Line-Out audio port for overhead paging. If there are more than 30 targets programmed in the file for the 30SZ model any entries beyond 30 are ignored. This also applies to the WARP Pager 15 except that no more than 15 entries will be used.
Here is a link to some examples file:
ftp://ftp.pikatech.com/outgoing/WarpPager/Configuration-File-Examples/