asterisk users - Apr 2005 - MWI for SER and Asterisk - ast_data vs "realtime"

Bug 002980 contains a patch that delivers MWI from Asterisk to SIP clients
registered with SER. It requires ast_data which doesn't patch the current
CVS HEAD. Since I need MWI and I want Asterisk and SER to store data in a shared
database I could:
- use an old version of Asterisk and install ast_data. The patch author runs a
large-scale clustered SER/Asterisk environment and believes ast_data to be
superior to "realtime". However "realtime" may now have
developed to the point that these objections are no longer relevant. Specific
problems still seem to be SIP clients behind NAT and voicemail notifications
(both very important to me)
- use realtime and write something that gives me the functionality required and
hope that the NAT and voicemail issues get fixed soon. Apart from it being a
pain to write this I also have not heard of anyone using SER + Asterisk
"realtime" in a large-scale production environment. If anyone has had
any such successes it would be good to know about them.

I would appreciate thoughts on these (or any other) alternatives.

Regards

Cameron
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050406/392ee53c/attachment.htm

I'm not familiar with the use of the word "realtime" in this
context.
What do you mean? I have been using vmnotify to toggle MWI
on 79x0 phones that are registered to SER and use Asterisk for
voicemail and it works great. Admittedly we have a small installation
(about 75 users) but so far this approach works reliably.



Cameron Beattie wrote:
> Bug 002980 contains a patch that delivers MWI from Asterisk to SIP 
> clients registered with SER. It requires ast_data which doesn't patch 
> the current CVS HEAD. Since I need MWI and I want Asterisk and SER to 
> store data in a shared database I could:
> - use an old version of Asterisk and install ast_data. The patch 
> author runs a large-scale clustered SER/Asterisk environment and 
> believes ast_data to be superior to "realtime". However
"realtime" may
> now have developed to the point that these objections are no longer 
> relevant. Specific problems still seem to be SIP clients behind NAT 
> and voicemail notifications (both very important to me)
> - use realtime and write something that gives me the functionality 
> required and hope that the NAT and voicemail issues get fixed soon. 
> Apart from it being a pain to write this I also have not heard of 
> anyone using SER + Asterisk "realtime" in a large-scale
production
> environment. If anyone has had any such successes it would be good to 
> know about them.
>  
> I would appreciate thoughts on these (or any other) alternatives.
>  
> Regards
>  
> Cameron
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users@lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>

Matthew Boehm wrote:
>> Bug 002980 contains a patch that delivers MWI from Asterisk to SIP
>> clients registered with SER. It requires ast_data which doesn't
>> patch the current CVS HEAD. Since I need MWI and I want Asterisk and
>> SER to store data in a shared database I could:
>> - use an old version of Asterisk and install ast_data. The patch
>> author runs a large-scale clustered SER/Asterisk environment and
>> believes ast_data to be superior to "realtime". However
"realtime"
>> may now have developed to the point that these objections are no
>> longer relevant. Specific problems still seem to be SIP clients
>> behind NAT and voicemail notifications (both very important to me)
>> - use realtime and write something that gives me the functionality
>> required and hope that the NAT and voicemail issues get fixed soon.
>> Apart from it being a pain to write this I also have not heard of
>> anyone using SER + Asterisk "realtime" in a large-scale
production
>> environment. If anyone has had any such successes it would be good
>> to know about them. 
Umm..did you not read that whole bug report? This patch is not stable
and not very good. It is currently being worked on by Mark. It should
not contain anything related to ast_data so you might as well remove
this patch and wait for a better version from Mark.

ast_data is replaced by ARA (Asterisk RealTime Architecture). That is
why you can't compile ast_data on HEAD.
 
 ARA has fixed the NAT/MWI issues by using RTC (RealTime Cache).
 
 -Matthew