Re: [reSIProcate-users] repro

[Byron Campen <bcampen@xxxxxxxxxxxx>]

	Registration is only used for binding your AOR to a contact that you  
can be reached at; it is not for setting up any kind of auth binding  
(ie, it is not in any way comparable to "logging in" to a system).  
IMS has decided to use REGISTER in this way (which gives the folks  
who work on IETF SIP plenty of headaches), but repro is not an IMS  
proxy. The credentials must be present in every request (although  
repro makes an exception for ACK and BYE).

Best regards,
Byron Campen


> i'm using sipp as client...
>
> 1)  i send a REGISTER request
> 2)  repro responds with 407 proxy authentication required
> 3)  then i send REGISTER again with Proxy-Authorization
> 4)  repro responds with 200 OK
> 5)  Next i send INVITE message. This message does not have Proxy- 
> Authorization
> 6)   repro responds with 407 proxy authentication required
>
>
> If i have registered earlier in REGISTER message, then why should i  
> send authorization information again??
>
> In step 5, i tried sending INVITE with Proxy-Authorization....but I  
> get back 403 authentication failed message.
> But i'm using the same information for proxy authorization as used  
> in REGISTER message....still i get 403 error...
>
> I'm sending INVITE message to another client running in another  
> terminal. This client is REGISTERED and is waiting for INVITE message.
> But since the previous client failed, INVITE message never arrives  
> at this one.
>
> I'm new to SIP and reSIProcate...please HELP......
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature