biddyweb / android-rcs-ims-stack Goto Github PK

What steps will reproduce the problem?
1.some offline display/delivery reports are waiting for client
2.the client goes online
3.the client does not get display/delivery reports

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

The client should get display/delivery reports. 
According to our analysis, it is SBC that rejects 'TCP SYN' which is used for 
TCP connection establishment. 
Then we contact with the SBC guys. They explain us that the client uses 
a=recvonly in SDP for session negotiations, and this a=recvonly cannot be used 
for TCP connection, because TCP connection is both directions connection, not 
receive only.

Do you agree their explanation?

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


Please provide any additional information below.
We tested it in a real IMS/RCSe environment.

What steps will reproduce the problem?
1. Receive a message with CPIM base64 encoded (text or delivery notification)

What is the expected output? What do you see instead?
Message could be decoded. Base64 encoded string is displayed.

What version of the product are you using? On what operating system?
2.3.4, Android 2.3.3

Please provide any additional information below.
According to RFC 3862 Chapter 9, Content-Transfer-Encoding: base64 is allowed. 
Application could be ready to receive such messages, giving flexibility for 
support of additional clients.
Since Base64 class is alrwady included in the project, adding decoding to text 
messages and delivery reports is a 10-lines-of-code-job

What steps will reproduce the problem?
1.Establish one-to-one chat session between two clients - A and B(2.2.8)
2. Client A does not have the chat session in the foreground and Client B sends 
a chat message
3. No chat notification to Client A to indicate the new chat message.
4. No chat history stored for the clients A and B in the 'List of active 
sessions' in the 'Chat Sessions' activity.

What is the expected output? What do you see instead?
1) Push notification should be sent for a new chat message to Client A when 
chat session is not in foreground for Client A.
2) No chat history stored for the clients A and B in the 'List of active 
sessions' in the 'Chat Sessions' activity.

What version of the product are you using? On what operating system?
RCS-e client, version 2.2.8

Please provide any additional information below.

It looks like there is no TCP transport in the SIP stack.  Are there plans to 
implement it?

This problem has been encountered when trying to register an android phone 
emulator using the android-rcs-ims-stack in an openIMS network.

What steps will reproduce the problem?
1.use of a openIMS network. 
2.configuration of the user in order to use the network server. 
3.start the RCS service application on the android emulator.

What is the expected output? What do you see instead?
After receiving a REGISTER message from the android phone emulator, the openIMS 
network responds with a challenge request "401 unauthorized". This request 
contains authentication rules where the qop is equal to "Auth, Auth-int". The 
android phone responds with a REGISTER request that contains a response to the 
challenge request. This response contains the option qop with one of the values 
listed in the challenge: "Auth" or "Auth-Int".

The problem is that the response to the challenge returns the list of qop 
values except one of them. This is not compliant with the RFC2617 where it is 
written that:

 qop :Indicates what "quality of protection" the client has applied to
 the message. If present, its value MUST be one of the alternatives
 the server indicated it supports in the WWW-Authenticate header.
 [...]. Note that this is a single token, not a quoted list of 
 alternatives as in WWW- Authenticate. [...].

What version of the product are you using? On what operating system?
The version used is the 2.0.8 available for download.
This is used with an android emulator 2.2

Please provide any additional information below.
The error has been localized in the method writeSecurityHeader of the class 
HttpDigestRegistrationProcedure called from the method createRegister of the 
SipMessageFactory class. This class is localized under directory 
core\src\com\orangelabs\rcs\core\ims\network\registration.
The qop value is retrieved from the 401 SIP response, if its value starts with 
"auth", the complete value is pasted in the REGISTER SIP request.

