Java MIDlet API Forums

« Back to Technical Discussion

RE: MIDlet signing ?

Combination View Flat View Tree View
 
The desk phones require a MIDlet to be signed by Cisco before they
are permitted to run. This is mainly to protect the desk phones
from a MIDlet that is less than well behaved.
 
This signing can be a barrier to deployment, because it makes
MIDlet development a bit harder, in that small variations each
have to be signed before they can run. It's very unlikely that
unsigned MIDlets will ever be permited to run in the 7900
or 9900/8900 series of desk phones.
 
The wireless phones do not require a MIDlet to be signed. If the
MIDlet behaves badly this is unlikely to affect normal phone
operation. As a result, we don't anticipate having to enforce any
signing of MIDlets for the 792x series of hand held wireless
phones.

What's the reason for treating the bigger phones like a lesse member?
Mobile phones are mostly more resource limited, and offer only limited screen real-estate - is there a fundamental difference in how Java works on the mobile and stationary devices?
 
XSI development on the hardphones is often limited, and the limited ways we have to start an app means usability for some useful apps is pretty poor and we've been waiting for years to see Cisco do something about it and I was kinda hoping perhaps with opening up the mobile phones to Midlets we'd finally see that for the hardphones too.
 
My employer has a significant Alcatel-Lucent presence and their upcoming generation of phones is open for app developers (not that I like Javascript over Java but at least we're able to do quite a bit more than with XSI).

RE: MIDlet signing ?
Answer
11/25/10 1:20 AM as a reply to Stephan Steiner.
There is Java MIDP support for the desk top phones. But the JVM is used for all the visual display and presentation in the desk phones. If a MIDlet were to misbehave it could cause the phone to stop operating correctly. For that reason any MIDlet that runs in the desk phones has to be signed by Cisco, to ensure that it is not going to damage regular phone operation.
 
That process is a bit laborious and very few people have gone through the process. There are some Cisco
MIDlets that run in the phones, Telepresence control for example, and visual voicemail.
 
The hand held phones don't use the JVM for anything except add on applicatons, and we don't have
the same concern about a MIDlet causing problems to the phones.

There is Java MIDP support for the desk top phones. But the JVM is used for all the visual display and presentation in the desk phones. If a MIDlet were to misbehave it could cause the phone to stop operating correctly. For that reason any MIDlet that runs in the desk phones has to be signed by Cisco, to ensure that it is not going to damage regular phone operation.
 
That process is a bit laborious and very few people have gone through the process. There are some Cisco
MIDlets that run in the phones, Telepresence control for example, and visual voicemail.
 
The hand held phones don't use the JVM for anything except add on applicatons, and we don't have
the same concern about a MIDlet causing problems to the phones.

 
 
I want to develop a midlet for my desk phone.. is midlet signing is open now at Cisco?
 
Thanks,
Marwa

Dear Conrad and colleagues,
 
many thanks for maintaining this forum!
It would indeed be interesting to get a few more details about the signing process. Can you say a few words on what the requirements and steps are (does one need to be a Cisco Partner, how costly is it in terms of money and time)?
 
Thanks a lot,
 
   Paul
 
 
There is Java MIDP support for the desk top phones. But the JVM is used for all the visual display and presentation in the desk phones. If a MIDlet were to misbehave it could cause the phone to stop operating correctly. For that reason any MIDlet that runs in the desk phones has to be signed by Cisco, to ensure that it is not going to damage regular phone operation.
 
That process is a bit laborious and very few people have gone through the process. There are some Cisco
MIDlets that run in the phones, Telepresence control for example, and visual voicemail.
 
The hand held phones don't use the JVM for anything except add on applicatons, and we don't have
the same concern about a MIDlet causing problems to the phones.

RE: MIDlet signing ?
signing
Answer
7/25/11 12:54 PM as a reply to Paul Holleis.
Dear Conrad,
 
I have the same doubts of Paul about the signing process. Can you please help us on this issue?
 
Thanks,
 
Fábio Krohn
 
Dear Conrad and colleagues,
 
many thanks for maintaining this forum!
It would indeed be interesting to get a few more details about the signing process. Can you say a few words on what the requirements and steps are (does one need to be a Cisco Partner, how costly is it in terms of money and time)?
 
Thanks a lot,
 
   Paul
 


There is Java MIDP support for the desk top phones. But the JVM is used for all the visual display and presentation in the desk phones. If a MIDlet were to misbehave it could cause the phone to stop operating correctly. For that reason any MIDlet that runs in the desk phones has to be signed by Cisco, to ensure that it is not going to damage regular phone operation.
 
That process is a bit laborious and very few people have gone through the process. There are some Cisco
MIDlets that run in the phones, Telepresence control for example, and visual voicemail.
 
The hand held phones don't use the JVM for anything except add on applicatons, and we don't have
the same concern about a MIDlet causing problems to the phones.


 Go

By API/SDK: