Documentation 1.6

2012-09-24T11:17:14Z

Call Server 1.4

2012-09-24T11:17:00Z

== IOS Config for Call Server == === 987654 Dial Peer for CVP === *Description* This video shows the reason behind the manditory dial-peer needed for Play Media and Play Data micro-app with CVP and if using CVP Standalone. [[987654 Dial Peer Video|^987654.wmv]] === How big should your GW logging buffer be? === *Description* This video tells you how to calculate your logging buffer for CVP on your Ingress and VXML Gateways. * [[Gateway Logging Buffer Video|^GW Logging Buffer Size And Config.wmv]]

Software Releases 1.4

2012-09-20T06:54:25Z

CVP Releases

Version	Type	FCS Date	Solution Release	Status	Highlights
8.0(1)	Feature	Spring 2010	8.0	In Development	New Features
7.0(2)	MR	August 15, 2008	7.0(2)	Shipping	defect fixes
7.0(1)	Feature	March 26, 2008	7.0	Shipping	basic and full video support
4.1(1)	Feature	November 30, 2007		Shipping	Voice Application Debugger, Subroutine support, WSDL support, Java 5, Admin API
4.0(2)	MR	June 7, 2007			defect fixes
4.0(1)SR1	Feature	January 25, 2007		EOS Nov 12, 2008	SIP, Reporting, OAMP
3.1	Feature			EOS started
3.0	Feature	September 1, 2004			VXML Server, Call Studio
2.x	Feature			EOS End of Support

MR: Maintenance Release

CVP streaming from analog device 1.2

2012-09-20T06:54:06Z

Here we provide to you a solution for encoding analog input from a sound card to G.711 u-law format that can be delivered to the Helix server for further broadcast to a CVP solution. This encoder utility is not a CVP supported utility.

Providing G.711 u-law format audio streaming from Helix that had originated with input from an analog device:
The below attached AVTransmit3.java file is the code in which made this possible. The attached Stream.jar is the complied executable of this java code.
Along with this code, Java executables and JMF (Java Media Framework) is required to be installed on the executing machine.

Please download the JMF here:
http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/download.html

This java code will take analog input from the sound card of a server, convert it to G.711 u-law and then broadcast it to an open port on
the Helix server. Helix can then forward that encoded RTP on to its clients.

The block diagram of our test setup is as follows:

    CD Player -> analog audio cable into Sound card -> Stream.jar Encoder -> Helix Server -> RTP broadcast stream to Client

Due to the fact that the MCS7845 we have a Helix server running on does not have a sound card, we ran the
encoder on a sperate machine. This encoded stream was then forwarded for Helix for broadcast.
In our example, the encoder ran on the device 161.44.81.63 and Helix ran on 10.86.129.250.

If modifications to the java code are required, please refer to the attached JMF user guide.

Enabling Helix to allow the encoder to connect to it:
Placing an SDP file in the C:\Program Files\Real\Helix Server\Content\rtpencodersdp
of Helix will open a port on Helix to allow an encoder to attach to it.
This directory is the install directory of Helix, plus Content, plus the location of the Base Mount Point as
defined in the QT & RTP Encoding page of the Helix Administration GUI.
The default value is "\rtpencodersdp\"

The contents of the SDP file will be setup like so:

v=0
o=- <unique value> <unique session ID> IN IP4 <IP-address-of-encoder>
s=JMF
t=0 0
m=audio <Helix-listening-port> RTP/AVP 0
c=IN IP4 <IP-address-of-Helix>
a=MaxPacketSize:integer;160

In our example, these values are:

v=0
o=- 37 614155991 IN IP4 161.44.81.63
s=JMF
t=0 0
m=audio 17008 RTP/AVP 0
c=IN IP4 10.86.129.250
a=MaxPacketSize:integer;160

When creating multiple streams, you must create multiple SDP files each with its own unique session IDs and listening
port values.
For further information about the contents of SDP files, please see the RFC2327.
http://www.ietf.org/rfc/rfc2327.txt

Running encoder executable:
Attach a device to the analog input of the sound card on a server. At the command line
of this server in the directory where the Stream.jar is placed, run this command:

    java -jar .\Stream.jar <input-device> <ip-of-Helix> <port-of-Helix>

In our example, the parameters are

    java -jar .\Stream.jar javasound://44100 10.86.129.250 17008

This will run continuously until the program is stopped with a control-C.

ICM script changes:
The address in which clients will connect to hear the broadcast stream will be

    rtsp://<Helix-ip-address>/rtpencoder/<sdp-filename>

Note that the actual SDP file is not served to client, but rather used by Helix to know to forward the stream provided by the encoder.
In our example, the parameters are

    rtsp://10.86.129.250/rtpencoder/jmf.sdp

The path name "rtpencoder" is the value of the Mount Point as defined on the QT & RTP Encoding page of the Helix Adminstration GUI.
The default value is "\rtpencoder\".

The values of parameters within the ICM script that refer to the name of the file being accessed must be changed to now point at the SDP filename on Helix.

How To Videos 1.0

2010-05-27T18:28:15Z

* [[Call Server|Call Server]] * [[Reporting Server|Reporting Server]] * [[Video Media Server|Video Media Server]] * [[OAMP|OAMP]]

Troubleshooting 1.0

2010-05-27T18:27:01Z

Wiki Home 1.1

2010-05-27T18:22:16Z

This is the home page for the Customer Voice Portal (CVP) space.