ClickToCall

With the ClickToCall widget, a Web user can call another party such as a customer service representative by entering their phone number into an entry-field and clicking a Call Me button. To display the ClickToCall widget, click the Contact Us link in the PlantsByWebSphere Ajax Edition banner (masthead). You can also use the following direct link if PlantsByWebSphere Ajax Edition is running on a local application server that utilizes the default internal HTTP port (9080): http://localhost:9080/PlantsByWebSphereAjax/contactus.html. Before using the ClickToCall widget, you must first make a small modification to the contactus.html file. After installation, contactus.html is located in the following directory:

Within contactus.html, locate the 'widgetNumber' attribute (widgetNumber="sip:CSR@localhost"). Replace 'CSR@localhost' with the SIP number (address) to be contacted when a click-to-call request is initiated. (SIP phone numbers must be specified in the format sip:userName@hostName, where hostName is the host name or IP address of the IP-PBX.) When the Call Me button is clicked, a call will be attempted between the SIP number specified in the My Number entry-field and the SIP number specified in the 'widgetNumber' attribute. The numbers used by the ClickToCall widget must be registered with an IP-PBX. Additionally, the IP-PBX to which the numbers are registered must be configured as a CTI gateway in the CEA settings of the application server on which the PlantsByWebSphereAjax sample is running. For further information, see the Feature Pack for CEA Information Center.


To initiate a call, enter your number (the number that you wish to connect to the number specified in the 'widgetNumber' attribute) and click the Call Me button.


To terminate the call, click the End Call button or hang up the connected phones.


To initiate cobrowsing, click the Cobrowse button. Once a cobrowsing session is established, a modal collaboration dialog (window) will be displayed in each browser window. For further information about the collaboration dialog, see the Cobrowse topic.


Note: When evaluating the cobrowsing feature on a single machine, you must utlize two completely separate Web browsers from different vendors; otherwise, results will be unpredictable. For example, do not attempt to create a cobrowsing session that utilizes two tabs within the same instance of a given browser, or even two separate instances of the same browser, for example, Firefox. Always use two different completely separate browsers from different vendors, for example, Firefox and Internet Explorer, Chrome and Safari, and so on.