Look into the manual how to handle the authentication dynamically. The
contents of the Authorization header cannot be static as it is a
response to a dynamically changing challenge used to prove that the UAC
knows the shared secret. So the correct procedure is that you send a
request with no Authorization header at all (or one with an old
contents), and if the UAS sends you a 401 with an authentication
challenge, you re-send the same request with an Authorization header
with the correct answer to the challenge.
The UAC scenario must account for this possibility, it is not done
automatically. I.e. one possible implementation:
send INVITE without Authorization
recv 100, 180, 183, ... optional
recv 401 optional next auth-invite
recv 200 next call-success
label auth-invite
send INVITE with Authorisation
recv 100, 180, 183, ... optional
recv 401 optional next authentication-failure
recv 200
label call-success
...
label authentication-failure
Pavel
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
