Hi Tomek,
I think this is your answer ;) :
RFC 3261 22.1
While a server can legitimately challenge most SIP requests, there
are two requests defined by this document that require special
handling for authentication: ACK and CANCEL.
Under an authentication scheme that uses responses to carry values
used to compute nonces (such as Digest), some problems come up for
any requests that take no response, including ACK. For this reason,
any credentials in the INVITE that were accepted by a server MUST be
accepted by that server for the ACK. UACs creating an ACK message
will duplicate all of the Authorization and Proxy-Authorization
header field values that appeared in the INVITE to which the ACK
corresponds. Servers MUST NOT attempt to challenge an ACK.
--
PG
2007/11/8, Tomasz Zieleniewski <tzieleniewski(a)gmail.com>om>:
Hi,
When I invoke proxy_authorize and radius_proxy_authorize for an ACK
message the is no uid avp present.
All other messages which are authorized work fine.
Why is that so??
Is it the right behaviour??
Bests regards
Tomasz