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

Delayed playback on call connection

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Not A Bug
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
      None
    • CPU Architecture:
      x86-64
    • Kernel:
      Linux
    • Userland:
      GNU/Linux
    • Distribution:
      Debian
    • Distribution Version:
      Debian 8 jessie
    • Compiler:
      gcc
    • FreeSWITCH GIT Revision:
      Unknown
    • GIT Master Revision hash::
      Unknown

      Description

      Background

      freeswitch is installed in Nigeria.
      We are using that to make outbound calls and immediately playing messages.
      We initiate calls via AMQP (rabbitmq) that posts the message onto eventsocket of freeswitch.

      What we think

      We think that the A leg is connecting immediately, giving a channel uuid back, whilst the B leg takes a while to connect.

      What is experienced

      Call is made correctly except when the call connects it's between 6 and 12 seconds into the message already.

      What we'd like

      Ideally, if freeswitch can only return the channel uuid once the b-leg is connected, we would then be able to play the message once the call was truly connect.

      Help

      At Brian's request, we did a call with

      sofia global siptrace on
      

      The log file is attached.

        Attachments

          Activity

            People

            • Assignee:
              brian@freeswitch.org Brian West
              Reporter:
              bruskiza Bruce McIntyre
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: