Finished removing timings

docs/filters.rst

@@ -77,9 +77,6 @@ The following types are implemented:
 \*notexists
 	Is the negation of *\*exists*.
 
-\*nottimings
-	Is the negation of *\*timings*.
-
 \*destinations
 	Will make sure that the *Element* is a prefix contained inside one of the destination IDs as *Values*.
 

docs/rals.rst

@@ -51,7 +51,7 @@ FallbackSubjects
 RatingPlan
 ^^^^^^^^^^
 
-Groups together rates per destination and relates them to event timing. Configured via the following parameters:
+Groups together rates per destination. Configured via the following parameters:
 
 ID
 	The tag uniquely idenfying each RatingPlan. There can be multiple entries grouped by the same ID.
@@ -59,11 +59,8 @@ ID
 DestinationRatesID
 	The identifier of the :ref:`DestinationRate` set.
 
-TimingID
-	The itentifier of the :ref:`Timing` profile.
-
 Weight
-	Priority of matching rule (*DestinationRatesID*+*TimingID*). Higher value equals higher priority.
+	Priority of matching rule (*DestinationRatesID*). Higher value equals higher priority.
 
 
 .. _DestinationRate:
@@ -150,36 +147,6 @@ GroupIntervalStart
 	Activates the rate at specific usage within the event.
 
 
-.. _Timing:
-
-Timing
-^^^^^^
-
-A *Timing* profile is giving time awarness to an event. Configured via the following parameters:
-
-ID
-	The tag uniquely idenfying each *Timing* profile.
-
-Years
-	List of years to match within the event. Defaults to the catch-all meta: *\*any*.
-
-Months
-	List of months to match within the event. Defaults to the catch-all meta: *\*any*.
-
-MonthDays
-	List of month days to match within the event. Defaults to the catch-all meta: *\*any*.
-
-WeekDays
-	List of week days to match within the event as integer values. Special case for *Sunday* which matches for both 0 and 7.
-
-Time
-	The exact time to match (mostly as time start). Defined in the format: *hh:mm:ss*
-
-
-
-.. Note:: Due to optimization, CGRateS encapsulates and stores the rating information into just three objects: *Destinations*, *RatingProfiles* and *RatingPlan* (composed out of *RatingPlan*, *DestinationRate*, *Rate* and *Timing* objects).
-
-
 
 .. _Accounting:
 

docs/tut_cgrates_usage.rst

@@ -10,7 +10,6 @@ started with custom configuration, depending on the tutorial you have followed.
 For our tutorial we load again prepared data out of shared folder, containing
 following rules:
 
-- Create the necessary timings (always, asap, peak, offpeak).
 - Configure 3 destinations (1002, 1003 and 10 used as catch all rule).
 - As rating we configure the following: