Browse code

tmrec: updated the content of the readme file

Daniel-Constantin Mierla authored on 01/09/2015 07:18:17
Showing 1 changed files
... ...
@@ -16,7 +16,15 @@ Alex Balashov
16 16
 
17 17
    <abalashov@evaristesys.com>
18 18
 
19
+Edited by
20
+
21
+Richard Fuchs
22
+
23
+   <rfuchs@sipwise.com>
24
+
19 25
    Copyright � 2012 asipto.com
26
+
27
+   Copyright � 2012 Sipwise GmbH
20 28
      __________________________________________________________________
21 29
 
22 30
    Table of Contents
... ...
@@ -138,7 +146,11 @@ modparam("tmrec", "separator", ";")
138 146
        subsequent intervals do not overlap. For non-recurring intervals,
139 147
        durations of any positive length are permitted. Zero-length
140 148
        duration means "forever". Negative-length durations are not
141
-       allowed. See RFC 2445 for the format of duration.
149
+       allowed.
150
+       See RFC 2445 for the format of duration. In short for common cases
151
+       when the duration doesn't exeed a data, it must start with PT
152
+       followed by the value for hours, minutes or seconds - e.g., a
153
+       duration of 8 hours must be written as PT8H.
142 154
      * frequency - can be one of the following values: "daily" - specify
143 155
        repeating periods based on an interval of a day or more; "weekly" -
144 156
        specify repeating periods based on an interval of a week or more;
... ...
@@ -208,7 +220,7 @@ modparam("tmrec", "separator", ";")
208 220
 
209 221
    Next is an example of evaluating multiple Byxxx parameters.
210 222
 
211
-   startdate="20100101T093000" duration="10H30M" frequency="yearly"
223
+   startdate="20100101T093000" duration="PT10H30M" frequency="yearly"
212 224
    interval="4" bymonth="3" byday="SU"
213 225
 
214 226
    First, the interval="4" would be applied to frequency="yearly" to match