486 Busy Here Messages

When using MRCP-enabled voice platforms with Capacity Private Cloud, you may encounter "486 Busy Here" responses in the Media Server logs. This article explains the causes and how to diagnose the issue.

Error Response Format

A typical 486 Busy Here response appears in logs as follows:

RTSP/1.0 486 Busy Here
CSeq: 0
Content-Length: 98

v=0
o=- 1234 5678 IN IP4 127.0.0.1
s=LumenVox Media Server/1.1.100
c=IN IP4 127.0.0.1
t=0 0

Common Causes

This error typically occurs for one of two reasons:

1. Licensing Issues

The request requires a license type that is not available. For example, attempting to use ASR (speech recognition) when only TTS (text-to-speech) licenses are provisioned, or vice versa.

2. Service Communication Failure

The Media Server cannot establish communication with the backend ASR or TTS services. This may indicate network connectivity issues, service unavailability, or misconfiguration.

Diagnosis

To identify the specific cause, examine the media_server_app.txt log file. Look for entries that provide additional context about the failure.

Example log entry indicating license exhaustion:

2026-03-02 10:15:32.456 [ERROR] OpenPort returned -1. PortStatus: -26 (All available licenses are in use.)

This message indicates that all licenses of the requested type are currently in use. Consider:

  • Reviewing your license allocation
  • Checking for sessions that may not be releasing properly
  • Contacting support if you need additional capacity

Example log entry indicating service connectivity issues:

2026-03-02 10:15:32.789 [ERROR] Failed to connect to ASR service

This message indicates the Media Server cannot reach the speech service. Verify:

  • The service endpoint is correct in your configuration
  • Network connectivity between components
  • The target service is running and healthy

Protocol-Specific Responses

The error response differs depending on the protocol in use:

  • RTSP: Returns "404 Not Found"
  • SIP: Returns "486 Busy Here"

The underlying cause and resolution steps are the same regardless of the response code.

Related Resources


Was this article helpful?