Improve Jingle error messages

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: 2.5.0
  • Fix Version/s: 2.5.1
  • Component/s: Jingle
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

The Jingle error messages need to be better. I tried a call with Daniel that failed due to a strict firewall on his side. My error was "Voice chat ended". His error was "Voice chat was rejected". We need to list out all the possible reasons why a Jingle call can fail and provide the best error messages possible to avoid user frustration. For example:

"Unable to negotiate audio session. This may be caused by firewall configuration problems."

or, maybe something even better.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Thiago Rocha Camargo added a comment -

We already have conditions to warn about firewalls.
But jingle don't provide a session termination due an error stanza for transport candidates connectivity fail.

Show
Thiago Rocha Camargo added a comment - We already have conditions to warn about firewalls. But jingle don't provide a session termination due an error stanza for transport candidates connectivity fail.
Hide
Permalink
Thiago Rocha Camargo added a comment -

Improved Messages. But still needs firewall warnings.

Show
Thiago Rocha Camargo added a comment - Improved Messages. But still needs firewall warnings.

People

  • Assignee:
    Thiago Rocha Camargo
    Reporter:
    Matt Tucker
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: