What should be done to correct this issue?

Refer to the exhibit.

You have received a trouble ticket that two engineers at the HQ site tried to
conference at a user location at the Branch site and the ad-hoc conference failed.
Further investigation reveals that the remote user can occasionally be conferenced in. Phones are
configured to use G.711 for intra-site calls and G.729 for inter-site calls. All phones at the remote
site are configured to use MRGL_Branch, which contains only the media resource group named
BRANCH.
What should be done to correct this issue?

Refer to the exhibit.

You have received a trouble ticket that two engineers at the HQ site tried to
conference at a user location at the Branch site and the ad-hoc conference failed.
Further investigation reveals that the remote user can occasionally be conferenced in. Phones are
configured to use G.711 for intra-site calls and G.729 for inter-site calls. All phones at the remote
site are configured to use MRGL_Branch, which contains only the media resource group named
BRANCH.
What should be done to correct this issue?

A.
The software conference bridge CFB_2 should be removed from the Branch media resource
group.

B.
The hardware conference bridge CFB0012005FEEF1 should be listed first in the Branch media
resource group so it is utilized if it is available.

C.
Additional hardware conference resources should be added.

D.
The number of sessions allowed per conference should be increased.

Explanation:
The software conference bridge can support only G.711



Leave a Reply 0

Your email address will not be published. Required fields are marked *