When configuring the Cisco CVP Courtesy Callback feature in the ingress and VXML gateway, which configuration is needed to ensure that SIP is set up to forwards SIP INFO messaging.

Question

Options

• Asignaling forward unconditional
• Bsignaling forward conditional
• Csignaling forward conditional sip info
• Dsignaling forward unconditional sip info
• Esignaling sip forward unconditional

• A
  83% (44)
• B
  2% (1)
• C
  9% (5)
• D
  2% (1)
• E
  4% (2)

Explanation

Option A (signaling forward unconditional) is correct because this is the valid Cisco IOS command configured under voice service voip > sip that instructs the gateway to forward all SIP signaling messages-including SIP INFO-regardless of call state. Since Courtesy Callback relies on SIP INFO messages to signal callback events between the gateway and CVP, unconditional forwarding ensures those messages always pass through without being filtered or dropped.

Why the distractors are wrong:

• B (signaling forward conditional) only forwards SIP signaling when specific call-state conditions are met, which can cause SIP INFO messages to be dropped outside those conditions-unreliable for Courtesy Callback.
• C and D append sip info as if they are valid sub-parameters, but this syntax does not exist in Cisco IOS; the command does not accept that trailing argument.
• E (signaling sip forward unconditional) reverses the keyword order, which is invalid syntax and will not be accepted by the CLI.

Memory tip: Associate "unconditional" with "no exceptions"-the gateway forwards every SIP message it sees, no questions asked. If you see any option that adds extra words after unconditional or changes the word order, it's a fabricated distractor exploiting unfamiliarity with exact CLI syntax.

No community discussion yet for this question.