SIP user 1011111 is trying to call SIP user 1011111. If Session Manager cannot find a matching SIP Communication Profile for 1011111 in its SIP registry, what happens next?

Question

Options

• AThe call is sent to Communication Manager to check if the number dialed exists in CM's call
• BThe Caller receives a busy tone.
• CNetwork Routing Policy (NRP) is consulted for further routing instructions.
• DThe call is routed to voicemail to check if the extension is associated to mailbox.

• A
  2% (1)
• B
  88% (36)
• C
  5% (2)
• D
  5% (2)

Explanation

When Session Manager has no SIP Communication Profile for the dialed number, it has zero record of that endpoint - it cannot register, route, or forward the call in any meaningful way. With no identity to act on, SM returns a failure response (typically a SIP 4xx error) back toward the originating side, which the calling device presents as a busy/reorder tone. The call processing ends there at the SM level.

Why the distractors are wrong:

• A (sent to CM): CM is only reached if a routing rule (via NRP or an Adaptations/Entity Link) explicitly sends traffic there. SM doesn't blindly pass unrecognized calls to CM.
• C (NRP consulted): NRP is part of the normal routing flow when SM recognizes a destination and needs to determine a path. With no Communication Profile at all, there is no anchor for NRP to act on.
• D (voicemail): Voicemail routing would require a dial rule or routing policy pointing to the voicemail system - that's a configured behavior, not a default fallback.

Memory tip: Think of the SIP Communication Profile as the entry in the phone book. If the name isn't in the book at all, the operator can't connect the call and hangs up - that's the busy tone. No profile = no record = no call.

No community discussion yet for this question.