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
In From/To/Contact always use name-addr format regardless there is display-name or not. A SIP URI allows ":" in a UR param value, but if such a URI appears in a header allowing name-addr/spec-addr like header (To/From/Contact/) then the URI must be enclposed between < > (so name-addr format is required).
Also do it in Contact within the new ua.contact.toString(anonymous=false) mechanism. I would suggest that such a toString method ALWAYS returns a name-addr style Contact value, so if you need to pass ;ob to the URI do it by passing some kind of optional argument to contact.toString() method:
ua.contact.toStrking({
anynomous: true,
outbound: true // this would add ";ob" in Contact URI params
});
The text was updated successfully, but these errors were encountered:
In From/To/Contact always use name-addr format regardless there is display-name or not. A SIP URI allows ":" in a UR param value, but if such a URI appears in a header allowing name-addr/spec-addr like header (To/From/Contact/) then the URI must be enclposed between < > (so name-addr format is required).
Also do it in Contact within the new
ua.contact.toString(anonymous=false)
mechanism. I would suggest that such a toString method ALWAYS returns a name-addr style Contact value, so if you need to pass ;ob to the URI do it by passing some kind of optional argument to contact.toString() method:The text was updated successfully, but these errors were encountered: