486 busy here messages
When using the LumenVox Media Server with an MRCP-enabled voice platform, you may sometimes see messages like the following in your media_server_app.txt log file (or in a packet capture):
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/11.1.100
c=IN IP4 127.0.0.1
t=0 0
If you are using MRCPv2, you would see the message in response to a SIP INVITE instead of an RTSP SETUP, but otherwise the contents would be similar.
The 486 Busy Here message indicates that the Media Server is running and receiving traffic correctly, but is unable to establish the requested ASR or TTS session. There are two primary reasons for this:
- You do not have the appropriate licenses, e.g. you are trying to establish an ASR session but only have TTS licenses. Make sure that you have your License Server running and that it has the licenses you expect it does.
- The Media Server is unable to communicate with the ASR or TTS server. Verify that the appropriate services are running, and ensure that you have basic functionality working.
You can also refer to the media_server_app log, which should log an error and the reason why it is returning Busy Here. Here is an example of a failure resulting from no ASR licenses:
04/11/2013 10:25:02.441,DEBG,Rtsp_SETUP ,RTSP: Received SETUP request 'rtsp://10.0.0.171:554/media/speechrecognizer'
04/11/2013 10:25:06.563,ERRO,OpenPort ,OpenPort returned -1. PortStatus: -26 (All available licenses are in use.)
04/11/2013 10:25:06.563,ERRO,RTSP_Setup ,Returning Busy Here due to open port failure (Speech Port not Opened), new StreamRecognizer
Please note that starting with LumenVox version 13.1, RTSP users will see these being reported as 404 Not Found instead of 486 Busy Here messages, but the meaning is the same, SIP users will continue to see 486 Busy Here in these instances.
If you are experiencing a Busy Here message for another reason, it may be time to contact LumenVox Support.