[asterisk-dev] [Code Review] SIP: for an INVITE transaction, treat all 2XX responses the same as a 200

[sst at sil.at]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/935/#review2777
-----------------------------------------------------------


sorry after reading rfc 3265 again, i see i have missunderstood something.
a 202 could be the response to a SUBSCRIBE not to a NOTIFY. But even after a 202 you will get a notify as subscriber (that was my missunderstanding ;) 
Until asterisk didnt send subscribes out the only way a 202 would be received is the REFER state, and thats allready handled.

for me its a ship it but after saying that amount of wrong information i am afraid of give it ;)

- schmidts


On 2010-09-22 17:03:18, David Vossel wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/935/
> -----------------------------------------------------------
> 
> (Updated 2010-09-22 17:03:18)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> Currently if Asterisk receives any 2XX response to an outgoing INVITE other than a 200 it is ignored.  I have changed this behavior to treat all 2XX responses the same as a 200.  RFC3261 section 13.2.2.4 which outlines how a 2XX response should be handled in response to an INVITE request seems to treat all 2XX responses the same.  I don't see any reason why our implementation should be specific to only 200 Ok responses. 
> 
> 
> Diffs
> -----
> 
>   /trunk/channels/chan_sip.c 288419 
> 
> Diff: https://reviewboard.asterisk.org/r/935/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> David
> 
>