Time condition Breaks

ConFusious

New Member
Dec 1, 2020
20
0
1
51
In a previous post I was having trouble creating a Time Condition that needed a lunch time destination same as after hours destination. One of the members here kindly provided an example where he did something similar. I was able to accomplish what I needed from that Time Condidtion (701) and proceed that with another Time Condition (700) that provides the holiday destinations. I was still in the testing phaze and not deployed. all this worked with my test phones and no inbound DIDs. I add a Call Flow (280) and still tested ok. Then we deployed it with incoming destinations pointed to Time Condition (700.) That seemed to break the chain. all calls went to the afterhours destination. I had other issues where I had to create another Call Flow (281) as a destination from Call Flow (280) to send day mode calls to a ring group that calls an external number. I got that working with the DID destination set to Time Condition 701. As soon as I inserted Time Condition (700) ahead of Time Condition (701) it breaks and uses the afterhours destination during business hours. I am posting screen shots of what I built hopefully in the correct order. If anyone can spot what I did wrong and correct me I would be most grateful.
 

Attachments

  • Time Condition 700 1.png
    Time Condition 700 1.png
    87.8 KB · Views: 14
  • Time condition 700 2.png
    Time condition 700 2.png
    52.4 KB · Views: 13
  • Time condition 701 1.png
    Time condition 701 1.png
    61.4 KB · Views: 10
  • Time Condition 701 2.png
    Time Condition 701 2.png
    86.2 KB · Views: 8
  • Call Flow 280.png
    Call Flow 280.png
    89.8 KB · Views: 8
  • Call Flow 281.png
    Call Flow 281.png
    50.1 KB · Views: 11