Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6.10, 1.6.11
    • Fix Version/s: 1.8
    • Component/s: core, freeswitch-core
    • Security Level: public
    • Labels:
      None
    • Environment:
      Debian 8, FusionPBX 4.20
    • CPU Architecture:
      x86-64
    • Kernel:
      Linux
    • uname:
      Linux bls-pbx 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 GNU/Linux
    • Userland:
      GNU/Linux
    • Distribution:
      Debian
    • Distribution Version:
      Debian 8 jessie
    • lsb_release:
      Hide
      No LSB modules are available.
      Distributor ID: Debian
      Description: Debian GNU/Linux 8.6 (jessie)
      Release: 8.6
      Codename: jessie
      Show
      No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.6 (jessie) Release: 8.6 Codename: jessie
    • Compiler:
      gcc
    • FreeSWITCH GIT Revision:
      11.6.11-19-5e413fe~64bit
    • GIT Master Revision hash::
      1.9.0+git~20161011T002129Z~11f4b3c4f7~64bit

      Description

      Dear Developers,

      first of all many thanks for your great work on FreeSwitch and the continuing development!
      Please find below a description of what I think is a bug. Kindly let me know if you need any further information or details.


      Call Setup & Description:
      * Polycom VVX600 (2@10.10.40.100) calls Yealink T49G (1@10.10.40.100) both Phones are Video Phones, H263 & H264 enabled in FS gobal_codec_prefs.
      * The VVX600 is transferred to the VM of the registered T49G line.

      Results:
      There are at least two things that do not work out properly in such case:
      * Playback of 1st message after recording the voicemail is not working. At this point in time the following error is shown "switch_ivr_play_say.c:496 Unable to establish inbound video stream" The log looks like "vm-listen_to_recording.wav" is played, but the 1st you can hear on the phone is "vm-press.wav". It gives the impression as if the time of "vm-listen_to_recording.wav" has to elaps before you hear the "vm-press.wav".
      * When saving the message another error shows up: [ERR] switch_utils.c:1211 EMAIL NOT SENT, error [Cannot open tmp file]
      This error is very misleading because it looks like there is an issue with the path or permissions on the file FS tries to write, but this is definitely not the case, a call coming from another extension without video active in the SDP is recorded & stored properly.

      What I've already checked:
      replacing the error in switch_utils:1211 with the file variable clearly showed that FS tries to write to the same location as it writes the files from non-video calls.

      What I'd have expected:
      * Proper playback of all VM files.
      * Beeing able to write the files to the location.
      * and/or seeing an error that gives a better idea what is going on in this situation.
      * Video beeing disabled / ignored.

      Attachments:
      * freeswitch.xml.fsxml
      * freeswitch_ivr_video-call.log


      Many thanks for your attention!

      Best regards,
      Harald Gutmann

      1. freeswitch_ivr_video-call.log
        72 kB
        Harald Gutmann
      2. freeswitch.xml.fsxml
        288 kB
        Harald Gutmann

        Activity

        Hide
        brian Brian West added a comment -
        I replicated the issue and did a patch in Master, can you please test and give me feedback. In my testing it works, I just remove the SWITCH_FILE_FLAG_VIDEO flag and continue with audio only if we fail to get any video data.

        /b
        Show
        brian Brian West added a comment - I replicated the issue and did a patch in Master, can you please test and give me feedback. In my testing it works, I just remove the SWITCH_FILE_FLAG_VIDEO flag and continue with audio only if we fail to get any video data. /b
        Hide
        hargut Harald Gutmann added a comment -
        We've been using Yealink T49G, Polycom VVX 600 & baresip for testing. All of them showed the same problem.

        Will test the patch in the next hours, and report back. Thank you very much for your help!
        Show
        hargut Harald Gutmann added a comment - We've been using Yealink T49G, Polycom VVX 600 & baresip for testing. All of them showed the same problem. Will test the patch in the next hours, and report back. Thank you very much for your help!
        Hide
        hargut Harald Gutmann added a comment -
        Tested & recording now works nicely!

        Many thanks for fixing this issue.


        Best regards,
        Harald
        Show
        hargut Harald Gutmann added a comment - Tested & recording now works nicely! Many thanks for fixing this issue. Best regards, Harald
        Hide
        hargut Harald Gutmann added a comment -
        Additionally I'd like to ask for another small change, as it took me quite long to figure out what the error messages want to tell me. Actually this is not really related to this bug, but came up during trouble shooting as the recording failed, and the mailing tried to access the file later on.

        For debugging it would be really helpful to have an error message that provides the information that it is a read attempt and additionally it would be perfect to know which file is attempted to be opened.

        The relevant part can be found at src/switch_util.c:1033
        {code}
                                if ((ifd = open(file, O_RDONLY | O_BINARY)) < 0) {
                                        rval = SWITCH_FALSE;
                                        err = "Cannot open tmp file\n";
                                        goto end;
                                }
        {code}

        It took me quite long (until looking into the source) to find out that the error message described a read attempt, and also which file it was trying to read. My first impression was that I have some permission problem on the location FreeSwitch is trying to access.

        Best regards,
        Harald Gutmann
        Show
        hargut Harald Gutmann added a comment - Additionally I'd like to ask for another small change, as it took me quite long to figure out what the error messages want to tell me. Actually this is not really related to this bug, but came up during trouble shooting as the recording failed, and the mailing tried to access the file later on. For debugging it would be really helpful to have an error message that provides the information that it is a read attempt and additionally it would be perfect to know which file is attempted to be opened. The relevant part can be found at src/switch_util.c:1033 {code}                         if ((ifd = open(file, O_RDONLY | O_BINARY)) < 0) {                                 rval = SWITCH_FALSE;                                 err = "Cannot open tmp file\n";                                 goto end;                         } {code} It took me quite long (until looking into the source) to find out that the error message described a read attempt, and also which file it was trying to read. My first impression was that I have some permission problem on the location FreeSwitch is trying to access. Best regards, Harald Gutmann
        Hide
        mikej Mike Jerris added a comment -
        if its not related to this jira please create a new one for the different issue and we can review.
        Show
        mikej Mike Jerris added a comment - if its not related to this jira please create a new one for the different issue and we can review.

          People

          • Assignee:
            mikej Mike Jerris
            Reporter:
            hargut Harald Gutmann
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development