String qop = digest.getQop();
if ((qop != null) && qop.startsWith("auth")) {  
    auth += ",nc=" + digest.buildNonceCounter() +
    ",qop=" + qop +

What steps will reproduce the problem?
1. Send a chat message with non-latin character(s)

What is the expected output? What do you see instead?
Content-Length with correct number of characters. Currently incorrect number is 
included.

What version of the product are you using? On what operating system?
2.3.4, Android 2.3.3

Please provide any additional information below.
Example is with sending a text message with content of "cześć" which in 
Polish means "hi". It contains two special characters - "ść". 
Characters are encoded using UTF-8 (octal) which is visible in trace as 
"cze\305\233\304\207". Content-Length is calculated as 5 (which is true for a 
human) but really is 7 (two special characters are encoded as 4 - 
\305\233\304\207).
A strict SBC or application of other party may reject such message.
Example below (special characters in CPIM are dotted, numbers and domain 
hidden): 
(...)

--boundary1
Content-Type: message/cpim
Content-Length: 296

From: <sip:+48xxxxxxxxx@xxxxxxxxxxxxxxxx>
To: <tel:+48xxxxxxxxx>
NS: rcse <urn:g5:rcse:im>
imdn.Message-ID: MsgxrVsdTTABA
DateTime: 2012-01-14T19:28:35.000Z
imdn.Disposition-Notification: positive-delivery, negative-delivery, display

Content-type: text/plain
Content-length: 5

cze....
--boundary1--

The actual Content-lenght is 7. All parent Content-lengths (SIP & CPIM) are 
also therefore incorrect.

Current code codifies capabilities in Contact Header repeating the feature tag:
Contact: 
XXXX;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.im";+g.3gpp.
iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.ft"

This is against SIP RFC3261, that clearly states that

"Even though an arbitrary number of parameter pairs may be attached to a header 
field value, any given parameter-name MUST NOT appear more than once."

RFC 3840 and 3GPP TS 24.229 (section 7.9.3) mandate the format of the feature 
tags: the value MUST be separated by "," (and then probably encoded using the % 
format).

Example, using an example given the RFC3840, this is what the RFC3840 says is 
the proper way to encode a "methods" tag:

Contact: <sip:[email protected]>;audio;video
     ;actor="msg-taker";automata;mobility="fixed"
     ;methods="INVITE,BYE,OPTIONS,ACK,CANCEL"

This is what we the client would be doing:

Contact: <sip:[email protected]>;audio;video
     ;actor="msg-taker";automata;mobility="fixed"
     ;methods="INVITE";methods="BYE";methods="OPTIONS";methods="ACK";methods="CANCEL"

I think this formatting is against IARI 3GPP and RFC, and also against basic 
SIP formatting rules.

Use two android devices
Source=Sony Ericsson Xperia
Destination=Nexus S

What steps will reproduce the problem?
1. Start RCS 2.0 RI on Android and select Rich Call
2. Select Initiate image sharing
3. Select User 
4. Select a picture
5. Press the Invite button

What is the expected output? What do you see instead?
There should be a prompt on the destination mobile phone asking for approval to 
accept shared image

Instead: I am getting an alert message: Error 2

Detailed trace on adb
03-22 16:19:13.264: INFO/[RCS][OriginatingContentSharingSession](2716): Session 
error: 2, reason=Session Not acceptable

What version of the product are you using? On what operating system?
RCS 2.0 Reference Implementation 2.1.1
Android 2.1-Update1

Please provide any additional information below.
If I start up imsdroid on the destination (source still using RCS RI client), 
it works.

I config the cleint User Profile to point to a Local SIP Server(Using Emulator 
an also wifi with a Device) and provide valid user credentials. However the 
Client does not Do anything once the RCS Service is started. it does not send 
the REGISTER request( as seen in ethereal)

I suppose the Address Book Shown after the Settings are configured and RCS 
option is Enabled

I am using version 2.0.0

Please let me know of any steps(or all the steps) that in missed in the Client 
set up so as to use the service.

Thanks and Regards
Shashi Kiran G M

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 
[email protected]
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.

On the XCAP HTTP interface, the RCS client is sending this as the request line 
of the PUT message:

PUT 
/xcap-root/resource-lists/users/sip%3A%2B36304722911%40rcse.tst/index/~~/resourc
e-lists/list%5B@name=%22rcs%22%5D/entry%5B@uri=%22sip%3A%2B36204869989%40rcse.ts
t;user=phone%22%5D HTTP/1.1

At the end of the URI the semicolon is not escaped in "...rcse.tst;user=phone" 
value.

According to the sources, the encodeURL() function of 
core/src/com/orangelabs/rcs/core/ims/service/presence/xdm/HttpUtils.java file 
needs to be extended with semicolon escaping support.

What steps will reproduce the problem?
1. Configure client with xcap support.
2. Ensure xcap server supports org.openmobilealliance.xcap-directory, and has a 
document (any document) provisioned in the user's resource-lists tree.
3. Client does an XCAP GET operation with an unquoted If-match header field 
value.

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

From the XCAP GET:
GET 
/resource-lists/users/sip%3AAndroid1%40example.com/index/~~/resource-lists/list%
5B@name=%22rcs%22%5D HTTP/1.1
Host: example.com:80
User-Agent: OrangeLabs-RCS-client 2.2.0
X-3GPP-Intended-Identity: Android1
If-match: DGS9Db3adCY=
Content-Length: 0

The If-match header field value is malformed; it should read as follows (see 
RFC 2616 Sec 3.11):

GET 
/resource-lists/users/sip%3AAndroid1%40example.com/index/~~/resource-lists/list%
5B@name=%22rcs%22%5D HTTP/1.1
Host: example.com:80
User-Agent: OrangeLabs-RCS-client 2.2.0
X-3GPP-Intended-Identity: Android1
If-match: "DGS9Db3adCY="
Content-Length: 0

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.

What steps will reproduce the problem?
1. Configure the outbound proxy without a port.

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

Ideally, using an outbound proxy with no port should cause NAPTR/SRV lookups to 
be used as specified in 3263 (which will result in TCP being used if DNS is set 
up to prefer it). Instead, no DNS lookups are performed, and no SIP traffic is 
observed. (As I understand it, you are using the NIST JAIN SIP stack, which has 
a 3263-compliant resolver here: 
http://code.google.com/p/jain-sip-rfc3263-router/ )


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

Please provide any additional information below.

How do  test the android-rcs-ims-stack?   Can use Open IMS Core ?
What XCAP ( or XDM ) SERVER ?
Please give suggestions on how to build a test environment.

What steps will reproduce the problem?
1.Which method send Regist message?
2.
3.

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


What version of the product are you using? On what operating system?
2.2.0   on Android 2.2

Please provide any additional information below.

What steps will reproduce the problem?
1. Configure client to talk to an xcap server

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

3GPP TS 24.109 defines the BNF for X-3GPP-Intended-Identity as follows:

*snip*
   X-3GPP-Intended-Identity = "X-3GPP-Intended-Identity" ":" DQUOTE identity DQUOTE
   identity = *(%x20-21 / %x23-7E)
*snip*

The client emits the following:

*snip*
X-3GPP-Intended-Identity: Android1
*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.

This is not a bug but a current limitation. 

Currently RCS supports only low quality video (H263 176 by 144px). 

What can we do to support high quality video (H264 480 by 360px)?

What steps will reproduce the problem?
1.invite another rcs account using 3g not using wifi
2.the receiver is going into the chat view, but the inviter cannot get into the 
chatview
3.check the log i got the exception

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

 Unexpected internal error FIXME!! Cannot create ACK - no ListeningPoint for transport towards next hop found:UDP
 javax.sip.SipException: Cannot create ACK - no ListeningPoint for transport towards next hop found:UDP
     at gov.nist.javax.sip.stack.SIPDialog.createAck(SIPDialog.java:2443)
     at com.orangelabs.rcs.core.ims.network.sip.SipMessageFactory.createAck(SipMessageFactory.java:632)
     at com.orangelabs.rcs.core.ims.protocol.sip.SipInterface.sendSipAck(SipInterface.java:727)
     at com.orangelabs.rcs.core.ims.network.sip.SipManager.sendSipAck(SipManager.java:172)
     at com.orangelabs.rcs.core.ims.service.im.chat.OriginatingOne2OneChatSession.handle200OK(OriginatingOne2OneChatSession.java:300)
     at com.orangelabs.rcs.core.ims.service.im.chat.OriginatingOne2OneChatSession.sendInvite(OriginatingOne2OneChatSession.java:225)
     at com.orangelabs.rcs.core.ims.service.im.chat.OriginatingOne2OneChatSession.run(OriginatingOne2OneChatSession.java:153)
ERROR/[RCS][SipMessageFactory](470): Can't create SIP message
 java.lang.RuntimeException: Unexpected internal error FIXME!! Cannot create ACK - no ListeningPoint for transport towards next hop found:UDP
     at gov.nist.core.InternalErrorHandler.handleException(InternalErrorHandler.java:45)
     at gov.nist.javax.sip.stack.SIPDialog.createAck(SIPDialog.java:2495)
     at com.orangelabs.rcs.core.ims.network.sip.SipMessageFactory.createAck(SipMessageFactory.java:632)
     at com.orangelabs.rcs.core.ims.protocol.sip.SipInterface.sendSipAck(SipInterface.java:727)
     at com.orangelabs.rcs.core.ims.network.sip.SipManager.sendSipAck(SipManager.java:172)
     at com.orangelabs.rcs.core.ims.service.im.chat.OriginatingOne2OneChatSession.handle200OK(OriginatingOne2OneChatSession.java:300)
     at com.orangelabs.rcs.core.ims.service.im.chat.OriginatingOne2OneChatSession.sendInvite(OriginatingOne2OneChatSession.java:225)
     at com.orangelabs.rcs.core.ims.service.im.chat.OriginatingOne2OneChatSession.run(OriginatingOne2OneChatSession.java:153)
 Caused by: javax.sip.SipException: Cannot create ACK - no ListeningPoint for transport towards next hop found:UDP
     at gov.nist.javax.sip.stack.SIPDialog.createAck(SIPDialog.java:2443)
     ... 6 more

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

Please provide any additional information below.

It's was ok in the simulator.

What steps will reproduce the problem?
1.Install 2.2.8 rcs-e client application on the android phone.
2.Initiate one-to-one chat with another phone.
3.SIP INVITE does not go through.
(Please refer to packet 1274 in the attached capture.)

What is the expected output? What do you see instead?
- SIP INVITE should go through and the chat session should be established. The 
INVITE does not go through and 403 Forbidden Error is received.Please refer to 
packet 1274 in the attached capture.

What version of the product are you using? On what operating system?
- RCS-e client, version 2.2.8, 

Please provide any additional information below.
We fixed the SIP INVITE failure by making the following changes in 
com.orangelabs.rcs.core.ims.network.sip.SipMesageFactory.java -

1) Route: header needs to be prefixed to include both defaultRoute and Route.

Ex: Route: <sip:10.67.64.21:4060;lr;transport=UDP> needs to be changed to 
something like - Route: 
<sip:10.67.64.21:4060;lr;transport=UDP>,<sip:[email protected]:6060;lr>

Code snippet
============
            // Set the Route header
            Vector<String> defaultRoute = dialog.getSipStack().getDefaultRoutePath();
            for(int i=0; i < defaultRoute.size(); i++) {
                Header defaultRouteHeader = SipUtils.HEADER_FACTORY.createHeader(RouteHeader.NAME, defaultRoute.elementAt(i));
                invite.addHeader(defaultRouteHeader);
            }

            // Set the Route header
            Vector<String> route = dialog.getRoute();
            for(int i=0; i < route.size(); i++) {
                Header routeHeader = SipUtils.HEADER_FACTORY.createHeader(RouteHeader.NAME, route.elementAt(i));
                invite.addHeader(routeHeader);
            }


2)Formatting the P-Preferred-Identity header to remove the 'user=phone' tag

