Need info on RCS server to accept REGISTER requests

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install these apk's in device.
2. A sip proxy server is running in the device itself , so give the outbound 
proxy details in provisioning to this server.
3. Start the RCS service from settings.

What is the expected output? What do you see instead?
User is getting registered to my sip server and server is giving 200 OK but RCS 
app is throwing error as 'Registration failed: Cant read a SIP-URI from the 
Associated P-Associated-URI header '. I guess my SIP server doesnot include any 
private headers.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Requesting you to please help me in running this application on the device.

Please tell me if there is any public RCS SIP server available so that I can 
give that server's details as outbound proxy.

Original issue reported on code.google.com by archana...@gmail.com on 27 May 2011 at 5:35

[GoogleCodeExporter]

In fact your IMS platform don't send the P-Associated-URI header which is used 
to set the public URI from the registration procedure. I will do a patch to 
correct this issue in order to be more open at this level.
Thanks for your feedback.

Original comment by jmauffret@gmail.com on 27 May 2011 at 6:53

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Now we authorize 200 OK without a P-Associated-URI

Original comment by jmauffret@gmail.com on 27 May 2011 at 7:32

[GoogleCodeExporter]

Hi,
Thanku for your response.
If i do a checkout of the code now, will I get the latest code with the above 
changes?

Original comment by archana...@gmail.com on 27 May 2011 at 7:38

[GoogleCodeExporter]

HI, 
I downloaded the code and checked. Still its getting associated header in 
handle200OK.
PLease tell me when could this be fixed and updated in the code.

Original comment by archana...@gmail.com on 27 May 2011 at 9:09

[GoogleCodeExporter]

I just done the correction in the source code. This is not yet produced in the 
apk file.

Original comment by jmauffret@gmail.com on 27 May 2011 at 9:29