Hi Michael, Yes, that's correct, if the UAS requires authentication, the firs INVITE from UAC (going out without authentication fields in headers) is challenged with 401 or 407, where UAS specifies its realm. Then, if user name and password were set by the app for this realm, HMP automatically sends the second invite, already with authentication data populated. Is this what you are seeing? Please send me the wireshark or RTF snippet where this exchange is seen.
↧