Ex:P-Preferred-Identity: "anu" <sip:[email protected];user=phone> 
needs to be changed to P-Preferred-Identity: <sip:[email protected]>

Code snippet
============
            // Set the P-Preferred-Identity header
            AddressImpl formatAddress = (AddressImpl)SipUtils.ADDR_FACTORY.createAddress(dialog.getLocalParty());
            formatAddress.removeParameter("user");
            Header prefHeader = SipUtils.HEADER_FACTORY.createHeader(SipUtils.HEADER_P_PREFERRED_IDENTITY, formatAddress.getURI().toString());
            invite.addHeader(prefHeader);


Please let us know if the above fixes are correct and also if there are any 
other changes that 2.2.8 apks are missing.

What steps will reproduce the problem?
1.
2.
3.

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


What version of the product are you using? On what operating system?
release 2.2.0,on android 2.2

Please provide any additional information below.
The RCS-e 1.1 standards requires SSO/GIBA Authentication, but I had not found 
any code about this in the stack, will it be implemented?

What steps will reproduce the problem?
1. A initiates IM session to B. SIP level is OK. SIP session established.
2. B responds via MSRP with cpim message containing Content-Type header (note 
capital T).
3. A party's client does not process the message correctly and therefore does 
not display the message to user A

What is the expected output? What do you see instead?
Expected would be to see the message.

What version of the product are you using? On what operating system?
2.3.4, checked also on older versions, same result. Android 2.3.4 & 2.3.3.

Please provide any additional information below.
N/A

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.

