i've heard that the Tomcat server installaed on on CUCM should not be touched to develop Webservices. So, i would take an external WebServer and buildt on that. Question:
What are the different access methods i hae?
There are the XML Objects available on IP Phones, then there is the AXL browser and there is the SDK. What shall be used for what?
May be some links to documents would be great,
Kind regards, Patrick
It would take an insane amount of time to go into details.. each API has some functionality that it's best at, and you just need to compare the developer guides I linked to to get down to the details (and I figure most people settle for one API.. even though the syntax is similar, if you are used to Java you generally don't like going back to malloc and free, whereas if you're a hardcore C user, you probably like bothering with memory allocation and pointers)
One thing that can be said about TAPI versus JTAPI. Obviously it's a language thing.. TAPI is C whereas JTAPI is Java. Then, TAPI is meant for first party call control (meaning you install the TAPI Service Provider on the PC of the user who owns a particular phone.. and installing multiple TSPs to handle multiple phones concurrently is usually either a PITA or simply impossible), whereas JTAPI is meant for third party call control.. so you have your central application server that manages a bunch of phones.
And yes, you will lose certain features by going the JTAPI route.. e.g. there's no media playback (that's in the JTAPI specs but Cisco decided not to implement it for whatever reason.. many here are quite disappointed about that). But you also gain certain things besides the ones I already mentioned.. e.g. the super provider which allows you to monitor any device without having to configure an application user.