CEA 188.8.131.52 now gives system administrators the ability to extend their telephony and J2EE architecture to include 3rd party SIP-CTI enabled PBXs. This feature strategically allows IT environments running WebSphere Application Server (WAS) the flexibility to extend their current applications to include features and functionality supplied through the WebSphere implementation of the SIP-CTI (ECMA TR/87) API.
From an interoperability standpoint, we attempted to make the setup and configuration of an external PBX as painless as possible. We’ve created a panel that will require you to specify the hostname, port, and protocol of the SIP CTI (ECMA TR/87) Gateway. Also, if your gateway supports this, you can specify a “superuser” that will be solely utilized to authenticate and authorize outbound calls through the gateway. Conversely, if your PBX does not support the use of a “superuser”, an application developer has the option of extracting the username from the request and using it to authenticate and authorize the outbound call.
For those out there who do not have access to their PBX, we’ve also included a sample PBX application which can be deployed on stand alone appserver. Although this application is for test purposes only, this sample PBX will allow a customer to get a feel as to how to deploy and test applications that interact with a virtual SIP CTI enabled PBX.
It’s our hope that you take action in deploying and consuming all of the new features made available in the CEA feature pack. In future posts, I will be blogging about some of the technical nuances that you should be mindful of when deploying a CEA solution with specific vendor PBXs.