- Oct 12, 2007
- Reaction score
yum -y install coreutils curl git epel-release yum -y --enablerepo=epel install jq
Have you contacted Skyetel for support??Followed the install guide for Raspberry Pi. The new endpoint group was created in Skyetel and the initial IP address was populated. Subsequent public IP address changes have not updated to the endpoint. I don't see a new cron entry, nor am I am able to find logging for the cron when run. Any tips on what to check in logs or the cron job to ensure that install is applied correctly?
Piping to logger is just a way of jacking into the operating system's method of logging. The "-p X.Y" option is just telling the logging system where to send the log message (facility) and how important it is (log level). It's a somewhat portable way to let Raspbian, CentOS, or Debian choose whatever their 'normal' log files are use them.Pipping logger -p is something that I am not familiar. Where would I look for the resulting log file to review?
Yes, I kind of got a generic response.
OH MY LORD!! What a rookie mistake! It was my IP address on my end. We been getting a lot of power outages because of the high winds in NY. One visit to whatsmyip.org and then updated on the Skyetel endpoint and BAM everything went green again! Thanks ramageai!@Deltahotel If it helps with your troubleshooting, the only way that Endpoint Health will appear as "red" is if Skyetel's published IP addresses are actively sending SIP messages to your IP address and not getting a response back. That is almost always caused by a firewall preventing the messages arriving at your PBX, or your PBX is not configured to respond to the messages, or maybe your IP has changed?