Contarra introduces a new version of its Service Delivery platform Cameleon CCP platform: CCP 2007-1a. This release contains major new features and enhancements to the CCP architecture, with the addition of a strong VOIP implementation, the integration of Dialogic HMP 3 version and Dialogic SS7 support. Cameleon is Contarra  technology designed to build professional services; targeting the ASP market. It is the ideal platform for the Application Hosting business for Service providers and Carriers.

This document contains the following subjects. Click on the link to go to the subject. 

Backward compatibility

Free demo license included

Highlights of new features in Cameleon CCP2007-1a

Improvements and fixes since version CCP2004-2SP4

Summary of available packages and features of the new Cameleon CCP2007-1a

This version is backwards compatible with applications written using previous releases of the CCP platform, such as CCP2003-2, CCP2004-1, CCP2004-2SP1/SP4. When  upgrading from a previous release, a new license for  this release is required. 

NOTE: Please pay attention to RFS399, where existing applications may show a compile error due to a more strict checking of the application call flow logic

This section presents the latest fixes in CCP2007-1a from the previous release CCP2004-2SP4.

RFE173 : MCU TelismaASR : Continue processing after unsuccessful session
The minimal confidence level is now used for No solution result. In this case the engine is restarted and continues to process the audio.

RFS416 : MCU Diva: Redirection Number not set
The redirection number was not set on an incoming call event. This was a feature that was lost.

RFS415 : MCS: Information missing in CDR
When setting the call type of outbound calls, the CDR ANI field was missing/corrupted.

RFS417 : MCU DialogicGC: TASKFAIL on outbound ISDN call
When placing outbound ISDN calls with Host Controlled Release option, the channel became dead when reaching the timeout. This was observed with SR6 drivers only.

RFS414: MCU DialogicGC: Blind Transfer support using VoIP
If a bind transfer was unsuccessful using VoIP, the call was not properly released.

RFS411: MCU NMS: Performance problem in heavy load with play/record
To workaround a problem that appeared in NMS 2005-1 SP2, a critical section was introduced to avoid race condition between event thread and play/record API. This critical section is not necessary anymore. Performance could be increased in some cases.

RFS408: MCU NMS: Missing Alerting event
When placing an outbound call in alert mode and a proceeding was received from the network before the alerting, the alerting event was not reported by the MCU. Introduced by RFS332.

RFS398: MCU DialogicGC: IPT boards limited to 120 channels
Up to 4 IPT boards can now be declared in the .cfg file

RFS413: MCS: Stopping backup SS7 MCU was dropping the active calls
When stopping a SS7 MCU in Backup state, connected calls were disconnected.

RFE172: MCU OSR: Continue processing after unsuccessful session
The minimal confidence level is now used for all types of result: no match, incomplete, non speech... In this case the engine is restarted and continues to process the audio. maxspeechtimeout must be set to a long value (longer than the max time you expect in ASR sessions), preferably in the user.xml.

RFS407: MCUDialogicGC: RFE74 not working anymore
The RFE74 functions "get display" name and indicators were not working due to a conflict with RFS247. They are now accessible in the CAS calling_name field after placing the call. Use grp_getInfo to retrieve this field.

RFS406: MCUDialogicGC: Extended SIP configuration
The SIP/H323 stacks now can be configured through the IPTBx sections of the .cfg file. Up to 4 virtual IPT boards can be created.

RFS405: MCU NMS: Switching between an IP channel and another channel located on another board fails
Trying to make a switching between an IP channel and another channel (whatever the type) located on another board fails. Making the link starting with another channel (not IP) to IP located on another board is successful. Due to change of IP channel behavior on new version, the IP channel should be declared as a H100 bus resource instead of an IP bus resource.

RFS404: CCPCSRTC:CTTalk Runtime engine: IP_Shutdown returning error 10038
When calling IP_Shutdown on the main socket handle of a TCP connection, an error code 10038 (Invalid socket) was returned.

RFS403: MCU NMS: Unable to open RTP endpoint on ts > 127 on board > 0
When a CG6x was declared as board ID > 0 and RTP was trying to be opened on ts > 127, a failure CTAERR_BAD_ARGUMENT happened. In fact MSP service was tried always on board 0.

RFE168: MCU NMS: Defaulting all CTBus streams to 8MHz instead of 0-15 to 2 and 16-31 to 8
Without a specification the stream speed on some NMS board (Legacy boards) is the NMS default - for MVIP compatibility reasons. Changed to be all set to 8 MHz by default.

RFE166: MCU Eicon: Redirection Number notification support
When a call is transferred to CCP in such a way that first the consultation call is received and then the original call is transferred, the PBX can send a notification about it (including the original calling number). This original calling number is provided by the Eicon driver as redirection number. 
Eicon SDK 4.0 or higher is required
dssdk 4.0.0.615 or higher

RFS402: MCU NMS: VoIP linking with TDM was not full duplex and channel were lost
Due to a workaround for previous SP3 of NMS 2005-1, full duplex was not possible after more than one link with a TDM channel. Also opencircuit for the same RTP endpoint failed after the first closecircuit.

RFS401:MCU NMS: Codec Initialization  wasn't done with board number (+G711 forced)
During channel initialization, the board number was not specified and G711FullDuplex was forced.

RFS400: DBMS MySQL: Stored procedures call failure
Error 1312 (0A000): PROCEDURE proc_name can't return a result set in the given context.

RFS399: CCPCSCP: CTTalk compiler: Goto module without Label not detected
If the Goto module was not specifying a Label, no errors were issued during the compilation and the code generated was corrupted.

RFE163: CCPDaemon: Extra SMTP configuration parameters
In order to pass some spam filters, the SMTP module now supports the authentication method and non-anonymous sender.

