Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to determine control URL - Code 824 #117

Closed
hthetiot opened this issue Dec 27, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@hthetiot
Copy link

commented Dec 27, 2014

Hello,

I have the following error when I use the player.

{message: "RTSPClient: Unable to determine control URL.", code: 824}

Here is the log from the player:

API is ready. play can now be called
RTSPClient: STATE_OPTIONS
RTSPClient: STATE_DESCRIBE
Ignored unknown SDP directive: i=N/A
Ignored unknown SDP directive: c=IN IP4 192.168.1.21
SDP contained 2 track(s). Calling SETUP for each.
RTSPClient: STATE_SETUP
Can't determine track URL from block.control:trackID=0, session.control:undefined, and > content-base:192.168.1.57:8086/
Object {message: "RTSPClient: Unable to determine control URL.", code: 824}

Here is my RTSP server logs:

Request: OPTIONS

requestString: OPTIONS * RTSP/1.0
request header: CSeq: 2
request header: User-Agent: Locomote 0.5.0

Response: OPTIONS

RTSP/1.0 200 OK
Server: MajorKernelPanic RTSP Server
Cseq: 2
Content-Length: 0
Public: DESCRIBE,SETUP,TEARDOWN,PLAY,PAUSE

Request: DESCRIBE

requestString: DESCRIBE rtsp://192.168.1.57 RTSP/1.0
request header: CSeq: 3
request header: User-Agent: Locomote 0.5.0
request header: Accept: application/sdp

Response: DESCRIBE

RTSP/1.0 200 OK
Server: MajorKernelPanic RTSP Server
Cseq: 3
Content-Length: 465
Content-Base: 192.168.1.57:8086/
Content-Type: application/sdp
v=0
o=- 0 0 IN IP4 192.168.1.57
s=Unnamed
i=N/A
c=IN IP4 192.168.1.21
t=0 0
a=recvonly
m=audio 5004 RTP/AVP 96
a=rtpmap:96 mpeg4-generic/8000
a=fmtp:96 streamtype=5; profile-level-id=15; mode=AAC-hbr; config=1588; SizeLength=13; IndexLength=3; IndexDeltaLength=3;
a=control:trackID=0
m=video 5006 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=420014;sprop-parameter-sets=J0IAFKaBQfE=,KM48gA==;
a=control:trackID=1

I think there is an issue in the locomote SDP parser or in my RTSP server response.
I can connect to my RTSP server using VLC but not using locomote player.

@hthetiot

This comment has been minimized.

Copy link
Author

commented Dec 27, 2014

Ok I was missing the protocol "rtsp://" into the "Content-base" header, fixed.

@hthetiot hthetiot closed this Dec 27, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.