[SIPForum-discussion] Proxy-Authorization in initial INVITE

Ayyanar PK pkayyanar at in.com
Wed Nov 11 12:58:53 UTC 2009


Hi all,I want to make a call through a REGISTRAR; after registering when I call, I receive 407.On receiving 407 the following are the credentials usually sent in a new INVITE ProxyAuthorization: Digest username="5069028",realm="asterisk",nonce="065f0127",algorithm=MD5,uri="sip:00497119581217 at 87.193.224.70;user=phone",response="4ad396434a537a3cfe26ca1db9e74a00"Authentication Scheme: DigestUsername: "5069028"Realm: "asterisk"Nonce Value: "065f0127"Algorithm: MD5Authentication URI: "sip:00497119581217 at 87.193.224.70;user=phone"Digest Authentication Response: "4ad396434a537a3cfe26ca1db9e74a00"I don't want to receive 407, instead I want to send Authorization credentials in the initial itself so that the proxy allows the call. Please read RFC3261 section referred below. In that case what are the parameters to be sent in ProxyAuthorization header in initial invite.I tried with username and realm parameters alone but I only received 407. RFC does not mention about the particular crede
 ntial fields to be sent in initial INVITE if a UAC is not willing to receive 407. Can some one clarify this ?22.3 ProxytoUser AuthenticationAny UA that wishes to authenticate itself to a proxy server  usually, but not necessarily, after receiving a 407 (Proxy Authentication Required) response  MAY do so by including a Proxy Authorization header field value with the request.The Proxy Authorization requestheader field allows the client to identify itself (or its user) to a proxy that requires authentication.The ProxyAuthorization header field value consists of credentials containing the authentication information of the UA for the proxy and/or realm of the resource being requested.Regards,Ayyanar Dear discussion ! Get Yourself a cool, short @in.com Email ID now!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20091111/dcbb3eaa/attachment-0002.html>


More information about the discussion mailing list