The developers are definitely incorrect. The 302 might not even be
originating from your UAS. It could have been a device further upstream
that triggered the 302 (and/or yet another device that triggered the 183
for that matter).

Regards,
Brian 

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 02, 2007 12:53 PM
> To: [email protected]
> Subject: Re: [Sip] 302 question
> 
>    From: Mihaly Zachar <[EMAIL PROTECTED]>
> 
>    The UAS has a feature, that if the called number is 
> matching with a 
>    pattern, it will send 183 Session in progress, than plays 
> an RTP stream 
>    and then redirect the UAC with 302 Moved Temporarily..
> 
>    There is an UAC, and it's developers says that I should 
> not send 302 
>    Redirect after the 183 Session in progress.
> 
> I believe the developers are incorrect.  In RFC 3261, section 
> 13.1, top of page 78, we see:
> 
>    After some time, those UASs can accept the invitation (meaning the
>    session is to be established) by sending a 2xx response.  If the
>    invitation is not accepted, a 3xx, 4xx, 5xx or 6xx response is
>    sent, depending on the reason for the rejection.  Before sending a
>    final response, the UAS can also send provisional responses (1xx)
>    to advise the UAC of progress in contacting the called user.
> 
>    After possibly receiving one or more provisional responses, the UAC
>    will get one or more 2xx responses or one non-2xx final response.
> 
> This text implies that a provisional response may precede a 
> non-2xx final response.
> 
> Dale
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> [EMAIL PROTECTED] for questions on current sip 
> Use [EMAIL PROTECTED] for new developments on the application of sip
> 


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to