[asterisk-bugs] [Asterisk 0014771]: [branch] Asterisk iCalendar Integration

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14771 
====================================================================== 
Reported By:                lmadsen
Assigned To:                twilson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14771
Category:                   Resources/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Target Version:             1.6.3.0
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-26 16:13 CDT
Last Modified:              2009-03-31 18:35 CDT
====================================================================== 
Summary:                    [branch] Asterisk iCalendar Integration
Description: 
This is a place holder for tracking any outstanding issues with the
iCalendar integration in Asterisk.

Currently the iCalendar integration is in a branch available here:

http://svn.digium.com/svn/asterisk/team/twilson/calendaring
====================================================================== 

---------------------------------------------------------------------- 
 (0102511) twilson (administrator) - 2009-03-31 18:35
 http://bugs.digium.com/view.php?id=14771#c102511 
---------------------------------------------------------------------- 
I have fixed the segfault, and updated the code to work with the new
exports code (the calendar_config variable is shared between the modules,
and wasn't being properly exported).

If I adjust the resolutions, I will just make both minutes.  For
development purposes, I wanted to be able to do quick refreshes so I didn't
have to wait around to see if changes worked, etc.  In real life, I doubt
that anyone would really want to query their server more than 1/minute.

I could probably make the CALENDAR_QUERY_RESULT change.  It is a long
function name to type many times.  :-)

I also need to add read/write support for handling attendees.  They were
harder since they are actually a list, instead of just a key/value pair. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-31 18:35 twilson        Note Added: 0102511                          
======================================================================