fix(cc-components): show dialed number instead of entrypoint for outdial calls by bhabalan · Pull Request #657

fix(cc-components): show dialed number instead of entrypoint for outdial calls by bhabalan · Pull Request #657 · webex/widgets

…ial calls

When making an outdial call via dialpad, the incoming task, task list, and
active task were incorrectly showing the entrypoint number (ANI) instead of
the actual dialed number (DN). This fix checks for outboundType === 'OUTDIAL'
and uses the DN field from callAssociatedDetails for the title display.

CAI-7359

marked this pull request as ready for review

March 18, 2026 02:33

…lint errors

Add 4 new test cases each for IncomingTask and TaskList outdial scenarios:
- Empty dn string fallback to ani
- CALLBACK outboundType uses ani (not dn)
- Social media outdial uses customerName
- Non-browser outdial button states

Fix prettier formatting in source files.

CAI-7359

… ID and phone number for inbound and outdial calls

Refactor logic to determine caller number based on call type, ensuring that for inbound calls, the caller ID is derived from ANI, while for outdial calls, it uses DN for caller ID and ANI for the phone number. Update tests to validate these changes and ensure accurate rendering in various scenarios.

- Scope renderPhoneNumber to telephony only (fixes chat/email regression)
- Fix inverted ANI/DN comment for outdial semantics
- Extract OUTBOUND_TYPE enum to replace magic strings
- Deduplicate caller identifier logic into shared getCallerIdentifier()
- Add regression test for standard inbound (outboundType undefined)