Client does not handle SUBSCRIBE/202 responses properly

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run client against a presence server, that needs to wait for IO before 
determining auth policy.
2. Server responds to SUBSCRIBE with a 202 (see RFC 3265 Sec 3.1.4.1)

What is the expected output? What do you see instead?

Client logs indicate that it considers the subscription failed:
*snip*
V/[RCS][SipInterface](  261): <<< Receive SIP 202 response
V/[RCS][SipInterface](  261): Callback object found for transaction 
v4NbY5SKAA@10.0.2.15
I/[RCS][PresenceSubscribeManager](  261): Subscribe has failed: 2, reason=202 
Accepted
V/[RCS][PresenceSubscribeManager](  261): Stop timer
V/[RCS][PresenceService](  261): Subscribe manager can't be started for presence
*snip*

What version of the product are you using? On what operating system?
2.2.0, emulator on OS X 10.6.6

Please provide any additional information below.

Original issue reported on code.google.com by docfara...@gmail.com on 24 Feb 2011 at 4:36

[GoogleCodeExporter]

You are right. This will be corrected in the next release. Thanks.

Original comment by jmauffret@gmail.com on 2 Mar 2011 at 6:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by jmauffret@gmail.com on 28 Mar 2011 at 6:40

• Changed state: Fixed