RFS396: MCU NMS: Wrong timeslot assignment with CG6060 board
Wrong timeslot assignment with NMS CG6060 board for DSP channels. This made the board unable to properly run media functions.

RFE162: MCU DialogicGC: SIP blind transfer support
Added support for SIP and H323 blind transfer.

RFS395: MCS: Routing rules
It is now possible to specify URI or ANI and DNIS criterias. This is required for VOIP call routing.

RFS392: CCPCSRTC: CTTalk Application Runtime engine: VX_Interrupt not returning
In some cases, depending on the compile order of the Start modules, the VX_Interrupt was either not returning or not waiting on the completion of the command.

RFS391: MCU NMS: mismatch between signaling and DSP when mixing RAW and protocol into digital trunk
When RAW is defined before a protocol on a digital trunk, one timeslot is defined on the DSP (in a linear way). This leads to a change on the "default" DSP assignment for the trunks with a protocol defined. By default NMS put the protocol event on the "default" DSP, therefore the event for a greater PSTN timeslot is coming on the default DPS timeslot. Correction made for ISDN protocol, not for CAS (needs to establish default connection for signaling at board start, only default connections for voice are made).

RFS390: MCU NMS: Play/Record on heavy load can freeze the MCU (and NMS ctdaemon)
Change on NMS policy made the play and record first and second callback call to be on the same thread as call adiStartXXX. This causes a lock under heavy load. Change to use adiXXXAsync instead.

RFE161: MCU Kallastra: Extra G.726codec
Added support for G.726 40, 24 and 16kbps

RFE160: MCU NMS: Change VOIP behavior, delete gateway mode
It was not possuble to enter an RTP endpoint in conference.Two modes were possible: gateway (DS0 created on channel) or media (DS0 created on RTP). The "advantage" for gateway mode would have been use of a universal port. We have only kept media mode to simplify. The behavior will be the creation of the connection between RTPDS0 at the openCircuit. All switching (link/reconfig/conference) will just be a use of the regular switching methods between channel/dsp and channel/channel.

RFS389: MCU Eicon: Prompt corrupted when using TTS
When TTS play was called continuously with short text, the audio output was corrupted.

RFS388: MCU NMS: play and record stopped even if only play should be stopped
This bug was introduced by RFS374. Instead of testing if function play is active AND requested to stop (same for record) the test was ORed.

RFS387: MCU: Buffer lost when using TTS
On a fast machine, audio buffers around the 5th second were lost if the TTS engine was producing too much data before the MCU playing those buffers was starting to retrieve them.

RFE159: MCU OSR: Low confidence results
The recognition Barge-in (mode 0) can be improved by setting a minimal confidence level. Moreover, the PromptDone state can be forced when using good echo cancellation.

RFE158: MCU DialogicGC: Call Progress Analysis for digital trunks
By doing a vx_putdtmf after a successful outbound call with the following parameters, the application can determine the connection type.
ca_intflg=7;ca_pamd_spdval=3;ca_pamd_qtemp=11
Other parameters are: ca_nbrdna, ca_noanswer, ca_cnosig, ca_pamd_failtime, ca_pamd_minring.
Result is retrieved using CC_CallResult. This feature requires CCPCSRTC v2.0.0.11 or higher.

RFS386: MCU NMS: Correction of VOIP
Adding media server mode, correct some minor parts.

RFE157: MCU DialogicGC: SS7 Global Call support
Support of SS7 using GlobalCall Universal API.

RFS385: MCU DialogicGC: Recovery on failed blind transfer
Attempts to recover driver failure during blind transfer.

RFE156: Platform: Audio and Video codecs support
Introducing the support of Audio and Video codecs negotiation.

RFS384: MCU Eicon: Conferencing AddMember issue
Sometimes Addmember returns an invalid state when more than one function is called at the same time.

RFE154: MCU Eicon: Color Fax support
Enabling Color Fax support.

RFS382: MCS: Backup ARDB files not use in certain corruption cases
This is the Application and Routing rule database file. If an ARBD file was corrupted, the MCS was not always able to load the backup ARDB, depending on the type of corruption of the previous ARDB.

RFS380: MCU SIP: Compatibility issues with Cisco routers
This includes adding the Remote-Party-ID field.

RFS379: MCU DialogicGC: HMP 3.0 compatibility
SIP outgoing call and conferencing were not working properly.

RFS378: MCU Kallastra: Long distant communication
The TTL (Time To Live) used for RTP packet was set to 10. The default is now 32 and can be set in the TTL parameter of the board section.

RFE149: APPSDK & MCS: Ability for Application to suspend receiving or making calls
A new function that allows an application to suspend incoming calls and outbound calls in order to resume itself or stop gracefully..

RFE148: MCU SIP: Proxy/Registrar usage
The SIP MCU can now use a Proxy/Registrar.

RFS377: MCU Synway: New SHD-120 Board support
SHD-120A-CT/PCI/SS7 not supported. This board can be used now as an ISDN link only.

RFS361: MCU SDK: OAM commands not done on Signaling link
All messages related to a signaling link were (wrongly) done on circuits rather than on the signaling device.

RFS350: Cameleon Application Designer: Start module process ID list errors
Start module changes a list of process IDs such as "1,2,11,12" to "1-2,11-12" - then rejects it. Also, for a simple ID list, a space will be added after the comma: "1,3" => "1, 3" - this is rejected too.

RFE128: MCU DialogicGC: Disabling call progress on analog lines
New flag to disable call progress on analog lines.

RFS225: MCU Aculab: Digits not correctly detected
In some circumstances, when DTMFs were pressed too fast, they were not detected. (Cf.:Aculab support suggested not to restart the listening function at every media function. They recommended to call this function only once for all).
_____________________

End of List