Test CMS Calls

Test CMS Calls

At this point the Unified Communications Manager and Meeting Server have all the configuration needed for you to be able to place a call from Jabber on your laptop into a space. Jabber should already be launched and registered. Test dialing by URI by calling pod2user4.space@conf.pod2.cms.lab directly from the Jabber client.


             

Once that is successful, it's worth emphasizing that ActiveControl has negotiated. This means that the Jabber client realizes it is in a CMS conference. The regular ad-hoc conference button will be greyed out, but you can invite other users.

  1. Click Invite Participants
  2. In the search enter Pod2 User1
  3. Now over of the Pod2 User1 entry and click the green call icon.
  4. Click the Work URI (pod2user1@pod2.cms.lab) for that user to place the outbound call from CMS to the user.
  5. This user will auto-answer, so as seen in the participant list, we have added them to the conference. If we hover over the participant entry for Pod2 User1, we see the icon that gives us the ability to remove this participant from the conference.
  6. NOTE: If the remote side does not answer, this usually means Jabber on PC1 is either not launched or on an active call. Access PC1 via the Remote Desktop shortcut on your desktop. Then disconnect/restart Jabber on PC1.

Features such as the active conference participant list, ability to remove participants, as well as the layout features, are available because we have a version at or later than Jabber 12.5 and have allowed ActiveControl on our SIP Trunks by enabling Allow iX Application Media on the SIP Profile applied to our trunks to CMS.

A number of these capabilities can be further customized in CMS. For instance, you will now add the ability to mute a remote participant in a conference by accessing the CMS API via Postman.

Leave the current conference up for the next section, since these changes are dynamic and you will make them system-wide:

  1. Launch Postman
  2. Make sure you have still specified the GET verb.
  3. Change the URL field to https://cms1a.pod2.cms.lab:8443/api/v1/system/profiles
  4. Click Send. Your Postman screen and the result should look like this:

  5. From the output, copy the callLegProfile id. This is the ID of the system profile, the one calls use by default.
  6. Change the URL filed to https://cms1a.pod2.cms.lab:8443/api/v1/callLegProfiles/
  7. Paste this callLegProfile id at the end of the URL
  8. Change the verb from GET to PUT since you will now modify this existing callLegProfile.
  9. Click on Body
  10. Make sure x-www-form-urlencoded is selected
  11. Remove any old Key / Value pairs by clicking on the X next to their row.
  12. For the Key enter muteOthersAllowed
  13. In the Value field next to muteOthersAllowed, enter true
  14. Click Send. Your Postman screen and the result should look like this:

  15. Verify that you received a 200 OK message back, then return to the active Jabber call (or start another conference as in the previous steps if disconnected).
  16. When you hover over the other participant in the conference, Pod2 User1. You should now see the mute icon, which will turn red when clicked.
  17. Disconnect the remote user by clicking on on the icon next to the Pod2 User1 and confirming with the Remove button.
  18. Hover over the remaining video window and click the button to disconnect the call.

Keep in mind that this change was made to the callLegProfile associated with the systemProfile. If you recall the hierarchy below, this means that every Space, as long as it does not have a different callLegProfile that overrides this behavior, will inherit the ability to muteOthersAllowed property.

cmsapi-callprofiles.png

 


MAIN LAB COMPLETE!

You've finished the main portion of the lab. There are multiple additional optional lab sections, depending on your time and interest, to continue on.