A customer reports that when they make a call from an H.323 endpoint at the Main office to an H.323 telephone at the Branch office across the WAN, the call fails due to codec mismatch. If…

Question

Options

• Aip-network-region
• Bip-codec-set
• Cip-services
• Dip-network-map
• Enode-names ip

• A
  76% (26)
• C
  6% (2)
• E
  18% (6)

Explanation

Options A, B, and D are correct because codec negotiation in Avaya CM depends on a chain of three interconnected forms: ip-codec-set (B) defines which codecs are available and in what priority order - if the sets on each side share no common codec, the call fails outright. ip-network-region (A) controls which codec set is applied between two regions across the WAN - a misconfigured inter-region codec assignment causes a mismatch even if the codec sets themselves are fine. ip-network-map (D) maps endpoint IP addresses to network regions - if a branch endpoint is assigned to the wrong region, it will negotiate using the wrong codec set, producing a mismatch despite everything else being correct.

Why the distractors are wrong: ip-services (C) manages IP connectivity services (CLAN/PROCR communication) and has no role in codec selection. node-names ip (E) simply stores name-to-IP mappings for system nodes (media gateways, processors) and is unrelated to codec negotiation.

Memory tip: Think of the codec path as "Set → Region → Map." The Set lists the codecs, the Region picks which set to use across the WAN, and the Map determines which region each endpoint lands in. If any link in that chain (B → A → D) is broken, the codec negotiation fails.

No community discussion yet for this question.