What steps will reproduce the problem?
1. Setup ekiga account with device's full mobile number
2. Provision the stack with the account information. Login successful
3. Add a contact. This contact is another device logged in to RCS stack using 
[email protected]
4. Initiate voice call between the devices. Both the devices are 3G enabled.
5. Open RI app -> Rich call -> Initiate Image sharing

What is the expected output? What do you see instead?
Added contact should be available in the drop down. I see no contact is listed. 
Attaching the screen shot of the issue.


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

Please provide any additional information below.
Same observation for Messaging -> Transfer File
But I can see contacts listed in Capabilities -> Request Capabilities

Because of this problem I am not able to initiate any communication between the 
2 RCS devices.

I am trying to use the code for v2.2.0 to use for my project. When I try to 
generate apks using Eclipse, and try to install it on the device or on an 
emulator, the application force closes itself. Could you let me know why would 
that occur? Also, if this is not how it is to be done, then what steps should 
be followed to correctly generate the apks. Thanks a lot.

What steps will reproduce the problem?
1.
2.
3.

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


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

Please provide any additional information below.
it seems to lose a in core version 2.3.0:
com.orangelabs.rcs.core.ims.service.SessionIdGenerator

it added in version 2.3.1, but it may course errors when check out 2.3.0.

Is tablet(Androd 3.x platform) suppoprted?

I have installed RCS-e stack/provision/service on a Xoom Tablet and 
Thunderbolt.  I have no problem of starting/registering RCS-e client on the 
Thunderbolt (Android 2.x).  However, I am not able to start RCS-e service on 
the Xoom.  DDMS shows that following errors.  

Thanks in advance,
Feng


09-26 15:05:04.160: INFO/[RCS][Core](844): Terminal core initialization
9-26 15:05:04.160: ERROR/[RCS][RcsCoreService](844): Can't instanciate the RCS 
core service
09-26 15:05:04.160: WARN/System.err(844): java.lang.NullPointerException
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.utils.DeviceUtils.getDeviceUUID(DeviceUtils.java:32)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.core.Core.<init>(Core.java:127)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.core.Core.createCore(Core.java:93)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.service.RcsCoreService.startCore(RcsCoreService.java:221)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.service.RcsCoreService.onCreate(RcsCoreService.java:158)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread.handleCreateService(ActivityThread.java:2039)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread.access$2500(ActivityThread.java:122)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1059)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.os.Handler.dispatchMessage(Handler.java:99)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.os.Looper.loop(Looper.java:132)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread.main(ActivityThread.java:4028)
09-26 15:05:04.160: WARN/System.err(844):     at 
java.lang.reflect.Method.invokeNative(Native Method)
09-26 15:05:04.160: WARN/System.err(844):     at 
java.lang.reflect.Method.invoke(Method.java:491)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
09-26 15:05:04.160: WARN/System.err(844):     at 
dalvik.system.NativeStart.main(Native Method)
09-26 15:05:04.170: INFO/AudioHardware(226): mSetVolumeIndex=0, 
mIsMusicPlaying=0, musicvolumeindex=8

I am trying to build the source on my mac but get error following error. Can 
you point me any doc/info on how to build? Particular version of android api?

I want to retrieve add Service-Route header from 200 OK of REGISTER request and 
than use while sending INVITE/MESSAGE.  This is required header for OpenIMS 
core. 

See the below build failure error. 

 [aaptexec] WARNNG: Using deprecated 'resources' attribute in AaptExecLoopTask.Use nested element(s) <res path="value" /> instead.
 [aaptexec] WARNNG: Using deprecated 'outfolder' attribute in AaptExecLoopTask.Use 'apkfolder' (path) instead.

BUILD FAILED
/Users/rohitjoshi/Projects/workspace/ims-client/trunk/core/build.xml:320: 
aaptexec doesn't support the "basename" attribute
    at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:396)
    at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:344)
    at org.apache.tools.ant.Task.maybeConfigure(Task.java:202)
    at org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:196)
    at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
    at org.apache.tools.ant.Task.perform(Task.java:347)
    at org.apache.tools.ant.Target.execute(Target.java:390)
    at org.apache.tools.ant.Target.performTasks(Target.java:411)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
    at org.apache.tools.ant.Main.runBuild(Main.java:801)
    at org.apache.tools.ant.Main.startAnt(Main.java:218)
    at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
    at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Caused by: The <aaptexec> type doesn't support the "basename" attribute.
    at org.apache.tools.ant.IntrospectionHelper.setAttribute(IntrospectionHelper.java:402)
    at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:388)
    ... 15 more

What steps will reproduce the problem?
1. Establish an Image Share session where the image receiver establishes the 
MSRP connection to the sender

What is the expected output? What do you see instead?
As per RFC 4975, section 5.4, the Active endpoint (which initiates the 
connection) must send immediately issue a SEND request. This happens with File 
Transfer, but in Image Share it does not happen.

What version of the product are you using? On what operating system?
RCS-e 2.3.5.

Please provide any additional information below.
Here are the snippets of code from the File Transfer and Image Share modules. 
The obvious difference is the lack of a call to sendEmptyChunk() in the Image 
Share version.

