PIKA Forum FAQ

Here you can find answers to questions about how the board works. Use the links or search box below to find your way around.

Some of my phones are just ringing and not auto-answering the page?

Verify that the phone was located by the WARP Pager on boot up. To verify this log into the WARP Pager, enter the ‘current’ directory and view the ‘pager.log’ file. Look for a log similar to this example:

2010-10-15, 02:34:33 PM, /persistent/pager/scanner_adv.sh: A phone with 0:8:5d:12:88:23 was not found

This will also show if you missed a colon or entered the MAC address improperly.

My WARP Pager is unable to register with my hosted PBX service provider?

First ensure that the WARP Pager is connected to a non V-LAN tagged port. Then verify that the’ username’, ‘auth_username’ and ‘auth_password’ in the configuration files match what is programmed on the hosted side. If these are correct then verify that the ‘domain’ and ‘domain_proxy’ strings are set correctly.

If the ‘domain’ or ‘domin_proxy’ strings are set to something unexpected by the hosted service provider then registration will fail.

If the FQDN in ‘domin_proxy’ or ‘domain’ is misspelled then it is likely that DNS is unable to resolve the address and therefore no SIP packets are being transmitted. To verify whether this is the case log into the WARP Pager, enter the ‘current’ directory and view the ‘messages’ file. If a log similar to this example is present then your ‘domain_proxy’ or ‘domain’ settings are incorrect:

[Oct 15 12:56:05] WARNING[13900] chan_sip.c: Probably a DNS error for registration to 103@192.168.68.50@sip.testsomeproxy.net, trying REGISTER again (after 20 seconds)
[Oct 15 12:56:25] WARNING[13900] chan_sip.c: No such host: sip.testsomeproxy.net

If this is not the issue then verify that the hosted service provider is receiving the registration requests and there is no firewall blocking the VoIP messaging.

All my paged Polycom phones just ring and do not auto-answer the page?

It is likely that you Polycom configuration needs to be augmented. Please see the following forum post:

http://forum.pikatechnologies.com/showthread.php?614-What-to-do-if-your-Polycom-phones-just-ring-and-do-not-auto-answer-a-Page

When I press a DTMF key to indicate the Page group nothing occurs?

I am calling the WARP Pager SZ30 and getting the group Page IVR.
However, when I press a DTMF key to indicate the Page group nothing occurs?

By default the WARP Pager is configured to support only RFC2833 DTMF input.

It is likely that the phone you are using is set to use only In-Band DTMF signaling or sending digits via SIP INFO methods.

You can change your phone to use only RFC 2833 or you can modify the WARP Pagers configuration. There is a configuration parameter called ‘dtmfmode’ that may be added to the < WARP Pager MAC Address >.cfg file (eg. 001e840000ce.cfg) or config.cfg if using a USB key for provisioning. Valid values for this parameter are:

info : Use SIP INFO messages for DTMF digits

rfc2833 : Use RFC2833

inband : Inband DTMF (requires 64 kilobit codec -alaw, ulaw)

auto : Use RFC2833 if offered, otherwise, use inband.

Add the ‘dtmfmode’ parameter to the configuration file and the appropriate value set. Place the new configuration file back on the (T)FTP server and reboot the WARP Pager or insert you USB key allow the unit time to update and reboot when instructed on the LCD of the WARP Pager.

Note: If this single phone is using the SIP INFO method then it is highly recommended that you modify the configuration of this phone. Otherwise all other phones will need to use the SIP INFO to pass dialed digits onto the WARP Pager.

I insert my USB key into the WARP Pager but nothing happens?

It is likely that your USB key is FAT16 formatted and therefore not recognized by the WARP Pager.

Re-format your USB key with a FAT32 file system, re-apply your configuration files and then insert it back into the WARP Pager.

My configuration files are not found on my (T)FTP server?

Verify that a valid (T)FTP server address in being supplied to the WARP Pager via DHCP options 66 or 150.

Verify that the configuration files are present in the base directory of the (T)FTP server and the file names are correct. These files should be named in the following all ‘lower case’ format < WARP Pager MAC Address >.cfg and < WARP Pager MAC Address >.cfg (eg. 001e840000ce.cfg and 001e840000ce.phone). If the MAC address is incorrect the WARP will be unable to find its configuration files.

If using FTP verify that you have set the required user name and passwords correctly.

If the problem persists then view the WARP Pager logs for more diagnostic information using the ‘pager’ user account default password ‘pikapika’ . Enter directory named the ‘current’ and view the ‘pager.log’ file. This log will provide detailed information required to isolate the issue.

Is there an way to perform a call trace on the WARP Pager?

Yes, in fact a full packet capture trace utility is provided on board the WARP Pager.

You can use the application pcaplogs to collect network packet data. The syntax is as follows:

pcaplogs {on | off} [-h] [-n packets]

-h - Displays help and exits.
on - Enables the pcap logging when the system starts.
off - Disables the pcap logging when the system starts and stops any current pcap logging.
-n packets - The number of packets to capture before logging stops. The default value is 1000.

You must restart the WARP Pager to enable or disable PCAP logs. Logging stops automatically either when the requested number of packets has been collected or the next time the WARP Pager restarts.

To enable logging, you must log on to the WARP Pager using an SSH client. The WARP Pager has a pager user account and the corresponding default password is pikapika.

To enable pcap log, type sudo pcaplogs on at the Linux command prompt and then type sudo reboot to restart the WARP Pager. To enable pcap logs and change the number of packets to collect, type sudo pcaplogs on –n packets at the Linux command prompt and then type sudo reboot to restart the WARP pager.

You can set the number of packets to collect before or while logs are enabled. Changes take effect on the next restart. To stop logging, restart the WARP Pager.

The trace log generated is called 'pager.pcap' and will reside in the '/logs/current' directory until a reboot is performed. When the WARP Pager is rebooted then the 'current' log directory will be renamed to 'current-1' as the Pager supports a rotation log history for 5 reboots.

Search FAQ

Select this option if you would like your search to look in the text of FAQ items as well as their titles.

Select an option here to specify how you would like your search query to be treated. 'Any words' will return the most numerous but possibly least relevant results, while 'Complete phrase' will return only results that contain exactly what you are searching for.