[SR-Users] Message Waiting

Charles Chance charles.chance at sipcentric.com
Tue Mar 12 20:54:08 CET 2013


The script you specify (e.g. externnotify=myscript.sh) runs every time a
new message is left for a user or when a user exits the VoiceMailMain()
application (for instance, if they have dialled in to clean up their
mailbox).

The voicemail application passes certain things as parameters to your
script such as number of new/old messages etc - for more info and example
script take a look here:
http://www.voip-info.org/wiki/view/Asterisk+config+voicemail.conf

Cheers,

Charles



On 12 March 2013 19:45, Daniel W. Graham <dan at cmsinter.net> wrote:

> Can you describe how your implementation works without having to scan
> directory/database for changes?****
>
> ** **
>
> -Dan****
>
> ** **
>
> *From:* sr-users-bounces at lists.sip-router.org [mailto:
> sr-users-bounces at lists.sip-router.org] *On Behalf Of *Charles Chance
> *Sent:* Tuesday, March 12, 2013 3:42 PM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] Message Waiting****
>
> ** **
>
> The script method works fine for us - but we use the externnotify option
> in voicemail.conf instead of scanning for changes at directory/database
> level.****
>
> ** **
>
> Regards,****
>
> ** **
>
> Charles****
>
> ** **
>
> On 12 March 2013 19:32, Daniel W. Graham <dan at cmsinter.net> wrote:****
>
> While I have seen other posts I have not found anything that describes my
> scenario.****
>
>  ****
>
> Kamailio sets in front of a group of asterisk servers which are used in a
> round robin dispatch group. All asterisk servers share a common database in
> which voicemail boxes are defined and messages are stored.****
>
>  ****
>
> I’m looking for a way to make message waiting work in this example. I have
> tried creating a view with basic peer information for asterisk to use for
> message notification, however asterisk does not ‘see’ these peers until a
> call is made to the specific user and the peer info is retrieved from the
> database, which can delay notifications severely rendering them useless. I
> also want to avoid sending a copy of the registrations to asterisk servers,
> as the purpose of the distributed system is to eliminate the large number
> of sip registrations asterisk needs to manage.****
>
>  ****
>
> 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.****
>
>  ****
>
> What are others doing / what do others recommend as the best way to handle
> message waiting with a situation where kamailio sets in front of a
> voicemail server? ****
>
>  ****
>
> Any input is appreciated.****
>
> Dan-****
>
>  ****
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users****
>
> ** **
>
>
> 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.****
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>

-- 
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/20130312/593da4d7/attachment.htm>


More information about the sr-users mailing list