A transfer that works between two test extensions may fail when a mobile network, voicemail, or a different carrier enters the path. Test the actual provider combinations and record the caller’s audio experience alongside signalling.
Transfer compatibility has several boundaries
Cross-provider transfer testing checks whether originating service, transfer controller, destination network, and receiving device behave correctly together. Provider support claims alone do not prove that a particular route preserves audio, caller identification, or failure recovery.
Write down the transfer mode before testing. An attended transfer, a blind transfer, and an application-managed bridge can expose different events and recovery options. SIP primitives such as REFER and Replaces explain parts of those mechanisms, but provider configuration and network policy determine the deployed behaviour. See RFC 3515 and RFC 3891.
For a proposed test plan, identify each route by originating provider, destination provider, destination type, region, and transfer mode. Save configuration versions with the results so a later routing change does not silently invalidate the evidence.
Build a fictional compatibility matrix
Suppose an office receives calls through provider A and sends transfers to a desk phone on provider B or a mobile on provider C. Treat these as separate test routes. A passed desk-phone test says nothing about mobile voicemail classification.
| Route and condition | Evidence to capture |
|---|---|
| A to B, employee answers | Two-way audio and staff acceptance |
| A to C, mobile declines | Caller recovery without disconnection |
| A to C, voicemail answers | Correct policy outcome, not assumed human acceptance |
| A to B, caller hangs up first | Destination leg cleaned up |
| A to C, weak mobile signal | Audio continuity and final state |
Give each test a unique interaction reference. Correlate event timestamps, transfer attempt identifiers, and authorised test recordings. Redact telephone numbers before sharing evidence outside the test team.
Repeat the failed route with one changed variable at a time. Switching provider, transfer mode, and device together can produce a working call without identifying the original cause.
Decide which limitations block launch
Some differences are tolerable, such as a destination displaying the office number when policy permits it. Others, including one-way audio or a disconnected caller after rejection, can make the route unusable. Assign acceptance criteria before seeing the results.
A comprehensive matrix costs test time and may incur call charges. Prioritise routes used by actual staff, then add less common networks as coverage expands. The voice platform case study describes SIP integration experience; this matrix is a proposed validation method. Review handoff completion measurement for pilot reporting.
Provider transfer FAQ
Does a successful signalling response prove success?
No. Confirm usable audio and the intended recipient’s acceptance.
Should voicemail count as a completed handoff?
Only if the explicitly defined workflow permits voicemail as its destination.
When should compatibility tests be repeated?
After changes to routing, provider configuration, transfer mode, or the devices used by receiving staff.