Yeah, that's right the dreaded spelling mistake.

Provisioning the WARP Pager requires the creation of two configuration files. These provide the SIP User Agent account information required to register with a hosted PBX service provider, SIP phone Page targets, associated directory number and Page Group affiliation. A simple spelling mistake may prevent registration with the service provider or failure to locate all SIP phone Page targets.

The names of these files are dependent on the means in which they are administered. If they are created for provisioning via USB key then they will be named config.cfg and config.phones. Typical configuration dictates that they are retrieved via (T)FTP. In this case they are named <WARP Pager MAC Address>.cfg and <WARP Pager MAC Address>.phones (eg. 001e840000ce.cfg) which promotes Pager specific configuration file retrieval.
I have provided example files for you reference here:

001e840000ce.cfg / config.cfg:

This file contains the SIP User Agent account information used for registration with a hosted PBX service provider such as Broadsoft. The file consists of numerous parameters that are comma delimited from there associated values. Below is a list of typical parameters there possible values and brief functional explanation.

username,6135551234 -> Directory Number to register with BroadSoft
auth_username, some_name -> Username used for authentication
auth_password,password1234 -> Password used for authentication
domain, -> Domain used in registration URI
domain_proxy, -> Destination for the Registration Request
callerid_name,WARP-PAGER -> Optional: Call ID of pager. Default is WARP-PAGER
answer_string,Ring#Answer -> Optional: String used in the SIP ‘Alert-Info:’ header. Default is ‘RING#ANSWER’ (‘#’ denotes a space)
expiration,3600 -> Optional: Registration expiry time in seconds. Default is 30 seconds

The examples above will generate a REGISTER request that looks as follows:

Packet is sent to
Via: SIP/2.0/UDP;branch=z9hG4bK30f51f6f;rport
From: <>;tag=as50cf540f
To: <>
Call-ID: 322051c90f1c93ef4dc24c890e2ea146@
Max-Forwards: 70
Expires: 3600
Contact: <sip:warppager@>
Event: registration
Content-Length: 0

So if '' was misspelled well the FQDN likely would not resolve via DNS and the SIP packet would fail to transmit. If the username, auth_name or auth_password had a spelling mistake the registration with the service provider will fail.

If a mandatory parameter like 'username' was spelled incorrectly then the provisioning would fail a log will be generated and an error code written to the LCD.

It is imperative that an administrator check and re-check that the input parameters and there values are correct.

001e840000ce.phones / config.phones:

This file contains the MAC addresses of all SIP phone Page targets, there associated directory or extension numbers and any assigned page groups. As in the previous file all parameters are comma delimited as shown in the following example:


The first parameter must always be the MAC address of the SIP phone targeted for the page and MUST include the colon ':' separators. The next parameter is the directory number or extension the WARP Pager will use to Page the target. The remaining coma separated delimiter are the Page Groups each phone is a member of. Groups 0 and 1 also include the line-out for overhead paging.
A missing colon or miss typed MAC address will prevent the WARP Pager from locating the phone on the LAN. A miss entered directory or extension number can result in a phone rejecting the Page and a miss placed comma or lack there of may cause unexpected configuration results.

As rule when creating these file... check, re-check and check again!