Thanks to all for the input. I wrote a script to call sipsak to generate the notify and all seems to be working, however am having issues getting kamailio to forward to the endpoint.
The notify is sent unsolicited so I figured I could just add a statement such as:
if(is_method("NOTIFY") && ds_is_from_list("1")){ route(LOCATION); .....etc
(asterisk server sending notify is in the ds list.)
What would be the proper way for kamailio to handle this?
-----Original Message----- From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Juha Heinanen Sent: Thursday, March 14, 2013 3:44 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Message Waiting
Jon Farmer writes:
I have also seen a couple of script methods that look at the voicemail directory structure for file changes and trigger an application like sipsak to generate the notifications and let kamailio relay them. From what I see, the consensus is not to go this route. In my case the script would need to look at the database level, and maybe some sort of database trigger could be used.****
...
I have been using sipsak to generate the NOTIFY for the last 7 years. It never has caused an issue. I have a setup similar to you but I wrote a customer voicemail application in AGI instead of using the built in Asterisk app.
my sems voicemail application is using xmlrpc to make pua_publish call to presence server when status of user's message box changes.
-- juha
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users