Configuring the Voice Chat

Skip to end of metadata
Go to start of metadata

This documentation applies to Communications Suite 6 Update 1 at the time of its release. The most up-to-date documentation is available at the Communications Suite Documentation Home.

Configuring Voice Chat for Instant Messenger

This chapter gives an overview of the voice chat feature and explains the procedure to configure this feature in Instant Messenger. This chapter contains the following sections:

Voice Chat Overview

Instant Messaging version 7.3 provides the users of Instant Messaging the capability to talk to each other by using a PC-based audio hardware. The Instant Messaging client uses the Instant Messaging server to set up the call. The client uses the XEP-0166-Jingle protocol for VoIP in which the audio streams travel in peer-to-peer (p2p) signals. For more information about the XEP-0166 Jingle protocol, see http://www.xmpp.org/extensions/xep-0166.html.

Note
This feature does not support interactions with other VoIP providers.

Configuring Voice Chat

To enable this feature, select the Enable Audio option while deploying the Instant Messaging Client resources. After you select the Enable Audio option, you can chat and start the voice chat session. This feature enables only peer-to-peer chat. The voice chat option does not exist in a conference chat.

Note
Once you configure the Instant Messenger, you cannot enable or disable the Enable Audio option. To make any changes to this option, reconfigure Instant Messenger by invoking the init-config command.

Initiating Voice Chat

The Audio Pane is available at the bottom right of the Lower Message pane in the Instant Messaging client interface. This pane contains icons that can be used to initiate and end voice conversations with other users. The audio pane contains the following items:

Initiate a call: Click this icon to initiate an audio chat with other users.
Hang up: Click this icon to end an audio chat.

To initiate a voice chat, do the following:

  1. Start the text-chat session.
  2. Select the user from the participation list. The Initiate a call icon is enabled.
  3. Click the Initiate a call icon.
    The other user gets a request to accept the call. Once the user accepts the call, they are in connected status. The user can use the Hang up icon to end the call.
Note
There is no option to record or archive a voice chat conversation.

Firewall Consideration

A common issue with a client-to-client communication is the network and client-level firewalls that block incoming connections to random ports.

The voice chat feature uses an initial TCP client-to-server session to negotiate the client-to-client UDP VoIP link. The current voice chat feature does not have a method to restrict the UDP ports that are used on the clients that accept the connection.

One indication that a firewall might be blocking the establishment of the VoIP link is when the client which initiates the VoIP connection sees "Trying..." for 10 seconds and then a "Call Ended" message is displayed even though the incoming voice chat request was accepted by the other client.

To enable the Instant Messaging Client debug option, add the <argument> debug=true </argument> parameter in the im.jnlp file. The debug information appears in the Java Console output.

Note
If VoIP is enabled, the audio pane is available at the bottom right of the Lower Message pane of the chat window. If VoIP is not enabled during configuration, the audio pane is not available in the chat window.

There is currently no method to enable or disable the VoIP feature at a user or domain level.

Labels:
firewall firewall Delete
voip voip Delete
instantmessaging instantmessaging Delete
chat chat Delete
audio audio Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.