On an Avaya IP Office, the Line Group ID has a functional dependency to which two parameters? (Choose two.)

Question

Options

• AIncoming Call Route (ICR)
• BAlternate Route Selection (ARS)
• CTime profile
• DHunt group
• EVoice recording

• A
  70% (43)
• B
  16% (10)
• C
  10% (6)
• E
  3% (2)

Explanation

On Avaya IP Office, the Line Group ID is the identifier assigned to a trunk/line group that ties trunks to their routing logic. Incoming Call Route (A) directly references the Line Group ID to match incoming calls to the correct destination - if the Line Group ID changes, the ICR breaks its association with those trunks. Hunt Groups (D) use the Line Group ID in their outgoing configuration to determine which trunk group to seize for outbound calls, creating a direct dependency.

The distractors are wrong for these reasons: ARS (B) handles digit-based outbound routing via short codes and does not directly bind to a Line Group ID; Time Profile (C) controls when features are active but has no structural link to a Line Group ID; and Voice Recording (E) is a feature applied to extensions or channels, not a component that functionally references the Line Group ID.

Memory tip: Think of the Line Group ID as a "trunk tag" - it must be recognized inbound (ICR reads the tag to route the call) and claimed outbound (Hunt Group uses the tag to grab the right trunks). Only those two components hold a direct reference to the tag.

No community discussion yet for this question.