A customer explains that calls are failing to route from Avaya Aura® Session Manager (SM) A (managed by Avaya Aura® System Manager (SMGR) A) to an Avaya Aura® Session Manager (SM) B (managed by Avaya

Question

Options

• ASM B is defined as a SIP Entity of type "other" +Entity Link, Dial Pattern and Routing Policy.
• BSM B is defined as a SIP Entity of type "Session Manager" +Entity Link, Dial Pattern and Routing
• CSM B is defined as a SIP Entity of type "Session Manager" +Entity Link.
• DSM B is defined as a SIP Entity of type "other" +Entity Link.

• A
  11% (3)
• B
  78% (21)
• C
  4% (1)
• D
  7% (2)

Explanation

When SM B resides under a different SMGR, SM A must have a complete routing chain to reach it: the SIP Entity type "Session Manager" establishes a trusted peer relationship (Avaya treats inter-SM connections differently than generic SIP endpoints), the Entity Link defines the physical SIP trunk/connection, the Dial Pattern matches the called digits/URIs, and the Routing Policy ties everything together to determine how matched calls are forwarded - all four components are required for calls to route successfully.

Why the distractors fail:

• A & D use type "other," which is reserved for non-SM SIP endpoints (carriers, SBCs, third-party devices) - using it for SM B means Avaya won't apply the inter-SM trust model or proper routing behavior.
• C is close but omits the Dial Pattern and Routing Policy - without them, SM A has no rule to match incoming digits to SM B and no policy instructing it to route there, so calls simply won't match.

Memory tip: Think of it as "SMERP" - Session Manager type + Entity Link + Routing Policy + Pattern (Dial Pattern). If any piece is missing, the call has no path; if the type is wrong, the trust is broken.

No community discussion yet for this question.