Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

User variables and conditions 2

Status
Not open for further replies.

raist3001

Technical User
Jun 11, 2013
150
US
I would like to test out having a variable that a customer can turn on and off for holidays or inclement weather and also be able to record on the fly (if possible).

I have been reading all I can on the web in regards to User Variables but so far I have not had any luck in understanding how to configure.

I attached my current set up.

I understand that I should point a DID to the Test User Variable so the user can turn on and off. Not sure how to set up the variable.

If its true, it should go to the MAIN AA.
If its False, it should go to the Emergency AA.


UV_jtqbd6.png
 
 http://files.engineering.com/getfile.aspx?folder=87390e1a-860a-4e5b-9d18-6899df752b7b&file=UV.png
Or is this the way the way calls should flow?

UV2_izzls3.png
 
It may be easier to just come up with a bogus huntgroup, call it testAA. Assign a button on the phone to set HG out of service or set HG night service , or both. Then get the hunt group status using a generic action and route the calls using variable routing. That way there is a button that would actually light up on the phone indicting the route pattern. Here is an example:

 
Thanks Jinxs, but I'll need to be able to change the AA from home.
 
Set a short code to set the hunt group out of service, and another short code to put it back in service. Then create a menu to select options to transfer to those short codes. Or use the generic actions to set the hunt group out of service or in service. Then you can set another generic action to play a .wav file from the language folder to say changed after the option is selected. Either way will work. I prefer using generic actions verses transfer.
 

Download Kyle Holladay's "Standard Base Configuration", then import the VoicemailProR8.mdb and have a look.

Follow the call flow, and incorporate it into your own design. All calls are directed to menuDay. It jumps to checkConditions1 to make some tests, including to see if a variable called varCLOSED1 is set to CLOSED. If it is, a re-recordable greeting is played, the flow returns to menuDay, and based on the return goes to the menuNight.

To set or clear the closure remotely, you call in, reach the auto attendant, and dial the code to reach menuRecordings. In menurecordings, press 0 to get to menuEmergencyClosure. Now you select the site (usually site 1, but it was built for up to 4 sites sharing the voicemail), you hear the current status of the varCLOSED1 variable, and can change the variable to Open, Closed, or record the Emergency Closure Announcement
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top