What does Windows error code 7015 (ERROR_CTX_MODEM_RESPONSE_BUSY) mean?

Previous	Next
ERROR_CTX_MODEM_RESPONSE_NO_DIALTONE	ERROR_CTX_MODEM_RESPONSE_VOICE

ERROR_CTX_MODEM_RESPONSE_BUSY

Busy signal detected at remote site on callback.

ERROR_CTX_MODEM_RESPONSE_BUSY belongs to legacy Remote Desktop Services and Terminal Services session handling. A diagnosis of this result must connect the condition to the producing API, current state, object identity, and first lower-level diagnostic.

This result is Win32 error 7015 (0x00001B67) in legacy Remote Desktop Services and Terminal Services session handling. Interpret it at the call that produced it and use the system message above as the immediate condition rather than as a complete root cause.

Where the result appears

• processing a busy response from the remote callback destination.
• applying a user or server configuration that enables the relevant legacy feature.
• handling a session transition or device response in the Terminal Services stack.
• diagnosing a wrapper that translates a WTS or connection result into Win32 form.

State boundary to prove

This result applies to a busy response from the remote callback destination and does not by itself prove that the entire server, directory, disk, session, or application is unavailable. The state boundary to prove for it is whether the destination line becomes available and accepts the callback call. Use callback number, attempt count and spacing, and modem result code as independent evidence. When evidence for it disagrees, preserve timestamps and investigate the transition instead of selecting the most convenient value.

Likely causes

• the user line is already in use.
• the callback number points to a busy shared line.
• the PBX returned a busy result.
• repeated automatic callbacks overlap.

Diagnostic sequence

1. capture error 7015 immediately at the API boundary and record the operation that was attempted.
2. identify the exact owner of a busy response from the remote callback destination, including object generation, server, path, session, replica, or client context.
3. collect callback number before restarting a service or changing configuration.
4. compare attempt count and spacing with the documented or observed precondition.
5. correlate modem result code with TerminalServices operational logs, session and user-configuration records, device or modem diagnostics, and the caller’s connection trace.
6. determine whether side effects occurred and verify recovery after changing one responsible condition.

Evidence to collect

• callback number.
• attempt count and spacing.
• modem result code.
• PBX or telephony logs.

Correlate it with TerminalServices operational logs, session and user-configuration records, device or modem diagnostics, and the caller’s connection trace. Keep the first detailed status even when a later wrapper translates it to error 7015; the first status often distinguishes transport, authorization, storage, schema, state, and application-integrity causes that share the same final Win32 result.

Handling, retry, and recovery

The recovery objective is to apply bounded retry with sensible spacing, verify the destination number, and avoid parallel callbacks to the same endpoint.

Retry it only after the recorded condition changes and completion state is known. Idempotent queries may be repeated after recovery, but mutations require a state check first; backoff cannot repair malformed input, corruption, missing structure, or policy rejection.

Telemetry and support fields

• record ctx_modem_response_busy_api for the producing function or management operation.
• record ctx_modem_response_busy_target for the file, log, session, replica, object, or server identity.
• record ctx_modem_response_busy_state_before and ctx_modem_response_busy_requested_transition.
• record ctx_modem_response_busy_first_status for the earliest lower-level diagnostic.

For support escalation involving it, retain decimal 7015, hexadecimal 0x00001B67, the API, UTC time, target identity, and first subsystem-specific status. Include the smallest reproducible request and evidence that distinguishes this condition from nearby codes. In the context of it, several modem-related values describe legacy callback functionality. they should be interpreted in that historical configuration context rather than as a generic modern rdp network failure.

Difference from nearby results

ERROR_CTX_MODEM_RESPONSE_VOICE detects a voice endpoint; this code indicates a valid dial attempt that encountered busy signaling

Practical validation scenario

Two session attempts request callback to the same analog line. The second receives busy until the first connection ends, so serialization prevents repeated failures. The negative test should preserve the responsible condition and reproduce it; the recovery test should change only the identified cause, repeat the same operation, and verify both success and the absence of an unintended partial side effect.

Developer and administrator guidance

Administrators handling it should first decide whether the legacy callback or redirection feature is still required. Developers should treat connection-state notifications as state transitions and device failures as component-specific results instead of mapping every value to a generic RDP network outage. Code that exposes it through RPC, JSON, REST, PowerShell, or another protocol should preserve the Win32 domain, decimal 7015, hexadecimal 0x00001B67, and original component diagnostic.

References

• Microsoft: Win32 system error range containing this code — official context relevant to it.
• Microsoft: Remote Desktop Services API — official context relevant to it.
• Microsoft: WTS configuration classes — official context relevant to it.
• Microsoft: WTSAPI32 reference — official context relevant to it.

---

Looking for a different code? Search another status or error code.