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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Turn off recording annoucement on manually recorded calls
- Thread starter SysHaru
- Start date
Probably but would need to be tested.
The Voicemail Pro help includes notes on how to customize the manual and automatic recording call flows. So you could try turning off the warning by default. Then add custom call flows that are pretty much the default but on the automatic one has the warning played as an entry prompt.
Stuck in a never ending cycle of file copying.
The Voicemail Pro help includes notes on how to customize the manual and automatic recording call flows. So you could try turning off the warning by default. Then add custom call flows that are pretty much the default but on the automatic one has the warning played as an entry prompt.
Stuck in a never ending cycle of file copying.
- Thread starter
- #4
Yes, I noticed, yes it's a legal requirement here but we'd like to allow some users to say it manually instead of the auto recording. Is there a way to have different outbound messages for different groups? I messed around in VMPro but no luck so far.
You'd have to have a custom module where the value of $UUI is tested (Test Variable action) and for some matches plays different entry prompts before going to the Listen action and for no match plays the default prompt.
Stuck in a never ending cycle of file copying.
Stuck in a never ending cycle of file copying.
- Thread starter
- #6
You're right, I was able to get it to work but there has to be a smoother way. So what I was able to do was copy the module setup from the VMPro manual, I put $UUI as the mailbox. How it works now;
1. I call the person
2. I put them on hold and dial the short-code pointing to that VM Module
3. It puts me into my mailbox?? And then asks me if I want to create a message, I press 1 and #,
4. I conference and warn the person about the recording.
5. Call over, they hang up on their side, I press # to end recording and then it asks me to enter the VM Box # I want to send it to (can this be fixed?)
6. After that the call is viewable through visual VM.
This works kinda but there's no easy way with that setup to turn the recording on and off. I think doing it the way you mentioned first is best, off for everyone, on for certain groups. But I'm not sure what module in VMPro directs outbound only calls to be recorded, incoming call from huntgroup?
Testing.
1. I call the person
2. I put them on hold and dial the short-code pointing to that VM Module
3. It puts me into my mailbox?? And then asks me if I want to create a message, I press 1 and #,
4. I conference and warn the person about the recording.
5. Call over, they hang up on their side, I press # to end recording and then it asks me to enter the VM Box # I want to send it to (can this be fixed?)
6. After that the call is viewable through visual VM.
This works kinda but there's no easy way with that setup to turn the recording on and off. I think doing it the way you mentioned first is best, off for everyone, on for certain groups. But I'm not sure what module in VMPro directs outbound only calls to be recorded, incoming call from huntgroup?
Testing.
Hunt groups don't make outbound calls - so they don't record them. Outbound will always be associated with the user making the call.
Yes, with customization you probably lose some features in return for whatever you gain by the cleverness of your call flow creation.
But its the only way to get non-standard features - they're non-standard because Avaya don't think there's enough demand to justify the cost/time to make them standard.
Stuck in a never ending cycle of file copying.
Yes, with customization you probably lose some features in return for whatever you gain by the cleverness of your call flow creation.
But its the only way to get non-standard features - they're non-standard because Avaya don't think there's enough demand to justify the cost/time to make them standard.
Stuck in a never ending cycle of file copying.
- Status
Similar threads
- Question