Polycom SIP response 500 “Internal Server Error” – SOLVED

I was often seeing something like
— Got SIP response 500 “Internal Server Error” back from 192.168.0.10
on my asterisk server. Actually, its running the trixbox installation but asterisk is the application reporting the errors.

While running polycom firmware up to 2.1.1 this error appears. If you change to 2.1.2, the error goes away.

UPDATE: 2007/07/10

It appears that its come back. After a particularly nasty asterisk crash, im getting these errors again.

Bugger.

Asterisk alarm receiver – using triggers, mysql5

This requires MySql 5 or above as it uses triggers.

Asterisk alarm receiver – using triggers, mysql5

This is really rough but it works so far. YMMV.
butchered together by kevin at ilb dot com dot au
2006 07 29 – version 0.00 alpha

email me for any help or information.

This code has been shamelessly butchered from wakeup.php (http://www.voip-info.org/tiki-index.php?page=Asterisk+tips+Wake-Up+Call+PHP)
by Andy Wysocki awysocki at absoftware dot_here com

Andy, please don’t hate me.
Please don’t blame Andy for the complete lack of style, it was a quick fix and it works. Andy’s code had much niceness about it which i
removed while developing. I should have put it back and probably will one day.

Flow of events….
1. Alarm panel sends codes to asterisk box
2. Shell script is run by alarmreceiver
inserts alarmcode into alarm_event
triggers output_events creation
3. shell script then looks at output_events rows to see what work it has to do
4. shell script then tries to create call files (this step is also triggered by cron)

If its a call…
1. Plays message “The alarm has triggered”
2. plays site name using flite
3. plays zone, event code etc (read alarm.php for more info)
4. lets the user press 1 to ack. they get 3 calls if its not acked. alarm_calls for limits


eventcmd = /usr/local/ilb/asterisk/alarmproc (or whereever you want to put it)


/usr/local/ilb/asterisk/alarm_calls


alarm-out
exten => s,1,NoOp(ID == ${ID})
exten => s,n,AGI(alarm.php,ID=${ID})
exten => s,n,Hangupmake an alarm database and upload the sql into it
update triggers


* alarm_event contains the actual events, a trigger runs to …
** set all the appropriate cols
** insert rows into output_events table based on the triggers table
* areas contains the list of areas for each site
* users contains the list of users for each site
* event_groups is the major headings for each category of events
* event_types is the individual events that can be reported
* site is the list of sites with site codes that you listen for
* triggers is the table that has the alerting rules. pretty much, if its blank, it matches.
* action of call means dial
* action of email means emailalarmproc is called by alarmreceiver
alarm_calls just makes the calls (and is called by alarmproc and crontab)edit alarmproc and alarm_calls
* change server.domain.com.au to your mysql server
* set the username/passwords accordingly
* set callerid appropriately
* edit the sendmail line and adjust the from address

Evolution Smevolution

Ok its old, but ive been thinking about it for a while. Heres the quotes from Jon Stewart

Why are we here? And how did we get here? Not here necessarily, but HERE! For most of human history the answer took the form of what were called creation myths — traditional stories explaining our origins. They tended to follow a basic template. Typically a deity, either animalistic, anthropomorphic, or bearded, engages in some mystical, wonderous process, that eventually produces the misshapen progenitors of the human race — an thus becomes man. These myths comforted man, by allowing him to laugh at other cultures creation myths. For instance, the Aztecs say we were dug out of the earth by a giant pig. Everyone knows we sprouted from the heavenly ear of corn.

But the rise of Christianity brought a new Creation story to the forum. In six days, man was formed from a lump of clay. And woman sprung from man’s rib. It just made sense.

TreadingLightly 004

In Episode 4 of Treading Lightly…

This week we talk about;

  • Home vegetable gardens and chickens. (Kevin got Chickens !)
  • Clipsal cent-a-meter. (a little more detail)
  • Only a very little bit about the Prius. (Kevin got the second family Prius)
  • More details about how green power works
  • Some basic info on carbon credits and purchasing other peoples green options. We are looking at setting a carbon purchasing facility in australia.
  • Some basic water bore discussion

Over the next few episodes, we will be discussing….

  • Sea Shepheard
  • Water tanks (rain water)
  • Grey Water
  • Bores
  • Clipsal CBUS (and why it can be, but isn’t always good for the enviroment)
  • Renta-bike and community bicycle programs.
  • Mud brick houses (With a special guest who is in the process of building it).

 

Any questions you would like to have discussed or feedback on the show, you can email us here or call (02) 42270001 in Australia and +61 2 4227 0001 from everywhere else!

Treading Lightly #003 (Finally !)

In Episode 3 of Treading Lightly , we go some way to explain why the huge delay between shows 2 and 3.

This week we talk about;

  • Al Gores’ movie. (www.climatecrisis.net)
  • Home vegetable gardens and chickens.
  • Clipsal cent-a-meter.
  • Only a very little bit about the Prius.
  • Integral energy green power options
  • Some basic info on carbon credits and purchasing other peoples green options.

Over the next few episodes, we will be discussing….

  • Sea Shepheard
  • Water tanks (rain water)
  • Grey Water
  • Bores
  • Clipsal CBUS (and why it can be, but isn’t always good for the enviroment)
  • Renta-bike and community bicycle programs.
  • Mud brick houses (With a special guest who is in the process of building it).
  • A more detailed discussing about the carbon purchasing

 

Any questions you would like to have discussed or feedback on the show, you can email us here or call (02) 42270001 in Australia and +61 2 4227 0001 from everywhere else!