No inbound Service - Maintenance Related?

**usa2k** · 07-15-2009 09:18 AM

Mine has been good. Don't know how long after a test call I should see history? All previous history is on vPanel.

Network preferences say "You are currently connected to:"

Devices show I am registered.

They are readying enhancements of some sort, but I don't expect that any are live ...

Inbound works from my cell.

**VOIPoTim** · 07-15-2009 09:39 AM

This was unrelated to the maintenance.

One of our system admins was not following company policy and was doing work (rotating logs and adding new logs) on one of the nodes when they should not have been

An entire partition filled almost instantly with new logs and this caused a load issue on it.

There is no reason this should have happened and it would have not if policy had been followed.

**fisamo** · 07-15-2009 09:56 AM

Originally Posted by dswartz

could you share the script, please? having something like that just moved up on my list of priorities, and while i know i can code this, i'd rather not reinvent the wheel

thanks!

It would have taken me a while to learn how to code this, not because it seems terribly difficult, but because I have pretty much zero background in PHP, perl, or bash programming. I'm all for not reinventing the wheel!

If you go to this thread on the pbxinaflash forum, there are two scripts of interest.

http://www.pbxinaflash.com/forum/showthread.php?t=1968

Post #12 has a bash script that goes in the 'monitor trunk failures' box in FreePBX. This script will only run if someone attempts to make a call on that trunk and the call fails. (It won't monitor registrations.)

Post #31 has a perl script that does monitor registrations. I took it as is (thanks to those who posted and refined it, by the way!!) and set it to run every 5 mins via cron.

**dswartz** · 07-15-2009 09:57 AM

Ah, thanks. Since I am now running PIAF this is cool

**fisamo** · 07-15-2009 10:02 AM

NP. It looks like the failed call script (post 12) should work with any Asterisk/FreePBX distro, and the trunk monitoring one (post 31) should work with any Asterisk implementation, if my understanding of Asterisk is correct.

**voxabox** · 07-15-2009 12:38 PM

uhm,
MISSING "start time" in "call history"

edit: Never mind, someone must have read my mind, it's back now!

**sr98user** · 07-15-2009 12:55 PM

I lost registration again with 208.43.68.151 and it came back after 5 minutes.

**scott2020** · 07-15-2009 04:54 PM

I am having a lot of trouble staying connected to the new nodes, such as the 174.37.x.x IP addresses. My asterisk box is set to qualify and connections to that IP keeps dropping and re-registering. It has been happening all day.

EDIT: My trace routes show a lot of loss in the tbone.rr.com paths. I hope we don't have to rely on Road Runner to carry our traffic.

EDIT2: These rr.com routes change every time. Sometimes my traffic goes from Missouri to LAX and all the way back to East, when I trace to there. It is really terrible. 300ms + latency and tons of lost packets. Traces to west are the best so far so I might change it.

**VOIPoBrandon** · 07-15-2009 05:09 PM

Originally Posted by scott2020

I am having a lot of trouble staying connected to the new nodes, such as the 174.37.x.x IP addresses. My asterisk box is set to qualify and connections to that IP keeps dropping and re-registering. It has been happening all day.

EDIT: My trace routes show a lot of loss in the tbone.rr.com paths. I hope we don't have to rely on Road Runner to carry our traffic.

Scott -- this node has been stable if you are seeing service issues, it may definitely indeed be between the route of your network and ours. Have you tried any of our other nodes?

Please try a connection to sip-east01.voipwelcome.com -- advise how this works out for you, thanks!