TerminatingFileSharingSession.java:
if (localSetup.equals("passive")) {
  // Passive mode: client wait a connection
  msrpMgr.createMsrpServerSession(remotePath, this);

  // Open the connection
  Thread thread = new Thread(){
    public void run(){
    try {
      // Open the MSRP session                        msrpMgr.openMsrpSession(FileSharingSession.DEFAULT_SO_TIMEOUT);

      // Send an empty packet
       sendEmptyDataChunk();
    } catch (IOException e) {
      if (logger.isActivated()) {
      logger.error("Can't create the MSRP server session", e);
    }
  }   
}


TerminatingImageTransferSession.java:
if (localSetup.equals("passive")) {
  // Passive mode: client wait a connection
  msrpMgr.createMsrpServerSession(remotePath, this);

  // Open the connection
  Thread thread = new Thread(){
    public void run(){
      try {
        // Open the MSRP session
                              msrpMgr.openMsrpSession(ImageTransferSession.DEFAULT_SO_TIMEOUT);
      } catch (IOException e) {
        if (logger.isActivated()) {
          logger.error("Can't create the MSRP server session", e);
        }
      }
    }
  };

What steps will reproduce the problem?
1.
2.
3.

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


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

Please provide any additional information below.
In class 
com.orangelabs.rcs.core.ims.service.sharing.transfer.OriginatingContentSharingSe
ssion,
Line 296, it invoke method like "msrpMgr.sendChunks(stream, 
getContent().getEncoding(), getContent().getSize());",
but there is only method sendChunks(InputStream inputStream, String msgId, 
String contentType, long contentSize) in 
com.orangelabs.rcs.core.ims.protocol.msrp.MsrpManager , the parameters don't 
match.

Am I check out wrong?

I have installed RCS stack, provisioning and RI app on my GB android device. I 
created free SIP account on ekiga.net and provisioned it on the stack. The 
stack is able to register with ekiga.net. 
I repeated the same process on one more device with different ekiga account and 
stack is registered on that devices also.

Now, I want to test the voice call and presence. But could not find the way to 
dial SIP id using RI app. Also not able to find the way to add the contact 
details with SIP id. Please suggest how can I do the same ??

When I use IMSdroid (registered with ekiga SIP account) to dial device having 
RCS stack. The receiving device i.e. RCS stack terminates the call with error 
Unknown IMS service. Log for this issue:
V/[RCS][SipInterface]( 1658): <<< Receive SIP INVITE
V/[RCS][SipInterface]( 1658): Notify a SIP listener
V/[RCS][ImsServiceDispatcher]( 1658): Receive INVITE request
V/[RCS][SipInterface]( 1658): >>> Send SIP 100 response
V/[RCS][ImsServiceDispatcher]( 1658): Unknown IMS service: Automatically reject
V/[RCS][SipInterface]( 1658): >>> Send SIP 606 response

What steps will reproduce the problem?
1. Start a group chat
2. Have one of the invitees invite another participant (sends REFER)
3. Have that same invitee leave the chat (sends BYE)

What is the expected output? What do you see instead?
I expect the CSeq of the BYE to be one more than the CSeq of the previous 
REFER. Instead the BYE has the same CSeq.

What version of the product are you using? On what operating system?
2.3.5 on a variety of handsets and OS versions (an example is Android 2.3.3)

Please provide any additional information below.

Here are two sample messages received in sequence from the same handset:
REFER sip:[email protected]:5062 SIP/2.0
via: SIP/2.0/UDP 192.168.30.241:7050;branch=z9hG4bK8c44.c3136b55.0,SIP/2.0/UDP 
192.168.0.101:5060;branch=z9hG4bK60de132556aa30dd3e090fdaaae6d478323633;received
=24.89.236.25;
rport=63569
max-forwards: 69
call-id: np00-2-fGvT94kQdYko0NZW
from: <tel:+19024412865>;tag=eNcR4TT2BA
to: <tel:+19024528375>;tag=MfWMBnnFrYBipo7Y
cseq: 2 REFER
contact: <sip:24.89.236.25:63569>;+g.oma.sip-im
accept-contact: *;+g.oma.sip-im
refer-to: <tel:+19024528375>
user-agent: IM-client/OMA1.0 OrangeLabs-RCS-client/2.3.5
content-length: 0
p-preferred-identity: <tel:+19024412865>
refer-sub: false


BYE sip:[email protected]:5062 SIP/2.0
via: SIP/2.0/UDP 192.168.30.241:7050;branch=z9hG4bK8c44.d3136b55.0,SIP/2.0/UDP 
192.168.0.101:5060;branch=z9hG4bKd91382f510a95c7b7d2cbb0263b48d19323633;received
=24.89.236.25;
rport=63569
max-forwards: 69
call-id: np00-2-fGvT94kQdYko0NZW
from: <tel:+19024412865>;tag=eNcR4TT2BA
to: <tel:+19024528375>;tag=MfWMBnnFrYBipo7Y
cseq: 2 BYE
accept-contact: *;+g.oma.sip-im
refer-to: <tel:+19024528375>
content-length: 0
p-preferred-identity: <tel:+19024412865>
refer-sub: false

What steps will reproduce the problem?
1. Receive a file transfer INVITE with SDP containing in file-selector 
attribute only name & size (no type) selectors. Example would be: 
a=file-selector:name:"alf.jpg" size:24774

What is the expected output? What do you see instead?
Enable user to accept file transfer. Instead a '415 Unsupported Media Type' 
message is sent back.

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

Please provide any additional information below.
Looks like stack is expecting to get 'type' selector, like: 
a=file-selector:name:"alf.jpg" type:image/jpeg size:24774

According to RFC 5547, there is no must for such - only one is required (point 
6):
(...)When used in an SDP offer or answer, the 'file-selector' attribute MUST 
contain at least one selector.  Selectors characterize the file to be 
transferred.  There are four selectors in this attribute: 'name', 'size', 
'type', and 'hash'.(...)

The same happens for lack of 'size' selector.

What steps will reproduce the problem?
1. Create SIP Ekiga Account
2. Provision stack with the information
3. Try to register.

Registration fails:
INFO/[RCS][RegistrationManager](1640): Registration has failed: 2, reason=606 
Not Acceptable

My colleague in US is getting this error. But I am in India and I am able to 
register using same credentials. My colleague has tried both 3G and wifi but 
getting same issue.

Imp logs are:
---------------
12-21 09:51:02.770: INFO/[RCS][ImsConnectionManager](1640): IMS user profile: 
IMS username=14087726355, IMS private [email protected], IMS 
password=xxxx, IMS home domain=ekiga.net, XDM 
server=10.194.117.34:8080/services, XDM login=, XDM password=password, IM 
Conference URI=sip:[email protected]

12-21 09:51:02.848: VERBOSE/[RCS][PublishManager](1640): New entity tag: null, 
expire at=-1

12-21 09:51:02.856: INFO/[RCS][ImsModule](1640): IMS module has been created

12-21 09:51:02.856: INFO/[RCS][Core](1640): Terminal core is created with 
success

12-21 09:51:02.856: INFO/[RCS][ImsModule](1640): Start the IMS module

12-21 09:51:02.856: INFO/[RCS][CallManager](1640): Start call monitoring

12-21 09:51:02.864: INFO/[RCS][ImsModule](1640): IMS module is started

12-21 09:51:02.864: INFO/[RCS][AddressBookManager](1640): Start address book 
monitoring

12-21 09:51:02.879: INFO/[RCS][ImsServiceDispatcher](1640): Start background 
processing

12-21 09:51:02.887: VERBOSE/[RCS][RcsCoreService](1640): Handle event core 
started

12-21 09:51:02.903: INFO/[RCS][Core](1640): RCS core service has been started 
with success

12-21 09:51:02.911: INFO/[RCS][RcsCoreService](1640): RCS core service started 
with success

12-21 09:51:02.919: VERBOSE/[RCS][RcsWidgetProvider](1640): Widget mode set to 
ON but not registered

12-21 09:51:02.934: VERBOSE/[RCS][CallManager](1640): Call is IDLE: last 
number=null

12-21 09:51:02.934: VERBOSE/[RCS][RichcallService](1640): Abort all pending 
sessions

12-21 09:51:02.934: VERBOSE/[RCS][RcsWidgetProvider](1640): Widget mode set to 
ON but not registered

12-21 09:51:02.942: VERBOSE/[RCS][ImsConnectionManager](1640): Connection event 
android.net.conn.CONNECTIVITY_CHANGE

12-21 09:51:02.942: VERBOSE/[RCS][ImsConnectionManager](1640): Local IP address 
is 10.107.120.125

12-21 09:51:02.950: VERBOSE/[RCS][ImsConnectionManager](1640): Disconnect from 
IMS: IP address has changed

12-21 09:51:02.950: VERBOSE/[RCS][MobileNetworkInterface](1640): Registration 
has been terminated

12-21 09:51:02.950: INFO/[RCS][MobileNetworkAccess](1640): Disconnecting from 
null

12-21 09:51:02.950: INFO/[RCS][ImsConnectionManager](1640): Data connection 
state: CONNECTED to mobile

12-21 09:51:02.973: VERBOSE/[RCS][ImsConnectionManager](1640): Connect to IMS

12-21 09:51:02.973: INFO/[RCS][MobileNetworkAccess](1640): Connecting to 
10.107.120.125

12-21 09:51:02.973: INFO/[RCS][ImsConnectionManager](1640): Start the IMS 
connection manager

12-21 09:51:02.981: VERBOSE/[RCS][ImsConnectionManager](1640): Start polling of 
the IMS connection

12-21 09:51:03.012: VERBOSE/[RCS][ImsConnectionManager](1640): Polling: check 
IMS connection

12-21 09:51:03.020: VERBOSE/[RCS][ImsConnectionManager](1640): Not yet 
registered to IMS: try registration

12-21 09:51:03.020: VERBOSE/[RCS][MobileNetworkInterface](1640): Register to IMS

12-21 09:51:03.044: VERBOSE/[RCS][SipInterface](1640): SIP outbound proxy set 
to 86.64.162.35:5060

12-21 09:51:03.208: VERBOSE/[RCS][SipInterface](1640): Default SIP provider is 
UDP

12-21 09:51:03.208: VERBOSE/[RCS][SipInterface](1640): SIP stack started at 
10.107.120.125:5062

12-21 09:51:03.208: VERBOSE/[RCS][SipInterface](1640): Add a SIP listener

12-21 09:51:03.223: INFO/[RCS][RegistrationManager](1640): Send REGISTER, 
expire=3600

12-21 09:51:03.231: VERBOSE/[RCS][SipInterface](1640): Create a transaction 
context [email protected]

12-21 09:51:03.231: VERBOSE/[RCS][SipInterface](1640): >>> Send SIP REGISTER

12-21 09:51:03.270: INFO/[RCS][RegistrationManager](1640): Wait response

12-21 09:51:03.301: DEBUG/dalvikvm(1640): GC_CONCURRENT freed 371K, 46% free 
3413K/6279K, external 716K/1038K, paused 4ms+5ms

12-21 09:51:03.309: INFO/dalvikvm(1640): Jit: resizing JitTable from 512 to 1024

12-21 09:51:04.747: INFO/urilc(2742): [ATURilListenerLoop]:  rxd 32 size packet

12-21 09:51:04.747: INFO/urilc(2742): [HandleNotificationPacket] 1009

12-21 09:51:04.747: INFO/urilc(2742): [DispatchNotifCallback] enter 0x0

12-21 09:51:04.747: INFO/urilc(2742): [DispatchNotifCallback] exit

12-21 09:51:04.762: DEBUG/SurfaceFlinger(1374): Layer[2b6680] [2] non-RGB565 
reloads

12-21 09:51:07.458: VERBOSE/[RCS][SipInterface](1640): <<< Receive SIP 606 
response

What steps will reproduce the problem?
1. Register client with IMS CN (default Expires in REGISTER is 3600)
Condition - expires (Expires) in 200OK is bigger than 1200
2. Wait for reregistration
3. Note interval between initial registration and reregistration.

What is the expected output? What do you see instead?
Reregistration should happen "either 600 seconds before the expiration time if 
the previous registration was for greater than 1200 seconds, or when half of 
the time has expired if the previous registration was for 1200 seconds or 
less". Instead registration is sent always after half of the time has expired.

What version of the product are you using? On what operating system?
2.3.4, Android 2.3.3

Please provide any additional information below.
According to TS 24.229, 5.1.1.4 User-initiated reregistration and registration 
of an additional public user identity
(…)
Unless either the user or the application within the UE has determined that a 
continued registration is not required the UE shall reregister an already 
registered public user identity either 600 seconds before the expiration time 
if the previous registration was for greater than 1200 seconds, or when half of 
the time has expired if the previous registration was for 1200 seconds or less, 
or when the UE intends to update its capabilities according to RFC 3840 [62] or 
when the UE needs to modify the ICSI values that the UE intends to use in a 
g.3gpp.icsi-ref media feature tag or IARI values that the UE intends to use in 
the g.3gpp.iari-ref media feature tag.
(…)

I have a problem on Core IMS to support GRUU. Is there an option in version 
2.3.3 of client to switch it off?

What steps will reproduce the problem?
1. In the provisioning part, enter a conference-URI with domain different than 
main domain. 
Example: [email protected], where main domain would be example.com, 
and user (PVI) like sip:[email protected]

What is the expected output? What do you see instead?
SIP INVITEs to conference URI from outside of user's domain could be supported. 
Currently application is expecting only user part and adds the main domain 
creating something like: [email protected]@example.com. 

What version of the product are you using? On what operating system?
2.3.4, Android 2.3.3

Please provide any additional information below.
-none-

What steps will reproduce the problem?
1.I had created a free SIP account with sip2sip.info.
2.I want to try the group chat with sip2sip.info.
3.Can you tell me wat i need to give at "IM conference URI for group chat" 
setting?


What is the expected output? What do you see instead?
In the mail i got from sip2sip when i created the account, its written that 
MSRP chat session is supported during Multi party conference.
So i tried to send an invite request with sip:[email protected]
in the To header field with sdp message body containing 'message' media type.
But I am getting a user not found Response or sometimes unsupported media type 
response.

Please help me to resolve this.

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


Please provide any additional information below.

What steps will reproduce the problem?
1. Use of openIMS as IMS core network
2. creation of a user in openIMS.
3. configuration of the rcs settings under the android emulator.
4. restart of the rcs service under the android emulator.

What is the expected output? What do you see instead?
After the android emulator sends a first REGISTER request, it receives from the 
openIMS network a "401" challenging response where qop is equal to "auth, 
auth-int" (as authorized in RFC2617, page 10). In this case, the android 
emulator has to send back a REGISTER request with qop equals to one of the 
proposed values (auth or auth-int but not both) and a md5 value calculated 
based partly on it.

Currently, the md5 value is not correct as the service is using the complete 
qop value received in the challenging response to calculate the md5 code. 

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

Please provide any additional information below.
The problem occurs in the method writeSecurityHeader of the 
HttpDigestRegistrationProcedure class in the response calculation. 
The used method calculateResponse uses the complete QoP value inherited from 
the "401" challenging response instead of one of the token of the QoP value.

the MD5 code is then calculated in the following way:
H(a1) + ":" + nonce + ":" + nc + ":" + cnonce + ":" + qop + ":" + H(a2)
where qop will be equal to : "auth, auth-int"
and H(a2) will be equal to H(method + ":" + uri) as the qop value is not 
strictly equals to "auth-int" and starts with "auth".


A possible correction consists in choosing by default the first token from the 
qop value list during the retrieval of the www-authenticate parameters which is 
performed in the readSecurityHeader method from the 
HttpDigestRegistrationProcedure class.

in this case, the line :
// Get qop              digest.setQop(response.getHeaderParameter("WWW-Authenticate", 
"qop"));

