[asterisk-bugs] [JIRA] (ASTERISK-24763) CalDav calendar fails to process day long event when time is set to 00:00

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-24763:
-----------------------------------

    Summary: CalDav calendar fails to process day long event when time is set to 00:00  (was: caldav integration doesn't work properly)

> CalDav calendar fails to process day long event when time is set to 00:00
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-24763
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24763
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_calendar_caldav
>    Affects Versions: 13.0.1, 13.1.1
>         Environment: debian wheezy amd64
>            Reporter: juanmol
>            Assignee: Rusty Newton
>            Severity: Critical
>         Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, 6.png, 7.png, 8.png, 9.png
>
>
> trying with periodic events the caldav integration doesn't works. At the moment of creation the event with any client tool, you can see updated events in asterisk, but in few hours the system doesn't works. For example:
> {noformat}
> asterisk -rx 'calendar show calendar calendar_matraca_es'
> Name              : calendar_matraca_es
> Notify channel    : SIP/TROLOLO
> Notify context    : calendar_event_notif
> Notify extension  : s
> Notify applicatio : Playback
> Notify appdata    : tt-weasels
> Refresh time      : 1
> Timeframe         : 2
> Autoreminder      : 10
> Events
> ------
> Summary     : fuera matraca_es
> Description : out
> Organizer   :
> Location    : 10
> Categories  :
> Priority    : 0
> UID         : 52339C61-408B-487D-AA34-9F7E3FB57B4A
> Start       : 2015-02-05 12:00:00 AM +0100
> End         : 2015-02-06 12:00:00 AM +0100
> Alarm       :
> Summary     : fuera matraca_es
> Description : out
> Organizer   :
> Location    : 10
> Categories  :
> Priority    : 0
> UID         : 52339C61-408B-487D-AA34-9F7E3FB57B4A
> Start       : 2015-02-05 12:00:00 AM +0100
> End         : 2015-02-06 12:00:00 AM +0100
> Alarm       :
> {noformat}
> it's a duplicated item with the same UID. If i see the same calendar with other clients, it shows correctly. For example with {{CalDAVClientLibrary}}:
> {noformat}
> ./runshell.py --server http://server:5232
> User: asterisk
> Password:
> cd asterisk/13A69070-B7CA-4F82-A698-1FFFCA73EBD4/
> /asterisk/13A69070-B7CA-4F82-A698-1FFFCA73EBD4 > ls
> 52339C61-408B-487D-AA34-9F7E3FB57B4A.ics
> 612ACABD-5BD0-44BE-9378-AC598A3F47E9.ics
> 8394DB77-2DCB-45A1-AE79-7FA534EB44D4.ics
> C68122B7-A0C1-419A-A10A-F6A6F0DBBCEA.ics
> E3516CC9-899C-42B3-A3C2-59E5AC76769C.ics
> {noformat}
> as you can see, there are only one {{52339C61-408B-487D-AA34-9F7E3FB57B4A.ics}} file and others event more that needs to be showed in asterisk calendar show command (same time and date).
> I have test with other asterisk 10.5.1 connected to the same server (same user/pass and conf file) and it works perfect.



--
This message was sent by Atlassian JIRA
(v6.2#6252)