A.In AAMS Element Manager, Select System Status > Element Status > More Actions > display active
sessions.

B.In AAMS Element Manager select Monitoring > Active Sessions.

C.From Avaya Aura System Manager (SMGR) home page, click on the Media Server, and click on the link:
list active sessions.

D.From SSH, go to the AAMS and issue the list active sessions current.command

A.Protect the quality of existing connections by preventing oversubscription

B.Protect the quality of existing connections by allowing oversubscription

C.Prevent the use of compressed Codecs during video call

D.Better determination of bandwidth usage at any location

E.Provide more DSP resources to the Remote Workers

A.If a direct media path cannot be established between two IP endpoints the call will fail from release 7.0.

B.SIP-SIP two-party calls will always use SIP Direct Media if Communication Manager (CM) is configured to
do so.

C.H.323-H.323 two-party calls will always shuffle to establish a direct media path if Communications Manager
(CM) is configured to do so.

D.Two-party calls originated by H.323 stations, trunks, or media gateways, and terminated by SIP stations or
trunks, cannot shuffle.

E.Two-party calls originated by SIP stations or trunks, and terminated by H.323 trunks, media gateways, or
other vendors' H.323 stations, will typically shuffle if Communications Manager (CM) is configured to do so.

A.If a direct media path cannot be established between two IP endpoints the call will fail from release 7.0.

B.Two-party calls originated by SIP stations or trunks, and terminated by H.323 trunks, media gateways, or other vendors' H.323 stations, will typically shuffle if CM is configured to do so.

C.H.323-H.323 two-party calls will always shuffle to establish a direct media path if CM is configured to do so.

D.SIP-SIP two-party calls will always use SIP Direct Media if Communication Manager (CM) is configured to do so.

E.Two-party calls originated by H.323 stations, trunks, or media gateways, and terminated by SIP stations or trunks, cannot shuffle.

A.Run the resetSM100command from RHEL Command Line Interface of Avaya Aura Session Manager
(SM).

B.Click the repair button on the Replication page with the affected Avaya Aura Session Manager (SM)
selected.

C.Click the Reset button on the Security Module Status page in Avaya Aura System Manager (SMGR).

D.Restart Services on the Avaya Session Border Controller for Enterprise (SBCE).