Timing EndTime

[Asoka Wardhana]

Hi CGRateS Team,

I’m currently working on configuring Timing with StartTime and EndTime using the APIerSv1.SetTPTiming API. However, I’m encountering an issue where the EndTime is not being set correctly.

Here’s what I’ve configured in the API request:

  "Time": "00:00:00;05:59:59"

But on log always show empty :

"Timing": {
  "ID": "TAD_00:00:00_05:59:59",
  "Years": [],
  "Months": [],
  "MonthDays": [],
  "WeekDays": [],
  "StartTime": "00:00:00",
  "EndTime": ""
}

Thank you for your time and help.

Best Regards,

Asoka

[Armir Veliaj]

Hi Asoka,

I tested to set Timing via API , the same format that you did and it worked fine.
Please sent us your cgr-engine version, complete APIs (both for set and get ) and any other config and logs so we can check on it.

Thanks,
Armir

[Asoka Wardhana]

Hi Armir,

Apologies for the delayed response. Attached is the API configuration for testing shared destinations with different timing parameters (Time_1, Time_2, Time_3).

When testing via APIerSv1.GetCost for Time_2 (e.g., "AnswerTime": "2025-03-18T19:22:23+07:00"), the result consistently returns DestinationRate: DST_Rate_Mobile_Time_1, even though Time_2 is configured.

I understand that this could be resolved by configuring a single destination shared across multiple Rating Plans/Destination Rates (Time_1, Time_2, Time_3). However, this approach would not include the Time-specific identifier (e.g., Time_1, Time_2) in the CDR’s DestinationID, which is critical for our reporting and tracking.

Is there a way to configure the system so that the DestinationID in the CDR reflects the Time parameter (Time_1, Time_2, Time_3) while still using the same underlying destination?

Thanks for your time and help.

Regards,

Asoka Wardhana

[Armir Veliaj]

Hi Asoka

Can you share some more complete examples for your case that you want to create?
Also it would be better if you reopen that issue on a new thread for better tracking in the future.

Thanks,
Armir