1. 13 7月, 2017 1 次提交
    • Anthony Minessale's avatar
      FS-9979: [verto.js] When verto client rejects a call returns hangup cause… · 89e3a7bb
      Anthony Minessale 提交于
      FS-9979: [verto.js] When verto client rejects a call returns hangup cause NORMAL_CLEARING #comment passing neither cause or causeCode will result in normal clearing, passing either one of cause or causeCode will result in that value being passed and parsed on the server side, if the cause is valid it will be accepted otherwise it will try to validate causeCode instead, if neither are true it defaults to normal clearing #resolve
      89e3a7bb
  2. 12 7月, 2017 2 次提交
  3. 11 7月, 2017 8 次提交
  4. 10 7月, 2017 2 次提交
    • Ethan Atkins's avatar
      FS-10485: Re-activate ICE on all attribute changes · 999a6dd0
      Ethan Atkins 提交于
      I ran into some ice failures when testing reinvites using
      bypass_media_after_bridge. Every ice session has ice-ufrag and ice-pwd
      attributes. When leg A sends those attributes to leg B, leg B is
      supposed to send stun packets to leg A using the credentials provided in
      those attributes. Freeswitch was not updating the session credentials
      when the phone sent a new invite containing new ufrag and pwd
      attributes. This caused ICE to fail on the client side (PJSIP in this
      case).
      
      The new_ice flag is set to true when freeswitch detects a change in
      those attributes. For whatever reason, the reinvite flows that I was
      testing did not set the CF_REINVITE flag on the channel, but new_ice was
      true. It seems to me that freeswitch should always reactivate ice when
      the ufrag and pwd credentials change.
      999a6dd0
    • Mike Jerris's avatar
  5. 07 7月, 2017 1 次提交
  6. 06 7月, 2017 9 次提交
  7. 05 7月, 2017 7 次提交
  8. 03 7月, 2017 8 次提交
  9. 30 6月, 2017 2 次提交