can be replaced by:
// Get qop              digest.setQop(response.getHeaderParameter("WWW-Authenticate", 
"qop").split(",")[0]);

Extract from RFC2617, page 10
qop-options
     This directive is optional, [ ... ]. If present, it is a quoted 
     string of one or more tokens indicating the "quality of protection" 
     values supported by the server.  The value "auth" indicates
     authentication; the value "auth-int" indicates authentication with 
     integrity protection; [ ... ]

What steps will reproduce the problem?
1.I want to send REFER message.
2.Which method may finish it?
3.A demo is better.

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


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

Please provide any additional information below.

REFER 
sip:[email protected]:5065;transport=tcp;fid=imsm_instance_PL_2_4_1 
SIP/2.0
Via: SIP/2.0/UDP 192.168.253.2;branch=z9hG4bK2247940305
From: <sip:[email protected]>;tag=1371874879
To: 
<sip:[email protected]:5065;transport=tcp;fid=imsm_instance_PL_2_4_1>
Call-ID: [email protected]
CSeq: 1 REFER
Contact: <sip:192.168.253.2>
Route: <sip:10.170.32.11:5060;transport=udp;lr>
Max-Forwards: 70
P-Access-Network-Info: 3GPP-UTRAN-FDD;utran-cell-id-3gpp=2620209329320065
Content-Length: 0
Refer-To: <tel:+8521341041106>
Refer-Sub: false
Require: norefersub; multiple-refer
Supported: norefersub
P-Preferred-Identity: sip:[email protected]
Accept-Contact: *;+g.oma.sip-im

