[SR-Users] Message Waiting

[Daniel W. Graham]

I've been struggling getting sipsak to perform srv lookups. I have exhausted my options and wanted to reach out and see if there was any input.

I compiled c-ares library and afterwards compiled sipsak, sipsak configure script detected the c-ares librarys, however when performing any sipsak command in which requires srv lookup I get a segmentation fault.

Anyone seen this or have another recommendation?

From: sr-users-bounces at lists.sip-router.org [mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Daniel W. Graham
Sent: Saturday, March 16, 2013 12:47 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Message Waiting

Yep, that was it. I forgot the port is included in the dispatcher list. Once I made the changes the forward worked. Now just to address sipsak srv lookups so I can make it work with multi-domain and it should be set.

Thanks again!
-Dan

From: sr-users-bounces at lists.sip-router.org<mailto:sr-users-bounces at lists.sip-router.org> [mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Charles Chance
Sent: Friday, March 15, 2013 5:43 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List
Subject: Re: [SR-Users] Message Waiting


>From past experience you may need to add another entry to the dispatcher list with a different setid because no doubt sipsak is sending the notify from a different port to that which Asterisk is listening on.

Eg. setid - 10, destination - sip:<asterisk_ip>:5065<sip:%3casterisk_ip%3e:5065>

Then - if(ds_is_from_list("10"))...

Cheers,

Charles
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 at lists.sip-router.org<mailto:sr-users-bounces at lists.sip-router.org> [mailto:sr-users-bounces at lists.sip-router.org<mailto:sr-users-bounces at 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 at lists.sip-router.org<mailto:sr-users at lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org<mailto:sr-users at lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

www.sipcentric.com<http://www.sipcentric.com/>

Follow us on twitter @sipcentric<http://twitter.com/sipcentric>

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham B7 4EJ.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130702/7993f235/attachment.html>