SIP #2 SDP (Session Description Protocol) - Cisco Collaboration

Поділитися
Вставка
  • Опубліковано 7 лис 2024

КОМЕНТАРІ • 22

  • @melkanibhaskar
    @melkanibhaskar 3 роки тому +3

    All your videos are too good. Thanks for sharing your knowledge. Kudos to you :)

    • @CollabCrush
      @CollabCrush  3 роки тому

      My pleasure 😊 Glad you're enjoying them.

  • @magpieenterprise6781
    @magpieenterprise6781 4 роки тому +1

    Very informative, to the point. You are among my favourites now!

    • @CollabCrush
      @CollabCrush  4 роки тому +1

      Awesome! Thank you very much!

  • @nasrallahlarech2216
    @nasrallahlarech2216 2 роки тому

    concise and very useful explanation 4 me looking 4 a technical start

  • @Jerry-bs3dv
    @Jerry-bs3dv 4 роки тому +1

    Nice video. You describe that in the O= field the value 2 represents the version. Isn't that value = 2 the session id for the SDP ? Just like we have the session id for an INVITE?

    • @CollabCrush
      @CollabCrush  4 роки тому

      Sorry, I missed your message until now. That might be right... I need to go back and take another look.

    • @martinh9099
      @martinh9099 2 роки тому

      Recommendation in RFC 4566 is for both session and version to be set to a timestamp (eg NTP value)

  • @Hiwot95
    @Hiwot95 3 роки тому +2

    Thank you so much for sharing this great video

  • @ravenbao3334
    @ravenbao3334 3 роки тому

    Hi, does WebEx SDP run a different interface selection algorithm when it comes to a VPN connection where there is more than one adapter available on endpoint? We found it always selected the local LAN adapter instead of the VPN virtual adapter to try to initiate the audio/video connection, which is different from all other types of WebEx traffics

  • @scofugate
    @scofugate 4 роки тому +1

    What did you use to capture the flow?

    • @CollabCrush
      @CollabCrush  4 роки тому

      In this particular case, I believe I was using a DX80, which has a built-in function for capturing network traffic. Otherwise, you could use something like Wireshark, or RTMT if you're using the CUCM.

  • @luisguizarsantaella6234
    @luisguizarsantaella6234 3 роки тому +1

    Amazing explanation. Thank you !

  • @deano1959
    @deano1959 4 роки тому +1

    Your videos are amazing.

    • @CollabCrush
      @CollabCrush  4 роки тому

      Very much appreciated!! Thank you!!

  • @valeriangelov5592
    @valeriangelov5592 4 роки тому +1

    Thanks a lot really helpful.

  • @danielrojas8509
    @danielrojas8509 5 років тому

    hello, thanks for sharing this video.
    In 5:39 you say: "the list of the five codecs that are available". So I can´t see clearly wich codecs are you talking about.

    • @CollabCrush
      @CollabCrush  5 років тому

      Hi Daniel. Match the numbers in the first line to the same rtpmap value in the following lines. For example, the first line says, ... "m=video 24940 RTP/AVP 97 126 96 34 123" The number, 97 in this line refers to ... "a=rtpmap: 97 H264/90000" So you're matching the 97 values. Notice in this line the part that says, "H264"? This is the codec. The next number in the first line (126) maps to"a=rtpmap: 126 H264. So this means that 126 also refers to the the H264 codec, but this one is using a different packetization mode. And we know that because of the line that says, a=fmtp:126... The next number (96) maps to rtpmap: 96. This codec is H263. So just follow the number down the line... Hope that makes sense.

    • @danielrojas8509
      @danielrojas8509 5 років тому

      @@CollabCrush Ok, it is clear. Thanks for your answer. Really nice videos, i'll wait for more.

  • @vivamedia5958
    @vivamedia5958 3 роки тому

    helped a lot. Thank you.