What steps will reproduce the problem?
1.init a group chat
2.quit group chat, send bye
3.wrong message returned;



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


What version of the product are you using? On what operating system?
product version 2.2.1 
on Android2.2

Please provide any additional information below.

I have read the README.txt on "/releases/v2.2.7/", it said:
the bug has been fixed.

v2.2.5
- Mantis #0011955   Stack: BYE failed on terminating chat group

I wound use the version in futrue, but I must resolve this problem with the old 
version now. I have read the newest verion and compared with the version I 
used, but I did not get any helpful information. would you please give me a few 
detail about this bug? Thanks a lot.

What steps will reproduce the problem?
1.Establish a chat session between two clients - A(initiator) and 
B(participant) (2.2.8)
2. When A quits the chat session B receives a message that the chat session has 
been terminated.
3. But, when B quits or terminates the chat session, A does not receive any 
notification indicating the same.

What is the expected output? What do you see instead?
A(initiator) should receive a message indicating when B(participant) terminates 
the chat session.

What version of the product are you using? On what operating system?
RCS-e client, 2.2.8

Please provide any additional information below.

What steps will reproduce the problem?
1. start a Chat
2. Look to the TCP-Packeges sent

What is the expected output? What do you see instead?
One should see that MSRP SEND Messages are confirmed with MSRP 200 OK Messages.
No MSRP 200 OK Messages are sent.

