[Live-devel] Get IP address of redirected RTSP servers

Liu, Eric liuri at amazon.com
Tue May 30 18:13:32 PDT 2023


Hi Ross,

Apologies for the delayed response. I built the openRTSP sample program from the latest source (2023.05.10) to check the SETUP response as you suggested. This is a snippet from the logs:


Sending request: SETUP rtsp://rtsp://192.168.1.151:554/stream0/trackID=1 RTSP/1.0
CSeq: 6
Authorization: Basic YWRtaW46bHVuY2h0aW1lMSE=
User-Agent: ./openRTSP (LIVE555 Streaming Media v2023.05.10)
Transport: RTP/AVP;unicast;client_port=55910-55911


Received 144 new bytes of response data.
Received a complete SETUP response:
RTSP/1.0 200 OK
CSeq: 6
Session:        900388509d
Transport: RTP/AVP;unicast;client_port=55910-55911;server_port=8208-8209;ssrc=009CC2F2


Setup "video/H264" subsession (client ports 55910-55911)
Sending request: SETUP rtsp://rtsp://192.168.1.151:554/stream0/trackID=2 RTSP/1.0
CSeq: 7
Authorization: Basic YWRtaW46bHVuY2h0aW1lMSE=
User-Agent: ./openRTSP (LIVE555 Streaming Media v2023.05.10)
Transport: RTP/AVP;unicast;client_port=54766-54767
Session: 900388509d


Received 144 new bytes of response data.
Received a complete SETUP response:
RTSP/1.0 200 OK
CSeq: 7
Session:        900388509d
Transport: RTP/AVP;unicast;client_port=54766-54767;server_port=8208-8209;ssrc=009CC2F2


Setup "audio/PCMA" subsession (client ports 54766-54767)


Since I don't see any "Source" or "source=" fields in any of the SETUP responses, would it be accurate to say that in this case the server is not replying with the "source=" parameter properly and we are not able to get the IP address through this method (with this server)? Just want to make sure that I am checking in the right place. In that scenario, is there another method to get the end IP address from the library? I can see in the logs that it is able to connect to the final redirected source so it must have some way of getting the end IP address - I'm just looking to be able to programmatically access that information.

Thanks,
Eric Liu

On 5/23/23, 1:48 PM, "live-devel on behalf of Ross Finlayson" <live-devel-bounces at us.live555.com <mailto:live-devel-bounces at us.live555.com> on behalf of finlayson at live555.com <mailto:finlayson at live555.com>> wrote:


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.






> On May 23, 2023, at 1:27 PM, Liu, Eric via live-devel <live-devel at us.live555.com <mailto:live-devel at us.live555.com>> wrote:
>
>
> From: "Liu, Eric" <liuri at amazon.com <mailto:liuri at amazon.com>>
> Subject: Re: [Live-devel] Get IP address of redirected RTSP servers
> Date: May 23, 2023 at 1:27:34 PM PDT
> To: LIVE555 Streaming Media - development & use <live-devel at us.live555.com <mailto:live-devel at us.live555.com>>
>
>
> Hi Ross,
>
> Thanks for your response. Do you know if the ip address returned by these functions (connectionEndpointName, getConnectionEndpointAddress) are specified by the end server or determined by the library? I'm testing this out and unfortunately the ip address does not seem to be set (it is always null or 0).


The IP address is the one that the server (is supposed to) send in its response to each RTSP “SETUP” command, as the “source=“ parameter. You can see this (“SETUP” response) by running “testRTSPClient” or “openRTSP”. Remember: You need to wait until you have (successfully) done a RTSP “SETUP” before checking this.




Ross Finlayson
Live Networks, Inc.
http://www.live555.com/ <http://www.live555.com/>




_______________________________________________
live-devel mailing list
live-devel at lists.live555.com <mailto:live-devel at lists.live555.com>
http://lists.live555.com/mailman/listinfo/live-devel <http://lists.live555.com/mailman/listinfo/live-devel>






More information about the live-devel mailing list