500-440 · Question #98
Which three options are valid when Cisco Unified Customer Voice Portal comprehensive call flow and survivability service handles SIP REFER? (Choose three.)
The correct answer is B. An application-controlled alternative is to set an ECC variable (user.sip.refertransfer) to the value C. Router require on a failed SIP Refer transfer where the survivability service is not handling the E. Unified ICM sends Unified CVP a routing label with a format of rfXXXX. In Cisco Unified CVP's SIP REFER handling, option B is correct because user.sip.refertransfer is a legitimate ECC variable that gives script designers application-level control over REFER transfer behavior - it's a documented alternative to label-based transfer. Option C is…
Question
Which three options are valid when Cisco Unified Customer Voice Portal comprehensive call flow and survivability service handles SIP REFER? (Choose three.)
Options
- ASIP trunk alternate destination routing (ADR) must be disabled for REFER
- BAn application-controlled alternative is to set an ECC variable (user.sip.refertransfer) to the value
- CRouter require on a failed SIP Refer transfer where the survivability service is not handling the
- DDirect Refer transfer using label works only if Send To VRU node is NOT used before the Refer
- EUnified ICM sends Unified CVP a routing label with a format of rfXXXX
- FStandalone Cisco Unified CVP with ICM Lookup label
How the community answered
(56 responses)- A13% (7)
- B80% (45)
- D5% (3)
- F2% (1)
Explanation
In Cisco Unified CVP's SIP REFER handling, option B is correct because user.sip.refertransfer is a legitimate ECC variable that gives script designers application-level control over REFER transfer behavior - it's a documented alternative to label-based transfer. Option C is correct because when a SIP REFER transfer fails and the CVP survivability service is not in scope, Unified ICM's router re-queues (requires) the call to find an alternate routing path. Option E is correct because Unified ICM signals CVP to execute a REFER transfer by sending a routing label in the specific rfXXXX format (e.g., rf5001), which CVP interprets as a REFER instruction rather than a standard transfer label.
Why the distractors are wrong:
- A is incorrect - ADR does not need to be disabled; it can coexist with REFER handling.
- D is incorrect - Direct REFER using a label is not blocked by prior use of the Send To VRU node; that restriction does not apply here.
- F is incorrect - Standalone CVP with ICM Lookup is a deployment topology, not a valid SIP REFER handling option.
Memory tip: Think BCE = "REFER's three pillars" - Behavior via ECC variable, Call re-route on failure, Exact label format (rf). The rf prefix in option E is the clearest giveaway - whenever you see a routing label that starts with rf, CVP knows to issue a SIP REFER.
Topics
Community Discussion
No community discussion yet for this question.