Username: avalogics

Password: aV@l0g!cS

1. Login to the ​admin portal​ using the a

​ valogics@maestroconference.com​ email address,
then access the ​monitoring tool​.
2. Login to the ​Check Registrations​ page and get the ​Conversation_String_Id ​(New Tab).
3. From a terminal window connect via ​SSH ​to the conf20 server.

Commands:
ssh ​avalogics@conf20.wakeupu.net
Password: aV@l0g!cS

4. Once inside the ​conf20 ​server, do another ​SSH​ to the voicevoice server this time.

Commands:
ssh ​avalogics@beta.voicevoice.com
Password: aV@l0g!cS

5. Inside the voicevoice server navigate to this directory:

/home/maestroconference/recording_script ​using the commands CD
6. List all the contents within this directory with the command: ​ll.​ You should see something
like this:

7. Using the linux command ​cat, s​ how on screen all the IP addresses available to be used
on the ​machineID-publicIP-List​ file

IMPORTANT: ​Remember to avoid using at all cost the ​209.51.170.11​ ip address as Sharjeel
indicated that that one ​doesn't work​ for recording purposes.
 8. Once the call has started, go back to the ​monitoring tool​ and collect the ​ConferenceID
located under the name of the call.
9. With this information, go back to the linux terminal and run the following .sh script:

./start_recording.sh + IPADDRESS + CONFERENCEID + CONFERENCENAME + 1

10. When you get the prompt shown on the image above then it means that the recording
has started. Make sure to keep tabs on the ​monitoring tool​ or the ​VoVo Recording
Convo's today​ skype group to find out once the meeting is over.
11. Once the meeting is over, make sure that you are still logged in to the ​SSH​ connection
and your current directory remains at: ​/home/maestroconference/recording_script​.
12. Next, run the ​cat ​linux command one more time against the ​machineID-publicIP-List
file to show on screen all the IP addresses available. You will notice that the IP Address
has now changed. Please write it down somewhere, we will need it later.
13. Finally to stop the recording use the following command:

./stop_recording.sh + NEW-IP-ADDRESS

IMPORTANT NOTE: ​Remember to run the stop command twice so that the recording truly
stops and gets uploaded.

You can now provide the recording link to your customer. It should look something like this:
voicevoice.blob.core.windows.net/voicevoice/vovobeta-recording/4561-27May2020-205821-tran
sformingadvocacy-1-beta.mp4
14. The procedure followed under the previous step is to instruct the instance to stop the call
from being recorded and converted to mp4 format. However, the instance is still running
so we need to shut it down. Otherwise, it will continue recording the session.

Use the following command:

./shutdown_instance.sh + NEW-IP-ADDRESS