You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
Make up our own enumerations and map them to SIP codes in implementations (informally document best-practice mappings) very much like we do for <reject/> etc. If we do this, what should the allowed values be?
The granularity of the SIP cause codes seems preferable at this point, although I personally think the XMPP codes being more generic would allow for greater future extensibility.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SIP Reason header should be settable, probably indirectly via named reasons in the Rayo spec.
The text was updated successfully, but these errors were encountered: