Motorola 49901 Software Release Notes - Page 43

RX_MAX_FIRST_DIGIT., Exception Encountered error.

Page 43 highlights

Software Improvements Part No. T0001-42, Rev C October, 2002 Page 43 of 103 Change Request (CR#) 11600 11600 11609 11612 11623 11628 11633 11636 11639 11642 Limitation Number DRFaa20291 DRFaa20353 DRFaa20320 DRFaa20332 DRFaa20506 DRFaa20368 DRFaa20403 DRFaa20400 DRFaa20405 DRCaa23278 Release Where Problem Was Reported 6.0.S100 6.0.P02A 6.0.S100 6.0.R00A 6.0.P02A 6.0.R00A 6.0.T02A 5.6.T2GA 6.0.T12A 6.0.S100 Interim Patch Release Replaced by Release 6.1 6.0.T19B 6.0.T19B N/A 6.0.T1AA N/A N/A 6.0.T15B N/A 6.0.T12B 6.0.T1EA Problem Description Vanguard 6400 Node crashed with FAULT: invalid semaphore. Vanguard 7300 Series Mishandling of incoming UPDATE messages when peer has become inactive. Vanguard 7300 On Net Proxy configuration causing node to continually reset. Vanguard 7300 Series LCON MIB correction needed for Entuity compatibility. Vanguard 7300 Series cannot access the node through IP when the CPU is running at one hundred percent. Vanguard 6400 Series Unable to make ATPAD to ATPAD calls after upgrading. Vanguard 320 is unable to run two TCOP ports. The node reports "Insufficient Ram for Configuration". Vanguard 6400 Series When a call comes into an E1 port configured as Q.Sig and the "Called Party Address" contains more than 17 digits, the called number is not recognized and the VG rejects the call as "RX_MAX_FIRST_DIGIT". Vanguard 6400 Series Node crash, FAULT: Program Exception Encountered error. Vanguard 6455 node crash caused by an attempt to register a ISDN socket without ISDN software loaded.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103

Part No. T0001-42, Rev C
October, 2002
Software Improvements
Page 43 of 103
11600
DRFaa20291
6.0.S100
6.0.T19B
Vanguard 6400 Node crashed
with FAULT: invalid semaphore.
11600
DRFaa20353
6.0.P02A
6.0.T19B
Vanguard 7300 Series
Mishandling of incoming
UPDATE messages when peer
has become inactive.
11609
DRFaa20320
6.0.S100
N/A
Vanguard 7300 On Net Proxy
configuration causing node to
continually reset.
11612
DRFaa20332
6.0.R00A
6.0.T1AA
Vanguard 7300 Series LCON
MIB correction needed for
Entuity compatibility.
11623
DRFaa20506
6.0.P02A
N/A
Vanguard 7300 Series cannot
access the node through IP when
the CPU is running at one
hundred percent.
11628
DRFaa20368
6.0.R00A
N/A
Vanguard 6400 Series Unable to
makeATPAD to ATPAD calls
after upgrading.
11633
DRFaa20403
6.0.T02A
6.0.T15B
Vanguard 320
is unable to run
two TCOP ports. The node
reports “Insufficient Ram for
Configuration”.
11636
DRFaa20400
5.6.T2GA
N/A
Vanguard 6400 Series
When a
call comes into an E1 port
configured as Q.Sig and the
“Called Party Address”
contains more than 17 digits,
the called number is not
recognized and the VG rejects
the call as
“RX_MAX_FIRST_DIGIT”.
11639
DRFaa20405
6.0.T12A
6.0.T12B
Vanguard 6400 Series
Node
crash, FAULT: Program
Exception Encountered error.
11642
DRCaa23278
6.0.S100
6.0.T1EA
Vanguard 6455
node crash
caused by an attempt to
register a ISDN socket without
ISDN software loaded.
Change
Request
(CR#)
Limitation
Number
Release Where
Problem Was
Reported
Interim Patch
Release
Replaced by
Release 6.1
Problem Description