Closed GoogleCodeExporter closed 9 years ago
Usually that's more linked to the sip server than from the client .
Read my comment here :
http://code.google.com/p/csipsimple/issues/detail?id=9#c10
The only thing I could try is to enforce encoding in my headers to let know the
other part that it is utf8 and cross the fingers it will not break things with
all others ;)
Original comment by r3gis...@gmail.com
on 29 May 2011 at 11:36
Ok, sounds that there is a problem with the jni glue.
To be fixed.
Original comment by r3gis...@gmail.com
on 4 Jan 2012 at 3:55
Issue 1315 has been merged into this issue.
Original comment by r3gis...@gmail.com
on 4 Jan 2012 at 3:56
It should be fixed in nightly builds. Could you tell me how it goes with latest
nightly (http://nightlies.csipsimple.com/trunk/)
There is probably a lot of regression on other part of this nightly, but if you
could just do a quick test to tell me if utf8 problem is fixed would be great :)
Thx in advance
Original comment by r3gis...@gmail.com
on 8 Jan 2012 at 5:29
I tried the latest trunk (17-Jan-2012) which seems to be ice cream sandwich
themed. Unfortunately, I can't receive English or Arabic sms. When I try to
compose a message it FC. I don't know if me not running ICS has anything to do
with it. I am on Android 2.3.5 sense 3.5. Ironically the DTMF seems to be
functioning well with in this version which never worked with me before.
Original comment by talebhr@gmail.com
on 17 Jan 2012 at 6:12
Thanks for feedback.
I did other fixes in UI for backward compatibility. Which should make things
better with 2.3. (http://nightlies.csipsimple.com/trunk/)
If you still get force close, can you try to collect logs (see HowToCollectLogs
wiki page) and reference to this issue number in the mail sent.
Thanks
Original comment by r3gis...@gmail.com
on 27 May 2012 at 10:50
Original issue reported on code.google.com by
igor.karasenko@gmail.com
on 26 May 2011 at 1:52