The JIRA you pointed to is more an a simple configuration issue that can be resolved by time conditions and forwarding in the user settings. The JIRA I pointed to says "I should be able to send the calls to a user(s) during certain time periods, but control that from the AA, not the user." This is essentially what you asked for. It has also been scheduled for 5.0.
Why can't we set up a dial plan route destination to be a time condition paring instead of an AA? Wouldn't this help consolidate time conditions so we don't have to repeat them in multiple locations? (AA dial plan, other dial plans, user time conditions) This would help in the logical flow of call progression as well. This would eliminate the need to clutter up users that are required to handle my scenario. As well as take care of the JIRA case. Have the time condition have two destinations, if match, and if doesn't match. I'd really like to point out the existing ACD is going away. So any improvements to it or integrations with it really need to be pointed towards the OpenACD solution. No improvements to ACD have been mentioned.
<<attachment: Max DiOrio.vcf>>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
