User-Agent parsing error using jainslee sipRa

[GoogleCodeExporter]

Hi, 
we are using a jainslee plataform to develop our sip AS. We have been testing 
with snoms ciscos and android phones (early versions of your program 2.0.431) 
however recently we've been getting an error when using your latest 
version(2.0.484).

when we are parsing using the opencloud jainslee standard compatible sipRa we 
get an error:
Caused by: java.text.ParseException: no character matching rule token found at 
current index, buf=", LG-P500"

this is caused by parsing the user-agent header on the sip invite:
User-Agent: IM-client/OMA1.0 android-ngn-stack/v2.0.484 doubango r685, LG-P500

there is a comma separating the mobile phone version from the rest of the 
information. and that is causing the problem. 

I think the problem is your since the user agent syntax does not include commas 
to separate the information:

http://www.ietf.org/rfc/rfc2616.txt
      User-Agent     = "User-Agent" ":" 1*( product | comment )
   Example:
       User-Agent: CERN-LineMode/2.15 libwww/2.17b3

so the solution might be removing the comma and let the empty space separate 
the information.

Mean while we will continue to test our program with your previous version that 
didn't put a comma in the user-agent field

thanks for your attention

Original issue reported on code.google.com by hugo...@gmail.com on 10 Apr 2012 at 10:22

Attachments:

• [New Text Document.txt](https://storage.googleapis.com/google-code-attachments/imsdroid/issue-339/comment-0/New Text Document.txt)

[GoogleCodeExporter]

Fixed in revision 486.
Will be part of the next release.
You should use the latest release which contains many fixes (crashes).

Original comment by boss...@yahoo.fr on 10 Apr 2012 at 8:12

• Changed state: Accepted

[GoogleCodeExporter]

Fixed byIMSDroid 2.0.487.

Original comment by boss...@yahoo.fr on 3 May 2012 at 11:51

• Changed state: Fixed