Uploaded image for project: 'FreeSWITCH'
  1. FreeSWITCH
  2. FS-9866

3pcc=proxy for FS client and local SDP

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6.10
    • Fix Version/s: None
    • Component/s: freeswitch-core
    • Security Level: public
    • Labels:
      None
    • Environment:
      x86_64 Linux
    • CPU Architecture:
      x86-64
    • Kernel:
      Linux
    • Userland:
      GNU/Linux
    • Distribution:
      Debian
    • Distribution Version:
      Debian 8 jessie
    • Compiler:
      gcc
    • FreeSWITCH GIT Revision:
      1.6.10
    • GIT Master Revision hash::
      1.6.10

      Description

      When using Freeswitch as a SIP endpoint and 3pcc=proxy enabled. On an Incoming INVITE w/o SDP, the user initiated answer triggers sending a 200 OK i.e[3PCC-PROXY, Sent a 200 OK, waiting for ACK] but the call fails with "SIP/2.0 500 No session set by user".

      After discussing with Anthony, I came to know the the 3pcc=proxy relies on the m_sdp variable to be populated with the SDP of the outgoing leg. However, in this case of a FS as a client usage the m_sdp will be NULL since there is no outgoing leg but the application triggering the answer.

      Anthony suggested "We could possible add a patch where, if we do not have the sdp from the variable that, at that moment we can generate a local sdp instead."

        Attachments

          Activity

            People

            • Assignee:
              anthm Anthony Minessale II
              Reporter:
              shaks Sharath Kumar
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: