时间戳

首页 > 解决方案 > Live555 RTSP 服务器不使用 UDP

c++ - Live555 RTSP 服务器不使用 UDP

问题描述

我有一个非常基本的 live555 RTSP 服务器和客户端来流式传输用 c++ 编写的 h264 流。

这是我为客户端提供的代码（改编自 testProgs/testRTSPClient.cpp，与 live555 捆绑在一起）

client->scheduler                   = BasicTaskScheduler::createNew();
  client->env                         = BasicUsageEnvironment::createNew(*client->scheduler);
  client->rtspClient                  = NULL;
  RTSP_CLIENT::eventLoopWatchVariable = 0;

  openURL(client, *client->env, string(string("rtsp://") + ip_address + ":" + to_string(BASE_RTSP_PORT + iris_id) + "/iris").c_str());

  client->env->taskScheduler().doEventLoop(&RTSP_CLIENT::eventLoopWatchVariable);

void openURL(RTSP_CLIENT* client, UsageEnvironment& env, char const* rtspURL) {
  // Begin by creating a "RTSPClient" object.  Note that there is a separate "RTSPClient" object for each stream that we wish
  // to receive (even if more than stream uses the same "rtsp://" URL).
  while (!client->rtspClient) {
    client->rtspClient = ourRTSPClient::createNew(env, rtspURL, RTSP_CLIENT_VERBOSITY_LEVEL, "main");
  }

  // Next, send a RTSP "DESCRIBE" command, to get a SDP description for the stream.
  // Note that this command - like all RTSP commands - is sent asynchronously; we do not block, waiting for a response.
  // Instead, the following function call returns immediately, and we handle the RTSP response later, from within the event loop:
  client->rtspClient->sendDescribeCommand(continueAfterDESCRIBE);
}

void continueAfterDESCRIBE(RTSPClient* rtspClient, int resultCode, char* resultString) {
  do {
    UsageEnvironment& env = rtspClient->envir(); // alias
    StreamClientState& scs = ((ourRTSPClient*)rtspClient)->scs; // alias

    if (resultCode != 0) {
      env << *rtspClient << "Failed to get a SDP description: " << resultString << "\n";
      delete[] resultString;
      break;
    }

    char* const sdpDescription = resultString;
    env << *rtspClient << "Got a SDP description:\n" << sdpDescription << "\n";

    // Create a media session object from this SDP description:
    scs.session = MediaSession::createNew(env, sdpDescription);
    delete[] sdpDescription; // because we don't need it anymore
    if (scs.session == NULL) {
      env << *rtspClient << "Failed to create a MediaSession object from the SDP description: " << env.getResultMsg() << "\n";
      break;
    } else if (!scs.session->hasSubsessions()) {
      env << *rtspClient << "This session has no media subsessions (i.e., no \"m=\" lines)\n";
      break;
    }

    // Then, create and set up our data source objects for the session.  We do this by iterating over the session's 'subsessions',
    // calling "MediaSubsession::initiate()", and then sending a RTSP "SETUP" command, on each one.
    // (Each 'subsession' will have its own data source.)
    scs.iter = new MediaSubsessionIterator(*scs.session);
    setupNextSubsession(rtspClient);
    return;
  } while (0);

  // An unrecoverable error occurred with this stream.
  shutdownStream(rtspClient);
}

这是我为服务器提供的代码（改编自 testProgs/testOnDemandRTSPServer.cpp，与 live555 捆绑在一起）

rtsp_server->taskSchedular          = BasicTaskScheduler::createNew();
  rtsp_server->usageEnvironment       = BasicUsageEnvironment::createNew(*rtsp_server->taskSchedular);
  rtsp_server->rtspServer             = RTSPServer::createNew(*rtsp_server->usageEnvironment, BASE_RTSP_PORT + iris_id, NULL);
  rtsp_server->eventLoopWatchVariable = 0;

  if(rtsp_server->rtspServer == NULL) {
    *rtsp_server->usageEnvironment << "Failed to create rtsp server ::" << rtsp_server->usageEnvironment->getResultMsg() <<"\n";
    return false;
  }
  rtsp_server->sms            = ServerMediaSession::createNew(*rtsp_server->usageEnvironment, "iris", "iris", "stream");
  rtsp_server->liveSubSession = H264LiveServerMediaSession::createNew(*rtsp_server->usageEnvironment, true);

  rtsp_server->sms->addSubsession(rtsp_server->liveSubSession);
  rtsp_server->rtspServer->addServerMediaSession(rtsp_server->sms);

rtsp_server->taskSchedular->doEventLoop(&rtsp_server->eventLoopWatchVariable);

我假设live555默认使用UDP将数据从服务器传输到客户端，这是我想要的，因为它比TCP具有延迟优势。然而，在运行服务器客户端时，我碰巧检查了 netstat，我发现了这个：

~# netstat | grep 8554
tcp        0      0 x.x.x.x:8554    wsip-x-x-x-x:39224 ESTABLISHED

然而，它表明通信是通过 TCP 而不是 UDP。我在这里有点困惑，我在这里误解了 netstat 吗？

我需要调整我的 c++ 代码以强制通信通过 UDP 而不是 TCP 吗？

标签： c++linuxlive555

解决方案

好的，所以我想出了答案。为了帮助其他对此感到好奇的人，代码实际上都是正确的。也没有对 netstat 的误解。RTSP 确实通过 TCP 而不是 UDP 运行。然而，A/V 数据的传输方法在 RTP 上运行，RTSP 只是协商和实例化一个连接。RTP 几乎总是会在 UDP 上运行。要确定 A/V 数据流通过的端口和协议，您需要嗅探通过 RTSP 发出的数据包。在我的情况下，A/V 数据流确实仍在通过 UDP。

推荐阅读