Asterisk monitoring via sipsak not working #179
Conversation
…urce agent script. As a result a 404 reply was being sent back by asterisk to the SIP OPTIONS sent. I haven't been able to get sipsak to send valid contact details in this mode so have instead made it do a SIP REGISTER. The resource agent now accepts an additional parameter=monitor_password, this is the sip account password you register with. I've tested the resource agent successfully against asterisk 1.6 and 1.8.18. Cheers, John [email protected]
|
Thank you for the patch. Detailed comments in line notes. |
|
gnuday: Do you want to update your contribution based on the comments? |
|
-----BEGIN PGP SIGNED MESSAGE----- Hi, Yes although I'm a little snowed under at the moment with work. I'll On 21/01/13 16:00, Dejan Muhamedagic wrote:
-----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJQ/WyQAAoJEJDWDcq/312/6RMP/1CDZYLRnayB6RZmZXmE7cKk |
|
This doesn't automatically merge anymore, please rebase. |
Hi,
When the original resource agent script called sipsak, it was sending a sip packet with an invalid contact URI. As a result Asterisk was sending back a 404 error in reply to the SIP OPTIONS sent. I haven't been able to get sipsak to send valid contact details in this mode so instead have made it do a SIP REGISTER. The resource agent now accepts an additional parameter=monitor_password, this is the sip account password you register with. I've tested the resource agent successfully
against asterisk 1.6 and 1.8.18.
Cluster configuration example of use
primitive resASTERISK ocf:heartbeat:asterisk
params realtime="false" monitor_sipuri="sip:[email protected]" \ monitor_password="eo34d84nvhekr"
op monitor interval="60"
op start interval="0s" timeout="120s"
op stop interval="0s" timeout="120s"
meta migration-threshold="1"
Cheers,
John
[email protected]