Comment #5 on issue 2173 by jean.deruelle: Handle Header
[Authentication-Info: nextnonce="xyz"] in sip authorization responses
http://code.google.com/p/mobicents/issues/detail?id=2173
Actually. It would be more cache the credentials when they are passed ie
when the request sent out gets challenged (so on the creation of the
challenged request to a 401/407). So that the container can reuse the
credentials to recalculate the response digest based on the nextnonce to
build the next subsequent request without any input.
The process will be the following
INVITE/REGISTER sent by MSS app
401/407 received
INVITE/REGISTER with correct Authorization headers value and the app use
the newly defined method to cache the username and password passed
200OK received with Authentication-Info containing nextnonce
MSS App sends subsequent requests which contains the correct nonce and
digest based on the nextnonce received in the 200OK and username and
password cached from the beginning.
