I've just ran into a problem that I haven't noticed before. We just added the Daylight Savings patch though sounds like a stretch for it to cause this.
I have a station programmed to a coverage path that goes to a VDN and vector. In the vector the call may ultimately get to a step that routes the call to a virtual station that goes to a coverage path that goes to a coverage answer group.
When you call the original station it gives a reorder tone as if the route to vector step has cov set to N but of course its set to Y. If I dial the VDN associated with the vector it works fine.
Troubleshooting this I took the vector out of it: I programmed a station with a coverage path that goes to a station that has a coverage path that goes to a coverage answer group. That scenario also provides a busy. If I dial the 2nd station it rings the coverage answer group.
Have I just not run into this before or what?
I have a station programmed to a coverage path that goes to a VDN and vector. In the vector the call may ultimately get to a step that routes the call to a virtual station that goes to a coverage path that goes to a coverage answer group.
When you call the original station it gives a reorder tone as if the route to vector step has cov set to N but of course its set to Y. If I dial the VDN associated with the vector it works fine.
Troubleshooting this I took the vector out of it: I programmed a station with a coverage path that goes to a station that has a coverage path that goes to a coverage answer group. That scenario also provides a busy. If I dial the 2nd station it rings the coverage answer group.
Have I just not run into this before or what?