What version of the product are you using? On what operating system?
Version 2.3.0 on Android 2.2 and 2.3.4

Please provide any additional information below.
-

What steps will reproduce the problem?
1.open project in eclipse
2.clean the project 
3.run project


What is the expected output? What do you see instead?
it should run in my phone which is connected to pc normally, instead, it output 
this:

[2011-12-29 16:52:11 - core] Dx 
trouble processing "javax/sip/address/Address.class":

Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.

This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.

However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.

If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.

If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.

If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.

[2011-12-29 16:52:11 - core] Dx 1 error; aborting
[2011-12-29 16:52:11 - core] Conversion to Dalvik format failed with error 1


What version of the product are you using? On what operating system?
my version is core 2.3.0, on win7 home pre x64

Please provide any additional information below.
i have googled about it, found some explanation
http://code.google.com/p/dalvik/wiki/JavaxPackages

it seems to android reject defining package named anroid.*, java.*, javax.*, 
but in core stack, we used javax.sip.*
my eclipse is 3.7.1, adt version is 16.0.1, android sdk tools version is 16, 
android sdk platform-tools version is 10.

so i have to find out my old adt and sdk tools which i used ago, it worked 
normally, the old version is eclipse 3.6.1, adt version 10, sdk tools version 8,
sdk platform tools version 1.

do you have any solution for it?

What steps will reproduce the problem?
1.
2.
3.

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


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

Please provide any additional information below.
What's the capability of "csVideo"? Is it different from capability of 
"videoSharing"? What's the different?

Thanks.

What steps will reproduce the problem?
1.I want to implement file-transfer in chat session.When A is chating with B,A 
transfer a file to B.
2.I think that I may call InstantMessageSession::sendContent(InputStream 
dataStream, String mimeType, long dataLength) in order to transfer a file in a 
chat session.
3.However how receiver should handle this file-transfer in a chat session?In 
the RI application ,what should receiver do?Write "private 
IFileTransferEventListener fileTransferSessionListener = new 
IFileTransferEventListener.Stub()" ?

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


What version of the product are you using? On what operating system?
2.2.0     on Android 2.2

Please provide any additional information below.

What steps will reproduce the problem?
1. Install open office or any document scanner or viewer
2. In file-transfer view, try transferring and picking a file other than a 
picture from gallery.

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


What version of the product are you using? On what operating system?
RCS-e 2.2.8;

Please provide any additional information below.

[2011-11-15 19:40:51 - SettingsDisplay] Dx 
trouble processing "javax/sip/address/Address.class":

Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.

This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.

However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.

If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.

If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.

If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.

[2011-11-15 19:40:51 - SettingsDisplay] Dx 1 error; aborting
[2011-11-15 19:40:51 - SettingsDisplay] Conversion to Dalvik format failed with 
error 1

What steps will reproduce the problem?
1.loaded on moto atrix and HTC Aria (both at 2.2)
2.open application and select 'settings' from menu
3.error message "the applications has stopped unexpectedly

What is the expected output? What do you see instead?
Open up the setting menu. Application Crashes

What version of the product are you using? On what operating system?
1.1 on android 2.2

Please provide any additional information below.

What steps will reproduce the problem?
1.What is RI and provisioning?
2.How to use API to implement Video Share?
3.Where may set my IMPU and IMPI in the program?

A whole call API demo is better.
What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
2.2.0   on Android 2.2

Please provide any additional information below.
I hope this message may be sent.

INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.253.3;branch=z9hG4bK2453275128
From: <sip:[email protected]>;tag=2530547806
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: <sip:192.168.253.3>;+g.3gpp.cs-voice
Route: <sip:10.170.32.11:5060;transport=udp;lr>
Max-Forwards: 70
P-Access-Network-Info: 3GPP-UTRAN-FDD;utran-cell-id-3gpp=2620209329320065
Content-Length: 281
P-Preferred-Identity: sip:[email protected]
Allow: INVITE,OPTIONS,BYE,CANCEL,ACK
Accept: application/sdp
Accept-Contact: *;+g.3gpp.cs-voice
User-Agent: SEMC_IMS_R3
Session-Expires: 1800;refresher=uac
Supported: timer
Accept-Encoding: identity
Content-Type: application/sdp

v=0
o=- 1249997756 1249997756 IN IP4 192.168.253.3
s=-
c=IN IP4 192.168.253.3
t=0 0
m=video 49152 RTP/AVP 96
b=AS:85
a=rtpmap:96 H263-2000/90000
a=fmtp:96 profile=0;level=45
a=sendonly
a=application:com.gsma.rts
a=type:videolive
a=framerate:10
a=framesize:96 176-144

What steps will reproduce the problem?
1.import project into eclipse.
2.some error: build.xml of RCS_Core
3.some error like The import 
com.orangelabs.rcs.service.api.client.messaging.IMessagingApi cannot be resolved

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


What version of the product are you using? On what operating system?
2.2.0    on Android 2.2 using eclipse

Please provide any additional information below.