Server

General Information

Releases Documented

Read These Release Notes in Conjunction With ...

Release Version 1.2

Incorporated Point Releases

New Features and Hot Topics

Installing this Release

Improvements

Restrictions and Limitations

FYI

Release Version 1.1

New Features and Hot Topics

Improvements

Release Version 1.0

New Features and Hot Topics

Legal Information

Copyright Notice

General Information

This file contains release information not currently documented in the documentation for CT Media Server 1.2.

• Visit our website at http://support.dialogic.com/CTmedia for the most current information about this release, including details about component changes, point releases and other issues.
• For Sales Offices and other contact information, visit our website at http://www.dialogic.com
• Extra information to help you design your CT Media 1.2 code to ease future porting to CT Media 2.0 is included in \PortingGuide\port_gde.pdf on your CT Media CD.

Releases Documented

• CT Media Server 1.2
• CT Media Server 1.1
• CT Media Server 1.0

Read These Release Notes in Conjunction With ...

• CT Media QuickStart for Windows NT
• CT Media Application Developer's Guide for Windows NT
• CT Media API Reference for Windows NT
• CT Media Administrator's Guide for Windows NT
• CT Media Container Developer's Guide and Reference for Windows NT
• Dialogic CT Media Resource User's Reference for Windows NT
• Dialogic CT Media Resource Configuration Guide
• Resource Package Release Notes

Release Version 1.2

Incorporated Point Releases

This release of CT Media Server 1.2 incorporates the following point releases:

New Features and Hot Topics

Multinode

CT Media can now be installed such that the CT Server runs on one machine and CT Media Resources run on a separate machine. See the QuickStart Guide and the Administrator's Guide for more details.

Resource Developer's Kit

The CT Media Resource Developer's Kit is not included in the CT Media Server 1.2 package. The RDK will be released at a later date.

Container Developer's Kit

Support for the development of media plug-ins is available for the CT Media Server 1.2 package at a beta level only. Contact your Dialogic sales representative regarding participation in our Container Development field trial.

Process Affinity

Services can be configured for binding a process to a processor. See the Administrator's Guide for details.

Version Discovery

In the Dialogic CT Server Administration Application, choosing Help | About this Application will display a dialog showing the version of CT Media for the Server and Client installation.

Access to Arrays of Arrays in KVSets

PTR 6118 - New API functions are defined to enable access to values which are arrays of arrays within KVSets. See the CT Media API Reference, Volume 1, for details.

Installing this Release

System Requirements Restrictions

1. This release of CT Media requires the pre-installation of Windows NT 4.0 SP5.
2. The behavior of CT Media is undefined if any installed files or directories are changed using methods other than those provided by the CT Media product.
3. CT Media is not guaranteed to function properly if system resources are insufficient. For example:

• If your system does not have enough virtual memory, parts of the CT Media Server may disappear; i.e. they terminate with no warnings or message boxes. In the server logs you may get a message saying that something has terminated unexpectedly.
• The CT Media Server will terminate if there is no space left on the hard disk.
• CT Media does not limit the demand placed on the server by any single client. If a rogue client overloads the CT Media Server, then processing could slow to an unacceptable level.

Installation Restrictions

1. CT Media may install files with duplicate names in different directories, depending on your installation choices. Make sure that your MSVC environment paths are set up to use the correct files for your development (eg \Server\RDK\include\ when you are developing with the RDK), especially if you have made any changes to installed files.
2. PTR 5572 - Installing CT Media by specifying an absolute path (computer\share name\path\setup.exe) greater than 70 characters will cause the error "Incorrect parameter". (2066)
3. PTR 5574 - If you install a third-party resource (service) after a fresh install of CT Media and find it does not run, it may be that:

