Issues Sorted by Type, Dialogic® Multimedia Platform (Continued)
Issue Type | Defect No. | SU | Product or | Description | |
No. | Component | ||||
|
|
| |||
|
|
|
|
| |
Known | IPY00034601 |
| clocking | The TDM clock manager does not switch to a valid | |
|
|
|
| clock that is located earlier in the fallback list before the | |
|
|
|
| failed entry. For example, if the last valid trunk clock | |
|
|
|
| source fails, the firmware chooses the internal oscillator | |
|
|
|
| as the clock source instead of a previously recovered | |
|
|
|
| trunk that is in the fallback list. The correct behavior is | |
|
|
|
| that the fallback list should be rescanned from the | |
|
|
|
| beginning before choosing internal oscillator. | |
|
|
|
| Note: if any clock recovers while internal oscillator is | |
|
|
|
| selected, then the firmware rescans the list from | |
|
|
|
| the beginning. | |
|
|
|
| Workaround: The user can reset the fallback list | |
|
|
|
| manually. At a minimum, there will always be a valid | |
|
|
|
| tx PSTN clock provided by internal oscillator. | |
|
|
|
|
| |
Known | IPY00033354 |
| conferencing (CNF) | The cnf_GetPartyList( ) function does not return | |
|
|
|
| correctly when max parties (240) are entered into the | |
|
|
|
| conference. | |
|
|
|
|
| |
Known | IPY00033349 |
| conferencing (CNF) | CNFEV_SET_ATTRIBUTE_FAIL is received when | |
|
|
|
| attempting to disable tone clamping. | |
|
|
|
|
| |
Known | IPY00035617 |
| configuration | The RFC2833 payload type is currently set to 101. | |
|
|
|
| Even though the user may specify another payload type | |
|
|
|
| for RFC2833, the software transmits RFC2833 with | |
|
|
|
| payload type of 101. | |
|
|
|
|
| |
Known | IPY00035616 |
| configuration | The RTCP port number is not configurable by the user. | |
|
|
|
| RTCP port will always be RTP+1. Currently this cannot | |
|
|
|
| be changed by the user. | |
|
|
|
|
| |
Known | IPY00035815 |
| firmware | The firmware tries to load the Rear Transition Module | |
|
|
|
| (RTM) PCI driver even when the RTM is not present. | |
|
|
|
| The firmware displays a KILLTASK message in the | |
|
|
|
| /var/log/messages file because the RTM driver failed to | |
|
|
|
| initialize. Since the RTM is not present, the firmware | |
|
|
|
| should not try to initialize the RTM driver and should not | |
|
|
|
| treat the failure as an error. | |
|
|
|
| The error can be ignored. | |
|
|
|
|
| |
Known | IPY00032953 |
| firmware | QERROR_WARNING received during download with | |
|
|
|
| Cause Tag: 80011, Location Tag: 49111. The warning | |
|
|
|
| can be ignored. | |
|
|
|
|
| |
Known | IPY00037689 |
| hardware | If the Dialogic® Multimedia Blade is shut down with an | |
|
|
|
| RTM present, the baseboard hotswap (blue) LED | |
|
|
|
| remains in a blinking state and never goes to a steady | |
|
|
|
| state as expected to indicate shutdown is complete. | |
|
|
|
| Workaround: Wait for all software services to shut | |
|
|
|
| down before extracting the board. | |
|
|
|
|
|
Dialogic® Multimedia Software for ATCA Release 1.0 Release Update, Rev 06 — January 23, 2008 | 13 |
Dialogic Corporation |
|