Implementing SIP REFER-Based Blind and Attended Transfers Across Carrier Boundaries

How-To-Articles
1

Implementing SIP REFER-Based Blind and Attended Transfers Across Carrier Boundaries

Executive Summary & Architectural Context

In a high-volume contact center, “Media Tromboning” is one of the most expensive and inefficient architectural patterns. Consider an agent who needs to transfer a customer to a third-party partner, such as a localized insurance adjuster or a specialized travel agent. The agent performs the transfer, the call connects, and the agent hangs up to take their next call. However, without a specialized transfer mechanism, the call remains “Tromboned” through your Genesys Cloud platform. Both the inbound caller’s path and the outbound partner’s path are still active, consuming two SIP sessions and valuable platform bandwidth-even though no agent is participating in the conversation. If 50 such transfers are active simultaneously, you are paying for 100 extra SIP sessions for calls you aren’t even managing.

A Principal Architect eliminates this waste by implementing SIP REFER-Based Transfers (also known as “Takeback and Transfer” or “Network Call Redirection”). Instead of keeping the call “Pinned” to the contact center, a SIP REFER command is sent to the carrier’s switch. This command essentially tells the carrier: “The contact center is done. Please connect these two parties directly in your own network and release our SIP sessions.” When successful, the call “Pops” off your platform entirely, freeing up your resources for new customer interactions.

This masterclass details how to engineer and troubleshoot SIP REFER workflows to optimize trunk capacity and reduce telephony costs.

Prerequisites, Roles & Licensing

Licensing & Permissions

  • Licensing Tier: Genesys Cloud CX 1, 2, or 3.
  • Granular Permissions:
    • Telephony > Trunk > View, Edit
    • Telephony > DID > View
  • Dependencies:
    • Carrier Support: The external carrier (e.g., Verizon, AT&T, Colt) MUST support the SIP REFER method (RFC 3515).
    • BYOC: This is typically implemented in Bring Your Own Carrier (BYOC) Cloud or Premise environments.

The Implementation Deep-Dive

1. The Architectural Strategy: The “Handoff” Method

There are two ways to execute a SIP REFER: Blind and Attended.

Blind Transfer (Unattended)

The agent simply sends the caller to the new number and hangs up immediately.

  1. The REFER: Genesys sends a SIP REFER to the carrier with a Refer-To header containing the destination number.
  2. The Result: The carrier sends a 202 Accepted, takes over the call, and sends a BYE to Genesys.

Attended Transfer (Consultative)

The agent talks to the third party first, introduces the customer, and then joins them.

  1. The “Replace” Header: This is the complex part. The REFER must include a Target-Dialog or Replaces header to tell the carrier: “Connect the existing call (Leg A) to this new active call (Leg B) that I have already established.”

2. Configuring Genesys Cloud for SIP REFER

In your SIP Trunk Configuration, you must explicitly enable the transfer logic.

Step 1: Enable the Toggle

  1. Navigate to the External Trunk settings.
  2. Under Transfer, find the Address Redirection (SIP REFER) setting.
  3. Set this to Enabled or Consultative.

Step 2: Configure the Redirection Domain

The carrier often requires the Refer-To header to match their specific gateway domain.

  • Action: Set the Redirection Target Domain to the carrier’s SIP Proxy address (e.g., trunk.carrier.com).

3. “The Trap”: The “Carrier-Reject” Loop

The Scenario: You have enabled SIP REFER. An agent attempts a transfer. The call appears to work for 1 second, but then the agent is re-connected to the customer, and the transfer fails.

The Catastrophe: The carrier rejected the REFER.

The root cause: Carriers are extremely strict about SIP REFER security. If the Refer-To number isn’t in a specific E.164 format (e.g., missing the +1), or if the “From” header doesn’t match a verified DID in their database, they will respond with a 403 Forbidden or 603 Decline.

The Principal Architect’s Solution: The “Normalization” Bridge

  1. Always Use E.164: Ensure your Architect flows and Agent scripts normalize every number to the global +CountryCodeNumber format before the REFER is sent.
  2. Identity Verification: In the Trunk settings, ensure the Identity Header (P-Asserted-Identity) is preserved during the transfer. The carrier needs to see that the “Request” is coming from a trusted source.
  3. The Fallback: Always have a “Fallback” plan in your Architect logic. If the REFER fails, the system should default back to a “Trombone” transfer (consuming the sessions) rather than dropping the customer.

Advanced: The “Target-Dialog” Challenge

In an Attended Transfer, the carrier needs to know which two calls to “Join.”

Implementation Detail:

  1. The agent places the customer on hold (Call ID 1).
  2. The agent dials the partner (Call ID 2).
  3. When the agent clicks “Transfer,” Genesys sends a REFER to the carrier regarding Call ID 1, with a Refer-To header that points to Call ID 2’s destination and includes the Target-Dialog ID of Call ID 2.
  4. The Fix: Ensure your SBC (if using one) is configured to “Pass-Through” the Target-Dialog and Replaces headers. If the SBC strips these headers to “Simplify” the SIP, the carrier won’t know how to link the two calls, and the attended transfer will fail.

Validation, Edge Cases & Troubleshooting

Edge Case 1: One-Way Audio After Refer

The failure condition: The transfer succeeds, the caller and partner are talking, but the partner cannot hear the caller.
The root cause: SDP (Session Description Protocol) Negotiation. When the carrier takes over the call, it might try to negotiate a new codec or IP address for the audio. If the partner’s phone doesn’t support the carrier’s preferred codec, the audio fails.
The solution: Ensure your carrier’s SBC is set to “Re-Negotiate” media during a REFER event. This forces both sides to agree on a common codec (like G.711) for the new direct path.

Edge Case 2: Ringback Tone Silence

The failure condition: During a blind transfer, the caller hears total silence instead of a “Ringing” sound.
The solution: Ensure the 180 Ringing packet from the carrier is passed through to the caller. You may need to enable “Early Media” or “Local Ringback” on the SIP trunk to ensure the customer knows the call is still alive during the handoff.

Reporting & ROI Analysis

The success of SIP REFER is measured by Operational Savings.

Metrics to Monitor:

  • REFER Success Rate: Percentage of external transfers successfully offloaded to the carrier.
  • Trunk Utilization (Before vs. After): Average concurrent sessions saved during peak transfer hours.
  • Telephony Cost Reduction: Monthly savings on “Inbound-Outbound Trombone” toll charges.

Target ROI: By implementing SIP REFER, you can reclaim 10-15% of your total trunk capacity and significantly reduce your per-minute telephony costs for inter-departmental or partner-based transfers.

Official References