Need to be able to have time zone aware Inbound Rules etc.

Discussion in 'Ideas' started by brendan.helsham, May 11, 2016.

Need to be able to have time zone aware Inbound Rules etc. 5 5 5votes
5/5, 5 votes

  1. brendan.helsham

    Joined:
    Jan 23, 2008
    Messages:
    35
    Likes Received:
    5
    When configuring ‘Specific Office Hours’ (Inbound Rules, individual extensions etc.), we need the ability to associate a time zone with these specific office hours (like when provisioning a phone), so that we don’t need to change dozens of settings every 6 months when DST starts or ends for rules that apply to offices in a different time zone to the server.

    o I also think that the actual entries for the office hours need to be in the local time zone. For example, with our clients that have an Office in QLD or WA (neither observe DST), I can create the inbound rule for these offices to open from 8am to 5pm, and they will automatically move forward and back an hour with DST in NSW. Also, by being able to configure these times in the local time, I don’t have to pre-configure the offset to NSW, especially as this changes during the year.
     
  2. brendan.helsham

    Joined:
    Jan 23, 2008
    Messages:
    35
    Likes Received:
    5
    Here we are nearly 18 months later and preparing to do the timezone dance this weekend. What a pain the backside. Disappointing that this idea managed to only attract 2 votes. Are we the only people that build systems that span timezones?
     
  3. Brad Cann

    Brad Cann New Member

    Joined:
    May 5, 2017
    Messages:
    106
    Likes Received:
    12
    Don't live in them backwards states then :)

    NSW for the win.
     
  4. Brad Cann

    Brad Cann New Member

    Joined:
    May 5, 2017
    Messages:
    106
    Likes Received:
    12
    seriously though why are you not using the time zone settings in the phone provisioning that was release with 15.5 sp1? that should make the phone work in the local time zone no matter what the "Global" time zone is.
     

    Attached Files:

  5. brendan.helsham

    Joined:
    Jan 23, 2008
    Messages:
    35
    Likes Received:
    5
    That's fine for the displayed time on the phone, but no good for creating an inbound rule to fire properly for a DID that is in a non-DST supported timezone.

    So, more specifically, we have several clients that span Australia. Twice a year, we need to manually muck around with the inbound rules applicable to their QLD/WA locations, as the server is hosted in NSW. All inbound rules are relative to the system-wide timezone, but using the QLD office example, if the inbound rule was set to be M-F 9am-5pm, we have to change it to 10am-6pm during DST and back again in April.

    It's a colossal pain in the backside...
     
  6. brendan.helsham

    Joined:
    Jan 23, 2008
    Messages:
    35
    Likes Received:
    5
    Only 2 votes for this idea? No-one else thinks it would be a good idea to open up the timezone option when specifying custom hours for an Inbound Rule or an Extension? Like you can for phone provisioning?

    Anyone?
     
  7. voiptoys

    voiptoys Member

    Joined:
    Feb 13, 2013
    Messages:
    493
    Likes Received:
    81
    I agree, this is messy. You could build a CFD application for making routing decisions for you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...