With Cisco UCCE and CVP, calls that are routed to nailed-up mobile agents keep failing, which two options could be the cause? (Choose two.)

Question

Options

• AIncorrect Mobile Agent codec configured in the PG setup.
• BUnified CM remote CTI Ports (RCP) has the outbound trunk in its calling search space.
• CUnified CM SIP trunk has RFC2833 DTMF signaling method.
• DThe mobile agents are using Finesse 11.1(1) as desktop.
• ENo MTP resources configured to handle DTMF method mismatch.

• A
  68% (21)
• B
  6% (2)
• C
  19% (6)
• D
  6% (2)

Explanation

A (Incorrect codec in PG setup) causes failures because the Peripheral Gateway must have the correct codec configured to match the media path used for mobile agent calls - a mismatch prevents the nailed-up connection from completing. E (No MTP resources for DTMF mismatch) is correct because nailed-up mobile agents rely on DTMF for call control signals, and when the DTMF method differs between endpoints (e.g., in-band vs. RFC 2833), a Media Termination Point must be present to translate - without it, signaling breaks and calls fail.

B is wrong because having the outbound trunk in the RCP's calling search space is actually the required configuration, not a failure condition. C is wrong because RFC 2833 on the SIP trunk is a valid DTMF method on its own; the problem only arises when there's a mismatch with no MTP to handle it (which is what E describes). D is wrong because the Finesse desktop version affects the agent UI, not the underlying nailed-up call path through Unified CM.

Memory tip: Think "media layer problems, media layer fixes" - both correct answers (A and E) live at the audio/media level: codec config at the PG and DTMF translation via MTP. If a call is nailed up but broken, look at how audio is being encoded and signaled, not at desktop software or CSS entries that are supposed to be present.

No community discussion yet for this question.