In JTAPI 1.1, the JtapiPeer class defines the point of contact between application and JTAPI implementation. However, access to this class in a Java client environment is not always easy to ensure short of installing the JtapiPeer instance on that client.
Clearly, the JtapiPeer as presented in JTAPI 1.1 is not a general solution to the problem of giving all types of applications and applets access to a JTAPI Provider.
A more general solution will be provided in the next release of JTAPI, while maintaining support for the existing JtapiPeer model. The current JtapiPeer class scheme is sufficient to support development of applications and implementations to JTAPI.
Call.connect() can return a Connection, whose destination Addresses may not be identified by the same string as used in the Call.connect() to identify the destination. This could be the result of some switch idosynchrosy, for instance. In such a situation, the implementation must maintain 'aliases' for a particular address to present a consistent view of Address references to the application.
This kind of detailed information, most often required by the JTAPI implementors is provided as much as possible in this specification. However, if any area of the spec is found ambiguous or lacking, please feel free to use the feedback section of this document to ask for more detailed assistance. Every reasonable effort will be made to address your questions.