locked
choppy sound in response groups RRS feed

  • Question

  • Hi,

    When calling in (PSTN) to one of our Response groups all audio files are really Choppy. The files are according to the SfB specs, and we have tried both *wav and *.wma files. If We make a call from inside, with the SfB client, the sound is fine. We have about 30 Hunt Groups/IVR's, but only one with this problem. We did create a test group to use for troubleshooting, and we get the same issue. The test group is also using a different gateway than the one we need to get fixed. Any Ideas?

    This is SfB 2015 on prem.

    Best regards


    • Edited by Rune Bilden Friday, November 17, 2017 2:58 PM
    Friday, November 17, 2017 2:56 PM

All replies

  • Hm, the audio file will be stored on the file share, maybe some problems to access the file share correct or performance issue on the mediation server which used from the response group?

    regards Holger Technical Specialist UC

    Saturday, November 18, 2017 12:58 PM
  • Hi Rune,

    Check the All wave files meet the following requirements:

    • 8-bit or 16-bit file
    • Linear pulse code modulation (LPCM), A-Law, or mu-Law format
    • Mono or stereo
    • 4MB or less

    For the best performance of wave files, a 16 kHz, mono, 16-bit Wave file is recommended.

    Based on my research, the choppy sound in response groups might be caused by insufficient network bandwidth, out of date video or network card driver and overloaded system resources.


    Regards,

    Leon Lu


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, November 20, 2017 6:53 AM
  • Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.

    Regards,

    Leon Lu


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, November 21, 2017 6:59 AM