Update to the ipm_StartMedia( ) function
An invalid state error is returned if a coder is not reserved prior to calling the ipm_StartMedia( ) function. All audio coders must be reserved using the dev_ReserveResourceEx( ) Dialogic® Device Management API library function prior to use in the ipm_StartMedia( ) function.
Update to Chapter 3, Events
The IPMEV_QOS_ALARM event description, on page 84, indicates that “No data is returned in the event.” This statement is misleading because it implies that it is not possible to determine which alarm triggered the event. Replace the description with the following text:
IPMEV_QOS_ALARM
Unsolicited event enabled via ipm_EnableEvents( ). Event is returned when desired QoS alarm gets triggered. For information on determining which alarm triggered the event, see the code example, and specifically the CheckEvent( ) function definition, in the Dialogic® IP Media Library API Programming Guide section on “Example Code for QoS Alarm Handling.”
Update to the IPM_AUDIO_CODER_INFO data structure
Update for the eCoderType field: The following possible values have been added for specifying the transmit bit rate when using AMR coders:
•CODER_TYPE_AMRNB_4_75k – 4.75 kbit/s, CMR type 0
•CODER_TYPE_AMRNB_5_15k – 5.15 kbit/s, CMR type 1
•CODER_TYPE_AMRNB_5_9k – 5.9 kbit/s, CMR type 2
•CODER_TYPE_AMRNB_6_7k – 6.7 kbit/s, CMR type 3
•CODER_TYPE_AMRNB_7_4k – 7.4 kbit/s, CMR type 4
•CODER_TYPE_AMRNB_7_95k – 7.95 kbit/s, CMR type 5
•CODER_TYPE_AMRNB_10_2k – 10.2 kbit/s, CMR type 6
•CODER_TYPE_AMRNB_12_2k – 12.2 kbit/s, CMR type 7
•CODEC_AUDIO_AMRNB_NONE – Don't care, CMR type 15. Indicates that the software does not care what bit rate it receives, the eCoderType field sets the CMR value in the transmitted packet.
For the MEDIATYPE_AUDIO_LOCAL_CODER_INFO media type, all of the above values are valid. For the MEDIATYPE_AUDIO_REMOTE_CODER_INFO media type, all values are valid except CODEC_AUDIO_AMRNB_NONE.
Update for the eFrameSize field: The only supported value for AMR is
CODER_FRAMESIZE_20. This is not a technical limitation, but part of the protocol.
Update for the unFramesPerPkt field: For AMR, the only supported value is 1 frame per packet.
Update for the eVadEnable field: For AMR, setting this field to
CODER_VAD_ENABLE is required.
Update for the unCoderPayloadType field: For AMR, negotiated by call control.
24Dialogic® Multimedia Software for ATCA Release 1.0 Release Update, Rev 06 — January 23, 2008 Dialogic Corporation