|
|
|
|
|
|
| Features in |
|
|
| 23 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR44x / AR450 | AR7x5 | AR750S |
| Rapier i |
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012594 | STT | 3 | With unidirectional traffic or small frames, an STT connection would sometimes | Y | Y | Y |
| Y | - | - |
| - | - | - | - |
|
|
| stop passing data. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Level 4
CR | Module | Level | Description |
CR00003286 | Core, ISDN | 4 | Previously, the log message generated when an ISDN call came up sometimes |
|
|
| reported the channel as “channel unknown” when the channel was encoded as |
|
|
| a channel map instead of a channel number. The type of encoding depends on |
|
|
| the local ISDN provider, so this issue only occurred in some parts of the world. |
|
|
| This issue has been resolved. When the channel has been encoded as a channel |
|
|
| map, the log message now displays one of the following: |
|
|
| ■ a channel number if only one channel is encoded (the most common case), or |
|
|
| ■ the entire channel map in decimal format if more than one channel is |
|
|
| encoded, for example: |
|
|
| 28 11:51:21 3 ICC CALL UP ISDN call ACTIVE, direction IN , channel map 12. |
|
|
|
|
AR44x / AR450 | AR7x5 | AR750S | Rapier i | ||||||
Y | Y | Y | Y | - | - | - | - | - | - |
|
|
|
|
|
|
|
|
|
|
Version