• the system path has not been properly applied. Try restarting Windows
• the system path contains a reference to a network path before the references to the CT Media Server binary directories. The fix is to remove network paths from the system path (we suggest shifting them into the user's path variable) and then restart Windows.(2317)

1. We require that users install the Windows NT Service Pack 3 before installing CT Media. If Service Pack 3 is not installed, then the CT Media performance counters will not work until a non CT Media counter is added. Use of Service Pack 5 is strongly recommended. (3533)
2. In a multinode install, the main CT Media directories on both the Server and Resource nodes must be shared using the name CTServer, even if CT Media was installed under a different directory name.

Deinstallation Restrictions

1. Do not use Control Panel | Add/Remove Programs to uninstall CT Media; use the supplied uninstall programs first for the Dialogic Resource Package (if installed) and then for CT Media. (3426)

Improvements

1. The following 1.2 beta release PTRs were not reproducible in CT Media Server Package 1.2 Production:
   PTR6922
2. The following 1.2 beta release PTRs have been resolved in CT Media Server Package 1.2 Production:
   PTR5738
   PTR6498
   For resolution details of these PTRs visit Dialogic online support at http://support.dialogic.com .
3. The following issue from the previous release has been fixed: "PTR 6118 - New API functions are defined to enable access to values which are arrays of arrays within KVSets (3747)".
4. The following issue from the previous release has been fixed: "PTR 4696 - CT Media does not return call progress analysis results on outbound calls. (2120)"
5. The following issue from the previous release has been fixed: "System Snapshot may not run automatically for third-party Services that fail.(3817)"
6. The following issue from the previous release has been fixed: "PTR 6751 - In the CT Media Event Viewer, when viewing Event Details, some Events will have nonsense characters at the end of their descriptions. These should be ignored. (4197)"
7. The following issue from the previous release has been fixed: "PTR 6750 - The Performance Monitor will not show any statistics for Services on the Resource Node in a multinode environment. (4060)"
8. The following issue from the previous release has been fixed: "PTR 6749 - The Container Manager cannot be run on the Resource Node in a multinode environment. (4082)"
9. The following issue from the previous release has been fixed: "PTR 6747 - When uninstalling the Resource Node in a multinode environment, if the CTMS Server Service is running, the uninstallation may hang and the uninstallation will need to be run again from uninstal.exe. To avoid this, stop the CTMS Server Service before uninstalling. (4224)"
10. The following issue from the previous release has been fixed: "PTR 5497 - The documented Detect Hangs option for a CT Media Service is not available and will not be visible from the Administration Application. (3419)"
11. The following issue from the previous release has been fixed: "PTR 5578 - The error "contmgr.cxx(1446) : Failed Register Interest in Session Manager " may be returned in the e_ise.log file and the following logged to the system event log: "An internal system error has ocurred! - To obtain technical support, please contact the supplier of the component cores.exe and provide the following details." This error does not indicate any functional failure and can be ignored. (3094)"
12. The following issue from the previous release has been fixed: "PTR 5575 - Depending upon your hardware, inbound calls may be possible at Server Level 4 (1600)"
13. The following issue from the previous release has been fixed: "PTR 5573 - Installing CT Media into a directory whose name has a space (e.g., "CT Media" ) can cause incomplete uninstallation. Note that this includes using the \Program Files\ directory. (3351)"
14. The following issue from the previous release has been fixed: "If an inbound call arrives for which there is no receiver, the e_cores file will display the failure error ".\GroupMgr\scrgroup.cxx(877) [03/13/98 09:07:48 142372270]: SCRGroup::HandOffComplete(): Failed to handoff group around line..." and e_ise log files will display ".\ise\ise.cxx(1132) [03/13/98 09:14:55 142799114]: DL_ISE::GroupHandedOff(): Failed HandOff, device...". These errors can be ignored. (3116, 3117)"
15. The following issue from the previous release has been fixed: "In the Administration Application, if you are changing the Server Level from 5 and it stops on Level 4, check that you have all CTMS Applications closed. (1704)". It is still a requirement, however, that all non-Administration Sessions connecting to the Server be terminated.

Restrictions and Limitations

Administration Restrictions

1. In a multinode environment, you must ensure that the Service names are unique on both the Server and Resource Nodes. In other words, do not install a Service on the Resource Node using the same name as an existing Service on the Server Node (3763)
2. PTR 6765 - In a multinode environment, if you shut down the CTMS Service on the Resource Node, the Server Node may not recognize that this is no longer available (4181)
3. When using Process Affinity with the HubProcessor Service, if the HubProcessor fails to bind to a process, the resulting error message refers to "SMPReg" rather than "HubProcessor" (4152)
4. In the Administration Application, if you use the Service | Stop option on a Service which is still in use by a running application, this could cause the CT Server to terminate abnormally. Using Change Server Levels to stop such a Service will ensure necessary cleanup. (1900)
5. In the Administration Application, if you try to add a new Service while the Server is still changing levels, the Server can hang. (3339)
6. PTR 6799 - Leaving any S.100 Administration Application running during a shutdown of the CT Server will cause a memory leak. This includes the Dialogic CT Server Administration Application. (4283)
7. PTR 5576 - In rare race conditions on Server shutdown, the CT Media Server can terminate abnormally.(3194)
8. PTR 6748 - If you have installed Administration Utilities on the Resource Node in a multinode environment, the option on the Server menu to Configure for Multinode can still be selected. The behavior of CT Media is undefined if you run this option on the Resource Node (4119)
9. The Performance Monitor may return random values for server statistics if the CT Media Server terminates abnormally or hangs.
10. PTR 6752 - If you are running low on diskspace, System Snapshot may indicate it has completed successfully, when actually it has created a SnapShot file with the space you have available. There is no notification that it could not collect all files. (4203)
11. PTR 4787 - Inbound calls will not be accepted if the Inbound Rules (in the SCR_RoutingRules profile) contain only a "LineID" condition. (2688)
12. If you delete all rules in the SCR_RoutingRules profile and then save the profile, you will not be able to open it again. You will have to start over with a new profile. (3806)
13. PTR 6753 - If you use reserved Symbols (e.g., Any_ECTF_Null) as KVSet names, in a profile, the Profile Editor may terminate. (3994)
14. The error ".\ise\isedev.cxx(94) [07:36:09 12/17/97]: L_ISEDevice::GetDevice() Unable to get device info for device "" " may be returned in the e_ise.01 log file. This error does not indicate any functional failure and can be ignored. (2801)
15. PTR 5577 - The DLGC_ISE service can terminate abnormally if a lot of calls are made on ISDN while ISDN is closed using the Service | Stop option (this option is not recommended). (1900)
16. If CT Media is installed on Windows NT without Service Pack 3 installed, then the CT Media performance counters will not work until a non CT Media counter is added. Installing Service Pack 3 will fix this problem. Use of Service Pack 5 is strongly recommended. (3533)

API Restrictions

1. CTadm_UpdateService() does not check that the supplied Service name is less than the maximum of 32 characters. Supplying a Service name that is too long can lead to memory corruption. (4420)
2. Resources allocated to a Group are not allocated in a "best-fit" manner. For example, if you request only a Group with a Player Resource, you could be allocated the only available hardware which also includes Fax resources. If you then requested a Fax Resource, it would not be available. (2006)
3. CT Media symbol format does not yet conform to the ECTF vendor registry or the S.100 Addendum. If you are porting an application from a Server which does conform, you will need to recompile the application. (2780)
4. PTR 5579 - CTcont_ReadContents will return an error of CT_errorBadArg if the size of the read is greater than 1 MB. (1129)
5. In CTgrp_GetParameters(), returning all parameters on an SPR-Group, some CCR parameters will also be returned. These should be ignored, as they are relevant only to a simulated CCR and are not accessible to the API user. (1642)
6. In an asynchronous CTgrp_Return() call with a valid group handle, if an unwind event for that group arrives before the completion of the CTgrp_Return(), the Group_ECTF_Completion event may show an error of NotOwner and an ACT of 0. (2269)
7. The function CTgrp_Retrieve() may cause commands already started by the current owner of the Group to fail, with varying results depending on the state of the command when the Group is retrieved. We recommend that:

• CTgrp_Retrieve should not be used unless application functionality requires it.
• A robust application will reliably handle an unwind event caused at any time by another application issuing a retrieve command. Failure to do so will impact the reliability of multi-vendor systems.
• A robust application will reliably handle completion events to all outstanding transactions, which may arrive even after an unwind, destroy, return, or handoff notification.

1. PTR 4844 - CTgrp_SetRTC() incorrectly accepts an RTC argument whose conditions (values) are of type CTsymbol, rather than CTsymbol[]. (3155)
2. PTR 5582 - If you call multiple asynchronous CTses_Stop()s, set to stop all transactions, one or more of the CTses_Stop()s may never terminate. At this point, any further CTses_Stop() calls will also not terminate. (2171)
3. PTR 6754 - CTscr_MakeCall() will not take NULL as the ASI or Config arguments; use "" instead. (3430)
4. Under certain conditions, the e_cores file will display the failure error ".\HandOff\HndOffCx.cxx(1020) [03/25/98 12:21:06 2652003]: HandOffProcessor::AnswerCallCmplt(): Failed to answer the call on a handed off group, error @23069805, group address = [ 1 3 49 ] {}" . This error can be ignored. (3168)
5. PTR 5586 - You can only query the state of a CCR (through the CCR_ECTF_State parameter) and the state of a Signal Detector (through the SD_ECTF_Mode parameter). No other resources' states can be queried. (3435)
6. PTR 6755 - Event messages that are sent to Application Services do not contain the correct ObjectID of the Object that sent the message. In order for the Application Service to respond to the message, it must first set ObjectID to its own Session ID before calling CTses_SendMessage(). (3914)
7. PTR 6756 - An Application Service may receive a Session_ECTF_Stop request to stop an outstanding request sent from a client. When the Application Service receives the stop request, it can extract the tranID of the transaction to be stopped from the eventData with key Session_ECTF_StopTransactionID (CTint) (4051)

CT Sim and SimD4x Restrictions and Limitations

The CT Sim utility and the simulated Resources (SimD4x) are not guaranteed to behave as a fully implemented testing environment. Not all validation is implemented as it might be on a real resource, and commercial robustness should not be expected. Some limitations include:

1. CT Sim will terminate if there is no space left on the hard disk. (886)
2. If you need to know whether a Simulated Resource is active, you must check both the state of the Resource and the command currently executing on that Resource. Simply checking the state will not guarantee an accurate reading of that state. For example, for a Player, you should check the state of the Player and check that the command is Player_ECTF_Play.
3. CT Sim allows negative values for the Size argument in a CTcont_ReadContents() call, although this is a CTuint. (1133)
4. Within a for loop, performing a waitres command and specifying a quit action on failure will only cause CT Sim to enter the next iteration of the for loop, not quit the program. (1430)
5. If you omit the next statement after a for loop, CT Sim does not return any warning. (1668)
6. SimD4x will allow you to succeed a command before the command has reached the active state. This means SimD4x can be put into a bad state by malicious use. (1787)
7. The CTsym_SymbolToName() function (in CT Sim) does not accept a Symbol as input. (2874)

Container Developer's Restrictions

The Container Developer's Kit is supported only at beta level to qualified field trial testers. Contact your Dialogic sales representative regarding participation in our Container Development field trial.

1. Container Statistics are not supported.
2. When a KVSet is returned in a Done function, (e.g.; SCstorage_ReadStreamDone), if you use CT_kvsNull, the Container system returns an error. Use an empty KVSet instead. (3695)
3. If you add debug streams tracing code into your Container DLL, your DLL must also include the following line in the Shutdown function: SC_dbgDeregisterLibrary(__SC_Library_Name). (4361)

Documentation Errata

API Reference, Volume 1

1. PTR 6774 - The Session_ECTF_Destroy event may be received as an unsolicited Event as well as the completion event for CTses_Destroy(). (4246)
2. In the completion event for the function CTadm_GetSPInfo() the key Admin_DLGC_SPAvailability should be Admin_DLGC_Availability. (4284)
3. PTR 15570 - For CTscr_MakeCall(), the Timeout argument lists "0 or CT_intNoWait" as a valid timeout. If you pass a 0 or CT_intNoWait timeout, no call attempt will be made. (4418)
4. All references to the include file ctapps.h should be ct_apps.h.

API Reference, Volume 2

1. All references to the include file ctapps.h should be ct_apps.h.

FYI

Installation Information

• The Dialogic Resource package must be installed before applications that use Dialogic's vendor specific Resource features can be run.(3413)
• Integrated help (F1) for CT Media is available in Microsoft Developer Studio (Visual C++ 5.0). To enable this:

1. Open the Registry Editor to the EXTENSION key under: HKEY_CURRENT_USER/Software/Microsoft/DevStudio/5.0/Help
2. Change the "Enable" value to 1
3. Restart Microsoft Developer Studio. Choose Help | Use Extension Help

NOTE: If you need to use the Books Online help, you must uncheck Use Extension Help.

• Upon installation of Windows NT 4.0, the file extension .hlp may be associated with the 16-bit version of help, winhelp.exe. To view the CT Media help files, you must change that association to winhlp32.exe using the standard procedure.
• When you view the included CT Media electronic documentation (ie, the .pdf files) be aware that Acrobat uses the Title Page as page 1. What you are seeing is an electronic representation of the physical Dialogic manuals, which use the first page of Chapter 1 as page 1. The Table of Contents and Index entries in the CT Media documentation refer to the page numbers which appear in the lower corners of the pages, not the page numbers assigned by Acrobat. (2948)

Run Time Information

• Symbols that are defined in ct_syms.h and are not in the API documentation are subject to change.

Release Version 1.1

New Features and Hot Topics

1. This release supports development only with MSVC++ v5.0 or above
2. There have been some improvements to the Container Manager. See the Technical Improvements section for details.
3. The default CT Media Server name has changed to "Default_Server" from "CTMS_Default_Server". This version of CT Media is backward-compatible and will work with CT Media applications written to Version 1.0.1, but you will no longer be able to add a Server entry for CTMS_Default_Server.
4. The constant CTses_intWaitForever is no longer defined. Use the standard timeout constant CT_intForever.
5. A System Snapshot utility is now available (see Improvements for details).

Improvements

Technical Improvements

1. Improvements have been made to the Container Manager:

• The default view is now List View. This is to improve performance with large numbers of Containers (i.e., greater than 100), .
• In all views, you can select a Data Object and press Alt-Enter to view details for the selected Object. This is particularly useful in List View when you have large numbers of Containers and it would take significant time to change to Details View, which shows details of all Data Objects.
• When you have large numbers of Containers, some Container Manager procedures may take a noticeable amount of time. In these cases, progress text will be displayed in the progress bar on the bottom right. During these procedures, Container Manager is not multitasking.

1. System Snapshot is an executable which will gather relevant information about your system. System Snapshot will be run automatically when the CT Media Server terminates abnormally, or you can run it yourself at any time to provide Dialogic with information to aid in solving problems you are having.

The executable for System Snapshot is at CTServer\server\bin\SnapShot.exe (adjust this if you have installed under a different directory than the default of CTServer).

The output from System Snapshot will be found in a new directory which is:

• at the same level as your CT Media installation directory
• named after your installation directory (e.g.; CTServerSnapShot for a default installation)

The latest output from the last execution of System SnapShot will always be in a subdirectory named SSLatest (e.g.; \CTServerSnapShot\SSLatest\). This directory is what should be zipped and sent to Dialogic Technical Support.

Older versions will be renamed when a new SSLatest is created (e.g.; SS1, SS2, etc). You should delete old versions from this directory periodically, to save space.

1. The following problem from the previous release is now fixed: "The uninstallation of the CT Media Server requires that the CT Media Server change to level 1. If this level change does not succeed, the uninstall will wait forever. If this happens, try rebooting your machine. Once the CT Media Server has (automatically) started, use the Administration Application to change the Server Level to 1. Then rerun the uninstallation. (1684)"
2. The following problem from the previous release is now fixed: "Some profiles may lose the first letter of their profile name when they are imported. (1876)"
3. The following problem from the previous release is now fixed: "PTR 5581 - The Profile editor allows profiles to be entered which stop the server from starting. If you have edited a profile and are subsequently unable to start the server, you may be able to edit the profile file to fix the problem. If you are unsure, contact Dialogic technical support. (1590, 3434)"
4. The following problem from the previous release is now fixed: "If the TCP/IP address for the Default_Server is changed, you must stop and restart the Administration Application to view the correct information from the new address. (771) "
5. The following problem from the previous release is now fixed: "In CTcont_ReadContents() and CTcont_WriteContents(), it is recommended that you read and write in "small" amounts - less than 100K, with 10K being ideal. The exact limit is system-dependent (1136)"
6. The following problem from the previous release is now fixed: "Calling CTgrp_Create() with a timeout of CT_intForever (or -1) means that the function cannot be stopped. It is recommended that you use a "very large" number for the timeout rather than CT_intForever. (2587)"
7. The following problem from the previous release is now fixed: "Playing a bad TVM will return the correct error to the application, but it will also log errors in the NT Event Log and the Media Service error log (1978)"
8. The following problem from the previous release is now fixed: "The Glossaries in the help files are not currently available. (1677)"
9. The following problem from the previous release is now fixed: "In the Administration Application, you cannot perform an emergency shutdown to your current level. This is relevant if you are trying to increase the Server level and it cannot increase for some reason. You will have to do an Emergency Shutdown to the level below the one you were on. If you were on Level 1, you will have to use the Server Start Stop utility to stop the CT Server. (1669)"
10. The following problem from the previous release is now fixed: "When you change any Service Properties, the Service will automatically start if the level of the CT Server is appropriate for the Service to be started. (1855)"
11. The following problem from the previous release is now fixed: "Using the page down key in the Generic Profile Editor will page down more than just a single page. (1791)"
12. The following problem from the previous release is now fixed: "In CTgrp_GetParameters() on Player_ECTF_CoderTypes, you may get the value Container_ECTF_6kADPCM instead of Container_ECTF_24kADPCM, and Container_ECTF_8kADPCM instead of Container_ECTF_32kADPCM . (1780)"
13. The following problem from the previous release is now fixed: "In the CTplyr_Play() function, there will be no error returned if the Offset specified is longer than the TVMs available to play. (1718)"
14. The following problem from the previous release is now fixed: "You cannot stop a script executing without also exiting CT Sim. (1026)"
15. The following problem from the previous release is now fixed: "CT Sim may still prompt for the parmList argument rather than the OptArgs argument. This will have no effect on functionality. (1692)"
16. The following problem from the previous release is now fixed: "CT Sim will display status values (eg CT_statusOK) in an abbreviated form (eg OK). This will be true even if you have specifically assigned the full status value to a variable. (1745)"
17. The following problem from the previous release is now fixed: "CT Sim type checking does not fail function calls which cast objects as strings. This could lead to memory loss. (1793)"
18. The following has been fixed: (PTR 4929) " CTcont_Copy would not allow the the copy to take place even if the target data object is opened for read access, since it assumes that it will have Write access to the target data object." (L2045)
19. The following has been fixed: (PTR 4935) "If I do a makecall() on an analog device that is not attached to anything with a long timeout the correct error CT_errorNoDeviceAvailable) is returned but the time after which it is returned is less than it should be." (L2074)
20. The following has been fixed: (PTR 4946) "Sometimes reconfigurations that can never be successful (given the resources in the system) do not return." (L2135)
21. The following has been fixed: (PTR 5035) "Stopping a make call is not supported under PRI SPP, although it can be done using the SR4 APIs relatively easily." (L2174)
22. The following has been fixed: (PTR 5034) "Create many (200) groups SPR headed "P" groups ASYNC and then wait for results. Some of the group creates never complete and when they do, they complete in "batches". Can be done using simulated resources." (L2170)
23. The following has been fixed: (PTR 5036) "There is an access violation in PRISPP.exe when running the entire test sweep. This takes approximately half an hour to reproduce and has been reproduced 3 times on the same setup." (L2177)
24. The following has been fixed: (PTR 5033) "Receiving a disconnect during an answer call causes the group to become lost. On shutdown the server becomes stuck at level 4. This condition was isolated by making a call with the caller side and the called side receiving their group's in the alerting state. As soon as the caller's group arrives it drops the call. (L2133)
25. The following has been fixed: (PTR 4715) "CTsg_SendSignals() does not generate a completion event when stopped using CTgrp_Stop, or CTses_StopTransaction, until a multiple of SG_DLGC_Duration" (L2140, L2337)
26. The following has been fixed: (PTR 4850) "Multi-thread invocation of CTsym_SymbolToName() causes access violation and application failure." (L2339)
27. The following has been fixed: (PTR 4477) "Wrong transaction ID and status values are returned when CTsym_LoadTable() is issued ASYNC." (L1733)
28. The following has been fixed: (PTR 5032) "Making an outbound call on a channel at the same time that an inbound call is being made (glare) causes the PRISPP.exe to hang. It will not respond to any requests including pings or shutdown requests." (L2105)
29. The following has been fixed: (PTR 4472) - "Using a sample profile defining an ASI ="AnswerDemo" and an ASIMap indicating that calls should be directed an application registering with an ASI="AnswerDemo", I was able to successfully issue a RequestGroup() call on an application with an ASI ="AnswerDemo", yet I was not able to take calls on that application. However, I was able to RequestGroup() and take calls when I specified an ASI = "AnswerDemo"." (L1732)
30. The following has been fixed: (PTR 4483) "Data returned in Player_ECTF_Offset and Player_ECTF_TVM is inconsistent with the functionality described in the manual and S.100 specification" (L1851)
31. The following has been fixed: (PTR 4789) "Server install shows error message if system PATH env var is missing. Install exits with no further messages. Server is left in workable state." (L2341)
32. The following has been fixed: "AtoDE <-> DEtoA is not symmetrical when a string field has a single " in it." (L1757)
33. The following has been fixed: "CTcont_Rename() will return the undocumented error CTerror_InvalidOp if you specify "" for the OldFullName." (L2055)
34. The following has been fixed: (PTR 5037) "When doing a blind transfer as specified in the API Reference, it doesn't work." (L2456, L2476)
35. The following has been fixed: (PTR 5024) "Use of the SD_ECTF_InterSigTimeout parameter may cause crashes." (L2538)

Documentation Improvements

1. The following issue from the previous release has been fixed: "All stoppable functions, as listed in the Cautions of CTses_Stop(), can return the error CT_errorStopped. (1929)
2. The following issue from the previous release has been fixed: "All arguments referring to Container or Data Object names in the Container API functions should be of type const char*. Currently some are listed as char*."
3. The following issue from the previous release has been fixed: "In the CTsym_SymbolToName() function, the prototype currently contains a const char* for the buffer in which to store the converted Symbol name. It should be simply a char*. It is recommended that users write their applications using char* rather than const char*, since this will be fixed in a future release. (1850)"

Release Version 1.0

New Features and Hot Topics

1. CTMS has been renamed by Dialogic to CT Media. The product and documentation for this version will still refer to CTMS.

Legal Information

Copyright Notice

All names, products, and services mentioned herein are the trademarks or registered trademarks of their respective organizations and are the sole property of their respective owners. DIALOGIC (including the Dialogic logo) is a registered trademark of Dialogic Corporation. A detailed trademark listing can be found athttp://www.dialogic.com/legal.htm .

Publication Date: December, 1999
Part Number: 00-2760-005

Dialogic Corporation
1515 Route 10
Parsippany NJ 07054

Visit our Technical Support website at http://support.dialogic.com.

For Sales Offices and other contact information, visit our website at http://www.dialogic.com