« Back to Cius Developer Questions

RE: using Cius Telephony API on real device

Combination View Flat View Tree View
Threads [ Previous | Next ]
I'm testing my application on the Cius device and it gives and error : Caused by:java.lang.SecurityException:Not allowed to bind to service Intent { act=com.cisco.telephony.ICCDevice}
So, i tried the sample application that comes in Cius add-on v0.2. "Sample Phone Application" didn't work on device either. It is also working fine on emulator.
What do i need to do to test the applications on device?

There was a change to the way this API is initialized in the 9.2.3 firmware release, perhaps this is the cause.
 
Please see this blog post for details:
http://developer.cisco.com/web/cius-developer/blogroll/-/blogs/cisco-telephony-manager-updates
 
And this blog post for the new supporting Add-on:
http://developer.cisco.com/web/cius-developer/blogroll/-/blogs/cisco-cius-add-on-version-1-0-released%21

Hey Guney,

What you are seeing is a permission exception. In old versions of the add-on there was no permission that needed to be used. I recommend that you grab the latest version of the Add-on and try running the sample again since you are using version 0.2 and we are currently on version 1.0. Let me know if you still have any trouble.

my active load is 9.2.2.49.
but i will try the new add-on anyway.

i changed the add-on version. the problem still exists

Hey Guney,

Sorry that didn't fix your problem. Did you actually use the new sample that comes with the Add-on while you were testing this? Also, does the code you are using to test this contain the following lines of code in your AndroidManifest.xml file:

<uses-permission android:name="cisco.telephony.permission.DEVICE_PERMISSION"></uses-permission>

This is the line that allows you access to ICCDevice which seems to be what you are having an issue with. If none of these fix your issue could you tell me if you are binding to the ICCDevice or if you are using our CiscoTelephonyManager. I'm not sure which comes with Add-on v0.2 as it is quite an old version.

Since you are running firmware earlier than 9.2.3, the API backward compatibility change would not be the problem (and using the new add-on may add to the confusion.)  Per Matt's suggestion, the next best guess would be the missing permission.