019-SW

LUCENT TECHNOLOGIES - BRASIL
BZ5000 LOCAL EXCHANGE SOFTWARE FOR UCP96058C AND

UCP99050A
SOFTWARE
109253856-SW
Approved by: Eugênio Lopes Daher 06/29/06

FITec Date
Elaborated by: Marcelo Correia Afonso 06/29/06
FITec Date
Lucent Technologies – Proprietary

Use Pursuant to Company Instructions
SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 1/1

Index
1. PRESENTATION ......................................................................................................................................11
2. PRODUCT HISTORY INFORMATION..................................................................................................11

2.1 REVISION: 001 – SOFTWARE UPDATE: -...................................................................................................13
2.1.1 Updates ..........................................................................................................................................13
2.1.1.1 DR 4159 - New feature: Call Interception Service – CIS (SIC)............................................................... 13
2.1.1.2 DR 4385 – Time stamp on alarms ......................................................................................................... 13
2.1.1.3 DR 4386 – Filter to show off-hook subscribers with command IT-SUB (IT-ASS)................................... 13
2.1.1.4 DR 4080 - Corrections in ANI procedure used in Ukraine...................................................................... 13
2.1.1.5 DR 4080 - Corrections in internetworking for Ukraine signaling............................................................ 13
2.1.1.6 DR 4080 - Corrections in the exhibition of A subscriber number in Caller ID for incoming calls using
Ukraine signaling.................................................................................................................................. 13
2.1.1.7 DR 4080 - New parameter CAS for trunks interfaces to indicate bit inversion of signaling channel ........ 13
2.1.1.8 DR 4080 - Corrections in the use of ANIREQ parameter of routes ......................................................... 14
2.1.1.9 DR 4430 - Call Forward Problems......................................................................................................... 14
2.1.1.10 DR 4176 - DDC blocking for PRI/ISDN subscribers .............................................................................. 14
2.1.1.11 DR 4176 - Increased the number of units that can have options of the same CPCT group ....................... 14
2.1.1.12 DR 4176 - Increased the maximum incoming and outgoing calls processed by one unit .......................... 14
2.1.1.13 DR 4176 - Updated Trillium stack......................................................................................................... 14
2.1.1.14 DR 4176 - Corrections in call release for ISDN subscribers ................................................................... 14
2.1.1.15 DR 4176 - Decreased time for MAP initialization.................................................................................. 14
2.1.1.16 DR 4176 - Corrected the unit reset due to PRI/ISDN physical level failures ........................................... 14
2.1.1.17 Corrections in command for trunk creation ............................................................................................ 14
2.1.1.18 CPCT group programming without subscribers in BLK (BLT) operating status...................................... 14
2.1.1.19 Fixed problems in query command for synchronism clock...................................................................... 14
2.1.1.20 New country: Greece ............................................................................................................................. 15
2.1.1.21 Corrections in failures supervision for trunks......................................................................................... 15
2.1.1.22 Changes in default values of synchronism mesh parameters ................................................................... 15
2.1.1.23 Changes in routes programming for outgoing trunks with Ukraine signaling .......................................... 15
2.1.1.24 Increased the kernel heap memory......................................................................................................... 15
2.1.1.25 PR13700 – SS password managed by the subscriber .............................................................................. 15
2.1.1.26 PR15000 – EBT service 102.................................................................................................................. 15
2.1.2 Remarks..........................................................................................................................................15
2.2 REVISION: 001 – SOFTWARE UPDATE : 001 .............................................................................................15
2.2.1 Updates ..........................................................................................................................................15
2.2.1.1 Colombia’s private version released ...................................................................................................... 15
2.2.2 Remarks..........................................................................................................................................15
2.3 REVISION: 002 – SOFTWARE UPDATE : -..................................................................................................16
2.3.1 Updates ..........................................................................................................................................16
2.3.1.1 Remote Alarm Indication (RAI) been sent by switch .............................................................................. 16
2.3.1.2 DR 4473 - Problems on calls with subscribers on busy state – Bolivia ................................................... 16
2.3.1.3 Semi-Permanent Switching.................................................................................................................... 16
2.3.1.4 DR4000 - ISDN for interface V5.2 (PR 8200)........................................................................................ 16
2.3.1.5 DR 4365 - Black List (PR 14900).......................................................................................................... 17
2.3.1.6 DR 4472 - Switch continuously reset ..................................................................................................... 17
2.3.2 Remarks..........................................................................................................................................17
2.4.1 Updates ..........................................................................................................................................17
2.4.1.1 DR 4772 – Number of senders Bina FSK change for 2........................................................................... 17
2.4.2 Remarks..........................................................................................................................................18
2.5.1 Updates ..........................................................................................................................................18
2.5.1.1 DR 4772 – Belize problem (HIGH PITCH TONE) – Bina FSK.............................................................. 18
2.5.2 Remarks..........................................................................................................................................18
2.6.1 Updates ..........................................................................................................................................18
2.6.1.1 COP-ORP command has been changed to not allow copy to the activated Originating Traffic Routing Plan
............................................................................................................................................................. 18
2.6.1.2 DR 4456 - Alarm in SS7 signaling route................................................................................................ 18
2.6.1.3 DR 4000 - ISDN for interface V5.2 ....................................................................................................... 18
2.6.1.4 DR 4000 - Problems in programming MSN for remote BRI subscribers ................................................. 18
2.6.1.5 DR 4529 – Increasing the number of Direct Line Supplementary Service ............................................... 18
2.6.1.6 DR 4464 – Programmable EOS (PR 2100) ............................................................................................ 19
2.6.1.7 DR 4484 – DDI calls routing problem ................................................................................................... 19
2.6.1.8 DR 4496 – ISDN Incoming calls in overlap mode (PR 19000) ............................................................... 19
2.6.1.9 ISUP Calls dropped in routes with the DGE parameter defined.............................................................. 19
2.6.1.10 New CDR format for the Philippines ..................................................................................................... 19
2.6.1.11 DR 4475 - New country: Guatemala ...................................................................................................... 19
2.6.1.12 Fixed the packing of the ISUP parameters 'Call reference' and 'Generic Digits'....................................... 19
2.6.1.13 DR 4321 – Argentine SS7 Standard Implementation for POTS (PR 13800)............................................ 19
2.6.1.14 DR 4483 – Line hunting group provisioning problem............................................................................. 20
2.6.1.15 Problems in V5 audio terminal creation ................................................................................................. 20
2.6.1.16 Problems in dial pulsing processing....................................................................................................... 20
2.6.1.17 DR 4528 – Voice mails sent by MAX TNT are not heard ...................................................................... 20
2.6.1.18 DR 4179 – Hardlock ............................................................................................................................. 20
2.6.1.19 DR 4447 – Dial pulsing in CSR alarm call ............................................................................................ 20
2.6.1.20 DR 4223 – Call distribution in PABX feature failure............................................................................. 20
2.6.1.21 DR 4465 – Absent Subscriber Service (PR02200) ................................................................................. 21
2.6.1.22 DR 4222 – Corrections in IT LSS command processing ......................................................................... 21
2.6.1.23 DR 4444 – Corrections in IT SLIDTR command processing................................................................... 21
2.6.2 Remarks..........................................................................................................................................21
2.7 REVISION: 003 – SOFTWARE UPDATE: 001 ..............................................................................................21
2.7.1 Updates ..........................................................................................................................................21
2.7.1.1 DR 4596 Increase in the number of BBB’s per route.............................................................................. 21
2.7.1.2 Automatic command been sent to block the other side of a trunk which have all the circuits blocked in
some way.............................................................................................................................................. 21
2.7.1.3 Time to check all the circuits in the switch changed............................................................................... 21
2.7.1.4 Cause’s value changed to 44 in case of a ISUP’s call been finished because of a failure in second level in
primary access....................................................................................................................................... 21
2.7.1.5 DR 4472 - Switch continuously reset every time .................................................................................... 21
2.7.1.6 DR 4472 - Problem in cause’s value translation in tandem calls............................................................. 21
2.7.2 Remarks..........................................................................................................................................22
2.8.1 Updates ..........................................................................................................................................22
2.8.1.1 DR 4622 – Fault in R2D/ISUP interworking when tandem call receives ACM message without indication
in outgoing trunk................................................................................................................................... 22
2.8.1.2 DR 4624 - Fault in the second choice of synchronism reference ............................................................. 22
2.8.1.3 DR 4627 -Field 33 in AMA147record was filled with “/” (slash) signal................................................. 22
2.8.1.4 DR 4623 - TUP adaptation to Philippines: new backward message for blocked or lockout subscriber ..... 22
2.8.2 Remarks..........................................................................................................................................22
2.9.1 Updates ..........................................................................................................................................22
2.9.1.1 DR 4321 - Argentine SS7 Standard Implementation for POTS (PR13800) ............................................. 22
2.9.1.2 DR 4487 - DTMF C tone for Greece (PR17600) .................................................................................... 23
2.9.1.3 DR 4467 - Remote Programming (PR2600) ........................................................................................... 23
2.9.1.4 DR 4531 - Traffic Generating Fail in the Relsup tool............................................................................. 24
2.9.1.5 Inconsistent data in long duration calls registering................................................................................. 24
2.9.1.6 ISDN subscriber been created in an instance already used ..................................................................... 24
2.9.1.7 DR 4647 - R2 adaptation for Indonesia Field Trial................................................................................. 24
2.9.1.8 DR 4630 - Pending Requirements Anatel Certification .......................................................................... 24
2.9.1.9 DR 4000 - ISDN for interface V5.2 ...................................................................................................... 24
2.9.1.10 COM2 in configuration mode ................................................................................................................ 25
2.9.1.11 Suppression of signaling link reporting “Invalid CIC” for different routes .............................................. 25
2.9.1.12 DR 4627 – Field 33 of the AMA147 records with a wrong character...................................................... 25

2.9.1.13 DR 4652 - Dual Stage call, using ISDN signaling .................................................................................. 25
2.9.1.14 DR4622 – ISUP/MFC interworking fault............................................................................................... 25
2.9.1.15 DR 4623 – TUP for the Philippines ....................................................................................................... 25
2.9.1.16 DR 4572 – Call restriction with RTT=DDC........................................................................................... 25
2.9.1.17 DR 4617 – PRI non expected alarms ..................................................................................................... 25
2.9.1.18 DR 4639 – R2/PRI interworking............................................................................................................ 25
2.9.1.19 DR 4624 – Fault in the election of the external clock references ............................................................ 26
2.9.1.20 DR 4004 – Software to enable Circuit Packs with 02 E1s and 02 MAPs (PR 09200).............................. 26
2.9.2 Remarks..........................................................................................................................................26
2.10.1 Updates ..........................................................................................................................................26
2.10.1.1 Pre paid feature enabled ........................................................................................................................ 26
2.10.2 Remarks..........................................................................................................................................26
2.11.1 Updates ..........................................................................................................................................26
2.11.1.1 DR 4630 – Pending Requirements Anatel Certification.......................................................................... 26
2.11.1.2 DR4709 - Fault in R2D/ISUP interworking when tandem call receives an ANM before terminates the
R2D signaling in the incoming trunk ..................................................................................................... 26
2.11.2 Remarks..........................................................................................................................................27
2.12.1 Updates ..........................................................................................................................................27
2.12.1.1 DR 4336 – LAN’s RTL driver more efficient......................................................................................... 27
2.12.1.2 DR 4666 – Hardware Key for Billing Unit............................................................................................. 27
2.12.1.3 DR 4179 – Hardware Key for Redundancy ............................................................................................ 27
2.12.1.4 DR 4647 – V5.2 and SS7 adaptations for Indonesia (PR 20200) ............................................................ 27
2.12.1.5 DR 4683 – How to adjust a T3 timer for ANI procedure on DP2............................................................ 28
2.12.1.6 DR 4760 – BZ5000 certification – gaps pause in ANI packet. ................................................................ 28
2.12.1.7 DR 4685 – CLIRP / CLIRO supplementary services for POTS subscriber (PR 24800)............................ 28
2.12.1.8 DR 4761 – Command IT-ESCTRD is presenting different values when is used as IT-ESCTRD
PLACA=XX-XX ................................................................................................................................... 28
2.12.1.9 DR 4652 – Dual Stage call, using ISDN signaling, is not working because the BZ5000 is not opening the
TX path................................................................................................................................................. 28
2.12.1.10 PR26900 – The MCB (B code matrix) may be treatment using the NOA (nature of address) parameter
presented in the IAM message............................................................................................................... 28
2.12.1.11 DR 4771 – Corrections in status parameter for CGUA and CGBA messages .......................................... 29
2.12.1.12 DR 4615 – Problems in SS7 trunks interface creation with exchange in operational state ....................... 29
2.12.1.13 DR4667 – Fails in the voice channel in DDR with extension blocked for collect calls ............................ 29
2.12.1.14 Corrections in suppression of V5 and SS7 signalling links ..................................................................... 29
2.12.1.15 DR4589 – ISDN Primary Access does not activate after the switch reset ................................................ 29
2.12.1.16 PR 22300 – TUP IAM handling for Philippines ..................................................................................... 29
2.12.1.17 Number of senders Bina FSK change for 2............................................................................................. 29
2.12.2 Remarks..........................................................................................................................................29
2.13.1 Updates ..........................................................................................................................................29
2.13.1.1 DR 4707 – Problems in calls from ISUP to ISDN with overlap .............................................................. 29
2.13.1.2 DR 4778 – Problems with messages IAM and ACM for Argentina......................................................... 29
2.13.1.3 PR 28900 – Send B subscriber number for intra switch ISDN calls........................................................ 29
2.13.2 Remarks..........................................................................................................................................30
2.14.1 Updates ..........................................................................................................................................30
2.14.1.2 DR 4796 – DTMF allocation for pre-paid subscribers............................................................................ 30
2.14.1.3 DR 4811 – Fault in PRI to ISUP calls and ISUP to ISUP calls when it involves 2 BBB .......................... 30
2.14.1.4 DR 4813 – Overlap addressing is not working in ISDN route................................................................. 30
2.14.2 Remarks..........................................................................................................................................30
2.15.1 Updates ..........................................................................................................................................30

2.15.2 Remarks..........................................................................................................................................30
2.16.1 Updates ..........................................................................................................................................30
2.16.1.1 PR 31200 – BZ5000 IAM signal adaptation for Philippines SS7 ............................................................ 30
2.16.1.2 DR 4810 – SS7 IAM FEATURE - Compatibility Testing between BZ5000 and NEAX61E.................... 31
2.16.2 Remarks..........................................................................................................................................31
2.17.1 Updates ..........................................................................................................................................31
2.17.1.1 DR 4788 – Indonesia Analog Subscriber Impedance (PR 28800)............................................................ 31
2.17.1.2 DR 4789 – Indonesia Caller Identification (PR 28800) .......................................................................... 31
2.17.1.3 DR 4799 – Frequency Pulse of 12KHz or 16KHz (PR 28800) ................................................................ 31
2.17.2 Remarks..........................................................................................................................................31
2.18.1 Updates ..........................................................................................................................................31
2.18.1.1 DR 4777 – Need to get setting for DTMF frequencies and codes (PR 29000)........................................ 31
2.18.1.2 DR 4793 – Need to change the procedure for Abbreviated Dialing feature (PR 29000) ......................... 32
2.18.1.3 DR 4794 – Need to change the subscriber use of call waiting and 3-party conference (PR 29000) ......... 32
2.18.2 Remarks..........................................................................................................................................32
2.19.1 Updates ..........................................................................................................................................32
2.19.1.1 DR 4686 – Supplementary Services for Belize (PR 16200) .................................................................... 32
2.19.1.2 DR 4795 – Indonesia modifications - Outgoing Call Baring (PR 29100) ................................................ 34
2.19.1.3 DR 4798 – Announcement Capacity (PR 29100).................................................................................... 34
2.19.1.4 PR 29100 – Configurable tolerance for DTMF frequencies detection ..................................................... 34
2.19.1.5 PR 29700 – Indonesia modifications – Lockout Situation....................................................................... 34
2.19.1.6 PR 29900 – Indonesia modifications – Loop Closed Seizure Timers....................................................... 34
2.19.1.7 DR 4812 – Problem BINA FSK enabled with V5.2 users (PR 31900) .................................................... 34
2.19.1.8 Units suppression with boards created ................................................................................................... 35
2.19.1.9 DR 4808 – Internal MTP failure cod=07................................................................................................ 35
2.19.1.10 -Call Interception System – Ukraine....................................................................................................... 35
2.19.1.11 DR 4772 – Belize problem (HIGH PITCH TONE) – Bina FSK .............................................................. 35
2.19.1.12 DR 4816 – Problems with CCS#7 (national indicator) ........................................................................... 35
2.19.1.13 DR4781 / DR 4799 – Increased the accuracy of 12/16kHz and polarity inversion pulses ......................... 35
2.19.2 Remarks..........................................................................................................................................35
2.20.1 Updates ..........................................................................................................................................35
2.20.2 Remarks..........................................................................................................................................35
2.21.1 Updates ..........................................................................................................................................36
2.21.1.1 DR 4832 – Establishing incoming calls problem on BZ5000.................................................................. 36
2.21.1.2 DR 4834 - Dual Stage from POTS subscribers....................................................................................... 36
2.21.2 Remarks..........................................................................................................................................36
2.22.1 Updates ..........................................................................................................................................36
2.22.1.1 PR 26200 - CIS for Russia (with black box) - Phase 1 ........................................................................... 36
2.22.1.2 PR 33200 - Indosat Tender PxP analysis and 2 Ni THY estimate ........................................................... 36
2.22.1.3 DR 4829 (AR 1-0843402) – Only first ISDN port can get dial tone – AR 1-0843402.............................. 36
2.22.1.4 DR 4833 (AR 1-0823295) - Unexpected cause value received by Called ................................................ 36
2.22.1.5 Error in the IAM message on transit calls with transfer parameter ......................................................... 36
2.22.1.6 DR 4835 (AR 1-0845827) - Error operation on the COLP service .......................................................... 37
2.22.1.7 DR 4825 (AR 1-0823310) -Screening Indicator ..................................................................................... 37
2.22.1.8 Different check sums of the switch after creating or suppressing a V5 interface. .................................... 37
2.22.1.9 Message CRG (charging) with wrong handling...................................................................................... 37
2.22.1.10 DR 4798 (AR 1-0783697) – Announcement Capacity (PR 29100).......................................................... 37
2.22.2 Remarks..........................................................................................................................................37
2.23.1 Updates ..........................................................................................................................................37
2.23.1.1 DR 4782 (AR 1-0784610) MF signals duration ..................................................................................... 37
2.24.1 Updates ..........................................................................................................................................38
2.24.1.1 PR 30800 (AR 1-0804756) BZ5000 ISDN Protection over V5.2 ............................................................ 38
2.24.1.2 DR 4852 (AR 1-0911425) CPU does not detect the Hardware key ......................................................... 38
2.24.1.3 DR 4839 (AR 1-0824937) Correction of INF message when the caller subscriber is programmed with
CLIRP service ....................................................................................................................................... 38
2.24.2 Remarks..........................................................................................................................................38
2.25.1 Updates ..........................................................................................................................................38
2.25.1.1 DR 4848 – Problems with double call control tone in BZ5000. .............................................................. 38
2.25.2 Updates ..........................................................................................................................................39
2.25.2.1 DR 4863 – Problems with Overlap with the BZ5000 under Inter-working ISUP/PRI.............................. 39
2.25.3 Updates ..........................................................................................................................................39
2.25.3.1 DR 4870 - ABCD bit for E&Mp line signaling not comply with Indonesian ........................................... 39
2.25.4 Remarks..........................................................................................................................................39
2.26.1 Updates ..........................................................................................................................................39
2.26.1.1 PR 28700 - ISDN CUG for Indonesia .................................................................................................... 39
2.26.1.2 PR 29300 - Call Hold and CLIP FSK..................................................................................................... 39
2.26.1.3 PR 31200 – BZ5000 IAM signal adaptation for Philippines SS7 ............................................................ 39
2.26.1.4 DR 4803(AR 1-0790370) - Line Test fail with parameter TYP=RES ..................................................... 39
2.26.1.5 DR 4826 (AR 1-0825253) - BZ5000 doesn't send I-15 signal at the end of call....................................... 40
2.26.1.6 DR 4833 (AR 1-0823295) - Unexpected cause value in ISDN calls........................................................ 40
2.26.1.7 DR 4836 (AR: 1-0845828) - Error in mapping sub-address from ISDN-CONN message to ISUP-ANM.. 40
2.26.1.8 DR 4842 (AR 1-0893364) - Problems with "Call Waiting" Supplementary Service ................................ 40
2.26.1.9 DR 4851 (AR 1-0895263) - Problems with transfer services .................................................................. 40
2.26.1.10 DR 4855 - V5ISDN - Answer to the command IT SUB RMT when it has MSN programmed. ................ 40
2.26.1.11 DR 4856 - V5ISDN - Remote BRI subscriber creation with high RMT number ...................................... 40
2.26.1.12 DR 4857 - V5ISDN – Command IT INT SUB doesn't work for remote BRI subscribers.......................... 40
2.26.1.13 DR 4858 – Answer to the command IT-V5LNK is incorrect for ISDN c-channel..................................... 40
2.26.1.14 DR 4859 – Fail in the V5 interface provisioning .................................................................................... 40
2.26.1.15 DR 4864 - V5ISDN - Creation and suppression of remote BRI subscriber during tentative of establishing
calls ...................................................................................................................................................... 41
2.26.1.16 DR 4868 (AR 1-0934817) - CIS - CIC Number is not present in CAD.................................................... 41
2.26.1.17 DR 4869 (AR 1-0934837) - CIS – Invalid Intercepted-Call-Direct values ............................................... 41
2.26.1.18 DR 4877 (AR 1-0946449) – Invalid value in the charge indicator field of the ACM ISUP message in
transferred calls..................................................................................................................................... 41
2.26.1.19 DR 4878 (AR 1-0946404) - The switch is resetting when receives an IAM message with the parameter
UUS and length equals to zero............................................................................................................... 41
2.26.1.20 DR 4881 - Problem in tandem ISDN calls .............................................................................................. 41
2.26.1.21 The Call Waiting programming was inhibited for ISDN subscribers. ...................................................... 41
2.26.1.22 Noise in the Announcement Machine..................................................................................................... 41
2.26.1.23 V5TMP9 and V5TMP10 default values changed.................................................................................... 41
2.26.1.24 Increase in CPU load during ISDN calls................................................................................................. 41
2.26.1.25 B-Channel Groups for ISDN-PRI interface was not working................................................................... 42
2.26.1.26 ISDN PRI call losses.............................................................................................................................. 42
2.26.1.27 Command MD-SUB generates different checksum of configuration data among units............................. 42
2.26.1.28 Problems with creation of MPS-C board with one and two links............................................................. 42
2.26.1.29 Command AT-SUPCHA does not show CPU load in a TCP/IP connection ............................................. 42
2.26.2 Remarks..........................................................................................................................................42
2.27.1 Updates ..........................................................................................................................................42
2.27.1.1 DR 4885 (AR 1-0950829) - Problem in ANI number inversion .............................................................. 42
2.27.1.2 DR 4889 (AR 1-0954868) - Incorrect Redirecting Number call forwarded.............................................. 42
2.27.1.3 DR 4870 (AR 1-0931593) – ABCD bits for E&Mp line signaling not comply with Indonesian............... 43
2.27.2 Remarks..........................................................................................................................................43
2.28.1 Updates ..........................................................................................................................................43
2.28.1.1 PR 14000 – Software driver implementation for RMTL Circuit Pack ..................................................... 43
2.28.1.2 DR 4872 - B-Code Matrix is not working for calls originated to DDRI routes ....................................... 43
2.28.1.3 DR 4876 (AR 1-0946452) - Problems with transfer calls when number of digits is less than starting index
............................................................................................................................................................. 43
2.28.1.4 DR 4886 (AR 1-0951729) - The outgoing ISDN calls are not being completed for countries that use I-15
signal (End of Number) ......................................................................................................................... 43
2.28.1.5 DR 4888 (AR 1-0954842) - CN (Connected Number) is showing the wrong number............................. 44
2.28.1.6 Caller ID service fails when an incoming call from a MFC signaling route is transferred to another
subscriber into the same switch ............................................................................................................. 44
2.28.1.7 Incorrect ring cadence in subscriber programmed with FSK Caller ID.................................................... 44
2.28.2 Remarks..........................................................................................................................................44
2.29.1 Updates ..........................................................................................................................................44
2.29.1.1 DR 4887 (AR 1-0951709) - Outgoing calls for the countries that use end of number signal were not being
completed for second choice route ......................................................................................................... 44
2.29.1.2 DR 4891 (AR 1-0955944) - Connected Number always showed in ANM message ................................. 44
2.29.1.3 DR 4894 (AR 1-0954842) - Connected Number in ANM message should be sent only when requested.. 44
2.29.1.4 DR 4898 (AR 1-0961298) - Corrections in the ANI protocol .................................................................. 44
2.29.1.5 DR 4900 - Configuration of the Area Code presence in Redirecting Number.......................................... 45
2.29.1.6 Problems with the CLIRO supplementary service .................................................................................. 45
2.29.2 Remarks..........................................................................................................................................45
2.30.1 Updates ..........................................................................................................................................45
2.30.1.1 DR 4840 – LAN driver and Boot Loader adaptation to use the Encore Ethernet Card ............................. 45
2.30.1.2 DR 4905 (AR 1-0959729) - Question about compliance with Q.764 for outgoing calls (TAM=4) ........... 45
2.30.1.3 DR 4911 - Charging problems for configured country as Argentina........................................................ 45
2.30.1.4 DR 4916 (AR 1-0995307) - Incorrect call release procedure on SLM trunks .......................................... 45
2.30.2 Remarks..........................................................................................................................................46
2.31.1 Updates ..........................................................................................................................................46
2.31.1.1 PR 35700 – Removal of all CIS related information.............................................................................. 46
2.31.1.2 PR 44800 – Operator Break In via ISUP Trunks .................................................................................... 46
2.31.1.3 PR 45000 – CCL message implementation for Russian.......................................................................... 46
2.31.2 Remarks..........................................................................................................................................46
2.32.1 Updates ..........................................................................................................................................46
2.32.1.1 PR 33800 – Call Interception System with Supplementary Services interaction for Russian .................. 46
2.32.1.2 PR 43900 – Russian Country ID Creation ............................................................................................. 46
2.32.1.3 PR 44600 – Disconnection Reasons for Russian LEMF ........................................................................ 46
2.32.1.4 DR 4928 (AR 1-1003785) – Problem with Redirection Service.............................................................. 46
2.32.1.5 DR 4938 (AR 1-1013043) – Switch was resetting when a SEQ and SEQ2 parameters of SEL had the same
values ................................................................................................................................................... 47
2.32.1.6 DR 4949 (AR 1-1003785) – The calling party category is not being correctly sent for Ukraine in
forwarding calls .................................................................................................................................... 47
2.32.1.7 DR 4978 (AR 1-1025831) – Called number info is missing in ASN message ......................................... 47
2.32.2 Remarks..........................................................................................................................................47
2.33 REVISION: 011 – SOFTWARE UPDATE: -001.............................................................................................47
2.33.1 Updates ..........................................................................................................................................47
2.33.1.1 DR 4958 (AR 1-1025900) - Problems receiving A6 signal working as a transit exchange with R2 signaling
............................................................................................................................................................. 47
2.33.1.2 DR 4980 (AR 1-1035600) - Original Called Number field is not correct ................................................ 47
2.33.2 Remarks..........................................................................................................................................48
2.34 REVISION: 012 – SOFTWARE UPDATE:.....................................................................................................48
2.34.1 Updates ..........................................................................................................................................48
2.34.1.1 PR 41200 - ANI Extension for CIS countries ......................................................................................... 48
2.34.1.2 PR 44400 - Modification in CDR for Russia market ............................................................................ 48
2.34.1.3 PR 44700 - Target Priority For CIS Russia* .......................................................................................... 48
2.34.1.4 DR 4914 - Modem PCI card driver implementation ............................................................................... 49
2.34.1.5 DR 4924 (AR 1-1016189) - Problems with calling address displaying in R2D signaling for Argentina .. 49
2.34.1.6 DR 4959 (AR 1-1016206) – Problem in transferring of calls when the number of digits is less than the
start index ............................................................................................................................................. 49

2.34.1.7 DR 4960 (AR 1-1029695) - The connected number is displayed with 0xA instead of 0x0 ...................... 49
2.34.1.8 DR 4961 (AR 1-1029703) - The redirecting number is displayed with 0xA instead of 0x0 ..................... 49
2.34.1.9 DR 5019 (AR 1-1058090) - No ASN messages for target subscribers.................................................... 49
2.34.2 Remarks..........................................................................................................................................49
2.35 REVISION: 013 – SOFTWARE UPDATE:.....................................................................................................49
2.35.1 Updates ..........................................................................................................................................49
2.35.1.1 PR 43000 – Calling Line Identification Presentation (CLIP) service for Philippines ............................... 49
2.35.1.2 PR 43200 – Calling Line Identification Presentation (CLIP) service for Philippines ............................... 50
2.35.1.3 PR 48100 (AR 1-0996637) – Remove the category of subscriber A in the caller ID for Argentina........... 50
2.35.1.4 PR 52000 - ANN after the ACM message.............................................................................................. 50
2.35.1.5 DR 4929 (AR 1-0961400) - The time slot information (CIC) is not being populated in the CAD register
for R2 signaling..................................................................................................................................... 50
2.35.1.6 DR 4951 – Error in the CLKTYP parameter in command MD-SYNCOPP ............................................. 50
2.35.1.7 DR 4963 (AR 1-1014284) - Problems on special local services .............................................................. 50
2.35.1.8 DR 5015 (AR 1-1057011) - Problems with multiple transfers ............................................................... 50
2.35.1.9 DR 5016 (AR 1-1058116) - Wrong charging on SEL services ................................................................ 50
2.35.2 Remarks..........................................................................................................................................50
2.36 REVISION: 014– SOFTWARE UPDATE: .....................................................................................................51
2.36.1 Updates ..........................................................................................................................................51
2.36.1.1 PR 44500 - Deferred Charging Timer for Russia market ........................................................................ 51
2.36.1.2 DR 5003 (AR 1-1049252) - NPUL parameter is not working correctly................................................... 51
2.36.1.3 DR 5005 (AR 1-1055466) - Redirecting Information with wrong fields.................................................. 51
2.36.1.4 DR 5020 (AR 1-1029715) - Problems with SS7 link uninhibition .......................................................... 51
2.36.1.5 Wrong message in HSTCEN log for GR-MSGDSP and COP-MSGDSP commands................................ 51
2.36.1.6 CDR – Russia – Wrong code for subscriber password programming service........................................... 51
2.36.2 Remarks..........................................................................................................................................51
2.37.1 Updates ..........................................................................................................................................52
2.37.1.1 DR 4901 - Call Hold – Switch doesn’t send message hold and retrieval reject while subscriber B is
ringing. ................................................................................................................................................. 52
2.37.1.2 DR 4902 - Call Hold – CPG message of the protocol ISUP was not been sending .................................. 52
2.37.1.3 DR 4903 – Call Hold – Problem with 3 ISDN terminals are plugged in only one BRI access point ......... 52
2.37.1.4 Wrong billing record for the “Do Not Disturb” service........................................................................... 52
2.37.1.5 The forwarded call (initial leg) was not been billed in incoming call...................................................... 52
2.37.2 Remarks..........................................................................................................................................52
2.38 REVISION: 015– SOFTWARE UPDATE: 001...............................................................................................52
2.38.1 Updates ..........................................................................................................................................52
2.38.1.1 DR 5086 - Overlap is not working when more than 16 digits are received.............................................. 52
2.38.1.2 DR 5087 - The NOA of the calling party address is incorrect for international transit call ...................... 53
2.38.2 Remarks..........................................................................................................................................53
2.39.1 Updates ..........................................................................................................................................53
2.39.1.1 PR48000 (AR 1-1018766) – MCT over CAS signaling for Russia Market.............................................. 53
2.39.1.2 DR 4867 - Problems with V5 interface .................................................................................................. 53
2.39.1.3 DR 5093 – The OCN in the IAM message was incorrect for Bolivian market......................................... 53
2.39.2 Remarks..........................................................................................................................................54
2.40.1 Updates ..........................................................................................................................................54
2.40.1.1 DR 5080 (AR 1-1075937) - CIS. Dialled digits in ASN messages.......................................................... 54
2.40.1.2 DR 5094 (AR 1-1130803) - Interworking problem in signalings MFSH ................................................. 54
2.40.1.3 DR 5095 (AR 1-1140655) - R2D -> ISUP interworking problem ........................................................... 54
2.40.1.4 DR 5116 (AR 1-1117372 - Problem in International collected calls........................................................ 54
2.40.2 Remarks..........................................................................................................................................54
2.41.1 Updates ..........................................................................................................................................54
2.41.1.1 DR 5102 (AR 1-1142191) – MF-Shuttle signals B1, B2 and B3 can not be programmable..................... 55
2.41.1.2 DR 5120 (AR 1-1150012) – SS7->DP1/RTR interworking does not work.............................................. 55
2.41.1.3 DR 5130 (AR 1-1166295) – Problem with MFSH->DP1 interworking................................................... 55
2.41.1.4 DR 5133 (AR 1-1140655) – R2D -> ISUP interworking problem........................................................... 55
2.41.1.5 DR 5138 (AR 1-1190523) – MCTP service cannot be assigned if country=RUS..................................... 55
2.41.1.6 DR 5139 (AR 1-1190520) – R2D routing to SS7 billing problem........................................................... 55
2.41.2 Remarks..........................................................................................................................................55
2.42.1 Updates ..........................................................................................................................................55
2.42.1.1 DR 5150 (AR 1-1217051) – MCT calling party number field................................................................. 55
2.42.1.2 DR 5151 (AR 1-1219501) – Incorrect subscriber category mapping for R2/ISUP.................................... 55
2.42.2 Remarks..........................................................................................................................................56
2.43 REVISION:017 – SOFTWARE UPDATE: - ...................................................................................................56
2.43.1 Updates ..........................................................................................................................................56
2.43.1.1 DR 5143 (AR 1-1198366) - Trunk disconnection procedure error on RTL and RTR trunks with DP1
Signalling.............................................................................................................................................. 56
2.43.1.2 DR 5149 (AR 1-1210612) - BZ5000 unblocks previously blocked trunks after an ISUP incoming test call.
............................................................................................................................................................. 56
2.43.1.3 DR 5156 (AR 1-1219490) - R2-MFSH interworking fail ....................................................................... 56
2.43.1.4 DR 5157 (AR 1-1230678) - R2D-DP1 interworking fail ........................................................................ 56
2.43.1.5 DR 5158 (AR 1-1233773) DP1 trunk left in SRV BLE status after finishing the call.............................. 56
2.43.1.6 DR 5166 (AR 1-1245447) – Fail when creating a V5.2 link with SLC equals to 0................................. 56
2.43.1.7 CLIRP fail when calling from a POTS subscriber to PRI or BRI subscriber........................................... 56
2.43.1.8 Blocked Trunk by TMR/AHT fail being alocated in SS7 calls............................................................... 56
2.43.1.9 The “address presentation restricted indicator” not treated correctly in interworking call, when the
outgoing call uses R2D signaling. .......................................................................................................... 56
2.43.1.10 Fail in CR-SUB command creating BRI subscribers in MAP2’s secondary trunk................................... 57
2.43.1.11 Fail in CR-SUB command when creating more than 144 BRI subscribers............................................. 57
2.43.1.12 When creating two trunks with route DP1 separeted with “&”, the second trink is created with CIC=31 57
2.43.2 Remarks..........................................................................................................................................57
2.44 REVISION:017 – SOFTWARE UPDATE: 001...............................................................................................57
2.44.1 Updates ..........................................................................................................................................57
2.44.1.1 DR 5164 - SUPSS7 for remote ISDN subscribers was not working ........................................................ 57
2.44.1.2 DR 5169 (AR 1-1252410) - The multimetering pulse cadence sent by switch to payphone was in a wrong
frequency .............................................................................................................................................. 57
2.44.1.3 DR 5181 (AR 1-1255380) - Call forwarding on busy was not working for BRI subscribers .................... 57
2.44.2 Remarks..........................................................................................................................................57
2.45.1 Updates ..........................................................................................................................................58
2.45.1.1 Corrections in OCP/BLQ led operation.................................................................................................. 58
2.45.1.2 The release cause indicatorrecorded in CDA(call data) was wrong for immediate diversion or call
diversion on busyl ................................................................................................................................. 58
2.45.1.3 Corrections in Call Waiting service ....................................................................................................... 58
2.45.1.4 DR 5186 (AR 1 –1254910) – For all outgoing calls via ISUP trunks, when B-party disconnects, BZ switch
was replying with a REL=102. .............................................................................................................. 58
2.45.1.5 DR 5171 (AR 1 –1255295) – (Russia FOA) CDR's INROUT/OUTROUT fields show wrong route values.
............................................................................................................................................................. 58
2.45.1.6 DR 5172 (AR 1 –1255297) – CDR END CAUSE field shows wrong value for calls disconnected by B-
party ..................................................................................................................................................... 58
2.45.1.7 DR 5175 (AR 1 –1255306) – For BRI subscribers, a new programming of EXELIN service by keypad is
not overriding the previous .................................................................................................................... 58
2.45.1.8 DR 5193 (AR 1 –1274868) – Problem in the "Special Service Indicator" field in AMA147 records........ 58
2.45.2 Remarks..........................................................................................................................................59
2.46.1 Binary files used at boards..............................................................................................................60
2.46.2 Updates ..........................................................................................................................................60
2.46.2.1 PR55700 - OA&M Improvements (alarms)............................................................................................ 60
2.46.2.2 PR60600 - MCTD FIXING FOR RUSSIA (AR 1-1190556), EXTEND MCT/MCTD FOR UKRAINE. .. 60
2.46.2.3 DR 5119: PR48000 - MCT in interworking mode .................................................................................. 60
2.46.2.4 DR 5205 - AR 1-1293415 - Calls to the second switch prefix are not successful..................................... 61
2.46.2.5 DR 5206 - Incorrect OCT value for test subscriber for Ethiopia ............................................................. 61
2.46.2.6 BZ5000 sends signal B7 for busy ISDN BRI subscribers in R2D incoming calls .................................... 61
2.46.2.7 Fault when creating MTL and MTLB boards without link associated..................................................... 61
2.46.2.8 Problem in the analysis of the 12 KHz signal during the MTL board test ............................................... 61
2.47.1 Updates ..........................................................................................................................................61
2.47.1.1 DR 5158 (AR 1-1233773): DP1 trunk left in SRV BLE status after finishing the call............................. 61
2.47.1.2 DR 5208 (AR 1-1297520): Announcement recording through COP-MSGDSP command is not successful.
............................................................................................................................................................. 61
2.47.1.3 Corrections on OCP/BLQ led operation ................................................................................................. 61
2.47.2 Remarks..........................................................................................................................................62
2.48.1 Updates ..........................................................................................................................................62
2.48.1.1 IT-BILHST doesn´t return an answer to BZ-VIEW................................................................................. 62
2.48.1.2 The usage percentages of the Originating Traffic Routing Plan tables are being wrongly set to zero. ...... 62
2.48.2 Remarks..........................................................................................................................................62
2.49.1 Updates ..........................................................................................................................................62
2.49.1.1 DR 5172 (AR 1-1255297): CDR's END CAUSE field shows wrong value for calls disconnected by B-part
for Russia and Ukrainey. ....................................................................................................................... 62
2.49.1.2 DR 5232: Wrong calling party number in a CPCT group........................................................................ 62
2.49.1.3 DR 5236: The SUPCHA and the SUPSS7 are losing messages. ............................................................. 62
2.49.2 Remarks..........................................................................................................................................62
2.50.1 Updates ..........................................................................................................................................63
2.50.1.1 DR 5234 (AR 1-1326334) - Some calls have crossed audio.................................................................... 63
2.50.1.2 DR 5250 (AR 1-1353810) - When abbreviated dialing service is active, calls to special services numbers
(SSN) with 2 digits number length can't be completed for Russia and Ukraine ....................................... 63
2.50.1.3 DR 5255 (AR 1-1370442) - Unrestricted Called Party Number length should be supported.................... 63
2.50.1.4 BZ5000 do not accept the TYP equal to V35 at semi-permanent connection creation. Only RS is available.
............................................................................................................................................................. 63
2.50.2 Remarks..........................................................................................................................................63
2.51.1 Updates ..........................................................................................................................................63
2.51.1.1 DR 5250 / DR 5266 (AR 1-1353810) - When abbreviated dialing service is active, calls to special services
numbers (SSN) with 2 digits number length can't be completed for Russia and Ukraine......................... 63
2.51.1.2 DR 5265 (AR 1-1400937) - The "Calling Party Category" should not be sent to "Caller ID device" at
Russia market ....................................................................................................................................... 64
2.51.1.3 DR 5259 (AR 1-1376691) - On DP1/DP2/MFSH x ISUP calls, the area code is not included at Calling
Party Number, even if programmed properly.......................................................................................... 64
2.51.1.4 DR 5248 (AR 1-1342189) - Hanging up inter and intra-module links ......................................... 64
2.51.1.5 DR 5247 (AR 1-1342133) - Sometimes DP1 trunks are left in SRV BLE state....................................... 64
2.51.1.6 DR 5237 (AR 1-1326099) Incoming DP1 toll call with incorrect ANI .................................................... 64
2.51.1.7 Fault in the incoming call routing based on CTO parameter for DP1, DP2 and MFSH signaling. ........... 65
2.51.2 Remarks..........................................................................................................................................65
2.52 REVISION:019 – SOFTWARE UPDATE: - ...................................................................................................65
2.52.1 Updates ..........................................................................................................................................65
2.52.1.1 PR64800 – Honduras Caller ID ............................................................................................................. 65
2.52.1.2 PR68400 – CDR formatting adjustments for Russia............................................................................... 65
2.52.1.3 DR 5237 (AR 1-1326099) Incoming DP1 toll call with incorrect ANI .................................................... 65
2.52.1.4 MD-TER command is not disabling the PDG and CNI parameters:........................................................ 65
2.52.2 Remarks..........................................................................................................................................65
3. COMPATIBILITY ....................................................................................................................................66
4. ATTACHMENTS ......................................................................................................................................67

1. Presentation
This document refers to releases of BZ5000 Local Exchange Software. This software was identified as
SOF98119 before has been coded by Lucent codification standard. Now, this software is identified by the
code LPN 109253856. This code is composed with two others numbers: the first is used to define as
version number, and the second is used to define the revision number. All version starts with revision “000”
and in this case the revision number is not used.
2. Product History Information
LPN.Revision.SU Date
109253856.001 05/30/02
109253856.001.001 06/13/02
109253856.002 06/28/02
109253856.002.001 02/07/03
109253856.002.002 03/12/03
109253856.003 07/30/02
109253856.003.001 09/06/02
109253856.003.002 09/30/02
109253856.004 11/19/02
109253856.004.001 11/20/02
109253856.004.002 12/16/02
109253856.005 02/14/03
109253856.005.001 02/27/03
109253856.005.002 03/27/03
109253856.005.003 03/27/03
109253856.005.004 04/11/03
109253856.006 02/27/03
109253856.006.001 03/10/03
109253856.006.002 04/30/03
109253856.006.003 04/30/03
109253856.006.004 07/31/03
109253856.007 08/31/03
109253856.007.001 09/03/03
109253856.007.002 09/30/03
109253856.007.003 10/30/03
109253856.008 11/29/03
109253856.008.001 12/22/03
109253856.008.002 01/28/04
109253856.009 02/27/04
109253856.009.001 03/30/04
109253856.010 04/30/04
109253856.011 05/31/04
109253856.011.001 06/29/04
109253856.012 07/28/04
109253856.013 08/30/04

109253856.014 09/30/04
109253856.015 10/29/04
109253856.015.001 11/30/04
109253856.016 12/28/04
109253856.016.001 01/28/05
109253856.016.002 03/29/05
109253856.016.003 06/03/05
109253856.017 07/05/05
109253856.017.001 07/28/05
109253856.017.002 09/09/05
109253856.018 09/30/05
109253856.018.001 10/28/05
109253856.018.002 11/28/05
109253856.018.003 12/30/05
109253856.018.004 02/24/06
109253856.018.005 04/28/06
109253856.019 06/29/06

2.1 Revision: 001 – Software Update: -
2.1.1 Updates
2.1.1.1 DR 4159 - New feature: Call Interception Service – CIS (SIC)
New commands were created for CIS:
English Portuguese
PR-CIS : ASS = xxxx-xxxx [, SEQ = xx..xx ] PR-SIC : ASS = xxxx-xxxx [, SEQ = xx..xx ]
; ;
IP-CIS [ : ASS = xxxx-xxxx ] ; IP-SIC [ : ASS = xxxx-xxxx ] ;
RP-CIS : ASS = xxxx-xxxx ; RP-SIC : ASS = xxxx-xxxx ;
REL-CAD REL-DAC
The maximum number of subscribers programmed with CIS depends on the way it is done:
- 40 subscribers with parameter SEQ configured
- No limits for subscribers without SEQ configured.
2.1.1.2 DR 4385 – Time stamp on alarms

The time information when an alarm was set on was added to alarm list.
2.1.1.3 DR 4386 – Filter to show off-hook subscribers with command IT-SUB (IT-ASS)
It’s possible to list all off-hook subscribers through command IT-SUB: STE=OSC (IT-ASS: EST=OCP).
2.1.1.4 DR 4080 - Corrections in ANI procedure used in Ukraine

Fixed the assembly of ANI string when the A subscriber category is “10” and last number is “0”.
According to ANI procedure, the signal “14” is sent when we have repeated numbers in sequence and as
digit “0” is sent using the same signal for “10”, the last digit of A subscriber shall be sent as “14”.
2.1.1.5 DR 4080 - Corrections in internetworking for Ukraine signaling

There was no ring back tone for toll / tandem calls when the start index equals total digits in the
Originating Traffic Routing Plan. This problem was solved.
The timer T11 for CCSS7 was implemented.
2.1.1.6 DR 4080 - Corrections in the exhibition of A subscriber number in Caller ID for incoming
calls using Ukraine signaling
The ANI procedure represents the digit “0” and category “10” of subscribers different than Caller ID does.
The ANI processing was modified to represent these numbers in the same way used for R2D.
2.1.1.7 DR 4080 - New parameter CAS for trunks interfaces to indicate bit inversion of signaling
channel
If parameter CAS = INV, the polarity of signaling bits of signaling channel will be inverted. If CAS =
NOR, normal polarity is used.
English Portuguese
MD-TRKINT: ... [, CAS = xxx ]; MD-TRONCO: … [, CAS = xxx ];
where “xxx” = INV / NOR
2.1.1.8 DR 4080 - Corrections in the use of ANIREQ parameter of routes
Fixed problems in use of ANIREQ parameter for toll/tandem, DP1 SL and DP1 SLM calls. The calls were
being released improperly.
The processing of this parameter is now conditioned to programming country as Ukraine (UA).
2.1.1.9 DR 4430 - Call Forward Problems

The national code was not being sent in forward calls when trunks have CNAC operational parameter
programmed. It was fixed.
2.1.1.10 DR 4176 - DDC blocking for PRI/ISDN subscribers

The software was modified to process DDC (collect call) blocking for terminated calls in PRI/ISDN
subscribers.
2.1.1.11 DR 4176 - Increased the number of units that can have options of the same CPCT group
Was increased from 4 to 16 the maximum number of units that can have options of the same CPCT group.
2.1.1.12 DR 4176 - Increased the maximum incoming and outgoing calls processed by one unit
Was increased from 128 to 256 the maximum number of incoming and outgoing calls that can be processed
by one unit of the exchange.
2.1.1.13 DR 4176 - Updated Trillium stack

The Trillium stack was changed by the distribution of 29/08/00 of version 3.3 (which has patches ld001.33
to ld035.33 already applied) and after that, the patches ld036.33, ld037.33 and ld038.33 were applied.
2.1.1.14 DR 4176 - Corrections in call release for ISDN subscribers

When an ISDN subscriber hang-off before the exchange receives signaling, the unit could reset. This was
solved.
2.1.1.15 DR 4176 - Decreased time for MAP initialization

The MAP initialization is faster than last software release.
2.1.1.16 DR 4176 - Corrected the unit reset due to PRI/ISDN physical level failures
When “error in Q93x protocol cod. 4222” happened in the exchange due to failures in physical level of PRI
access it could cause a unit reset. This problem was solved.
2.1.1.17 Corrections in command for trunk creation

The use of command CR-TRK:TRK = xx-xx-xx&..&xx-xx-x, … (CR-JUN:JUN = xx-xx-xx&..&xx-xx-x,
…) to create a set of trunks could cause some unexpected behavior of software. It was fixed.
2.1.1.18 CPCT group programming without subscribers in BLK (BLT) operating status
The software was modified to allow programming CPCT group without subscribers in BLK operating
status during configuration mode of the exchange.
2.1.1.19 Fixed problems in query command for synchronism clock

The CSR software was locking when executed a query command for synchronism clock created in services
units. This problem was fixed.
2.1.1.20 New country: Greece

Was created a new country that can be programmed through command MD-CTRY: CTRY=GRE (MD-
PAIS: PAIS=GRE).
The CDR (RDC) for Greece, when the country is programmed with GRE, has the same format used in
Ukraine
2.1.1.21 Corrections in failures supervision for trunks

The trunk and route numbers of block/unblock trunks alarms due to trunks failures were wrong. It was
corrected.
2.1.1.22 Changes in default values of synchronism mesh parameters

For R2 synchronism clock type, the default value of PGLF (GDFI) synchronism parameter changed from
50 to 20.
2.1.1.23 Changes in routes programming for outgoing trunks with Ukraine signaling
The software was modified to avoid programming the operational parameter OPP=STL (POP=SAT) for
routes when we have outgoing trunks using Ukraine signaling.
2.1.1.24 Increased the kernel heap memory
2.1.1.25 PR13700 – SS password managed by the subscriber

New command for supplementary services was created to allow subscribers change their user password
using the telephone set.
2.1.1.26 PR15000 – EBT service 102

The software is processing A subscriber number in the UUI field of SETUP message from PABX for
protocol converter feature.
2.1.2 Remarks
It will be necessary to reconfigure the exchange if it is using any version of the software SOF98119 and
start to use the LPN 109253856.001 or later.
2.2 Revision: 001 – Software Update : 001
2.2.1 Updates
2.2.1.1 Colombia’s private version released
A version with the pre-paid feature available was released specifically for Colombia’s issue. It’s very
important to advice that this version will work only in Colombia.
2.2.2 Remarks
NA

2.3 Revision: 002 – Software Update : -
2.3.1 Updates
2.3.1.1 Remote Alarm Indication (RAI) been sent by switch
This alarm is been indicated by switch when some problem occurs in a trunk's reception. This correction
doesn't have a DR associated! Netro’s company requested this issue.
2.3.1.2 DR 4473 - Problems on calls with subscribers on busy state – Bolivia

BZ5000 always sends an ACM message after receiving a CALL PROC message. As by this moment
BZ5000 does not know about the B status, then the ACM message will be sent with DC=0. If the B
subscriber is free then BZ5000 will receive an ALERT message and will send a CPG message to ISUP side
with DC=1. If the B subscriber is busy then BZ5000 will receive a DISC message and will send a REL
message to ISUP side and will connect busy tone.
In Bolivia's scenario, BZ5000 was connecting the ring back tone after receiving CALL PROC and sending
the ACM message, without evaluating the B status indication (DC). The new implementation will connect
the ring back tone only if BZ5000 knows B status (DC=1), i.e., will not be connected after receiving a
CALL PROC message. This ring back tone will be connected only after receiving an ALERT message.
2.3.1.3 Semi-Permanent Switching

The semi-permanent switching facility between two terminals was not working ok, i.e., there was no audio
path established. This is a collateral problem inserted when BZ5000 was modified to extend the Multiple
Subscriber Number (MSN) facility to analog subscriber (SOF98119F1 on July 18th, 2001).
2.3.1.4 DR4000 - ISDN for interface V5.2 (PR 8200)

This feature implements the ISDN basic access (BRI) in the AN controlled by the LE through the V5.2
interface.
Now, it is possible to create a c-path in a V5.2 signaling link to carry the D channel information related to
the BRI access. This ISDN c-path can be created in the primary link (V5ENL with PRO=PRMRDSI) or in
an independent link (V5ENL with PRO=RDSI). If it is created in the primary link it belongs to the
protection group 1. Otherwise it will not be protected. In this first release, the ISDN c-path will not be
protected at all. It is possible to create more than one V5.2 signaling link per V5.2 interface that includes
the ISDN c-path.
To each AN BRI access is associated one specific ISDN V5.2 signaling link. Its D channel information will
be carried only on this signaling link.
In the LE, each BBB can control up to 256 ISDN access (local or remote). When a BRI remote access is
created in the LE it is controlled by the BBB where the associated V5.2 signaling link is located. So, in a
BBB it can be created up to 265 BRI remote access associated to all the V5.2 signaling link located in this
BBB.
In a call related to a BRI remote access associated to a BBB, the BCC protocol allocates the B channel
only in links of this BBB.

2.3.1.5 DR 4365 - Black List (PR 14900)
New commands were created to implement the Restriction / Permission List (Black / White List) feature.
English Portuguese
AT-SEQSCR ; AT-FILSEQ ;
DS-SEQSCR ; DT-FILSEQ ;
MD-SEQSCR : { INI | MD-FILSEQ : { INI |
TYP = xxxx | TIP = xxxx |
ROUT = xxx&..&xxx | ROTA = xxx&..&xxx |
TYP = xxxx, ROUT = xxx&..&xxx } ; TIP = xxxx, ROTA = xxx&..&xxx } ;
IT-SEQSCR ; IT-FILSEQ ;
PR-SEQSCR : SEQ = xxxxxxxxxx ; PR-FILSEQ : SEQ = xxxxxxxxxx ;
RP-SEQSCR : SEQ = xxxxxxxxxx ; RP-FILSEQ : SEQ = xxxxxxxxxx ;
IT-SEQSCR [ : SEQ = xxxxxxxxxx ] ; IT-FILSEQ [ : SEQ = xxxxxxxxxx ] ;
A new message for announcement machine was created in the following command:
English Portuguese
CR-JMA : JMA = xx-xx-xx, MSG = CLIS ; CR-JMA : JMA = xxxx, MSG = FSEQ ;
The CLIS constant allows the user sets up a new message for the Restriction or Permission List feature.
Some characteristics about the feature:

• This feature was implemented for toll calls only.
• The filter has up to 10.000 entries of sequence.
• The filter can be used to R2 and ISUP Signaling.
• The ROUT parameter accepts just outgoing routes.
• The TYP parameter can be REST or PERM.
• The SEQ parameter allows up to 10 digits.
• The filter will be sorted by sequence.
• The SEQ parameter accepts partial sequences.
• The ROUT parameter works overwriting the data.
2.3.1.6 DR 4472 - Switch continuously reset

Now, the messages of calls been supervisioned will be showed only if the switch has memory to do it.
2.3.2 Remarks
It will be necessary to reconfigure the exchange if it is using any older software than this release.
2.4.1 Updates
2.4.1.1 DR 4772 – Number of senders Bina FSK change for 2
Number of senders Bina FSK change for 2.

2.4.2 Remarks
This modification is available only in releases with LNP 109253856.002.xxx
To be used in Belize.
2.5.1 Updates
2.5.1.1 DR 4772 – Belize problem (HIGH PITCH TONE) – Bina FSK
Integrity supervision was developed for MPSC board and it will restart when found bugs.
2.5.2 Remarks
This modification is available only in releases with LNP 109253856.002.xxx
To be used in Belize.
2.6.1 Updates
2.6.1.1 COP-ORP command has been changed to not allow copy to the activated Originating Traffic
Routing Plan
The user can still change both Routing Plan (1 or 2) using AT-ORI ORI = 1|2 command, it doesn't matter
if it is active or not, but when he copies the changed plan (auxiliary routing plan) to the Routing Plan (1 or
2), it cannot be the active plan anymore. It has been changed due to the COP-ORP command doesn't take
care with the calls being set up and it cannot do it, it has to be done by AT-ORP ORP = X command.
2.6.1.2 DR 4456 - Alarm in SS7 signaling route

The alarms related to the SS7 signaling route were revised. They were not been turned off when the SS7
signaling route was deleted.
2.6.1.3 DR 4000 - ISDN for interface V5.2

The V5 b-channel allocation related to ISDN calls was adapted to restrict the allocation to the b-channels
created in the same unit that the associated ISDN c-path was created.
The ISDN ports activation and deactivation was reviewed to solve some synchronization problems between
the LE and AN ports state machines.
The activation of V5 interface with ISDN c-paths was revised. In some V5 signaling links configurations
the ISDN ports were not working.
2.6.1.4 DR 4000 - Problems in programming MSN for remote BRI subscribers

It was not being allowed to program MSM supplementary services for BRI-ISDN remote subscribers. This
problem was fixed.
2.6.1.5 DR 4529 – Increasing the number of Direct Line Supplementary Service

The number of the Direct Line Supplementary Service was increased from 80 per Switch to 150 per switch.
2.6.1.6 DR 4464 – Programmable EOS (PR 2100)
This feature replaces B5 signal with B1 signal for all outgoing trunk groups from BZ switches to PBX's via
DID (Direct Inward Dialing) operating with MFC-5C and MFC-5B registers signaling. The activation and
deactivation of this capability is done through O&M for each outgoing trunk group from BZ5000 switches
to PBX's.
2.6.1.7 DR 4484 – DDI calls routing problem

When a DDI route is provisioned with the parameter “TTF=BILCHA” in a call R2/ISUP, after the
outgoing trunk seizure, the switch does not send the A1 signals anymore. After a timeout, the call is
dropped. In this release this bug was fixed.
2.6.1.8 DR 4496 – ISDN Incoming calls in overlap mode (PR 19000)

This feature was implemented in this release. To activate this mode of operation, the operator should
specify the identification index with the same value of the start index in the sequences that terminate in the
access, via the command:
MD-ORI SEQ = XXX, ROT=XX-XX-XX,……….;
The switch was dropping all the incoming calls to routes with the DGE parameter defined.
2.6.1.9 ISUP Calls dropped in routes with the DGE parameter defined
The switch was dropping all the incoming calls to routes with the DGE parameter defined. This bug was
fixed in this release.
2.6.1.10 New CDR format for the Philippines

The same type of records used in the Ukraine and Greece are now being used by the Philippines.
2.6.1.11 DR 4475 - New country: Guatemala

It was implemented a new country that can be configured by CSR command MD-CTRY: CTRY=GUA
(English version) or MD-PAIS: PAIS=GUA (Portuguese version).
In this application, BZ sends the I15 signal to indicate end of B number (called party).
NOTE: the DR is not completed yet.
2.6.1.12 Fixed the packing of the ISUP parameters 'Call reference' and 'Generic Digits'
The packing of the ISUP parameters 'Call reference' and 'Generic Digits' was wrong. The problem was
fixed.
2.6.1.13 DR 4321 – Argentine SS7 Standard Implementation for POTS (PR 13800)
ISUP Compatibility Procedure defined in the ITU-T ISUP-92 recommendations. The procedures defined in
section 2.9.5 (Receipt of unreasonable signalling information messages) in the document Q.764 are
supported, except the item 2.9.5.3.3 (Unrecognized parameter values).
Changes in the CSR commands were implemented:
• Related to Parameter Compatibility Information: To enable the PCI parameter for a ISUP message:
MD-SNLISUP : MSG = xxx , PARAM = PCI ;
• Related to Message Compatibility Information: To enable the MCI parameter for a ISUP message:
MD-SNLISUP : MSG = xxx , PARAM = MCI ;
• Common: Pass On: To enable the 'Pass On' in a route: MD ROTA ROTA=xx, POP=PSD; Note: The
'Pass On' is enabled by default.
ISUP Hop Counter procedure defined in the ITU-T ISUP-92 recommendations. The procedures defined in
section 2.17 (Hop counter procedure) in the document Q.764 are supported.
• To enable and modify the central office Hop Counter: MD CENPOP POP=HC, HCIV=XX; Note: The
default value for the Hop Counter is 31.
• To enable the Hop Counter parameter for the IAM ISUP message: MD-SNLISUP : MSG = IAM ,
PARAM = HC ;
• To disable the handling of the Hop Counter parameter by a route: MD ROTA ROTA=xx, POP=HCD;
Note: The handling of the Hop Counter parameter is enabled by default.
ISUP Release message with the Signalling Point Code parameter.
• To enable the Signalling Point Code parameter for the REL ISUP message: MD-SNLISUP : MSG =
REL , PARAM = SPC ;
2.6.1.14 DR 4483 – Line hunting group provisioning problem

It was possible to create only 64 CPCT groups in the switch. This was increased to 254 CPCT groups.
2.6.1.15 Problems in V5 audio terminal creation

There was having some wrong alarms and processing by the switch when V5 audio terminals were being
created in any other trunk than the first. It was corrected.
2.6.1.16 Problems in dial pulsing processing

Dial pulsing, i.e. analog subscribers, was not being processed correctly. It was fixed.
2.6.1.17 DR 4528 – Voice mails sent by MAX TNT are not heard
The audio for trunk interface side will be closed for incoming ISDN calls when the exchange receives from
MAX TNT a Call Proceeding message with Progress Indicator 1,2 or 8.
2.6.1.18 DR 4179 – Hardlock

Implementation of Hardware Key as described in PR 12200
2.6.1.19 DR 4447 – Dial pulsing in CSR alarm call

The CSR alarm call can dial pulse digits.
2.6.1.20 DR 4223 – Call distribution in PABX feature failure

There was a call distribution failure in the PABX system. The same subscriber was receiving two
consecutive calls.
2.6.1.21 DR 4465 – Absent Subscriber Service (PR02200)
There is a new special service named Absent Subscriber Service. Details of this new service can be found
in the user manual.
2.6.1.22 DR 4222 – Corrections in IT LSS command processing

There was an error in IT LSS command processing.
2.6.1.23 DR 4444 – Corrections in IT SLIDTR command processing

There was an error in IT SLIDTR command processing.
2.6.2 Remarks
2.7 Revision: 003 – Software Update: 001
2.7.1 Updates
2.7.1.1 DR 4596 Increase in the number of BBB’s per route
In the old version the routes could be distributed among 8 BBB’S. In this new version they can be
distributed among all 16 BBB’s.
2.7.1.2 Automatic command been sent to block the other side of a trunk which have all the circuits
blocked in some way
If all the circuits of a respective trunk were blocked in some way, a command will be send to the other side
of this trunk blocking it as well.
2.7.1.3 Time to check all the circuits in the switch changed

Now, instead of 30 seconds, the verification will be done each 15 seconds. This process will certify if all
the circuits of a specific trunk are in service or not. If all were out of service, the previous issue (2.5.1.2) of
this document will be executed.
2.7.1.4 Cause’s value changed to 44 in case of a ISUP’s call been finished because of a failure in
second level in primary access
Now, the switch will send back the ISUP_DEST_OUT_OF_ORDER when the ISDN terminal is out of
service.
2.7.1.5 DR 4472 - Switch continuously reset every time

Tandem calls, using outgoing trunks with SS7 signaling, were not releasing memory blocks allocated
during call setup. This fault was occurring only in unsuccessful calls (wrong B number, called party busy
and others). When no more memory blocks were available, the memory task manager was resetting the
CPU in order to recover from this faulty condition. The interval between consecutives resets is impossible
to estimate because it depends of the number of unsuccessful calls (approximately, the reset is after 2,500
calls).
2.7.1.6 DR 4472 - Problem in cause’s value translation in tandem calls

The cause’s value translation in tandem calls, when incoming and outgoing trunks were using SS7
signaling, was wrong during call setup. This problem was fixed.
2.7.2 Remarks
NA
2.8.1 Updates
2.8.1.1 DR 4622 – Fault in R2D/ISUP interworking when tandem call receives ACM message
without indication in outgoing trunk
When a tandem call received ACM message without indication in outgoing trunk, the incoming trunk did
not change to B group signaling (in fact, the incoming trunk did nothing). Then the R2D signaling was
canceled by timeout and call was released. This is a wrong behavior.
Now, when a tandem call received ACM without indication in outgoing trunk, the incoming trunk sends A3
signal (change to B group) followed by B1 signal (subscriber free with charging) or B5 signal (subscriber
free with no charge).
2.8.1.2 DR 4624 - Fault in the second choice of synchronism reference

An error in the process of choosing the second choice of synchronism reference of the BZ5000 was fixed.
When a link was blocked through the MD-TRON command, the software was not changing to the second
choice of reference.
2.8.1.3 DR 4627 -Field 33 in AMA147record was filled with “/” (slash) signal
The fault was fixed.
2.8.1.4 DR 4623 - TUP adaptation to Philippines: new backward message for blocked or lockout
subscriber
For blocked subscribers, the backward signal should be SSB but LOS was sent.
For lockout subscribers, the backward signal should be LOS but SSB was sent.
2.8.2 Remarks
NA
2.9.1 Updates
2.9.1.1 DR 4321 - Argentine SS7 Standard Implementation for POTS (PR13800)
Circuit Group Query procedure defined in the ITU-T recommendations. The procedures defined in section
2.8.3 (Circuit group query) in the document Q.764 are supported. No changes in the CSR commands were
implemented;
UCIC message procedure defined in the ITU-T recommendations. The procedures defined in section 2.12
(Unequipped circuit identification code message) in the document Q.764 are supported. No changes in the
CSR commands were implemented;

Charging Procedure. The charging definition is based on Charging Plan composed of Subscriber Charge
Class and Charge Modality. The mapping of Charge Class is done by the relationship between NDZ
parameter received in the CRG message during call establishment that has a code correspondence to
Charge Class. This feature is used only when the central office is provisioned to operate in Argentina. No
changes in the CSR commands were implemented;
Trunk Offering This feature covers the situation that the called subscriber is engaged either on an incoming
or outgoing call, and is given an information by the trunk-operator that a caller is attempting to obtain
connection to his number. The subscriber to whose the call is offered can accept the call by terminating his
existing call, after which the offered call is connected to him using the trunk connections already in use for
the connections between trunk-operator and called subscriber. This feature is used only when the central
office is provisioned to operate in Argentina. Changes in the CSR commands were implemented:
To change the intrusion tone: MD-TOM : TOM = TINT, CAD = , FREQ = ;
Malicious Call Trace. The implementation of Malicious Call Service for POTS Subscribers using ISUP
Signaling provides the registration of incoming call information (e.g. calling number) for identification of
malicious call originator. The registration can be activated for all incoming calls or on demand (upon the
subscriber request during the call).
It was created two new supplementary services: MCTP - Malicious Call Trace Permanent and MCTD -
Malicious Call Trace on Demand, to configure the service at the subscriber (calling number).
English Portuguese
PR-SSV : ASS = xxxx, SSV = MCTD | MCTP ; PR-SSU : ASS = xxxx, SSU = TCMD | TCMP ;
IP-SSV : SSV = MCTD | MCTP ; IP-SSU : SSU = TCMD | TCMP ;
RP-SSV : ASS = xxxx, SSV = MCTD | MCTP ; RP-SSU : ASS = xxxx, SSU = TCMD | TCMP ;
New commands were created to manipulate the malicious call registers:
English Portuguese
REP-MCT ; REL-TCM ;
IT-MCT : [ LOC = "xx..xx" [ ENV = xxx ] ] IT-TCM : [ LOC = "xx..xx" [ AMB = xxx ] ]
[ IDAT = xx-xx-xx ] [ EDAT = xx-xx-xx ] [ DATI = xx-xx-xx ] [ DATF = xx-xx-xx ]
[ CDPN = xx..xx ] ; [ ASSB = xx..xx ] ;
RV-MCT : [ LOC = "xx..xx" [ ENV = xxx ] ] RE-TCM : [ LOC = "xx..xx" [ AMB = xxx ] ]
[ IDAT = xx-xx-xx ] [ EDAT = xx-xx-xx ] [ DATI = xx-xx-xx ] [ DATF = xx-xx-xx ]
[ CDPN = xx..xx ] ; [ ASSB = xx..xx ] ;
2.9.1.2 DR 4487 - DTMF C tone for Greece (PR17600)

The DTMF C tone is sent back to calling subscriber when called subscriber answers the call. The tone is
send to the calling subscriber only, the called subscriber does not receive the tone. After the tone, the call
proceeds normally. This feature is used only when the central office is provisioned to operate in Greece.
• To change the DTMF tone signal level: MD-CENPOP : POP = NVLDTMF , NVLG = xx ;
• To enable the DTMF C tone in a route: MD-ROTA : ROTA = xx , POP = DTMFATD ;
2.9.1.3 DR 4467 - Remote Programming (PR2600)

This functionality allows POTS/ISDN and DEBS users to remotely change their supplementary services
data on "home" office from any other terminal (POTS/ISDN BRI) in the public telephony network.
• To create/change/remove/interrogate the Register Directory Number: CR-ASSPREM : ASS = xxxx ,

cla = yy ;
• To remove the Register Directory Number: SU-ASSPREM : ASS = xxxx ;
• To change the Register Directory Number: MD-ASSPREM : ASS = xxxx , cla = yy ;
• To interrogate the Register Directory Number: IT-ASSPREM ;
• To program the service to a subscriber: PR-SSU : SSU = PRGREM , ASS = xxxx ;
• To assign a password to a subscriber: MD-SSUASS : ASS = xxxx , SEN = yyyy ;
• To program new messages in the announcing machine: CR-JMA : JMA = xx-xx-xx , MSG = xxxxx ;
where the new messages are: NROLST, NLINV, SEN, SENINV, CODSRV, CSINV, RSRV,
SRVBLQ;
2.9.1.4 DR 4531 - Traffic Generating Fail in the Relsup tool

The Routes Congestion Supervision was not accounting the lost calls correct. It was fixed.
2.9.1.5 Inconsistent data in long duration calls registering

Some fields of this record were filled incorrectly.
2.9.1.6 ISDN subscriber been created in an instance already used

During the creation of an ISDN subscriber, some new consistency checks were implemented.
2.9.1.7 DR 4647 - R2 adaptation for Indonesia Field Trial

The R2 adaptation are composed by:
• E&M signaling in bit A
• Semi-compelled multi-frequency code (SMFC) signaling
2.9.1.8 DR 4630 - Pending Requirements Anatel Certification

• Call waiting cadence tone was adjusted to 60-250-60-9000 instead 50-250-50-9000;
• Fixed treatment of controlling of bit C (echo suppressor) of signaling channel (channel 16);
• The field “category of A subscriber” was filled with 11 in case of a transferred call.
2.9.1.9 DR 4000 - ISDN for interface V5.2

The following bugs were fixed:
• SU-ASS was not working properly with EP other than the number 1, in remote subscriber deletion.
• Fault in CR-ASS and SU-ASS when it refers to BRI remote subscribers with V5ENL of unit, which is
not MSTSIS.
• SU-ASS could cause a fault if it refers to remote subscribers.
• CR-ASS and SU-ASS related to an MSN of a remote BRI subscriber could interfere in the default
subscriber.
• Fault in the V5/ISDN call establishment when MSTINT other than 1.
• Fault in creation of more than 128 ISDN subscribers per unit.
• The activation of the ISDN access physical interface without the related subscriber created can cause
an reset, even to local BRI and PRI access.

• The activation status of BRI remote access was not working properly in case of V5 interface shutdown
or in case of port blocking. It could cause activation problems in this access.
• Problems in CR-ASS and SU-ASS related to d-channel handlers allocation.
• MD-ASSEST was not working properly for ISDN remote subscribers when a call was already
established.
• It could block the subscriber forever.
• SU-ASS of a remote subscriber (POTS or ISDN), when the V5 interface was not active, generates a
wrong message to the operator, and can make future creation not work properly.
• The V5 signaling link could be created in time-slots other than the 15, 16 and 31.
• IT-SUPBRI execution was revised to avoid a reset when TRM parameter refers to a POTS subscriber,
and INI-SUPBRI execution was revised to initialize the counters of a remote subscriber.
• The V5 signaling link could be created in time-slots other than the 15, 16 and 31.
2.9.1.10 COM2 in configuration mode

The CSR connection through COM2 was enabled in configuration mode.
2.9.1.11 Suppression of signaling link reporting “Invalid CIC” for different routes
When two different routes in common channel signaling had the same CIC number, the command for
suppression of links was returning “invalid CIC” wrongly, preventing the suppression of one of them.
2.9.1.12 DR 4627 – Field 33 of the AMA147 records with a wrong character

Field 33 of the AMA147 records were being wrote with the character ‘/’. This bug was fixed.
2.9.1.13 DR 4652 - Dual Stage call, using ISDN signaling

Dual Stage call between the BZ5000 and MAX-TNT, using ISDN signaling, was not working because the
BZ5000 was not closing the TX path of the subscriber side. This bug was fixed.
2.9.1.14 DR4622 – ISUP/MFC interworking fault

Receiving an ACM with “no indication” the BZ was not sending A3+B1 or A3+B5. As the signals were
not being sent, the call was dropped due a timeout.
2.9.1.15 DR 4623 – TUP for the Philippines

The following bugs were fixed:
• For Blocked Subscribers, the backward signal should be SSB but LOS was sent.
• For Lockout Subscribers, the backward signal should be LOS but SSB was sent.
2.9.1.16 DR 4572 – Call restriction with RTT=DDC

Subscribers with the restriction DDC and transfer capabilities (follow me, etc) were receiving calls. Now,
the restriction DDC has priority over the other services.
2.9.1.17 DR 4617 – PRI non expected alarms

PRI subscribers created in the database and not installed were generating alarms of lockout subscribers.
This bug was fixed.
2.9.1.18 DR 4639 – R2/PRI interworking

Receiving a “call proceeding” from the access with “no indication” the BZ was not sending A3+B1 or
A3+B5. As the signals were not being sent, the call was dropped due a timeout.
2.9.1.19 DR 4624 – Fault in the election of the external clock references

Trunks blocked by the operator via command were being chosen in the election. This bug was fixed.
2.9.1.20 DR 4004 – Software to enable Circuit Packs with 02 E1s and 02 MAPs (PR 09200)
The processing of new boards with two trunks, identified by MAPB and JTSB, was developed.
For this LPN only the first trunk of these boards can be used.
2.9.2 Remarks
2.10.1 Updates
2.10.1.1 Pre paid feature enabled
Pre paid subscriber feature is enabled in this release.
2.10.2 Remarks
NA
2.11.1 Updates
2.11.1.1 DR 4630 – Pending Requirements Anatel Certification
• BZ5000, as a toll switching, was changing the “ISDN user part indicator” value from 0 to 1 in the
IAM message. It was fixed.
• When BZ5000 terminates an ISUP call, it sends a REL message with value 16 (normal call clearing)
in the cause indicator parameter and starts a T1 timer and waits a RLC message. If T1 elapsed before
receiving a RLC message, BZ5000 must sends a second REL message with the same cause indicator.
But BZ5000 was changing the cause indicator from 16 (normal call clearing) to 31 (normal
unspecified). It was fixed.
• The cause indicator used for not supported service must be 65, but BZ5000 was using the value 34. It
was fixed.
• The PRISUP supervision was showing wrong number for allocated channel in level three when the
allocated channel is from 17 to 31. It was fixed.
• BZ5000 must starts a T8 timer when receives an IAM message with continuity indicator in preceding
circuit (DC=10). When the T8 elapsed, BZ5000 must sends a backward REL message with value 31
in the cause indicator and a forward REL message with value 16 in the cause indicator. But BZ5000
was sending both REL messages with the value 31 in the cause indicator. It was fixed.
• BZ5000 is changing the INR and INF messages when it is a toll / tandem switching. It was fixed.
2.11.1.2 DR4709 - Fault in R2D/ISUP interworking when tandem call receives an ANM before
terminates the R2D signaling in the incoming trunk

Timing to send answer signal to incoming trunk when outgoing trunk receives the answer signal before
incoming trunk has been completed the address signaling (MFC). Normally, BZ5000 sends the answer
signal immediately after the address signaling is completed, but switches of other vendors do not
understand this signal as an answer signal and abort the call. It was fixed.
2.11.2 Remarks
NA
2.12.1 Updates
2.12.1.1 DR 4336 – LAN’s RTL driver more efficient
The driver’s transmission is using all the chip’s descriptors and a new local FIFO to transmit.
2.12.1.2 DR 4666 – Hardware Key for Billing Unit

New Hardware Key for Billing Unit.
2.12.1.3 DR 4179 – Hardware Key for Redundancy

Hardware Key for redundancy.
2.12.1.4 DR 4647 – V5.2 and SS7 adaptations for Indonesia (PR 20200)
2.12.1.4.1 V5.2 adaptations for Indonesia
The following changes were implemented:
• The exchange must be configured to operate in Indonesia with the CSR command:
MD-CTRY CTRY=INA; (English)

MD-PAIS PAIS=INA; (Portuguese)
• BCC timers TBBC1 and TBCC4 must have the value of 500 ms. Configurable timer V5TMP4 is
used to configure both timers and it accepts values in the range of 500 to 1500.
MD-EXCTME V5TMP4=500; (English)

MD-CENTMP V5TMP4=500; (Portuguese)
• When terminating calls in a subscriber without Caller ID service LE must send ESTABLISH
message with element information CADENCED RING: Ring Type = 0.
• When terminating calls in a subscriber with Caller ID service LE must send ESTABLISH message
with element information PULSED SIGNAL: Initial Ring, Suppression Indication = 0, Pulse
Duration Type = 0, Acknowledge Request Indicator = 2, Number of Pulses = 1. DTMF digits must
be sent from 500 ms up to 1500 ms after receiving the PULSE NOTIFICATION message sent
from AN. After sending DTMF digits LE must send the signal CADENCED RING message.
• Element information “Acknowledge Request Indicator” in METER PULSE and PULSED

REVERSED POLARITY messages must be filled with value 2.
2.12.1.4.2 SS7 adaptations for Indonesia
The following changes were implemented:
• Implementation of the optional parameter National Forward Call Indicator used in the IAM
message. Change in the CSR command were implemented to enable the NFCI parameter for the
IAM ISUP message: MD-SNLISUP : MSG = IAM , PARAM = NFCI;
• Analysis of the Redirection Counter value of the Redirection Information parameter in IAM
message to allow a maximum of 5 call redirections. No changes in CSR commands;
2.12.1.5 DR 4683 – How to adjust a T3 timer for ANI procedure on DP2

It was implemented a new timer (called TANI) in the MD-CENTMP (Portuguese version) or MD-
EXCTME (English version) command. The default value is 600 ms and the acceptable value is from 200
up to 3000 ms in steps of 50 ms.
2.12.1.6 DR 4760 – BZ5000 certification – gaps pause in ANI packet.

The problem was fixed.
2.12.1.7 DR 4685 – CLIRP / CLIRO supplementary services for POTS subscriber (PR 24800)
These supplementary services are available for any country (not only for Belize).
2.12.1.8 DR 4761 – Command IT-ESCTRD is presenting different values when is used as IT-
ESCTRD PLACA=XX-XX
2.12.1.9 DR 4652 – Dual Stage call, using ISDN signaling, is not working because the BZ5000 is not
opening the TX path.
The BZ is opening both paths (RX and TX) after receives the CALL PROCEEDING with the
PARAMETER INBAND INFO AVAILABLE then the ALERTING message is received and two ringing
tones are heard by the A-party, one from the MAX-TNT and other from the BZ. Now only the ringing tone
from the MAX-TNT shall be heard.
2.12.1.10 PR26900 – The MCB (B code matrix) may be treatment using the NOA (nature of address)
parameter presented in the IAM message.
The CSR command MD-MCB may accepted the parameter NOA which values can be LOC, NAT or INT,
as showed below:
MD MCB MCB=x, ROUT=x, NOA=LOC/NAT/INT, SEQ=x (English version)
MD MCB MCB=x, ROTA=x, NOA=LOC/NAT/INT, SEQ=x (Portuguese version)
The NOA parameter is optional then the command without NOA parameter must be accepted as showed
below:
MD MCB MCB=x, ROUT=x, SEQ=x (English version)
MD MCB MCB=x, ROTA=x, SEQ=x (Portuguese version)
The NOA parameter is used only in tandem call when the incoming call is ISUP. If no have a MCB defined
for a NOA received in the message, BZ will try in another MCB defined for the same rout, but without
NOA parameter defined.
The MCB without NOA parameter will be used in the tandem call when the incoming call is no ISUP.

2.12.1.11 DR 4771 – Corrections in status parameter for CGUA and CGBA messages
The mandatory “status” parameter for CGUA and CGBA messages was not being sent when the exchange
receives CGU and CGB messages. It was fixed.
2.12.1.12 DR 4615 – Problems in SS7 trunks interface creation with exchange in operational state
It was necessary to deactivate and activate the SS7 link set when a ISUP trunk interface was created with
exchange in operational state. It was fixed.
2.12.1.13 DR4667 – Fails in the voice channel in DDR with extension blocked for collect calls
The audio channel was being disconnected when the exchange received a SUS message for outgoing calls.
It was fixed.
2.12.1.14 Corrections in suppression of V5 and SS7 signalling links

Could happen a link down in V5 and SS7 signalling links created in unit 1, when signaling links created in
others units were suppressed. It was fixed.
2.12.1.15 DR4589 – ISDN Primary Access does not activate after the switch reset
Sometimes the MAP board was not properly initialized, causing this problem. The program now detects
this situation and restarts the board.
2.12.1.16 PR 22300 – TUP IAM handling for Philippines

The switch shall handle the ITU-T TUP IAM message, if it is received in incoming trunks and if the
country is Philippines.
2.12.1.17 Number of senders Bina FSK change for 2

Number of senders Bina FSK change for 2.
2.12.2 Remarks
2.13.1 Updates
2.13.1.1 DR 4707 – Problems in calls from ISUP to ISDN with overlap
Calls from ISUP to ISDN with overlap don't mature due BZ is mapping the first ALERTING message to
CPG, instead of ACM. It was fixed.
2.13.1.2 DR 4778 – Problems with messages IAM and ACM for Argentina
The IAM and ACM messages that are being sent on forward call scenario does not comply with the ISUP
recommend Argentina. It was corrected.
2.13.1.3 PR 28900 – Send B subscriber number for intra switch ISDN calls
The B subscriber number is sent with overlap in intra switch calls for ISDN access.

Integrity supervision was developed for MPSC board and it will restart when found bugs.
2.13.2 Remarks
NA
2.14.1 Updates
Some problems were fixed in the integrity supervision developed for MPSC board.
2.14.1.2 DR 4796 – DTMF allocation for pre-paid subscribers

When the pre-paid subscriber is in the minimal credits level and receives the alert message before the dial
tone, if the DTMF is allocated from other unit than the subscriber’s, some times the dialed digits are not
detected (don’t off the dial tone).
2.14.1.3 DR 4811 – Fault in PRI to ISUP calls and ISUP to ISUP calls when it involves 2 BBB
PRI originating calls outgoing to ISUP routes, or ISUP to ISUP toll/tandem calls, when it involves two
BBB, cause failure in the BBBs communicating protocol. This problem was fixed.
2.14.1.4 DR 4813 – Overlap addressing is not working in ISDN route.

In ISUP to PRI scenario when receiving the SAM (ISUP) message before having the call reference for the
ISDN side was leading to call abort. This problem was fixed.
2.14.2 Remarks
NA
2.15.1 Updates
2.15.2 Remarks
NA
2.16.1 Updates
2.16.1.1 PR 31200 – BZ5000 IAM signal adaptation for Philippines SS7

Adaptation for Philippines SS7 signaling to accept the category code sent to the BZ5000 in incoming
international calls and properly terminate this calls in the HICOM PBX connected to the BZ5000 through
R2.
In other words, the BZ5000 will be able to: receive calling Party’s Category 19, coming from IAM TUP,
convert to signal II-7 and route it by R2D and vice versa.
2.16.1.2 DR 4810 – SS7 IAM FEATURE - Compatibility Testing between BZ5000 and NEAX61E
For TUP signaling incoming calls, when the switch received an IAM or IAI message with invalid A
subscriber category the BZ released the call indicating invalid number. Now every unknown category will
be converted to common subscriber category.
2.16.2 Remarks
NA
2.17.1 Updates
2.17.1.1 DR 4788 – Indonesia Analog Subscriber Impedance (PR 28800)
New analog subscribers profile has been added providing different range of sets compounded by gains
parameters and different impedance balance for analog interface subscriber, attending for Indonesia
National Standard for switch that requires a 600 Ω analog interface. Note: In spite of been requested to
supply Indonesia needs this new feature is already done to be worldwide available.
2.17.1.2 DR 4789 – Indonesia Caller Identification (PR 28800)

The caller identification "Caller ID" for Indonesia National Standard for Switch has been adjusted and it
doesn't exhibit the calling party category anymore.
2.17.1.3 DR 4799 – Frequency Pulse of 12KHz or 16KHz (PR 28800)

The range of frequency pulse 12KHz or 16KHz concerned to public telephone settings is now an option
configurable by the operator through the management software command below:
MD-EXCTME TSP18 = 50..2000 (in milliseconds, default 150).
Note: In spite of been requested to supply Indonesia needs this new feature is already done to be worldwide
available.
2.17.2 Remarks
This is a trial release to be used in Indonesia.
2.18.1 Updates
2.18.1.1 DR 4777 – Need to get setting for DTMF frequencies and codes (PR 29000)
The current implementation supports +/- 1.8% of variation.
2.18.1.2 DR 4793 – Need to change the procedure for Abbreviated Dialing feature (PR 29000)
The abbreviated dialing feature is accessed by digits **X or **XX, where X or XX means the list entry.
For lines with 1-digit list entry code, 4-second timer will be initiated when the first dialed digit is received.
The call will be completed to the address in the list corresponding to the dialed list entry when the timer
elapsed or when a digit # is dialed. For lines with 2-digits, the call will be completed after second digit
dialed is received.
2.18.1.3 DR 4794 – Need to change the subscriber use of call waiting and 3-party conference (PR
29000)
The call waiting will be answered when flash button is pressed. After this, the subscriber can switch
between the two calls by flash button.
The subscriber can add a third party to the call. To add, the subscriber presses the flash button, receives
dial tone and dials the third party number. After this call is answered, the subscriber can switch between
the two calls by flash button. If the subscriber presses the flash button twice, the three parties will be put in
the conversation (a conference call).
2.18.2 Remarks
This is a trial release to be used in Indonesia.
2.19.1 Updates
2.19.1.1 DR 4686 – Supplementary Services for Belize (PR 16200)
The syntax of programming the supplementary services in Belize, listed below, is different to that one
currently implemented on BZ5000 for Brazil:
• Unconditional Call Forward
To activate: dial * + access code, get special tone, dial DN + # and receive accepted operation tone
or accepted operation message.
To verify: dial * + # + access code, get special tone, dial DN + # and receive accepted operation
tone or accepted operation message.
To deactivate: dial # + access code + # and receive accepted operation tone or accepted operation
message.
The access code required is 21 and this value is the same as the default value. But this code can be
changed by CSR command (MD-SRV SRV=TMPTRF, COD=new code).
• Call Forward on Busy

message.
The access code required is 22, but the default value is 63. Then this code must be changed by
CSR command (MD-SRV SRV=TRFBSY, COD=new code).

• Call Forward on No Reply
message.
changed by CSR command (MD-SRV SRV=TRFNA, COD=new code).
• Subscriber Outgoing Call Baring

To activate: dial * + access code + password + # and receive accepted operation tone or accepted
operation message.
To verify: dial * + # + access code # and receive accepted operation tone or accepted operation
message.
To deactivate: dial # + access code + password # and receive accepted operation tone or accepted
operation message.
changed by CSR command (MD-SRV SRV=BLCALL, COD=new code).
To use this feature when the call is barred: dial DN, wait inter-digit timer expiration, get special
tone and then dial password or dial DN + #, get special tone and dial password.
• Abbreviated Call Dialing

To activate: dial * + access code + list position number (0-9) + DN + # and receive accepted
operation tone or accepted operation message.
To verify: dial *+ # + access code + list position number (0-9) + DN + # and receive accepted
To deactivate: dial # + access code + short code (0-9) + # and receive accepted operation tone or
accepted operation message.
To use: dial * + list position number (0-9) and wait timer expiration (4 seconds) or dial * + list
position number (0-9) + #.
changed by CSR command (MD-SRV SRV=ABDIAL, COD=new code).
• Wake up call
To activate: dial * + access code, get special tone, dial HHMM + # and receive accepted operation
To verify: dial * + # + access code, get special tone, dial HHMM + # and receive accepted
To deactivate one alarm: dial # + access code + HHMM + # and receive accepted operation tone or
accepted operation message.
To deactivate all alarms: dial # + access code + # and receive accepted operation tone or accepted
operation message.
changed by CSR command (MD-SRV SRV=ALARCLK, COD=new code).
The special tone provided on the Call Forward on Busy, Call Forward on No Reply, Unconditional Call
Forward, Outgoing Call Barring and Wake Up Call supplementary services will use the frequency of 440

Hz, already implemented on the MPS firmware and CSR. This tone is configured by CSR command MD-
TON TON=SDT, FREQ=HZ440.
The CSR commands MD-CTRY and IT-CTRY shall support the parameter CTRY=BIZ, the country
profile for Belize.
The switch does not send the category of the calling subscriber in CLIP service
2.19.1.2 DR 4795 – Indonesia modifications - Outgoing Call Baring (PR 29100)

The BZ5000 accept the Outgoing Call Barring Traffic Class be programmed by the subscriber dialing the
digits shown below:
*33*password*traffic class#
The acceptable values for traffic class are:
• 1 = the subscriber can only receive call
• 2 = the subscriber can receive call and originate intra and local call
• 3 = the subscriber can receive call and originate intra, local and long distance call
The traffic class has a direct correlation with RTO parameter in CSR command MD SSVSUB
SUB=NNNN, SSU=BLCALL, RTO=X, as shown below:
• traffic class 1 means RTO=16
This implementation is valid only for Indonesia (MD-CTRY CTRY=INA).
2.19.1.3 DR 4798 – Announcement Capacity (PR 29100)

Enable to handling 24 announcements and each announcement has 32 seconds duration maximum. This
implementation is valid only for MPS 94196C and all the countries configured.. Any modification was
implemented for MPS 94196B.
2.19.1.4 PR 29100 – Configurable tolerance for DTMF frequencies detection

The tolerance for DTMF detection is now configurable to ±1.8% in the switch through command:
MD-EXCOPP : OPP = DTMFTOL, TOL = 1.8;
The switch must be in “configuration mode” and ±1.5% is the default value.
2.19.1.5 PR 29700 – Indonesia modifications – Lockout Situation

The lockout timer can be changed by CSR command. The lockout is when the subscriber to be in off hook
for a long duration time without make any call. When the timer had been over shall be send an alarm.
The CSR command is MD-EXCTME TFCALL=X, where the value is in minutes. The default value for
TFCALL is 1440 minutes, and the acceptable range is from 3 to 1440 minutes.
2.19.1.6 PR 29900 – Indonesia modifications – Loop Closed Seizure Timers

The subscriber loop closed seizure timer can be changed by CSR command. The timers are for recognize
the off hook and on hook events. The CSR command is MD EXTME TONHK=X, TOFFHK=X; where the
both values are in mile-seconds (ms). The default value for TONHK is 200 ms and the acceptable range is
from 140 to 1000 ms; and the default value for TOFFHK is 50 ms and the acceptable range is from 20 to
1000 ms.
2.19.1.7 DR 4812 – Problem BINA FSK enabled with V5.2 users (PR 31900)

This problem was fixed. The LE sends a ESTABLISH (PULSED SIGNAL – INITIAL RING) to the AN,
then waits a SIGNAL (PULSED NOTIFICATION) to transmit the CAID information.
2.19.1.8 Units suppression with boards created

The switch was allowing suppressing a unit with boards created. It is not allowed anymore.
2.19.1.9 DR 4808 – Internal MTP failure cod=07

The failure was caused by MSU messages with invalid size. The problem was fixed so those messages are
not generated anymore.
2.19.1.10 -Call Interception System – Ukraine

The intercepted subscriber was being charged by the automatic call generated to the EMS. This bug was
fixed.

Corrected the MPSC firmware fixing the problem.
Removed the integrity supervision developed for MPSC board and returned the number of FSK CallerId
senders (Bina FSK) to 4.
2.19.1.12 DR 4816 – Problems with CCS#7 (national indicator)

When the switch is programmed to send the origin national area code, through operational parameter
OPP=CNAC or through BILHET in routing programming, the national area code is sent together with A
subscriber number. However, the A subscriber address nature was being sent indicating “Subscriber
Number” instead of “National Number”. It was fixed.
2.19.1.13 DR4781 / DR 4799 – Increased the accuracy of 12/16kHz and polarity inversion pulses
Increased the pulse duration accuracy of 12Khz, 16kHz and polarity inversion pulses. The accuracy was
smaller than specified in recommendations.
2.19.2 Remarks
NA
2.20.1 Updates
2.20.2 Remarks
NA

2.21.1 Updates
2.21.1.1 DR 4832 – Establishing incoming calls problem on BZ5000.
The switch BZ5000 is not establishing the incoming calls reached in its own subscribers, when these are
received from an ISUP route and the ID of the B subscriber presents the (F) end indicator in the IAM
message. The switch BZ5000 is dropping the call and sending back a release with value of cause 1 (i.e.
Unallocated “unassigned” number).
This problem is taking place when the country configuration is programmed for Bolivia (BOL). For
country selected as Brazil (BRA) the problem doesn't happen. It was fixed.
2.21.1.2 DR 4834 - Dual Stage from POTS subscribers

The switch BZ5000 is not opening up the audio channel after receiving the message Call Proc for POTS
subscriber. It was fixed.
2.21.2 Remarks
NA
2.22.1 Updates
2.22.1.1 PR 26200 - CIS for Russia (with black box) - Phase 1
Call Interception Service implemented according to requirements (RQS-03056-02-CIS_Russia.doc) and
based on ETSI standards.
2.22.1.2 PR 33200 - Indosat Tender PxP analysis and 2 Ni THY estimate

Two new parameters were introduced in the MD-OPC command, ALTOPC and ALTNIC. These
parameters were introduced to support the switching office working as a gateway between SS7 networks
with different Network Indicator Codes (NIC).
Originally, messages received with a NIC other than the one configured for the switch were simply
discarded. With this change, messages received with a NIC equal to the configured ALTNIC and sent by a
point code identified as ALTOPC are received and processed as if the NIC was the same.
2.22.1.3 DR 4829 (AR 1-0843402) – Only first ISDN port can get dial tone – AR 1-0843402
Considering the ISDN BRI subscribers, only the one connected to the first port of the MAB can get dial
tone. This bug was fixed.
2.22.1.4 DR 4833 (AR 1-0823295) - Unexpected cause value received by Called

The cause code 16 was sending to the ISDN access on the terminated call when the option “not answer”
was activated. The right value is 102.
This bug was fixed.
2.22.1.5 Error in the IAM message on transit calls with transfer parameter
When the BZ switch was configured as switching tandem, the following errors were occurring:
- The BZ was inserting the parameters REDIRETING NUMBER and ORIGINAL CALLED NUMBER in
the message IAM in the original IAM message received.
- When a call transfer happens, the BZ was increasing the counter of transferred call (REDIRECTION
COUNTER). This counter can only be increased in the switch that owns the subscriber programmed with
the transfer service.
This bug was fixed.
2.22.1.6 DR 4835 (AR 1-0845827) - Error operation on the COLP service

When the subscriber with the COLP service is originating a call for a DDRI subscriber, the BZ switch
sends for the default (PRI) subscriber number and the “screening ind” parameter with the value equals to
“network provided”.
The BZ switch receiving a CONN message on the PRI side with the parameter Connected Number, is not
forwarding correctly to the ISUP side through the IAM message or CON message.
These bugs were fixed.
2.22.1.7 DR 4825 (AR 1-0823310) -Screening Indicator

When receiving the message CONN (PRI) with the “screening ind” set as "user provided", the switch
forwards to the ISUP side through the IAM or (CON) message with the “screening ind” set as "network
provided". This bug was fixed.
2.22.1.8 Different check sums of the switch after creating or suppressing a V5 interface.
After creating or suppressing a V5 interface on the switch during an operational mode, the database was
being corrupted, provoking different check sums “CKS” between the switch units. This bug was fixed.
2.22.1.9 Message CRG (charging) with wrong handling

BZ5000 is handling CRG message improperly when field ZONE NUMBER has the value from 13 to 200
or from 213 to 255. The subscriber counter should be initially increased by the value defined in the
message field UDT (charge units), but BZ5000 is increasing with the value defined in Charge Class 32.
This bug was fixed.
2.22.1.10 DR 4798 (AR 1-0783697) – Announcement Capacity (PR 29100)

BZ5000 was not handling properly the announcements when the binary file (created by Message
Generator) is greater than 4Mbytes or when announcement 17 to 24 is recorded by subscriber command
(by subscriber telephone). MPS 94196C has 8Mbytes to record announcement, but only lower 4Mbytes is
been accessed. The upper 4Mbytes is not accessible. It is necessary to replace the CI16 component (for
more information, please see the document ECN 212).
2.22.2 Remarks
2.23.1 Updates
2.23.1.1 DR 4782 (AR 1-0784610) MF signals duration
Currently, BZ5000 can recognize MF signals only if duration of received signals are equal or greater than
60ms, but Russian Standards ask for to recognize in the range of 30-135ms. This bug was fixed.

To recognize MF signals with duration less than 60 ms, it is necessary to define a new operational
parameter in the MD-EXCOPP command, as shown below:
MD EXCOPP OPP=SHORTMFC
2.24.1 Updates
2.24.1.1 PR 30800 (AR 1-0804756) BZ5000 ISDN Protection over V5.2
If the ISDN c-path is created in the primary link (V5ENL with PRO=PRMRDSI) it belongs to the
protection group 1. In this case, from now on, it is protected and ISDN line can up again after the
switchover from the primary link to secondary one.
In order to avoid that calls drop during the switchover, the V5 timers #9 and #10 should be programmed to
values less than 10 seconds.
The following related issues were reviewed:

• Fault in terminating calls to remote ISDN lines.
• Switchover by command became faster.
2.24.1.2 DR 4852 (AR 1-0911425) CPU does not detect the Hardware key
The driver to access Hardlock was changed with new timers and serial port is now configured according to
Vendor specifications received from Aladdin German Support. A serial port where Hardware Keys are
connected can't be used by other purpose, as specified in the owner's manual.
2.24.1.3 DR 4839 (AR 1-0824937) Correction of INF message when the caller subscriber is
programmed with CLIRP service
When the A subscriber is programmed with CLIRP service, the B subscriber is programmed with BINA
service and the ISUP is programmed with POP=NIDENT, the INF message from A to B must send the A
number and must have the "Address presentation restricted indicator" set with "Presentation Restricted".
It was being sent "Presentation Allowed" in this field and was corrected.
Now, both POTS and ISDN have access for CLIRP service.
2.24.2 Remarks
NA.
2.25.1 Updates
2.25.1.1 DR 4848 – Problems with double call control tone in BZ5000.
When a POTS subscriber originates one call that takes a DDRI route, the BZ5000 is applying a call
control tone that overlaps the tone sent by the destination switch. The subscriber was receiving a double
call control tone. This fault is occurring when configured country was Bolivia. This problem was
corrected.

2.25.2 Updates
2.25.2.1 DR 4863 – Problems with Overlap with the BZ5000 under Inter-working ISUP/PRI
When the SAM message is received (ISUP side) before the switch sends the SETUP message (PRI side),
the call was not being completed. It was occurring because sometimes the SAM message was being
ignored. Now, this message is bufferized and treated correctly.
2.25.3 Updates
2.25.3.1 DR 4870 - ABCD bit for E&Mp line signaling not comply with Indonesian
The B bit will be always “1” when the trunk is programmed with “E&M Signaling in Bit A”,
independent of the signaling programmed in the trunk (normal or inverted). To make this, the
program puts the B bit in “1” when the signaling is normal and in “0” when the signaling is
inverted.
2.25.4 Remarks
NA.
2.26.1 Updates
2.26.1.1 PR 28700 - ISDN CUG for Indonesia

CUG feature was implemented for ISDN subscribers with Indonesia variants.
2.26.1.2 PR 29300 - Call Hold and CLIP FSK

The Call Hold feature for ISDN remote subscribers, and the CLIP FSK were implemented.
2.26.1.3 PR 31200 – BZ5000 IAM signal adaptation for Philippines SS7

2.26.1.3.1 Error transporting the 10h category received in IAM message
In inter-working TUP-TUP for Philippines, when the switch receives the 10h category in IAM message, it
must forward the same category but it was sending 13h instead. This problem was fixed.
2.26.1.3.2 Error sending LOS and SSB message when the subscriber is blocked or in fault
When the B subscriber is blocked by the operator and receives a TUP incoming call, the LOS message
must be sent back, but the SSB message was being sent instead. When the B subscriber is in fault, and
receives a TUP call, the SSB message must be sent back, but the LOS message was being sent instead.
These problems were fixed.
2.26.1.3.3 Error sending LOS and SSB message in lockout situation

When the B subscriber is in lockout, and the switch receives an TUP incoming call, for Philippines the
LOS message must be sent back to the A subscriber and the SSB message must be sent for other countries.
The switch was sending CCD message for both cases.
This problem was fixed.
2.26.1.4 DR 4803(AR 1-0790370) - Line Test fail with parameter TYP=RES

When a Line Test was activated with the parameter TYP=RES on circuits of the MTA98038A (LPN
109157453) pack, there was a fail (“Execution Failed”). This problem was fixed.
2.26.1.5 DR 4826 (AR 1-0825253) - BZ5000 doesn't send I-15 signal at the end of call
For the countries that use the I-15 signal (End of Number), the BZ5000 was not sending it in a call
originated from a PRI subscriber to a R2 trunk. This problem was fixed.
2.26.1.6 DR 4833 (AR 1-0823295) - Unexpected cause value in ISDN calls

In an intra switch call from an ISDN subscriber to another ISDN subscriber, in a no answer scenario, the
BZ is sending to the calling subscriber a REL message with cause value 102, but it should send the cause
value 19. In an outgoing call from an ISDN subscriber to an ISUP trunk, in a no answer scenario, the BZ
is sending to the calling subscriber a REL message with cause value 16, but it should send the cause value
102. Both of these problems were fixed.
2.26.1.7 DR 4836 (AR: 1-0845828) - Error in mapping sub-address from ISDN-CONN message to
ISUP-ANM
The switch was not transporting the "Connected Party Sub-address (EID 0x4D)" information element
received in a CONNECT message coming from an ISDN interface into "Access Transport" of ISUP
ANM/CON message, causing the loss of the information. This problem was fixed.
2.26.1.8 DR 4842 (AR 1-0893364) - Problems with "Call Waiting" Supplementary Service
The switch has the EXCOPP programmed as NMUSIC. A has Call Waiting feature. A calls B and they
start to talk. C Calls A, so A can hear a Call Waiting beep. A push "FLASH + 2", in order switch to the
second call and hear C. A and C start to hear each other normally, A and C cannot hear B but B can hear
both of them. The problem is that B should not hear A and C, while it is retained. This problem was fixed.
2.26.1.9 DR 4851 (AR 1-0895263) - Problems with transfer services

When the subscriber has two kinds of transfer services programmed and activated (TRFNA and TRFBSY),
if anyone of these is removed before being deactivated, it remains activated. It does not occur if just one
transfer service was programmed. This problem was fixed.
2.26.1.10 DR 4855 - V5ISDN - Answer to the command IT SUB RMT when it has MSN programmed.
To be compatible with IT TER, it was created a new command, IT TRM that exhibits all the subscribers
that have SSU=MSM linked to same TRM.
2.26.1.11 DR 4856 - V5ISDN - Remote BRI subscriber creation with high RMT number
This DR fixed the problems in the remote BRI subscriber creation (ISDN over V5.2) with high RMT
number (above 127).
2.26.1.12 DR 4857 - V5ISDN – Command IT INT SUB doesn't work for remote BRI subscribers
2.26.1.13 DR 4858 – Answer to the command IT-V5LNK is incorrect for ISDN c-channel
The answer to the command IT-V5LNK was displaying an incorrect operational status if the protocol
(PRO parameter) was ISDN. This problem was fixed.
2.26.1.14 DR 4859 – Fail in the V5 interface provisioning

When the master of the V5 interface was in a unit different from one, it was impossible to establish ISDN
calls. It was also fixed a problem related to ISDN subscriber creation.
2.26.1.15 DR 4864 - V5ISDN - Creation and suppression of remote BRI subscriber during tentative of
establishing calls
When a remote ISDN subscriber was removed and created again with the switch in operation mode, this
subscriber became in SRV BLE state, even after being put in service. To fix its state, it was necessary to
block and to unblock it. This problem was fixed.
2.26.1.16 DR 4868 (AR 1-0934817) - CIS - CIC Number is not present in CAD
The CIC number information was not present in the CAD (Call Associated Data). The problem was fixed.
2.26.1.17 DR 4869 (AR 1-0934837) - CIS – Invalid Intercepted-Call-Direct values

The Intercepted-Call-Direct [4] parameter value, in the IRI-Content record, was invalid for originating and
terminating target. The problem was fixed.
2.26.1.18 DR 4877 (AR 1-0946449) – Invalid value in the charge indicator field of the ACM ISUP
message in transferred calls
When a called subscriber B in BZ was provisioned with CTT equals to 7 (subscriber free with no charge,
in Argentina) an it has a transfer provisioned (temporary or on busy) to a C subscriber outside the BZ
(subscriber free, charge), the BZ was sending an ACM with the charge indicator equals to 2 (Charge)
instead of the correct value 1 (no charge). This problem was fixed.
2.26.1.19 DR 4878 (AR 1-0946404) - The switch is resetting when receives an IAM message with the
parameter UUS and length equals to zero.
It was occurring a reset in the switch when it was receiving an IAM message with the parameter UUS and
length equals to zero and this call was being forwarded (transfer or transfer on busy). This problem was
fixed
2.26.1.20 DR 4881 - Problem in tandem ISDN calls

In a tandem call, when the switch was receiving an IAM message with the parameter UUS and length
equals to zero, this call was being aborted. This problem was fixed.
2.26.1.21 The Call Waiting programming was inhibited for ISDN subscribers.
This supplementary service was inhibited for ISDN subscribers, because it does not make sense in the
current ISDN implementation.
2.26.1.22 Noise in the Announcement Machine

It was verified that after recording messages through command GR-MSGDSP, there was a noise in the
audio. This problem was fixed.
2.26.1.23 V5TMP9 and V5TMP10 default values changed.

The default value for timers V5TMP9 and V5TMP10 were changed in order to avoid LAPD link down for
remote ISDN subscribers, during a V5 switchover. The default values are V5TMP9=6 and V5TMP10=6
for LE side.
2.26.1.24 Increase in CPU load during ISDN calls

It was observed an abnormal increase in CPU load during traffic tests when doing ISDN calls, leading to
call loss in some cases. This was caused by long loops in control program generated by the increase in
maximum subscribers count for this release. The program was optimized to avoid this long loops.
2.26.1.25 B-Channel Groups for ISDN-PRI interface was not working

The ISDN-PRI B-Channel groups programming was not working properly. If the SETUP message received
included a calling number different from the one for the default ISDN subscriber, the group used was ever
the one associated to the access default number. This problem was fixed.
2.26.1.26 ISDN PRI call losses

There was 1% call losses observed with the following scenario:
[call generator]----PRI----[BZ5000]----PRI----[call generator]
This was happening due to inefficient code for handling the SETUP received from an ISDN-PRI
subscriber. The code was optimized to fix this problem.
2.26.1.27 Command MD-SUB generates different checksum of configuration data among units
An error on treatment of MD-SUB command could generate inconsistency of configuration data among
units, if some parameters specified in the command were applied to the subscriber but other parameters
were not. The problem was fixed.
2.26.1.28 Problems with creation of MPS-C board with one and two links
When the circuit pack MPS-C was created with two PCM links, and the user chages the MPS-C board
configuration to one PCM link, in the high position, it stopped working. This problem was fixed.
2.26.1.29 Command AT-SUPCHA does not show CPU load in a TCP/IP connection
The command AT-SUPCHA does not show CPU load in a switch to BZ-VIEW TCP/IP connection. The
problem was fixed.
2.26.2 Remarks
2.27.1 Updates
2.27.1.1 DR 4885 (AR 1-0950829) - Problem in ANI number inversion

The ANI number was being inverted before the treatment of the repeated numbers. Therefore, the 0x0E
(14) character was inserted in the wrong place. This problem was fixed, treating these repetitions before
inverting the number.
2.27.1.2 DR 4889 (AR 1-0954868) - Incorrect Redirecting Number call forwarded

When the BZ5000 receives a SS7 call and transfers to another switch through SS7 protocol, the
Redirecting Number in IAM message was filled with the called address digits received in the first IAM
message. However, for Argentina, only Area Code and B number had to be included. This problem was
fixed.

2.27.1.3 DR 4870 (AR 1-0931593) – ABCD bits for E&Mp line signaling not comply with Indonesian
The C and D bits for E&Mp signaling was configured for 1 and 0 respectively, when the correct is fixed in
0 and 1. This problem was fixed.
2.27.2 Remarks
NA.
2.28.1 Updates
2.28.1.1 PR 14000 – Software driver implementation for RMTL Circuit Pack

2.28.1.1.1 600 ohms impedance line audio test
It was implemented the tests of audio of psophometric noise and impulsive noise, for the subscriber with
the impedance of line in 600 ohms.
2.28.1.1.2 16KHz pulse metering measurement
It was implemented the treatment of the measure of the 16kHz metering pulse used in the subscriber line
interface.
2.28.1.1.3 Ring test failure
This problem is relative to the ring measurement test when the call traffic increases. This problem was
fixed.
2.28.1.1.4 Isolation test
The isolation measurement test was revised.
2.28.1.2 DR 4872 - B-Code Matrix is not working for calls originated to DDRI routes
When a subscriber made a call to a DDRI route, and BCM was configured, the switch was not inserting the
digits defined in the BCM for the dialed number. This problem was fixed.
2.28.1.3 DR 4876 (AR 1-0946452) - Problems with transfer calls when number of digits is less than
starting index
The switch was not transferring the calls when the number configured for the transference was outside of
the switch and the number of digits was less than starting index. This problem was occurring for countries
that was using I-15 signal (End of Number). This problem was fixed including the I-15 signal at the end of
the transfer number.
2.28.1.4 DR 4886 (AR 1-0951729) - The outgoing ISDN calls are not being completed for countries
that use I-15 signal (End of Number)
The switch was not inserting I-15 signal for ISDN calls. Therefore, as the start index was configured with
one digit more than the dialed number, the call was not being completed. This problem was fixed.

2.28.1.5 DR 4888 (AR 1-0954842) - CN (Connected Number) is showing the wrong number
The Connected Number was showing the wrong number when the correct is to be filled with the "Area
Code + B Number".
The Nature of Address Indicator was showing the Subscriber Number when the correct is to indicate the
National Number. These problems were fixed.
2.28.1.6 Caller ID service fails when an incoming call from a MFC signaling route is transferred to
another subscriber into the same switch
When a subscriber A calls to B using a route with MFC signaling, and B transfers to C - since C and B are
in the same switch- if B doesn't have Caller ID service, C's Caller ID only shows A category.
This problem was fixed, by showing the B category and number in C's Caller ID.
Case B has this service too, them A category and number will be shown.
2.28.1.7 Incorrect ring cadence in subscriber programmed with FSK Caller ID

The duration of the first ring pulse in subscriber lines programmed with FSKCAID are incorrect. Some
times this pulse can be greater or less than the time programmed in IRC parameter of MD-TON command.
2.28.2 Remarks
NA.
2.29.1 Updates
2.29.1.1 DR 4887 (AR 1-0951709) - Outgoing calls for the countries that use end of number signal
were not being completed for second choice route
When the subscriber tried to originate an outgoing call with the end of number signal (I15) and the first
route was out of service, the call would have to follow through the second choice route. This was not
occurring when the starting index of the route was greater than the amount of digits of the B number + 1
(end of number digit). In this case, the call was lost. This problem was fixed.
2.29.1.2 DR 4891 (AR 1-0955944) - Connected Number always showed in ANM message
The Connected Number was being showed in the ANM message, even if the parameter CN was not
assigned in the MD-SNLISUP command. This problem was fixed. Now, the Connected Number is showed
only when this parameter is assigned.
2.29.1.3 DR 4894 (AR 1-0954842) - Connected Number in ANM message should be sent only when
requested
The Connected Number was being sent always in ANM message, even when it was not requested by the
IAM message. The problem was fixed. When the CN is assigned in the MD-SNLISUP command, the CN
sending will be defined by IAM message.
2.29.1.4 DR 4898 (AR 1-0961298) - Corrections in the ANI protocol

The problem was occurring when the switch operated in inter-working mode with ISUP/DSS1/R2 incoming
calls and MFshuttle and DP signaling outgoing calls. The Calling Number received from ISUP/DSS1/R2
signaling can have more than 7 digits (area code + Calling Number). However, the ANI protocol used with
DP and MFshuttle signaling supports only supports 7 digits format for the Calling Number. The switch
was always sending the 7 first received digits. Now, it sends the last 7 digits extracting the area code.
2.29.1.5 DR 4900 - Configuration of the Area Code presence in Redirecting Number

The RCNAC parameter was created in the CR/MD-ROUT commands (opp = RCNAC) to assign the
National Code in Redirecting Number. During call transference, if RCNAC is assigned, the Redirecting
Number will be sent with Area Code. Otherwise, it will be sent without the Area Code.
2.29.1.6 Problems with the CLIRO supplementary service

When a subscriber A assigned with CLIRP supplementary service calls subscriber B, assigned with caller
ID and CLIRO supplementary services, the A number was not showed in the caller ID. This problem was
fixed.
2.29.2 Remarks
NA.
2.30.1 Updates
2.30.1.1 DR 4840 – LAN driver and Boot Loader adaptation to use the Encore Ethernet Card
The LAN driver and the Boot Loader were modified to support the RTL8139D Ethernet controller (Realtek
manufacturer) used in the Encore ENL832-TX+ Network Adapter.
2.30.1.2 DR 4905 (AR 1-0959729) - Question about compliance with Q.764 for outgoing calls
(TAM=4)
When the trunk allocation method is four (TAM = 4), changed how to access to the group of circuits the
exchange is non-controlling. Of this group, the latest released circuit (for each BBB) is selected, if all
circuits in the controlling group are busy.
2.30.1.3 DR 4911 - Charging problems for configured country as Argentina

Two problems were occurring when the configured country was Argentina and the originating switch was
not receiving a backward CRG message. The first problem was occurring during the call answering when
the route “charging class” (CHCL) was being changed to "default" (CHCL = 32) while the correct
operation should be to keep the original CHCL. This change would only have to occur if the CHCL was
“External Multi-Metered Call” (EXMM). The second problem was related to the number of pulses
generated automatically when the B subscriber answers the call. The pulse generation was not in
accordance with the NPUL parameter configured in the route CHCL. These problems were fixed.
2.30.1.4 DR 4916 (AR 1-0995307) - Incorrect call release procedure on SLM trunks
The supervision signaling “Clear Backward “ was defined as bit A and B with value ZERO instead of bit
A with ONE and bit B with ZERO. This problem was fixed.

2.30.2 Remarks
NA.
2.31.1 Updates
2.31.1.1 PR 35700 – Removal of all CIS related information

When the connection to the CIS EMS (Element Management System) is lost or the BZ5000 switch is
down, all CIS related information will be removed. Loss of connection to the CIS EMS means: HI1 (CIS
Administration interface) and HI2 (call Associate Data interface) lost connection.
2.31.1.2 PR 44800 – Operator Break In via ISUP Trunks

The functionality Operator Break In via ISUP Trunks was implemented for POTS and ISND subscribers.
It was implemented the Call Waiting supplementary service for local ISDN Basic Access.
2.31.1.3 PR 45000 – CCL message implementation for Russian

During interworking with local switch, when the originating switch clears first it sends a CCL (Clear
Calling Line) ISUP message to the BZ5000 that sends REL (CV=16) back.
2.31.2 Remarks
NA.
2.32.1 Updates
2.32.1.1 PR 33800 – Call Interception System with Supplementary Services interaction for Russian
The Call Interception System (CIS) was implemented for POTS and ISDN subscribers, considering the
interaction with Call Hold, Call Waiting, Call Forwarding Unconditional, Call Forwarding on No
Replay and Call Forwarding on Busy supplementary services.
2.32.1.2 PR 43900 – Russian Country ID Creation

It was created a new country ID for Russian based on the features implemented for the Ukraine.
2.32.1.3 PR 44600 – Disconnection Reasons for Russian LEMF

It was implemented five new disconnection reasons for the Russian Law Enforcement Monitoring Facility
(LEMF). The disconnection reasons implemented were: Abnormal Call Hanging-up, Hang up after
interrupted dialing, party busy, party does not answer and normal disconnection.
2.32.1.4 DR 4928 (AR 1-1003785) – Problem with Redirection Service

The following problems were resolved:

• For programmed countries as Russian and Ukraine, when the Redirecting Number (B subscriber)
is displayed at the IAM message, the Calling Party Number was showing the B number. It was
corrected to show the A subscriber (the originated subscriber).
• A problem occurred when B had Call Forwarding supplementary service and A and B were in the
same switch. In this case, the IAM message from B to C (C in another switch) was not showing the
Redirecting Number.
• Another problem was found related to the presence of National Code in the Redirecting Number.
It was requested for programmed country as Ukraine that the National Code should be shown in
accordance with the RCNAC parameter setting. This was changed for all countries. Now all the
countries use the RCNAC route parameter to set the code number in the redirecting number.
2.32.1.5 DR 4938 (AR 1-1013043) – Switch was resetting when a SEQ and SEQ2 parameters of SEL
had the same values
When a special service SEL was programmed with parameters SEQ and SEQ2 with same values and the
SEQ number was dialed, a loop was generated in switch and it was restarted. This problem was occurring
also when more then one SEL was programmed with one SEQ2 pointing to the SEQ of the other creating a
loop. These problems were fixed.
2.32.1.6 DR 4949 (AR 1-1003785) – The calling party category is not being correctly sent for Ukraine
in forwarding calls
For programmed country as Ukraine, the Calling Party Category in the IAM message of a transferred call
was not correct. It was being showed value E5h, but it should be the originating subscriber category itself.
2.32.1.7 DR 4978 (AR 1-1025831) – Called number info is missing in ASN message
The described problem was resolved in the implementation of the feature PR 44600.
2.32.2 Remarks
NA.
2.33 Revision: 011 – Software Update: -001
2.33.1 Updates
2.33.1.1 DR 4958 (AR 1-1025900) - Problems receiving A6 signal working as a transit exchange with
R2 signaling
While acting as a transit exchange, and using R2 signaling in both incoming and outgoing trunks, when the
switch received A6 signal instead of a A3 B6 sequence, the call was not being properly completed. This
bug was fixed. Now, when the switch receives the A6 signal from the outgoing trunk, it sends A3 to the
originating switch, waits the reception of the category, does not send the category to the outgoing trunk,
and sends B6 to the originating switch.
2.33.1.2 DR 4980 (AR 1-1035600) - Original Called Number field is not correct

In a transferred call the transferring IAM message (from "B" to "C") was sending the Nature of Address
(NoA) of the Original Called Number (OCN) according to the TYPE of the "B" to "C" switch routing
plan. Besides, the OCN was always being sent as a "Subscriber Number". This bug was fixed. Now the
switch sends the OCN and its NoA exactly like it was received from the "A" switch.
2.33.2 Remarks
NA.
2.34 Revision: 012 – Software Update:
2.34.1 Updates
2.34.1.1 PR 41200 - ANI Extension for CIS countries
The Automatic Number Identification (ANI) is a service that provides the receiver of a telephone call with
the number of calling party. The ANI procedure needed to be extended to comply with CIS countries
(Russian, Ukraine, Kazakhstan) specifications. The main implementation is to provisional timers to
interoperate with other switches.
The following new timers were added to MD-CENTMP command:
ANI Timer MD-CENTMP Parameter

To1 TO1ANI
To2 TO2ANI
To3 TO3ANI
To4 TO4ANI
Ti1 TI1ANI
Ti2 TI2ANI
Ti3 TI3ANI
Ti4 TI4ANI
T5min T5MINANI
T5max T5MAXANI
2.34.1.2 PR 44400 - Modification in CDR for Russia market

It was created a new CDR for Russia's country, based on the implemented CDR for Ukraine's software,
with the new field: Pulse Counter.
2.34.1.3 PR 44700 - Target Priority For CIS Russia*

The Call Interception System (CIS) is a switch-based mechanism for a Telecommunications Service
provider to deliver intercepted call content (e.g., voice, packet data, Modem data) and Call Associated Data
(CAD) information to authorized agencies.
Whenever a target originates or receives a call, it should be intercepted and the call contents should be sent
through available trunks to Law Enforcement Monitoring Facility ( LEMF).

PR 44700 defines two priority levels to intercepted targets: high priority and low priority. If a high priority
target originates or receives a call, and there is no available trunk to communicate to LEMF, a low priority
intercepted call shall be dropped, and the released trunk should be used to intercept the high priority target
call.
2.34.1.4 DR 4914 - Modem PCI card driver implementation

Driver implementation to the new Modem PCI card, model 3CP5610A produced by 3COM manufacturer.
2.34.1.5 DR 4924 (AR 1-1016189) - Problems with calling address displaying in R2D signaling for
Argentina
A problem was occurring in calls with R2D signaling for Argentina. In the calls that were necessary to
send the calling address, it should be sent "C" digit when the number could be displayed and "F" if it was
restricted. However those digits were inverted. The "C" digit was being sent when the display was restricted
and "F" when it was allowable. This bug was fixed.
2.34.1.6 DR 4959 (AR 1-1016206) – Problem in transferring of calls when the number of digits is less
than the start index
For countries that use end of number digit (0x0F), the calls for subscribers with transfer supplementary
services should be forwarded independently of the start index value. Those calls were being transferred only
when the start index was equal to or shorter than the length of the programmed sequence plus one. This bug
was fixed.
2.34.1.7 DR 4960 (AR 1-1029695) - The connected number is displayed with 0xA instead of 0x0
The switch is sending 0xA instead of 0x0 in connected number parameter. This bug was fixed.
2.34.1.8 DR 4961 (AR 1-1029703) - The redirecting number is displayed with 0xA instead of 0x0
In forwarded calls the redirecting number was being displayed with 0xA instead of 0x0. This bug was
fixed.
2.34.1.9 DR 5019 (AR 1-1058090) - No ASN messages for target subscribers

In some cases we do not receive ASN messages about particular targets. After more deep investigation we
understood that the problem is in two last digits of a target subscriber phone number.
If subscribers are in numbering range XXXXX00-XXXXX39 they can be set under control and everything
works properly. If subscribers are in numbering range XXXXX40-XXXXX99 we do not receive ASN
messages for such subscribers.
2.34.2 Remarks
2.35 Revision: 013 – Software Update:
2.35.1 Updates
2.35.1.1 PR 43000 – Calling Line Identification Presentation (CLIP) service for Philippines

The calling party category will not be sent in the Calling Line Identification Presentation (CLIP) service
when Philippines is the current country. This modification affects BZSP.
2.35.1.2 PR 43200 – Calling Line Identification Presentation (CLIP) service for Philippines
when Philippines is the current country. This modification affects BZ5000.
2.35.1.3 PR 48100 (AR 1-0996637) – Remove the category of subscriber A in the caller ID for
Argentina
when Argentina is the current country. This modification affects BZ5000.
2.35.1.4 PR 52000 - ANN after the ACM message

The switch will send the ANN after the ACM message, if the incoming calls via TUP are routed to the
internal Announcement Machine Trunk and if the target subscriber is in the blocked operational state (STE
subscriber parameter = BLK).
The ANN message is necessary to improve the indicator of completed call answer by BZ5000
2.35.1.5 DR 4929 (AR 1-0961400) - The time slot information (CIC) is not being populated in the
CAD register for R2 signaling
When call interception service was programmed, the time slot information (CIC) should be populated in the
CAD register, but it only occurred for ISUP signaling. This bug was fixed. Now, the CIC information is
shown for R2 signaling when country is programmed as Russia.
2.35.1.6 DR 4951 – Error in the CLKTYP parameter in command MD-SYNCOPP

The product BZ-SP has no support to Clock type R1, and the parameter CLKTYP with value R1 in
command MD-SYNCOPP was normally acceptable. This problem was solved.
2.35.1.7 DR 4963 (AR 1-1014284) - Problems on special local services

A subscriber, whose class has originating restriction (RTO) to a call type (TYP), originates a call to a
programmed sequence with special local service (LSS). This LSS is programmed to call an outgoing
sequence, whose TYP, configured on the routing plan, is the same of the subscriber's RTO. The call was
being blocked. This bug was fixed.
2.35.1.8 DR 5015 (AR 1-1057011) - Problems with multiple transfers

The call forward service was not working correctly when countries that allow multiple transferences were
programmed at the switch. The problem was occurring in intra-switch calls, when only one transfer was
happening. This bug was fixed. Now, Argentina and Indonesia are allowed to make until 5 transferences.
2.35.1.9 DR 5016 (AR 1-1058116) - Wrong charging on SEL services

When SEL (Especial Local Service) was programmed, the charging was following the parameters of the
second sequence .The correct charging process is to follow the parameters programmed in the first
sequence. This problem was solved.
2.35.2 Remarks
NA.
2.36 Revision: 014– Software Update:
2.36.1 Updates
2.36.1.1 PR 44500 - Deferred Charging Timer for Russia market
The BZ5000 allows deferred charges for outgoing calls on route basis. The timer is used for Detailed
Billing and Multimetering. The charging and/or billing is started only when timer is expired, and the timer
is started when the switch receives the answer signal.
The value of this timer is provisional through BZ-VIEW system and is available for Russian market only.
The CR-ROUT and MD-ROUT commands were changed to include the optional DCT parameter. The
Deferred Charging Timer parameter is valid only for outgoing routes and defined in seconds, the valid
range is 0 up to 60 seconds with step of 1 second. The default value is 0 (zero) seconds.
If the DCT parameter is defined in CR-ROUT or MD-ROUT commands when BZ5000 is in use for no
Russian market, the BZ-VIEW will display the error message "Parameter is not allowed to the programmed
country"
2.36.1.2 DR 5003 (AR 1-1049252) - NPUL parameter is not working correctly

The number of charging pulses on answering, defined in the NPUL parameter, was not correctly sent to the
pay-phones configured with PSV=FREQ. This bug was fixed.
2.36.1.3 DR 5005 (AR 1-1055466) - Redirecting Information with wrong fields

The Original Redirection Reason information and the Redirection Reason information were wrong. After
the modification, the Original Redirection Reason receives the value of the first call transfer and the
Redirection Reason receives the value of the last call transfer. When the number of call transfers is1 (one),
only the first octet (Original Redirection Reason) is sent.
2.36.1.4 DR 5020 (AR 1-1029715) - Problems with SS7 link uninhibition

The BZ5000 is connected to another network point by a SS7 link set with two links.
The inhibition of a link seemed to work properly, but after asking the link uninhibition by BZ-VIEW
command, the BZ5000 was not sending LUN message and was showing the answer in BZ-VIEW: "Error
not expected". This bug was fixed.
2.36.1.5 Wrong message in HSTCEN log for GR-MSGDSP and COP-MSGDSP commands
When the commands "GR-MSGDSP" and "COP-MSGDSP" were executed in BZ-VIEW, the event log
(HSTCEN) was registering "Initialization of controller program copy". Now, the BZ-VIEW registers
"Initialization of voice message file copy".
2.36.1.6 CDR – Russia – Wrong code for subscriber password programming service
When programmed country is Russia, it’s shown for the CDR’s ssu field the value 14 for subscriber
password programming.
2.36.2 Remarks
It will be necessary to reconfigure the exchange to update to this release.

2.37.1 Updates
2.37.1.1 DR 4901 - Call Hold – Switch doesn’t send message hold and retrieval reject while
subscriber B is ringing.
When an ISDN subscriber calls another subscriber and tries to send a HOLD or RETRIEVE message
while subscriber B is ringing, in this moment, the switch sends a message STAT. The correct process is
sending a message HOLD_REJECT or RETRIEVE_REJECT to ISDN subscriber with the reason value
equals to 101 (message type not compatible with call state). This bug was fixed.
2.37.1.2 DR 4902 - Call Hold – CPG message of the protocol ISUP was not been sending
In a normal call using ISUP protocol, if a HOLD or RETRIEVE requesting is required by an ISDN
subscriber, the switch needs to send a CPG message with indicator parameter field fill with REMOTE
HOLD or REMOTE RETRIEVE, and the destination switch needs to send a NOTIFY message to the
ISDN subscriber in both requests. But BZ5000 was sending only a RESUME message on ISUP protocol
when a RETRIEVE was request and in the destination switch receives the RESUME message and sends a
NOTIFY to the subscriber. This bug was fixed.
2.37.1.3 DR 4903 – Call Hold – Problem with 3 ISDN terminals are plugged in only one BRI access
point
If two ISDN terminals are proceeding a call, and one of those terminals request a HOLD and at the same
time the third ISDN terminal hook off, the terminal that request a HOLD can’t proceeding the call, because
the switch blocked it sending “no circuit available”. This bug was fixed.
2.37.1.4 Wrong billing record for the “Do Not Disturb” service
The fields ASSB and CATA for billing record generated when subscriber had “Do Not Disturb” service
were wrong. ASSB field was being filled with “Do Not Disturb” service code and CATA with “11”.
Changes were made so that for Russia and Ukraine, ASSB and CATA fields are filled with number of
subscriber B and A’s category.
2.37.1.5 The forwarded call (initial leg) was not been billed in incoming call.
When the call was terminated in a subscriber with call forwarding service active and this subscriber has
billing service programmed, any bill was generated for the forwarded call (initial leg). This bug was fixed.
2.37.2 Remarks
Not applicable.
2.38 Revision: 015– Software Update: 001
2.38.1 Updates
2.38.1.1 DR 5086 - Overlap is not working when more than 16 digits are received

The BZ was sending more than 11 octets in the IAM called party number parameter, but the SS7
standard allows the maximum of 11 octets. This bug was fixed. Now, the other digits are sent through the
SAM message.
2.38.1.2 DR 5087 - The NOA of the calling party address is incorrect for international transit call
In an ISUP - ISUP international transit call, the BZ is always changing the calling party NOA according to
the routing plan. It should happen only if the incoming call had calling party NOA as local. This bug was
fixed.
2.38.2 Remarks
Not applicable.
2.39.1 Updates
2.39.1.1 PR48000 (AR 1-1018766) – MCT over CAS signaling for Russia Market
The MCT service allows the registration of incoming call information (e.g. calling number) upon
subscriber requesting. The subscriber can invoke the registration during the established call (in
conversation state) or after the calling subscriber release the call, when the called subscriber has TSUPT
time to invoke the registration.
The MCTD (Malicious Call Trace on Demand) supplementary service is provisionable by BZ-VIEW,
using MML commands (PR/RP/IT-SSV) already known. The service is invoked by subscriber dialing the
access code *39#, after flash (during conversation) or off hook (after call released). The access code can be
changed by BZ-VIEW using the SRV commands.
The TSUPT (Trace Supervision Timer) timer can be changed by BZ-VIEW. The default value to TSUPT
is 15 seconds and its range is 0 up to 60 seconds with steps of 1 second.
The service is supported to ISUP, R2D, DP1, DP2 and MFSH signaling, where the DP1, DP2 and MFSH
signaling has to use SL or ZSL protocols which has the ANI REQUEST procedure implemented.
The registered information is available by BZ-VIEW which has the following data:
- Calling Party Number;
- Called Party Number;
- Local time and date of the call;
When the Calling Party Number is not available, the BZ5000 switch will inform instead:
- Origination Point Code (OPC), Incoming Route, and Circuit ID Code (CIC), when the
incoming call comes over ISUP signaling.
- Incoming Route, and used trunk number, when the incoming call comes over CAS signaling.
2.39.1.2 DR 4867 - Problems with V5 interface

After creating a V5 interface between an LE and an AN switch, both in operation mode, the ISDN
subscribers were not allocating channel. For the correct working of these subscribers, it was necessary to
block and unblock the V5 interface in the LE side. This bug was fixed.
2.39.1.3 DR 5093 – The OCN in the IAM message was incorrect for Bolivian market
The OCN parameter in the IAM message was filling in with the forwarding subscriber number instead of
the calling subscriber number. This bug was fixed.

Only for information, the countries Argentina, Bolivia, Indonesia, Russia and Ukraine have the same
implementation as described above, and the other countries fill in OCN parameter with the forwarding
number.
2.39.2 Remarks
It will be necessary to reconfigure the exchange to update to this release.
2.40.1 Updates
2.40.1.1 DR 5080 (AR 1-1075937) - CIS. Dialled digits in ASN messages

An ASN message contains the called party number, which is represented as a sequence of bytes. As an
example, the number 9813333 is represented as 0x09 0x81 0x33 0x33 (09813333). When the number of
digits of a called party number is odd, then the sequence is adjust with digit “0” in the first or last digit, but
it is rather difficult to decide if the first and the last 0 have a meaning or not. The solution is the
meaningless is always the first digit in the sequence, and number “F” must represent this digit.
2.40.1.2 DR 5094 (AR 1-1130803) - Interworking problem in signalings MFSH

In local interworking calls (non DDD or IDD call), which an incoming trunk is configured as MFSH
signaling, the "start index" must also be configured with the same number of digits of the route this trunk
belongs. This is necessary because this kind of call must not send a B2 backward signal after it has
received all the digits to routing the call in the outgoing trunk. BZ5000 as a transit exchange must receive
all the digits from originating exchange, sends a B4 backward signal and then sends all digits to terminating
exchange. For long distance call (DDD or IDD), "start index" has the BZ5000 normal function.
2.40.1.3 DR 5095 (AR 1-1140655) - R2D -> ISUP interworking problem

In Ukraine and Russia standards, the A number can be requested by transit switch after it receives the first
digit of the called number. Normally, BZ5000 as transit switch, requests the A number only when it starts
to routing the call in outgoing trunk, defined by “start index” in the MD-ORP command. To solve this
problem, the A number now can be requested after has received the X digits, where X is defined in the ANI
= X parameter in the CR-ROUT command.
2.40.1.4 DR 5116 (AR 1-1117372 - Problem in International collected calls

The TUP call was being dropped before answer signal. This bug was not happening in SW
LPN109253856.006.002, but happens in SW LPN109253856.013.000. The SS7 timers were adjusted
because the time division was changed when PR41200 was implemented (this PR was released on SW
LPN109253856.012).
2.40.2 Remarks
Not applicable.
2.41.1 Updates

2.41.1.1 DR 5102 (AR 1-1142191) – MF-Shuttle signals B1, B2 and B3 can not be programmable
It was created a new parameter, called FBS – first backward signal, in the CR-ROUT and MD-ROUT
command, which acceptable values are 1, 2 or 3. This paramenter can be programmable only in
bidirectional or incoming routes, and it is used only in trunks using MFSH signaling. The parameter can be
checked with IT-ROUT command. If this parameter is not defined, then MFSH will be started with B-1
signal.
2.41.1.2 DR 5120 (AR 1-1150012) – SS7->DP1/RTR interworking does not work

BZ5000 was sending a ST signal received from SS7 trunk as a valid digit in the DP1 trunk (ST signal has
the value 15). This bug was fixed.
2.41.1.3 DR 5130 (AR 1-1166295) – Problem with MFSH->DP1 interworking

BZ5000 was sending B9 signal in the MFSH incoming trunk when the interworking call was using a DP1
outgoing trunk. The correct signal must be B4 because BZ5000 must receive all incoming digits before
sending these digits in the outgoing trunk. This bug was fixed.
2.41.1.4 DR 5133 (AR 1-1140655) – R2D -> ISUP interworking problem

BZ5000 was asking for more digits sending B1 signal in the R2D incoming trunk after receive a end of B
number (signal 15), and end of B number was sending in SAM message to SS7 outgoing trunk. This bug
was fixed. This problem is the same reported in DR 5139.
2.41.1.5 DR 5138 (AR 1-1190523) – MCTP service cannot be assigned if country=RUS

The MCTP (Malicious Call Trace Permanent) feature must be available as already implemented to Russia.
2.41.1.6 DR 5139 (AR 1-1190520) – R2D routing to SS7 billing problem

BZ5000 was asking for more digits sending B1 signal in the R2D incoming trunk after receive a end of B
number (signal 15), and end of B number was sending in SAM message to SS7 outgoing trunk. This bug
was fixed. This problem is the same reported in DR 5133.
2.41.2 Remarks
It will be necessary to reconfigure the exchange to update to this release. See the item 3 – Compatibility
to check which element management must be used with this release.
2.42.1 Updates
2.42.1.1 DR 5150 (AR 1-1217051) – MCT calling party number field

The switch was showing "?" at the MCT report when it received "F" on the called party number. This
problem was fixed and now, only the called party number appears, without the "F" character.
2.42.1.2 DR 5151 (AR 1-1219501) – Incorrect subscriber category mapping for R2/ISUP
The category II-12 was been translated to ISUP category 228 for Russia and to ISUP category 10 for
Ukraine. But, in both countries II-12 must be mapped to ISUP category 228. This bug was fixed.

2.42.2 Remarks
Not applicable.
2.43 Revision:017 – Software Update: -
2.43.1 Updates
2.43.1.1 DR 5143 (AR 1-1198366) - Trunk disconnection procedure error on RTL and RTR trunks
with DP1 Signalling
The BZ5000 was sending RELEASE GUARD and waiting for a RELEASE GUARD to complete the
release procedure in trunks with DP1 signalling. It was an error because the DP1 signalling does not use
the RELEASE GUARD signal. This bug was fixed.
2.43.1.2 DR 5149 (AR 1-1210612) - BZ5000 unblocks previously blocked trunks after an ISUP
incoming test call.
When BZ was receiving an ISUP incoming test call on a blocked trunk, it was completing the call and
changing the blocked status to in service status after the call. This approach must be made only for normal
cal, in accord to Q.764 ITU-T standard. This bug was fixed.
2.43.1.3 DR 5156 (AR 1-1219490) - R2-MFSH interworking fail

BZ was requesting next digit of B-number by sending A-1 signal after receiving the I-15 signal. This bug
was fixed.
2.43.1.4 DR 5157 (AR 1-1230678) - R2D-DP1 interworking fail

BZ was requesting next digit of B-number by sending A-1 signal after receiving the I-15 signal. This bug
was fixed.
2.43.1.5 DR 5158 (AR 1-1233773) DP1 trunk left in SRV BLE status after finishing the call
Sometimes, the DP1 trunk was not been released correctly in abnormal routing. This problem is due to the
problem described in DR 5143. This bug was fixed.
2.43.1.6 DR 5166 (AR 1-1245447) – Fail when creating a V5.2 link with SLC equals to 0
When assigned the value 0 to the SLC of a V5.2 link on both AN and LE sides, the link wasn’t entering in
service. This bug was fixed.
2.43.1.7 CLIRP fail when calling from a POTS subscriber to PRI or BRI subscriber
This bug was fixed.
2.43.1.8 Blocked Trunk by TMR/AHT fail being alocated in SS7 calls

This bug was fixed.
2.43.1.9 The “address presentation restricted indicator” not treated correctly in interworking call,
when the outgoing call uses R2D signaling.

BZ5000 was sending “F” signal as “end A number indicator” in interworking call. This signal must be sent
only when “address presentation restricted indicator” is active. Otherwise, BZ5000 must send “C” signal
when “address presentation restricted indicator” is inactive. This bug was fixed.
2.43.1.10 Fail in CR-SUB command creating BRI subscribers in MAP2’s secondary trunk
BZ5000 was creating BRI subscribers in MAP2´s secondary trunk, independently if the secondary trunk
was provisioned or not. This bug was fixed.
2.43.1.11 Fail in CR-SUB command when creating more than 144 BRI subscribers
The switch was beeing reseted when more than 144 subscribers was been created. This bug was fixed
2.43.1.12 When creating two trunks with route DP1 separeted with “&”, the second trink is created
with CIC=31
This bug was fixed.
2.43.2 Remarks
2.44 Revision:017 – Software Update: 001
2.44.1 Updates
2.44.1.1 DR 5164 - SUPSS7 for remote ISDN subscribers was not working
It was detected that no call trace data was being displayed on supervision screens for remote ISDN
subscribers. This problem was fixed, and for remote subscribers, the value of ter (xx-xx-xxx) now
corresponds to unit-ep-pos.
2.44.1.2 DR 5169 (AR 1-1252410) - The multimetering pulse cadence sent by switch to payphone was
in a wrong frequency
The multimetering pulse cadence sent by switch to payphone was not correct. At some moments, the card
credits for payphones were being decremented, approximately, every second. The pulses, generally, must be
sent every 4 minutes. The multimetering pulse cadence sent by switch to payphone is now on the right
frequency. The card credits for payphones are being decremented according to the programmed cadence
and pulse sent.
2.44.1.3 DR 5181 (AR 1-1255380) - Call forwarding on busy was not working for BRI subscribers
The TRFBSY service could be properly assigned and activated to the BRI subscriber. But, while using the
both B channels by, for example, starting two calls from the subscriber, a third call to this subscriber was
not forwarded to the programmed destination. This problem was fixed.
2.44.2 Remarks
NA

2.45.1 Updates
2.45.1.1 Corrections in OCP/BLQ led operation

The OCP/BLQ led in JTS or JTSB board should be in red when all channels are blocked. This bug was
fixed.
2.45.1.2 The release cause indicatorrecorded in CDA(call data) was wrong for immediate diversion or
call diversion on busyl
The release cause indicator for immediate diversion or call diversion on busy always was 3 (called busy)
instead was 5 (normal disconnection). This bug was fixed.
2.45.1.3 Corrections in Call Waiting service

The Call Waiting service was not working correctly when subscriber assigned to the service tries to answer
the second call dialing a digit different from ONE or TWO. This bug was fixed.
2.45.1.4 DR 5186 (AR 1 –1254910) – For all outgoing calls via ISUP trunks, when B-party
disconnects, BZ switch was replying with a REL=102.
For all outgoing calls via ISUP trunks, when BZ receives a REL=16 (Normal Call Clearing) from far-end
switch, it replies with a REL=102. This bug was fixed.
2.45.1.5 DR 5171 (AR 1 –1255295) – (Russia FOA) CDR's INROUT/OUTROUT fields show wrong
route values.
During Russia FOA it was found following problem on CDR generated by Detailed Call Record
Supplementary Service or by parameter BILSYS in dialing plan (this problem does not appear on CDR
records generated by MCT services). For outgoing or incoming calls on BZ switch, the INROUT and
OUTROUT fields of the CDR records show wrong values. The values showed are trunk number instead of
rout number. This bug was fixed for Russia and Ukraine.
2.45.1.6 DR 5172 (AR 1 –1255297) – CDR END CAUSE field shows wrong value for calls
disconnected by B-party
The END CAUSE field in CDR records is wrong populated, for the case in which the call is disconnected
by the B-party. During FOA testing in Russia, it was found that for all calls in which B-party disconnected,
the value "3" was stored in CDR records instead of "2". This bug was fixed.
2.45.1.7 DR 5175 (AR 1 –1255306) – For BRI subscribers, a new programming of EXELIN service
by keypad is not overriding the previous
The Timed Hot Line service was not working correctly for BRI subscribers. This bug was fixed.
2.45.1.8 DR 5193 (AR 1 –1274868) – Problem in the "Special Service Indicator" field in AMA147
records
Now, the "Special Service Indicator" field in AMA147 records of BZ switch is properly filled according to
the AMA147 CSD (Brazil LOCAL/TOLL CALL ACCOUNTING - 147 byte format - CSD 719 Issue 1.0
- March 10, 2000).
Table B.34
Service Indicator
EBCDIC Format
Character
2 00 = Normal Call
01 = Call Forwarding Unconditional
02 = Call Forwarding No Reply
03 = Call Forwarding Busy
04 = Call Forwarding Mobile Subscriber Not Reachable
05 = Call Waiting
06 = Call Hold
07 = Multiparty or Three-Party Calling
08 = Calling Line ID Presentation
09 = Calling Line ID Restriction
10 = Incoming Call Barring
11 = Outgoing Call Barring
12 = Alarm Call Service
13 = Hot Line
This implementation considers remote and local subscribers, POTS and ISDN subscribers.
The following services are supported for originating calls: Call Forwarding Unconditional, Call Forwarding
No Reply, Call Forwarding Busy, Multiparty or Three-Party Calling, Alarm Call Service, Hot Line.
The following services are supported for incoming calls: Call Waiting, Call Hold, Calling Line ID
Presentation, Calling Line ID Restriction.
Ours understanding about the “Multiparty or Three-Party Calling” indicator is that this indicator has to be
set in the billing record when the subscriber are using one of the following services: Call Consulting service
or Call Transfer service or Three-Party Calling service.
Call Waiting and Calling Line ID indicators will not be support for local calls.
BZ switch does not support “Call Forwarding Mobile Subscriber Not Reachable” service, so this indicator
will not be treated.
Currently, BZ switch does not charge the “Incoming/Outgoing Call Barring” service, so both indicators
will not be treated as well.
As the “Alarm Call Service” is not working to ISDN subscribers the corresponding indicator is still not
being treated.
The “Hot Line” indicator will be set in the billing records when the subscriber is using the Hot Line and
Warm Line service.
When the subscriber has “Call Waiting” and “Calling Line ID” services provisioned and both services are
used simultaneously, the “Calling Line ID” indicator has priority about “Call Waiting” indicator.
2.45.2 Remarks
NA

This release is related to BZ11.0 Project.
2.46.1 Binary files used at boards
S95092B1.BIN MPS DSPs boot file for tone generation

S95083D5.BIN MPS DSPs boot file for tone detection
S98146A2.BIN MAB software
S99004A3.BIN MAP software
S98114A3.BIN JTS software
S00050A6.BIN Memory image of MTL-B DSP software
D00050A6.BIN Memory image of MTL-B DSP data
S00019A5.BIN MPS-C DSPs boot file for tone generation
S00020A1.BIN MPS-C DSPs boot file for tone detection
S01166A8.BIN MPS-C DSPs boot file for signal detection/generation
S01151A1.BIN Memory image of MTL-B v2 DSP software
D01151A1.BIN Memory image of MTL-B v2 DSP data
SMAPBV01.BIN MAPB software
2.46.2 Updates
2.46.2.1 PR55700 - OA&M Improvements (alarms)
The PR55700 will allow the alarms to be filtered by the switch during the Operation Log transference to
BZ-VIEW. This filtering will be based on the severity of alarms (urgent, semi-urgent, non-urgent and
occurrences) and on its contents (only present alarms will be transferred or all of them), and it will be
configurable by the command MD-ALACONFIG. It will also be possible to configure a threshold for the
Operation log by the same command. If this threshold is reached the alarm transference process will be
started. This PR will also implement a command to activate an urgent alarm in order to start the
transference process for testing purposes: EX-CSRCAL and it will also support the execution of the
command IT-ALARMLOC in CSR Standalone as it is supported by BZ-VIEW.
New commands implemented:
- For alarm transference configuration:
MD-ALACONFIG: [ TYPE = { PRES | ALL } ] [, ASE = { UR | SU | NU | ALL } ] [, THRHLD = 50..90];
- For displaying alarm transfer configuration parameters:

IT-ALACONFIG
- For generating a test alarm:
EX-CSRCAL
2.46.2.2 PR60600 - MCTD FIXING FOR RUSSIA (AR 1-1190556), EXTEND MCT/MCTD FOR
UKRAINE.
The MCT service was extended for Ukrainian (UA) market. The activation of the MCTD service could be
done under two ways: dialing FLASH only or dialing FLASH plus the entire access code, *39# by default.
The selection was made by country profile, and now this selection is made by a switch operating parameter
(MCTCOD). These parameter and new activation mode are only available for Russian and Ukrainian
Markets.
2.46.2.3 DR 5119: PR48000 - MCT in interworking mode

The ANI protocol was not being handled at BZ5000 in interworking mode. This bug was fixed and the
default value for timer To2ANI has been changed to 500 ms.
2.46.2.4 DR 5205 - AR 1-1293415 - Calls to the second switch prefix are not successful.
On ETC's numbering plan, subscriber will dial 10 digits for every call, including intra-switch call. The
issue is that BZ is treating wrongly intra-switch calls with 10 digits, if there is more than one prefix
created.
Solution: In the intra-switch calls with 10 digits, the BZ compares the dialed digits with the area code and
the prefix, instead of the prefix only as in the previous implementation. The function verifies if the digits
sequence is related to some created prefix and if it doesn’t find the correspondence, it redirects the call to
the first prefix on the heap.
2.46.2.5 DR 5206 - Incorrect OCT value for test subscriber for Ethiopia
For Ethiopia, the OCT value for the test subscriber was corrected to (6) instead of (3), as well the OCT
value for data communication subscriber was corrected to (12) instead of (6),
2.46.2.6 BZ5000 sends signal B7 for busy ISDN BRI subscribers in R2D incoming calls
For R2D incoming calls to a busy ISDN BRI subscriber BZ5000 was sending back signal B7. The correct
signal is B2. This bug was fixed.
2.46.2.7 Fault when creating MTL and MTLB boards without link associated.
It is not being possible to create MTL and MTLB in the central without link associated. This bug was
fixed.
2.46.2.8 Problem in the analysis of the 12 KHz signal during the MTL board test
The problem occurred because the new MTL board tolerates a larger range of voltage values for the 12
KHz signal, then the old one. The software was fixed and this new range of values is now being used.
2.47.1 Updates
2.47.1.1 DR 5158 (AR 1-1233773): DP1 trunk left in SRV BLE status after finishing the call
DP1 trunk was left in SRV BLQ status when the call is terminated due ANI package was evaluated as non-
correct and the rout is configured with ANIREQ operational parameter. This bug was fixed.
2.47.1.2 DR 5208 (AR 1-1297520): Announcement recording through COP-MSGDSP command is

not successful.
When using the procedure to create an announcement message file by command (RE-MSGDSP) then use
the same file to copy the announcement messages to another MPS board in another switch by command
(COP-MSGDSP) then verify the messages recorded we found that there are no messages there are only
noise. In fact, the RE MSGDSP was not correct. This bug was fixed.
2.47.1.3 Corrections on OCP/BLQ led operation

The OCP/BLQ led in JTS or JTSB board should be in red when all provisioned channels are blocked. This
bug was fixed.
2.47.2 Remarks
Not applicable.
2.48.1 Updates
2.48.1.1 IT-BILHST doesn´t return an answer to BZ-VIEW.

The command IT-BILHST didn’t return a response to BZ-View when there is no Billing Unit created in
BZ5000. It was necessary to cancel the command execution to release BZ-View. This bug was fixed.
2.48.1.2 The usage percentages of the Originating Traffic Routing Plan tables are being wrongly set
to zero.
The percentage of the memory space - reserved for originating routing plan - currently in use presented by
IT-ORP command was wrong. This bug was fixed.
2.48.2 Remarks
Not applicable.
2.49.1 Updates
2.49.1.1 DR 5172 (AR 1-1255297): CDR's END CAUSE field shows wrong value for calls
disconnected by B-part for Russia and Ukrainey.
The END CAUSE field of CDR's records generated by Detailed Call Record Supplementary Service or by
parameter BILSYS in dialing plan is being populated with the value 3 when the B-party subscriber
disconnects the call. The correct value is 2. The value 3 means network failure. This bug was fixed.
2.49.1.2 DR 5232: Wrong calling party number in a CPCT group

When a subscriber, member of a CPCT group, receives an incoming call and manually transfers it to
another number, the “Calling Party Address” in the IAM ISUP message is not been populated with the key
number of the CPCT group, although the CPCT group was provisioned to charge on the key number.
Moreover, the “Redirecting number” field was not supposed to be in the IAM ISUP message for this
scenario. This bug was fixed.
2.49.1.3 DR 5236: The SUPCHA and the SUPSS7 are losing messages.
The SUPCHA and the SUPSS7 are losing messages when the RAM has little free space. This bug was
fixed.
2.49.2 Remarks
Not applicable.

2.50.1 Updates
2.50.1.1 DR 5234 (AR 1-1326334) - Some calls have crossed audio

Boliviatel customer is noticing some calls that go thru BZ5000 had crossed audio with others, from the
time after the last digit is dialed until B-party answers the call. This problem was being noticed on about
15~20% of calls, on several different call scenarios (mobile-fixed, fixed-fixed, fixed-mobile, etc...). This
bug was fixed.
2.50.1.2 DR 5250 (AR 1-1353810) - When abbreviated dialing service is active, calls to special
services numbers (SSN) with 2 digits number length can't be completed for Russia and
Ukraine
BZ5000 was waiting for # symbol to complete digit collection. The correct sequence to use abbreviated
dialing service in Russia and Ukraine is ** NAb, where NAb = 0, 1, 2, ... 99. This problem was fixed.
2.50.1.3 DR 5255 (AR 1-1370442) - Unrestricted Called Party Number length should be supported
The Called Party Number length in IAM message was being limited to the range 4 to 11. This should be
applicable only to ARGENTINA country. This bug was fixed.
2.50.1.4 BZ5000 do not accept the TYP equal to V35 at semi-permanent connection creation. Only RS
is available.
The PR-CSP command was changed to include the parameter TYP
PR-CSP : CSP = xx, { TER1 = xx-xx-xx, TER2 = xx-xx-xx |

TER1 = xx-xx-xx, TRK1 = xx-xx-xx |
TER1 = xx-xx-xx, RMT1 = xx-xxx |
TER1 = xx-xx-xx, IBT = xx-xx, TYP = xxx |
TRK1 = xx-xx-xx, TRK2 = xx-xx-xx |
TRK1 = xx-xx-xx, RMT1 = xx-xxx |
TRK1 = xx-xx-xx, IBT = xx-xx, TYP = xxx |
TRK1 = xx-xx-xx, MPSB |
RMT1 = xx-xx-xx, RMT2 = xx-xxx } ;
- TYP: type of IBT interface. It can assume the values V35 (V35 interface) or RS (RS-232
interface).
2.50.2 Remarks
Not applicable.
2.51.1 Updates
2.51.1.1 DR 5250 / DR 5266 (AR 1-1353810) - When abbreviated dialing service is active, calls to
special services numbers (SSN) with 2 digits number length can't be completed for Russia
and Ukraine
When ABDIAL is active, calls to special services numbers (SSN) can't be completed. SSN in Ukraine
and Russia can be 2 (police, fire prevention, emergency) and 3 (information services) digits number
length. When subscriber with abbreviated dialing service dials two digits SSN he hears silence and after
that call is released on time-out. Calls to three digits SSN can be completed without any problems. This
bug was fixed.
2.51.1.2 DR 5265 (AR 1-1400937) - The "Calling Party Category" should not be sent to "Caller ID
device" at Russia market
In Russia, subscriber category should not be displayed to called party. This bug was fixed.
2.51.1.3 DR 5259 (AR 1-1376691) - On DP1/DP2/MFSH x ISUP calls, the area code is not included
at Calling Party Number, even if programmed properly.
BZ5000 doesn't add prefix to calling party number in case of DP2 -> SS7 interworking. Prefixing
(OPP=CNAC) works fine for SS7 -> SS7 interworking scenario. I assume that calling number prefixing
also doesn't work for MFshuttle -> SS7 and DP1 -> SS7. This bug was fixed.
2.51.1.4 DR 5248 (AR 1-1342189) - Hanging up inter and intra-module links

The customer observs very strange situation on his BZ5000: from time to time all trunks on unit 1 got to
be unuseable. If the call comes on ISUP7 trunk, it's released with CV=34. Incoming DP1 calls are just
released by BZ5000. At that time all trunks are in service and in IDLE state. It was not clear what
happens, and this situation can be resolved only with BZ-5000 init or unit 1 init: ex-reset:unit=1. The site
engineer found the command it-regsup, what output that when so situation is observed, all inter and intra-
module links on unit 1 are busy. As there is no busy trunks at this unit 1, we made a conclusion that all
links are hung-up. This bug was fixed.
2.51.1.5 DR 5247 (AR 1-1342133) - Sometimes DP1 trunks are left in SRV BLE state
After BZ-5000 implementation into the real network it was found by the customer the following problem:
sometimes DP1 trunks are left in SRV BLE state. On the end of rural exchange this trunk is idle. If
release signal is send from rural exchange (pulse more than 250 ms, with analog exchange it’s very easy
to realize), the trunk immediately get be unblocked and in some seconds is blocked (BLE) again. It
cannot be restored to service in other way than to make "ex-reset:board=1-5" for a whole board. This bug
was fixed.
2.51.1.6 DR 5237 (AR 1-1326099) Incoming DP1 toll call with incorrect ANI
BZ receives SZR on DP1/RTR on ZSL interface (DDD call) and provides second dial tone - according to
POP=SECTON parameter on DP1 route. This second dial tone is provided by BZ upon seizure . After
seizure BZ also starts ANI request procedure, receives ANI packet and evaluates its correctness. This
procedure takes rather long time (sometimes few seconds). But as A-subscriber (on rural exchange) got
second dial tone, he continues to dial further digits of B-number. BZ receives this digits , analyses them
and routes the call to outgoing C7 trunk, in IAM BZ sometimes even includes CgPN parameter with
some digits taken ,may be, from buffer. So, some stages of call setup are carring by BZ simultineously -
it requests ANI and at the same time routes the call to outgoing trunk.
As soon as BZ evaluates ANI as incorrect , it releases the call (sends release pulse to DP1 and to C7
trunk as it's already seizured) . The ANI procedure takes sometimes so long time that it's enough for call
to be routed to far-end, and even be answered for very short time ,- if far-end does not make A-number
checks. If far-end makes A-party checks, it releases the call without answering, etc. So, further call
scenario depends on many conditions.
The cause of this problem is that BZ provides second dial tone in incorrect place of call setup process:
according to ZSL interface standarts it has to provide SECTON after(!) ANI package check and if ANI is
evaluated by BZ as correct. Or- let BZ provide dial tone as now - upon seizure and before ANI is
checked, but collect B-party digits in some buffer and route the call to outgoing trunk only after(!) ANI is
evaluated as correct. Until ANI check procedure has finished BZ has NOT seizure outgoing trunk. This
bug as fixed.

2.51.1.7 Fault in the incoming call routing based on CTO parameter for DP1, DP2 and MFSH
signaling.
The incoming call was not routing for DP1, DP2 and MFSH signaling when the incoming routing plan was
configured with values in the CTO parameter different from 1&&15 (for example: CTO=1&&3). This bug
was fixed.
2.51.2 Remarks
Not applicable.
2.52 Revision:019 – Software Update: -
2.52.1 Updates
2.52.1.1 PR64800 – Honduras Caller ID

It was implemented Honduras as a new country profile based on the Guatemala country features and the
calling party category presentation of the Caller ID feature regardless the country profile. The category
presentation now depends on the OPP parameter: NOCT.
As default for the CLIP feature for internal calls, the system sends the digits corresponding to category and
full number (prefix + THTU) of the calling subscriber. For a country that is not necessary to send the
calling terminal category, is mandatory to include the NOCT operational parameter. The NOCT
operational parameter is configured through the command:
MD-EXCOPP OPP=NOCT
2.52.1.2 PR68400 – CDR formatting adjustments for Russia

It was implemented the CDR formatting adjustments for Russia country.
2.52.1.3 DR 5237 (AR 1-1326099) Incoming DP1 toll call with incorrect ANI
Correct ANI packed is always a pack started by D, finished by D with 8 digits between D's, which are: 1
digit for category and 7 digits for calling party number. The BZ can receive more than one packs
(maximum of five). If BZ receives more than one pack, the ANI will consider valid only when at least 02
packs have the same values between D's. This bug was fixed.
2.52.1.4 MD-TER command is not disabling the PDG and CNI parameters:
The MD-TER : TER = xx-xx-xx, PDG = WPDG, CNI = NCNI command should disable the PDG and
CNI parameters, but after its execution the parameters remained with the same values despite of the
command replying ok. This error was fixed.
2.52.2 Remarks

3. Compatibility
The table below shows the correct Management Software to be used according the release, i.e. revision and
software update, of the LPN 109253856.
LPN.Revision.SU Management Software

109253856.001 LPN 109232256.001.002
109253856.001.001 LPN 109232256.001.002
109253856.002 LPN 109232256.001.003
109253856.002.001 LPN 109232256.001.003
109253856.002.002 LPN 109232256.001.003
109253856.003 LPN 109232256.002 LPN 109297465.001
109253856.003.001 LPN 109232256.002 LPN 109297465.001
109253856.003.002 LPN 109232256.002 LPN 109297465.001
109253856.004 LPN 109232256.003 LPN 109297465.002
109253856.004.001 LPN 109232256.003 LPN 109297465.002
109253856.004.002 LPN 109232256.003 LPN 109297465.002
109253856.005 LPN 109232256.004 LPN 109297465.003
109253856.005.001 LPN 109232256.004 LPN 109297465.003
109253856.005.002 LPN 109232256.004.001 LPN 109297465.003.001
109253856.005.003 LPN 109232256.004.001 LPN 109297465.003.001
109253856.005.004 LPN 109232256.004.001 LPN 109297465.003.001
109253856.006 LPN 109232256.005 LPN 109297465.004
109253856.006.001 LPN 109232256.005 LPN 109297465.004
109253856.006.002 LPN 109232256.005.001 LPN 109297465.004.001
109253856.006.003 LPN 109232256.005.001 LPN 109297465.004.001
109253856.006.004 LPN 109232256.005.001 LPN 109297465.004.001
109253856.007 LPN 109232256.006 LPN 109297465.005
109253856.007.001 LPN 109232256.006 LPN 109297465.005
109253856.007.002 LPN 109232256.006 LPN 109297465.005
109253856.007.003 LPN 109232256.006.001 LPN 109297465.005.001
109253856.008 LPN 109232256.007 LPN 109297465.006
109253856.008.001 LPN 109232256.007 LPN 109297465.006
109253856.008.002 LPN 109232256.007 LPN 109297465.006
109253856.009 LPN 109232256.008 LPN 109297465.007
109253856.009.001 LPN 109232256.008.001 LPN 109297465.007.001
109253856.010 LPN 109232256.009 LPN 109297465.008
109253856.011 LPN 109232256.010 LPN 109297465.009
109253856.011.001 LPN 109232256.010 LPN 109297465.009
109253856.012 LPN 109232256.011 LPN 109297465.010
109253856.013 LPN 109232256.011.001 LPN 109297465.010.001
109253856.014 LPN 109232256.012 LPN 109297465.011
109253856.015 LPN 109232256.013 LPN 109297465.012
109253856.015.001 LPN 109232256.013.001 LPN 109297465.012.001
109253856.016 LPN 109232256.014 LPN 109297465.013
109253856.016.001 LPN 109232256.015 LPN 109297465.014
109253856.016.002 LPN 109232256.016 LPN 109297465.015
109253856.016.003 LPN 109232256.017 LPN 109297465.016
109253856.017 LPN 109232256.017.001 LPN 109297465.016.001
109253856.017.001 LPN 109232256.017.001 LPN 109297465.016.001
109253856.017.002 LPN 109232256.017.002 LPN 109297465.016.002
109253856.018 LPN 109232256.018 LPN 109297465.017
109253856.018.001 LPN 109232256.018.001 LPN 109297465.017.001
109253856.018.002 LPN 109232256.019 LPN 109297465.018
109253856.018.003 LPN 109232256.019 LPN 109297465.018
109253856.018.004 LPN 109232256.019.001 LPN 109297465.019.001
109253856.018.005 LPN 109232256.019.001 LPN 109297465.019.001
109253856.019 LPN 109232256.020 LPN 109297465.021
Others issues about hardware and software compatibility shall be seen in a specific document called
“BZ5000 Hardware / Software Compatibility Manual”, LPN109262626.
4. Attachments
The document attached bellow is the documentation for the old software SOF98119 that register the history
in which this software is based.

ATTACHMENT
DIRETORIA DE PESQUISA E DESENVOLVIMENTO
GERENCIA DE DESENVOLVIMENTO DE SOFTWARE
Programa Controlador da Central BZ5000
SOF98119G3
CONTROLE DE DOCUMENTO
RECEBIDO APROVADO EMITENTE

LUCENT FITEC
Rosa Maria Eugênio Daher Artur Cabral
DATA DATA DATA
ARQUIVO DATA No. Folhas

L98119G3.DOC 28/03/2002 39
CÓDIGO: 310377-SOF98119G3 EMISSÃO: 35 FL.: 1/39

ATTACHMENT
ÍNDICE
1. PRESENTATION.................................................................................................................................11
2. PRODUCT HISTORY INFORMATION ............................................................................................11

2.1 REVISION: 001 – SOFTWARE UPDATE: - .................................................................................................. 13
2.1.1 Updates.......................................................................................................................................... 13
2.1.2 Remarks ......................................................................................................................................... 15
2.2 REVISION: 001 – SOFTWARE UPDATE : 001 ............................................................................................. 15
2.2.1 Updates.......................................................................................................................................... 15
2.2.2 Remarks ......................................................................................................................................... 15
2.3 REVISION: 002 – SOFTWARE UPDATE : - ................................................................................................. 16
2.3.1 Updates.......................................................................................................................................... 16
2.3.2 Remarks ......................................................................................................................................... 17
2.4.1 Updates.......................................................................................................................................... 17
2.4.2 Remarks ......................................................................................................................................... 18
2.5.1 Updates.......................................................................................................................................... 18
2.5.2 Remarks ......................................................................................................................................... 18
2.6.1 Updates.......................................................................................................................................... 18
2.6.2 Remarks ......................................................................................................................................... 21
2.7 REVISION: 003 – SOFTWARE UPDATE: 001.............................................................................................. 21
2.7.1 Updates.......................................................................................................................................... 21
2.7.2 Remarks ......................................................................................................................................... 22
2.8.1 Updates.......................................................................................................................................... 22
2.8.2 Remarks ......................................................................................................................................... 22
2.9.1 Updates.......................................................................................................................................... 22
2.9.2 Remarks ......................................................................................................................................... 26
2.10.1 Updates.......................................................................................................................................... 26
2.10.2 Remarks ......................................................................................................................................... 26
2.11.1 Updates.......................................................................................................................................... 26
2.11.2 Remarks ......................................................................................................................................... 27
2.12.1 Updates.......................................................................................................................................... 27
2.12.2 Remarks ......................................................................................................................................... 29
2.13.1 Updates.......................................................................................................................................... 29
2.13.2 Remarks ......................................................................................................................................... 30
2.14.1 Updates.......................................................................................................................................... 30
2.14.2 Remarks ......................................................................................................................................... 30
2.15.1 Updates.......................................................................................................................................... 30

ATTACHMENT
2.15.2 Remarks ......................................................................................................................................... 30

2.16.1 Updates.......................................................................................................................................... 30
2.16.2 Remarks ......................................................................................................................................... 31
2.17.1 Updates.......................................................................................................................................... 31
2.17.2 Remarks ......................................................................................................................................... 31
2.18.1 Updates.......................................................................................................................................... 31
2.18.2 Remarks ......................................................................................................................................... 32
2.19.1 Updates.......................................................................................................................................... 32
2.19.2 Remarks ......................................................................................................................................... 35
2.20.1 Updates.......................................................................................................................................... 35
2.20.2 Remarks ......................................................................................................................................... 35
2.21.1 Updates.......................................................................................................................................... 36
2.21.2 Remarks ......................................................................................................................................... 36
2.22.1 Updates.......................................................................................................................................... 36
2.22.2 Remarks ......................................................................................................................................... 37
2.23.1 Updates.......................................................................................................................................... 37
2.24.1 Updates.......................................................................................................................................... 38
2.24.2 Remarks ......................................................................................................................................... 38
2.25.1 Updates.......................................................................................................................................... 38
2.25.2 Updates.......................................................................................................................................... 39
2.25.3 Updates.......................................................................................................................................... 39
2.25.4 Remarks ......................................................................................................................................... 39
2.26.1 Updates.......................................................................................................................................... 39
2.26.2 Remarks ......................................................................................................................................... 42
2.27.1 Updates.......................................................................................................................................... 42
2.27.2 Remarks ......................................................................................................................................... 43
2.28.1 Updates.......................................................................................................................................... 43
2.28.2 Remarks ......................................................................................................................................... 44
2.29.1 Updates.......................................................................................................................................... 44
2.29.2 Remarks ......................................................................................................................................... 45
2.30.1 Updates.......................................................................................................................................... 45
2.30.2 Remarks ......................................................................................................................................... 46
2.31.1 Updates.......................................................................................................................................... 46
2.31.2 Remarks ......................................................................................................................................... 46

ATTACHMENT

2.32.1 Updates.......................................................................................................................................... 46
2.32.2 Remarks ......................................................................................................................................... 47
2.33 REVISION: 011 – SOFTWARE UPDATE: -001 ............................................................................................ 47
2.33.1 Updates.......................................................................................................................................... 47
2.33.2 Remarks ......................................................................................................................................... 48
2.34 REVISION: 012 – SOFTWARE UPDATE: .................................................................................................... 48
2.34.1 Updates.......................................................................................................................................... 48
2.34.2 Remarks ......................................................................................................................................... 49
2.35 REVISION: 013 – SOFTWARE UPDATE: .................................................................................................... 49
2.35.1 Updates.......................................................................................................................................... 49
2.35.2 Remarks ......................................................................................................................................... 50
2.36 REVISION: 014– SOFTWARE UPDATE: ..................................................................................................... 51
2.36.1 Updates.......................................................................................................................................... 51
2.36.2 Remarks ......................................................................................................................................... 51
2.37.1 Updates.......................................................................................................................................... 52
2.37.2 Remarks ......................................................................................................................................... 52
2.38 REVISION: 015– SOFTWARE UPDATE: 001 .............................................................................................. 52
2.38.1 Updates.......................................................................................................................................... 52
2.38.2 Remarks ......................................................................................................................................... 53
2.39.1 Updates.......................................................................................................................................... 53
2.39.2 Remarks ......................................................................................................................................... 54
2.40.1 Updates.......................................................................................................................................... 54
2.40.2 Remarks ......................................................................................................................................... 54
2.41.1 Updates.......................................................................................................................................... 54
2.41.2 Remarks ......................................................................................................................................... 55
2.42.1 Updates.......................................................................................................................................... 55
2.42.2 Remarks ......................................................................................................................................... 56
2.43 REVISION:017 – SOFTWARE UPDATE: -................................................................................................... 56
2.43.1 Updates.......................................................................................................................................... 56
2.43.2 Remarks ......................................................................................................................................... 57
2.44 REVISION:017 – SOFTWARE UPDATE: 001 .............................................................................................. 57
2.44.1 Updates .......................................................................................................................................... 57
2.44.2 Remarks ......................................................................................................................................... 57
2.45.1 Updates.......................................................................................................................................... 58
2.45.2 Remarks ......................................................................................................................................... 59
2.46.1 Binary files used at boards ............................................................................................................. 60
2.46.2 Updates.......................................................................................................................................... 60
2.47.1 Updates.......................................................................................................................................... 61
2.47.2 Remarks ......................................................................................................................................... 62
2.48.1 Updates.......................................................................................................................................... 62

ATTACHMENT
2.48.2 Remarks ......................................................................................................................................... 62

2.49.1 Updates.......................................................................................................................................... 62
2.49.2 Remarks ......................................................................................................................................... 62
3. COMPATIBILITY ...............................................................................................................................66
4. ATTACHMENTS .................................................................................................................................67

ATTACHMENT
1 APRESENTAÇÃO
Este documento formaliza a liberação da versão do Programa Controlador identificado pelo

código SOF98119G3 para centrais BZ5000.
2 ALTERAÇÕES
2.1 VERSÃO SOF98119A5 – 19/02/1999 – MARCELO R. P. MIRANDA

2.1.1 Falha na Temporização para Detecção de Bloqueio e Desbloqueio para
Sinalização R2D - NT 99/006
O programa controlador passa a tratar o parâmetro TBLE existente no comando MD-CENTMP

utilizado na central.
2.1.2 Falha no Agendamento das Supervisões Estatísticas - NT 99/006
As programações das supervisões estatísticas (desempenho, tráfego, órgão, chamada, etc.)

programadas no dia 29/02/2000 iriam ocorrer de forma incorreta. O programa controlador foi
alterado de forma a corrigir este problema.
2.1.3 Bloqueio por Falha de órgãos MFC - NT 99/006
O programa controlador foi alterado para corrigir um erro que fazia com que os MFC’s 11 e 12
da unidade 1 ficassem bloqueados por falha aleatoriamente.
2.1.4 Falha na Interrogação do Assinante - NT 99/006
O programa controlador foi alterado para corrigir uma falha que quando se interrogava um
assinante no estado bloqueado era enviado uma mensagem incorreta a respeito deste.
2.1.5 Aumento do nível de 425Hz
O programa controlador foi alterado para que o nível do sinal de 425Hz sofresse uma elevação
de 5dB.
2.1.6 Falha na Sinalização de Linha R2D
A central Elcom não estava tratando de forma adequada o sinal de desconexão forçada.

ATTACHMENT
2.2 VERSÃO SOF98119B1 – 08/04/1999 – DENILSON M. COSTA
2.2.1 Protocolo V5.2
O programa controlador passa a incorporar toda a potencialidade do protocolo V5.2, sendo

capaz de se comunicar com quaisquer outras entidades que entendam tal protocolo. Essa
versão do software faz o papel da entidade LE (Local Exchange) desse protocolo. A
comunicação entre as duas entidades do protocolo V5.2 (AN e LE) é feita através de um link
de sinalização dentro de um enlace PCM, para tal, são utilizadas as placas MAP e/ ou JDT.
Deve-se salientar que toda a implementação do protocolo V5.2 foi desenvolvida em software,
não sendo necessário nenhum hardware adicional em relação à versão anterior.
Para essa versão estão sendo liberados apenas assinantes padrão PSTN.
2.2.2 Aumento da Capacidade de Tráfego
Essa versão do programa controlador é capaz de manipular uma matriz de comutação com
maior capacidade de tráfego.
A placa de matriz é configurável no formato 16X16 intramodular e 16X16 intermodular,
mantendo compatibilidade com a atual matriz de primeiro nível, ou no formato 24X24 enlaces
PCM, provendo até 12 enlaces de acesso ao segundo nível de comutação para cada gaveta. A
placa deverá ocupar a posição ocupada pela placa MMC93078A no SBE.
A placa poderá ser configurada para implementar as seguintes funções:
Configuração 1: Matriz de comutação intramodular no formato 16X16 enlaces PCM a
2048kbps, sendo 12 enlaces destinados às interfaces internas ao SBE e 4 enlaces destinados
à conexão com a matriz intermodular. Além da matriz de comutação intermodular no formato
16X16 enlaces PCM a 2048kbps.
2048kbps, sendo 16 enlaces destinados às interfaces internas ao SBE e 8 enlaces destinados
à conexão com a matriz intermodular.
2048kbps, sendo 12 enlaces destinados às interfaces internas ao SBE e 12 enlaces
destinados à conexão com a matriz intermodular.
2.2.3 Novo Robô de Testes
O programa controlador tem um novo robô de testes capaz de realizar novos testes na linha do
assinante e testes na interface do assinante. Possui, ainda, um maior número de atuadores
que o anterior, exibe os valores das grandezas amostradas e é capaz de se auto-calibrar. A
utilização do novo robô de testes está vinculada à placa MTL-B (MTL97086A).
Foram disponibilizados os seguintes comandos novos para o operador da central:
AT TSTINT - Ativação do teste de interface de assinante
IT TSTINT - Interrogação do teste de interface de assinante
DT TSTINT - Desativação do teste de interface de assinante

ATTACHMENT
PR TSTINT - Programação do teste de interface de assinante

RP TSTINT - Remoção da programação de teste de interface de assinante
2.2.4 Novo Plano de Numeração/Encaminhamento
Essa versão do software controlador está preparada para lidar com os novos conceitos de
planos de numeração e encaminhamento de chamadas pré-estabelecidos pela ANATEL.
Através da análise da data e hora da chamada e do resultado da análise do plano de
encaminhamento são obtidos 3 parâmetros necessários para a definição da tarifação da
chamada, que são o plano de tarifação (PTF), o tipo de tarifação (TTF) e a classe de tarifação
(CLTF) a serem aplicados à chamada. Esses parâmetros são descritos abaixo:
Plano de Tarifação (PTF): Consiste no conjunto de informações necessárias para que a
central possa realizar a tarifação das chamadas. A utilização de múltiplos planos de tarifação
tem sua principal aplicação em um ambiente com mais de uma prestadora de serviço
telefônico, onde cada prestadora utilize seu próprio plano de tarifação. Nesta aplicação, a
programação da central deve ser realizada de forma a definir, para cada prestadora do
serviço, um plano de tarifação independente.
Tipo de Tarifação (TTF): Conceito utilizado para diferenciar os tipos de tarifas a serem
aplicados nas chamadas em função da área tarifária de destino. Para cada tipo de tarifação
definido na central deve ser configurada uma tabela de modalidade de tarifa. Este conceito
permite que as tabelas de modalidade de tarifa das chamadas destinadas a áreas tarifárias de
destino diferentes sejam programadas de forma independente. Para cada plano de tarifação
definidos na central podem ser definidos múltiplos tipos de tarifação.
Classe de Tarifação (CLTF): A classe de tarifação é um apontador que, em conjunto com a
modalidade de tarifa em vigor na central, definem o método de tarifação, a cadência e o
número de pulsos no atendimento em função da classe do assinante originador ou classe de
rota de entrada e categoria do assinante originador e da seqüência discada. A tabela de classe
de tarifação é única para cada plano de tarifação definido na central.
2.2.5 Correções no Firmware e Drive da Placa de Assinante
O firmware das placas MTA97036A, MTA98036A, MTA98037A, MTA98038A e MTA98039A

recebeu modificações de forma tal que para cada mensagem de comando recebida, haverá
uma consistência da integridade das informações contidas na mensagem. Essa consistência é
baseada na verificação de um checksum acrescido no formato da mensagem. O drive dessas
placas passa a tratar a inserção de mensagens na FIFO de transmissão de forma orientada por
mensagens e não mais orientado por bytes.
2.2.6 Implementação do Tratamento de 3 placas MPS’s numa mesma gaveta

ELCOM
A central Elcom permite que sejam configuradas 3 placas MPS’s em cada gaveta de terminais.
Essas configurações devem ser nas posições 20, 21 e 22 de forma indistinta.
2.2.7 Correções na funcionalidade RDSI
Foram realizados ajustes no protocolo RDSI.

ATTACHMENT
2.2.8 Alterações da Tabela de Restrição (NT 98/174)
A tabela de restrição de originação para os assinantes programados com o SSU BLQCHM foi
alterada, passando a ter a seguinte configuração:
RTO GRAU DE RESTRIÇÃO

1 Irrestrito
2 DDI
3 DDI, DDD
4 DDI, DDD, ESP1
5 DDI, DDD, ESP1, ESP2
6 DDI, DDD, ESP1, ESP2, ESP3
7 DDI, DDD, ESP1, ESP2, ESP3, ESP4
8 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5
9 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6
10 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6, ESP7
11 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6, ESP7, ESP8
12 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6, ESP7, ESP8, REG
13 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6, ESP7, ESP8, REG, LOC
14 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6, ESP7, ESP8, REG, LOC, INTRA
15 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6, ESP7, ESP8, REG, LOC, INTRA, SEI
16 DDI, DDD, ESP1, ESP2, ESP3, ESP4, ESP5, ESP6, ESP7, ESP8, REG, LOC, INTRA, SEI, SEL
2.2.9 Flexibilização das Posições das placas de Tronco Digital
Nessa versão as placas de tronco digital (JDT) podem ser colocadas nas posições 1 até 20.
2.2.10 Alteração para permitir flexibilidade da temporização para transferência de

chamada não respondida (NT 98/186)
Nessa versão do software controlador é possível, através de comandos do CSR, configurar o

temporização para uma chamada não respondida. Esse valor pode ser configura de 5 até 60
segundos através do comando MD CENTMP. O valor configurado pode ser verificado através
do comando IT CENTMP.
2.3 VERSÃO SOF98119B2 – 16/04/1999 – MARCELO TROPIA REQUENA
2.3.1 Alteração para aumentar a profundidade de análise do plano de

encaminhamento originado
Nesta versão de software controlador a profundidade de análise do plano de encaminhamento

foi alterada de 10 para 16 dígitos.
2.3.2 Alteração para aumentar a capacidade de armazenamento de dígitos
Nesta versão de software controlador a capacidade de armazenamento de dígitos foi

aumentada de 20 para 30 dígitos.
2.3.3 Alteração do limite máximo do parâmetro “SEQ”

ATTACHMENT
Nesta versão de software controlador o limite máximo de dígitos do parâmetro “SEQ” passou
de 18 para 20 dígitos. O programa foi alterado para permitir a entrada dos 20 dígitos via
teclado telefônico ou comando do CSR. Os seguintes comandos foram afetados pela
modificação:
• CR-CSRCHM
• MD-CSRCHM
• IT-CSRCHM
• AT-TSTCHA
• MD-SSUASS
• IT-SSUASS
• CR-RVI
• IT-RVI
• MD-MCB
• IT-MCB
• MD-ASSLD
• MD-RENCHA
• IT-RENCHA
• IT-LOGCEN
2.4 VERSÃO SOF98119B3 – 03/05/1999 – DENILSON MARCELINO

COSTA
2.4.1 Tratamento do Alarme Externo NT 99/045
Nesta versão de software controlador foi corrigido a falha no tratamento de alarmes externos
PDT. O alarme era registrado no histórico porém não era retornado quando interrogado via
comando IT-ALARM.
2.5 VERSÃO SOF98119B4- 23/06/99 - DENILSON MARCELINO COSTA
2.5.1 Correção no comando IT-LOGCEN - NT 99/044
O programa controlador foi alterado de forma a corrigir um problema de BUG do milênio para
este comando. Ao interrogar o histórico de comandos após o início do ano 2000, eram
apresentados apenas os registros anteriores à virada do milênio que ainda estivessem
presentes na central.
2.5.2 Correção no Tratamento da Placa MPS na posição 22
Nesta versão do programa controlador foi corrigida uma falha que quando era feita uma
ligação para um número inexistente na central, estando a placa MPS na posição 22, não era
enviado nenhuma sinalização acústica para o assinante chamador.
2.5.3 Alteração na Recepção da REDE LAN

ATTACHMENT
O tratamento do protocolo de comunicação das unidades foi alterado de forma a isolar a rede
com problemas o mais rápido possível. O retorno desta para o modo ativo é automático,
bastando ser detectada a perfeita atividade da rede.
2.5.4 Falha no Tratamento do fio C do Tronco Digital
O fio C do tronco digital que é utilizado para o acionamento do supressor de eco estava
trocado. Esta versão do programa controlador corrige este problema.
2.6 VERSÃO SOF98119C1- 15/07/99 - EUGÊNIO L. DAHER
2.6.1 Projeto novas facilidades Elcom - PABX Virtual
O programa controlador passa a tratar as novas facilidades implementadas no PABX Virtual,

como por exemplo:
• Rechamada em caso de ocupado

• Rechamada em caso de não responde
• Estacionamento de chamadas (portabilidade)
• Grupo de busca CPCT para captura de chamadas
• Alteração Temporária de Identidade
• Siga-me programado no destino
• Mesa Operadora (por software)
• Encaminhamento de chamadas em caso de ocupado ou não responde (as chamadas são
encaminhadas para a Mesa Operadora)
2.6.2 Novos Indicadores de Qualidade
O programa controlador foi alterado de modo a possibilitar a programação de até 9

supervisões de tráfego e desempenho e atender os novos indicadores da qualidade solicitados
pela anatel. Os seguintes parâmetros foram alterados e/ou implementados para satisfazer as
determinações:
• Número de Ocupações DTMF

• Tempo Médio de Espera de DTMF
• Tempo Médio de Ocupação de DTMF
• Espera por Tom de discar para sinalização MF
• Tentativa de utilização de Registradores
• Ocupação de Registradores
2.6.3 Correções na funcionalidade RDSI
Foram realizados ajustes no protocolo RDSI.
2.6.4 Tratamento das placas do Projeto 100KT

ATTACHMENT
O programa controlador foi alterado de forma a operar com as seguintes placas:
• MMC 93078B
• MMC 94154B
• MMC 94156B
• MCE 96022B
• MCC 96021B
• MCC 97153B
• MCC 98109A
2.6.5 Correções na funcionalidade V5.2
Foram realizados ajustes no protocolo V5.2
2.7 VERSÃO SOF98119C2- 29/09/99 – DENILSON M. COSTA
2.7.1 ISDN Nível II na CPU da gaveta
O nível II do ISDN nessa versão roda na CPU da gaveta.
2.7.2 Correção no protocolo V5.2
Foram corrigidos alguns problemas apresentados no protocolo V5.2
2.7.3 Correções de problemas apresentados na MTA de 32 assinantes.
Foram corrigidos os problemas apresentados na MTA de 32 assinantes.
2.7.4 Correções no ISUP
Essa versão do software controlador corrige os problemas apresentados no ISUP.
2.8.1 Correções ISDN Nível II na CPU da gaveta
O nível II do ISDN nessa versão roda na CPU da gaveta.
2.8.2 Correções no protocolo V5.2
Foram corrigidos alguns problemas apresentados no protocolo V5.2
2.8.3 Bilhetador Rodando no Windows NT

ATTACHMENT
A nova versão do bilhetador é executada sobre o sistema operacional Windows NT.
2.8.4 Correções de problemas apresentados na MTA de 32 assinantes.
Foram corrigidos os problemas apresentados na MTA de 32 assinantes.
2.8.5 CSR via rede LAN
O CSR nessa versão pode conversar com a central através da rede LAN.
2.8.6 Assinante Pré-Pago
Essa versão do software controlador é capaz de tratar assinantes pré-pagos.
2.8.7 Testes SERA
Essa versão do software controlador oferece a funcionalidade de permitir testes na linha de

assinante e testes no circuito de assinante realizados por um testador externo. Para tal, é
necessário a criação de uma classe SERA, através do CSR. Essa classe deve conter o
parâmetro de serviço PSV definido como SERA e restrição de chamadas terminadas. Além
disso, é permitido configurar o tempo máximo de duração dos testes através da configuração
de tempos da central (md centmp).
2.8.8 Correções no ISUP
Essa versão do software controlador corrige os problemas apresentador no ISUP.
2.9.1 Ajustes no módulo HWMTAZ
Nessa versão do software controlador foi implementado a correção automática de

registradores dos QSLAC’s que percam a configuração em tempo de execução. apenas os
registradores de configuração definida estão sendo corrigidos. Os registradores de
configuração dinâmica não estão sendo corrigidos. Além do módulo hwmtaz, o módulo bdebug
foi alterado para facilitar a supervisão dos diversos registradores da placa.
2.9.2 Implementação de cadências de tons configurável
Essa versão do software controlador apresenta a facilidade de configuração, via CSR, das
cadências dos diversos tons de controle. Para tal, foram implementados dois comandos novos
no CSR, a saber: IT_TOM e MD_TOM.
2.9.3 Aumento do número máximo de bilhetes
O número máximo de bilhetes e o limites de bilhetagem foram alterados. O número máximo

de bilhetes permitidos no bilhetador, MAX_BILHETES, passa a ser 5000 bilhetes e o limite de
bilhetagem, LIMITE_BILHETAGEM, passa a ser 4000.

ATTACHMENT
2.10.1 Correções de empacotamento ISUP
Foi corrigido a função at_desempac(), pois esta estava desempacotando sempre um valor
constante (MAX_ELEM_INFO_AT) ao invés do número correto de octetos.
2. 10.2 Correções de consistência na comutação de enlaces
Antes de realizar a comutação os valores são agora consistidos. Caso os valores não sejam
válidos, a comutação não é mais realizada.
2. 10.3 Correções no protocolo V5.2
Foram feitas várias correções genéricas de ajuste no protocolo V5.2
2. 10.4 Correção do problema de LAN redundante
Foi feita alteração no diretório protqnxt para teste da solução que visa contornar o problema
verificado em campo, resultante do uso de lan redundante com motherboard TxPro Ι. Foi
gerada uma versão específica para testes na central de Bebedouro com essa característica e
logo após a mesma foi desabilitada (#ifdef __TESTE_LAN__).
2. 10.5 Correção do módulo SLA relativo ao corte de tom de discar
Foi corrigido o problema de se detectar FFG em A e cortar o tom de discar na primeira

transição de loop de assinante mesmo que esta transição fosse apenas um ruído e não um
pulso de discagem decádica.
2. 10.6 Alteração para permitir a criação de rota de canal comum no EP V5
O programa controlador foi alterado para permitir a criação de rota de canal comum no EP que
utiliza protocolo V5.2
2. 10.7 Correções no processamento de chamadas
Aumento do tamanho da fila de espera por DTMF e nova implementação do atraso da

resposta de alocação de DTMF com precisão de 50ms.
Foi corrigido, também, o número máximo de bytes enviados para a fifo de transmissão da
placa MTA-Z, e a distribuição das mensagens para todas as placas presentes no barramento
de forma paralela. Além disso, corrigiu-se a ocorrência de mensagens de FNG indevidas.
2.10.8 Correções no tratamento de assinante pré-pago
Alteração no tratamento de assinante pré-pago. Permite configuração de limiar de créditos

usado para emitir mensagem informando proximidade de término dos mesmos.

ATTACHMENT
2.10.9 Ajustes na alocação dinâmica de canais para a MTA-z
Foram feitos vários ajustes a adequar a alocação dinâmica de canais para a placa MTA_Z.
2.10.10 Correções no PABX virtual
Foram feitas várias correções de ajuste no tratamento do PABX virtual relativos ao

atendimento noturno.
2.10.11 Correções na alocação de canais da MTA-z
Na função que escreve mensagens no buffer de transmissão, as habilitações e desabilitações

de interrupção foram substituídas por chamadas à _push_flags_disable() e _pop_flags() que
recupera o estado anterior dos flags para evitar habilitar interrupção indevidamente.
Em todas as funções que precisam habilitar um determinado canal antes de escrever num
QSLAC, foi inserido um _push_flags_disable() antes da mesma e um _pop_flags() após, para
garantir que os comandos para o QSLAC sejam buferizados em seqüência sem que alguma
interrupção interfira nesta ordem.
2.11.1 Correção da seleção de enlace para a MAB
Foi criada a função mab_seleciona_enlace_pcm para corrigir a seleção de enlace para a MAB
que apresentava problemas quando esta placa compartilhava enlaces com outra qualquer.
2.11.2 Correções da MOP
Foram feitas correções no sistema de alocação, supervisão e reserva da MOP.
2.11.3 Correção no bit de identificação do enlace no protocolo V5.2
Foi corrigido o bit de identificação do enlace na recepção e transmissão da mensagem

M_LE_BIT_LID o ELCOM estava testando o bit 3, quando deveria testar o bit 1.
2.11.4 Correção no serviço suplementar BINA.
Foi corrigido o problema apresentado pelo ELCOM de não conseguir enviar sinalização DTMF
para dois assinantes da mesma placa simultaneamente.

ATTACHMENT
2.12 VERSÃO SOF98119D1- 19/06/2000 – HARLEY ANSELMO A. CARMO
2.12.1 Correções no protocolo V5.2
Foram feitas várias correções de ajuste na implementação do protocolo V5.2.
2.12.2 Alteração do número de interfaces V5.2 e assinantes de EP com V5.2
Foram alterados o número máximo de interfaces V5.2 de 128 para 16 e o número máximo de
assinantes de EP com interface V5.2 de 1000 para 1500.
2.12.3 Novo parâmetro de operação para a interface V5.2
Foi criado um novo parâmetro POP=PINVSTD para a interface V5.2, que altera o tipo de
mensagem enviada pelo LE para um assinante do tipo TP configurado com PSV=DINVPOL,
para que este faça a coleta de fichas. De acordo com a norma ABNT, esta mensagem deve
ser do tipo PULSED SIGNAL REVERSED POLARITY. Quando o parâmetro PINVSTD estiver
habilitado, o LE enviará as mensagens STEADY SIGNAL REVERSED POLARITY e em
seguida a mensagem STEADY SIGNAL NORMAL POLARITY.
2.12.4 Correções no ISDN
Foram feitas correções de ajuste na implementação do ISDN.
2.12.5 Novo firmware para placa MTA-Z
Foi feito o tratamento para o novo firmware – SOF97137B1 – da placa MTA-Z.
2.12.6 Aumento do número de placas MTL e MPS
Foi aumentado o número máximo de placas MTL e MPS de três para quatro placas por
unidade, configuradas a partir da posição 19.
2.12.7 DTMF pleno
O software foi alterado de forma que o DTMF pode agora ser compartilhado entre assinantes
de gavetas diferentes.
2.12.8 Temporizações da central programáveis
Criação de várias temporizações programáveis para a central, que podem ser alteradas
através do comando MD-CENTMP.

ATTACHMENT
2.12.9 Dígitos especiais programáveis
Foram tornados configuráveis os dígitos especiais utilizados para efetuar operações tais como
transferência de chamadas, reservas, etc. A programação dos dígitos especiais é feita através
do comando MD-DIGESP.
2.12.10 Alarme de falha do ventilador da CPU Industrial
Criação do alarme de falha do ventilador da CPU Industrial.
2.12.11 Alterações no robô de testes
Foram feitas alterações no robô de testes, com a alteração da faixa de valores válidos e
inserção de atraso nos testes de perda de retorno.
2.12.12 Tratamento para placa MPS-C
Foi feito o tratamento para a nova placa MPS-C (MPS94196C).
2.12.13 Criação de novo parâmetro de operação da central
O comando MD-CENPOP aceita agora um novo parâmetro POP=KHZ16, que altera a

freqüência normal gerada pela placa MPS-C de 12KHz para 16KHz.
2.12.14 Novo comando IT-MFT
Criação do comando IT-MFT para leitura das tensões da fonte de alimentação da placa
MPS-C.
2.12.15 Tratamento para placa JDT00012A
Foi feito o tratamento para a nova placa JDT00012A.
2.12.16 Novo parâmetro de operação para rotas – envio de código de área
Foi criado novo parâmetro de operação para rotas – POP=CNAC, modificado através dos
comandos CR-ROTA e MD-ROTA – para configurar o envio do código de área em chamadas
originadas.

ATTACHMENT
2.12.17 Sinalização R2
Foi criado o parâmetro ECA, alterado através do comando MD-SNLR2, que configura o sinal
MFC que deve ser interpretado como “Categoria de A”.
2.12.18 Criação do PMO – Ponto de Marcação de Origem
Na criação do assinante pode ser definido o parâmetro PMO, que identifica a “área” onde está
o assinante. A programação de Serviço Especial Local considera o PMO.
2.12.19 Aumento do número de prefixos
O número de prefixos aceitos pela central foi ampliado para 50.
2.13 VERSÃO SOF98119D2- 03/07/2000 – HARLEY ANSELMO A. CARMO
2.13.1 Alterações no teste de linha – NT 00/44
Foram feitas alterações no teste de linha para atendimento da NT 00/44.
2.14 VERSÃO SOF98119D3- 28/08/2000 – DENILSON MARCELINO COSTA
2.14.1 Alteração do estado do terminal associado ao assinante RDSI.
Esta versão altera o estado do terminal associado ao assinante RDSI com MSN quando esse
for o numero default
2.14.2 Novos Binários (firmware) para a placa MTL.
Esta versão está sendo liberada com novas versões dos binários da placa MTL.
2.14.3 Alteração dos parâmetros dos teste da MTL.
O tempo do teste de ring foi alterado para 1s e o limite superior para o teste multifreqüencial
foi alterado para 4000.
Outros parâmetros para testes de linha e paramétricos foram alterados.
2.14.4 Alteração do BOOT.
A função le_versao_boot() foi corrigida. A varredura de endereços para procura da assinatura

ATTACHMENT
do boot estava errada.
2.14.5 Correção da indição de falha na placa MTAZ.
O indicação de falha na placa MTAZ foi corrigida par indicar o campo placa corretamente.
2.14.6 Aumento do tamanho do buffer de transmissão da placa MTAZ.
O tamanho do buffer de transmissão da placa MTAZ foi alterado de 5k para 6k bytes.
2.14.7 Correção na configuração de assinante.
O teste do tipo do terminal antes da recuperação da informação de unidade e terminal, para

assinantes que não são locais, foi corrigido para prevenir a ocorrência de erro de proteção de
memória quando o controlador roda sob o sistema operacional DOS.
2.15 VERSÃO SOF98119E1- 30/08/2000 – GUSTAVO P. SOUZA
2.15.1 Temporizações da central programáveis
Foram implementadas mais trinta e nove temporizações programáveis para tratamento de

ISUP.
2.15.2 Alteração do estado do terminal do assinante RDSI
É possível diferenciar o estado de operação do MSN de seu número default.
2.15.3 Alteração no range de medição do ring
Alteração no range para correção da medida do ring a vazio.
2.15.4 Comandos para tratamento da sinalização ISUP
Foram implementados comandos de modificação e interrogação para tratamento das

mensagens de sinalização ISUP (MD SNLISUP, IT SNLISUP).
2.15.5 Comandos para especificação do país
Foram implementados comandos para especificação em qual país a central estará sendo
utilizada para que vários parâmetros sejam configurados. (MD PAIS, IT PAIS)
2.15.6 Criação de parâmetros opcionais para mensagem IAM (ISUP)

ATTACHMENT
Foram implementados quatro parâmetros opcionais (dígitos genéricos, referência de chamada,

número original chamado e número redirecionante) para a mensagem IAM.
2.15.7 Comandos para especificação do código de seleção de operadora
Foram implementados comandos para a especificação do código de seleção de operadora

(parâmetro novo no tratamento das rotas). (MD CSO, IT CSO)
2.15.8 Comandos para programação dos códigos dos serviços suplementares
Através de novos comandos, é possível realizar a programação dos códigos dos serviços
suplementares. (MD SRVSSU, IT SRVSSU)
2.15.9 Tratamento do novo grupo para sinalização R2 – grupo C;
Foi implementado um novo grupo, denominado grupo C, para a realização de troca de

sinalização R2 em outros países. (campos c_epa, c_ea1, c_cgt, c_eia)
2.15.10 Tratamento de tom diferenciado ou normal para o comando PR_SSU
Evitar que o tom diferenciado não cause interferência em aplicações com modem.
2.15.11 Correção da indicação de falha da placa MTA-z
O campo que informa a unidade – placa foi inicializado adequadamente.
2.15.12 Ajuste de algumas temporizações ISUP
As termporizações de falha na recepção da mensagem de reconhecimento de

bloqueio de circuito (BLA), falha na recepção da mensagem de reconhecimento de
desbloqueio de circuito (ULA), falha na recepção da mensagem Release Complete (RLC)
após o envio de reset de circuito (RSC), falha na recepção da mensagem de
reconhecimento de bloqueio de grupo de circuitos (CGBA), falha na recepção da
mensagem de reconhecimento de desbloqueio de grupo de circuitos (CGBA) e falha na
recepção da mensagem de reconhecimento de reset de grupo de circuitos (GRA) foram
ajustadas.
2.16 VERSÃO SOF98119E2- 27/10/2000 – RODRIGO Q. BARROS
2.16.1 Sinalização R2 em placa MAP

ATTACHMENT
Inclusão da possibilidade de configuração de juntores com sinalização R2 em placa MAP.
2.16.2 Ajustes no teste de linha
Para os teste que ligam o codec da placa de assinantes, porém não fazem comutação, foi
acrescentada a reserva do canal intramodular. Essa modificação foi necessária, devido ao fato
da ativação do codec sem a contrapartida alocação do canal intramodular estar interferindo em
chamadas correntes na mesma placa, pois, ao ativar um codec na MTAZ sem selecionar um
time slot a placa ativa sobre o time slot corrente.
Foi atualizada a versão do firmware da MTL.
2.16.3 Correção de falha na tarifação de serviço suplementar
Corrigida a identificação do serviço suplementar utilizado para a tarifação.
2.16.4 Alteração do protocolo de comunicação do CSR via TCP/IP
Alterado protocolo para permitir a detecção da queda de conexão pelo CSR quando conectado
via TCP/IP.
2.17 VERSÃO SOF98119E3- 01/12/2000 – RODRIGO Q. BARROS
2.17.1 Bilhetagem
Tratamento do bilhete com formato AMA 147.
2.17.2 Chamadas a cobrar para assinantes programados com transferência
Programa controlador alterado de forma a enviar para trás o duplo atendimento recebido à
frente, quando o assinante original chamado estiver com transferência externa habilitada.
2.17.3 Tratamento da placa MPS-94196C
Programa controlador alterado para trabalhar com a placa MPS-94196C

ATTACHMENT
2.18 VERSÃO SOF98119E4 – 20/02/2001 – RODRIGO Q. BARROS
2.18.1 Tratamento de 16 links SS7
O número de links SS7 da central passou de 8 para 16.
2.18.2 Tratamento de reset de placa
O comando EX_RESET foi alterado para aceitar mais um parâmetro – o número da placa. O
comando executará reset da placa especificada no parâmetro do comando sem executar reset
da gaveta.
EX_RESET [uni=xx], [placa=xx];
2.18.3 Aumento do Número de Juntores em Supervisão
O número de juntores em supervisão de chamada ativa passou de 8 para 30 por unidade.
2.18.4 Tratamento do serviço especial local com 5000 registros e CLR
Os comandos CR_SEL, IT_SEL e SU_SEL foram alterados para tratar as sequências

terminadas de rotas com CLR diferente. O número de registros configuráveis passou de 256
para 5000.
2.18.5 Carga instantânea do processador
O comando IT_SUPREG passou exibir a carga média dos processadores do central.
2.18.6 Trace de chamadas R2
Foi implementado trace das sinalizações de linha com canal associado. Trace pode ser ativado
programando-se os juntores para supervisão e ativando a janela da supervisão SS7.
2.18.7 Tratamento de estatísticas
O comando IT_SUPDES passou a exibir as estatísticas de carga média de processador, tempo

de links SS7 e troncos E1 fora de serviço.
2.18.8 Alarme da placa MTA-Z
O seguinte problema foi resolvido: na situação de chamada falsa, se a placa fosse retirada o
alarme continuava. Atualmente o alarme desaparece quando a placa for retirada.
2.18.9 Inibição do alarme de 2Mbps troncos digitais quando E1 está bloqueado.
Os alarmes de falha de transmissão deixarão de ser exibidos quando os troncos são

bloqueados através de comando MD_E1EST.

ATTACHMENT
2.18.10 CKS diferente após CR-SS7CJE:
O seguinte problema foi corrigido: o comando CR_SS7CJE causa corrupção da base de dados
das unidades do central. Atualmente a integridade e sincronismo das bases de dados da todos
unidade do central é garantida depois da execução do comando CR_SS7CJE.
2.18.11 Bilhetador
Correções de falhas no bilhetador
2.19 VERSÃO SOF98119E5 – 13/03/2001 – RODRIGO Q. BARROS
2.19.1 Tratamento da matriz de código de B (MCB)
Corrigida falha na MCB quando uma rota possuía juntores em mais de uma unidade.
2.19.2 Gravação de mensagens na placa MPS
Corrigido erro do software da versão E4, que permitia a gravação de apenas uma mensagem
na placa MPS. Nas versões anteriores à E4 não há problemas na gravação de mensagens.
2.20 VERSÃO SOF98119E6 – 25/04/2001 – ARTUR M. CABRAL
2.20.1 Trace de chamadas ISDN.
Foi implementado trace das sinalizações de ISDN. O Trace ISDN pode ser ativado
programando-se os terminais para supervisão e ativando a janela da supervisão SS7.
2.20.2 Nova mensagem de máquina anunciadora.
Implementada mensagem de bloqueio de originação que é enviada ao assinante quando este

se encontra no estado operacional BLO.
2.20.3 Tratamento de supervisão estatística contínua.
Foram implementadas as supervisões de desempenho e tráfego contínuas, renovadas a cada

15 minutos. Estes recursos podem ser acionados pelos comandos PR-SUPDES ,PER e PR-
SUPTRA, PER do CSR.
2.20.4 Tratamento de IRC. (CNID)
Foram criados novos comandos para criação, configuração, supressão e visualização de

identificadores de redes corporativas.

ATTACHMENT
2.20.5 Configuração de placa MPS que atende ao modem RLDF.
O controlador foi alterado para receber o parâmetro placa no comando MD-CENCOM do CSR.
Isto foi feito para tornar possível indicar qual a placa MPS que ficará responsável por atender
ao modem já que pode existir mais de uma placa MPS em uma mesma unidade.
2.20.6 Alteração do Driver da LAN.
Correção de problemas encontrados relativos a placa 3COM versão B. Estes problemas não
afetavam o funcionamento normal do produto. Estavam relacionados ao teste da placa para
aceitação na fábrica.
2.20.7 Correção da falha de cancelamento e desativação de programação de

supervisão de tráfego e desempenho.
Foi corrigida uma falha nas supervisões estatísticas que fazia com que desativações e
cancelamentos de programações eventualmente corrompessem a base de dados das unidades
diferentes da O&M.
2.20.8 Tratamento de índice de início no acesso básico/primário.
O programa controlador passa a tratar o índice de início em chamadas terminadas nos

acessos básicos e primários RDSI.
2.20.9 Tratamento de falha no sincronismo.
Quando os relógios já se encontravam sincronizados e o sistema já estava votando a maioria,

a falha em algum dos três relógios da central poderia fazer com que as unidades que não
possuíssem relógio se escravizassem em outra que não a mestre.
2.20.10 Gravação de mensagem de máquina anunciadora via CSR.
Foram criados comandos de CHM que possibilitam o envio de um arquivo, contendo

mensagens a serem gravadas na máquina anunciadora, das placas MPS.
2.20.11 Falhas de encaminhamento.
Em chamadas de entrada provenientes de uma rota com tipo igual a DDR com número chave
programado e terminadas na central, o bilhete gerado não mostrava o número do assinante
chamador.
Em chamadas de entrada provenientes de uma rota com tipo igual a DDR com número chave
programado e encaminhadas para fora da central, a central não enviava o código de área
associado a rota de entrada.
2.20.12 Tratamento de grupos de rotas.
O controlador foi alterado para possibilitar ao usuário criar grupos de rotas e definir as
porcentagens de alocações para cada rota do grupo através dos novos comandos; CR_GRP,

ATTACHMENT
MD_GRP, SU_GRP e IT_GRP.
2.20.13 Correção de problema nas programações de supervisão.
Uma falha permitia que o usuário programasse duas ou mais supervisões de mesmo tipo cujas
durações se interceptavam no tempo, o que não é permitido.
2.20.14 Tratamento de mensagem de limite de crédito.
Quando a mensagem de limite de crédito era reproduzida o assinante somente podia iniciar a
discagem após o seu término. O tratamento realizado possibilita agora ao assinante iniciar a
discagem antes do término da mensagem de limite de crédito.
2.20.15 Tratamento de assinante pré-pago para o Peru.
O programa controlador foi alterado para permitir que assinantes do Peru que estejam
configurados como pré-pagos possam efetuar chamadas, mesmo estando sem créditos,
quando estas forem do tipo não tarifadas.
2.20.16 Correção na supervisão de desempenho de enlaces SS7 e E1.
Alteração para resolver problema de contabilização de tempo de enlace SS7 e E1 fora de uso,
por ocasião de supervisão de desempenho. Se o enlace já se encontrava fora de uso quando
a supervisão se iniciava, ao final da supervisão o tempo apresentado ao usuário era zero para
estes enlaces fora de uso.
2.20.17 Correção de problema no modo de configuração da central.
Uma falha na inicialização do parâmetro khz16 colocava esta freqüência como padrão para
tarifação de telefones públicos.
2.21.1 Correção de falha na transmissão de dados na conexão TCP com o CSR .
Aumentada a consistência de envio de dados via conexão TCP.
2.21.2 Correção de identificação de bilhetador mestre.
Em alguns casos algumas unidades estavam identificando um bilhetador mestre diferente do

atual.
2.21.3 Alteração na interface com o bilhetador.

ATTACHMENT
O concentrador aguarda a confirmação de recebimento de bilhetes pelo bilhetador antes de

descartar um bilhete. A capacidade do buffer parcial foi aumentada de 100 para 1000 registros.
2.21.4 Alarmes indevidos das placas MTA32 quando unidade reiniciada.
Foram retirados os alarmes gerados por retirada de placas MTA32 quando a unidade é
reiniciada.
2.21.5 Correção de falha no teste de tarifação da MTL.
Corrigido problema no teste de tarifação de 12 Khz da MTL.
2.21.6 Implementação de serviço suplementar de CLIRP para Argentina.
Implementado o serviço suplementar de CLIRP para assinantes analógicos para a Argentina.
2.21.7 Correção de falha no tratamento do SERA
Ao final da sequência de comunicação com o SERA estava sendo enviado o caractere ‘A’,
agora ao final o caractere enviado é ‘#’.
2.22.1 Alteração no V5 .
Quando receber um DISCONNECT do AN, não envia Disconnect Request na liberação da

chamada.
Passa a tratar steady signal recebido em mensagem DISCONNECT.
2.22.2 Correção de falha na conexão com o CSR via TCP.
Quando a unidade mestre caía o CSR conectado via TCP a uma outra unidade ficava preso.
2.22.3 Correção de falha na placa MPS-A.
A placa MPS-A não estava gerando tom de discar e nem comunicação via MODEM.
2.22.4 Falha na sinalização R2 da Tailândia.
Quando a origem envia o sinal I-15 (fim de número de A), sai do estado de recepção de sinais
do grupo C e volta automaticamente a receber sinais do grupo A, não necessitando receber o
EPAC.

ATTACHMENT
2.23.1 Correção de falha em assinante pré-pago.
Em alguns casos o comando para incremento de créditos de assinante pré-pago estava

substituindo o valor anterior pelo quantia a ser incrementada.
2.23.2 Alteração de duração de pulsos de mfc.
Alteração de duração de sinal enviado de 100ms para 200ms.
2.24 VERSÃO SOF98119F1 – 18/07/2001 – ARTUR M. CABRAL
2.24.1 Identificação de erros de placa inválida ou placa ausente por ocasião dos
comandos GRAVA MSGDSP ou COPIA MSGDSP.
Quando os comandos GRAVA MSGDSP OU COPIA MSGDSP eram usados referenciando

uma posição onde não existia uma placa o comando não retornava até ser cancelado.
2.24.2 Novos serviços suplementares de transferência para caixa postal.
Implementados serviços suplementares de transferência para caixa postal quando terminal

ocupado (TCXPOCP) e para terminal não responde (TCXPNR).
2.24.3 Criação de nova mensagem da máquina anunciadora.
Criação de mensagem de máquina anunciadora para ser usada por ocasião de transferencias
para caixa postal.
2.24.4 Criação de novo tom.
Criado novo tom: TCCE (tom de controle de chamada em espera).
2.24.5 Criação de novas temporizações.
Implementadas as seguintes temporizações : temporização de tom de operação aceita (TOA);

temporização de tom de operação incorreta (TOI); temporização de tom de controle de
chamada em espera(TDTCE); temporização de sinal multifrequencial ausente para sinalização
5s (TA5S)e temporização de sinal multifrequencial presente para sinalização 5s (TP5S).
2.24.6 Alteração do comando IT-INST
Acrescentada a informação ao comando IT-INST de qual o mestre bilhetador corrente, quando

este existir.

ATTACHMENT
2.24.7 ( PR-02300 )Siga-me tem preferência sobre o grupo de busca.
O terminal que faça parte de um grupo cpct deixa de fazer parte do grupo de busca se possuir
siga-me habilitado.
2.24.8 ( PR-02500 )Inclusão de MSN para assinante analógico.
Os terminais analógicos podem possuir até dois números de assinantes diferentes desde que o
primeiro tenha o serviço suplementar de MSN ("Multiple Subscriber Number") habilitado.
2.24.9 ( PR- 02500 )Tratamento de "ring" diferenciado para MSN analógico.
O controlador envia um "ring" diferenciado para o terminal de assinante quando o número

referenciado é o segundo número para este terminal.
2.24.10 ( PR-5200 ) Inclusão no SUPTRA-CHM de contador de chamadas atendidas

após um tempo limite.
No supervisor de tráfego de chamadas foi incluído o contador para chamadas com tempo de
atendimento maior que um determinado intervalo medido em segundo que pode ser
configurado pelo operador.
2.24.11 ( PR-5600 ) Alteração no SUPDES-ROTA
Inclusão de número de juntores da rota na supervisão de desempenho de rota.
2.24.12 ( PR-9800 ) Alteração no Serviço Especial Local.
Alteração do comando de criação de serviço especial local para aceitar sequências iniciadas
com os símbolos '*' e '#'. As sequências de SEL iniciadas com os dois caracteres supracitados
não deverão ser programadas no plano de roteamento. Se alguma sequência programada para
SEL for igual a alguma outra já existente na tabela de serviços suplementares a sequência de
SEL prevalecerá, portanto a sequência de serviço suplementar deverá ser redefinida.
2.24.13 Utilização de tom de CGT.
O tom de ocupado (TOCP) somente será utilizado para indicar que o assinante B realmente
está utilizando o terminal, para todos os outros casos em que o tom de ocupado era utilizado
será utilizado o tom de congestionamento.
2.24.14 Resolução de falha de juntores JTS/JDL.
Quando somente os 15 primeiros juntores estavam criados, após uma queda do TX, os
juntores continuavam apresentando bloqueio externo mesmo depois de restabelecido o TX.

ATTACHMENT
2.24.15 Implementação do alarme de base de dados desatualizada.
Implementação de alarme de base de dados desatualizada.
2.24.16 Criação dos comandos MD-NDPRE e IT-NDPRE.
Criação dos comandos MD-NDPRE e IT-NDPRE.
2.24.17 Alteração do nível do alarme de falha no link de sinalização V5.
Alteração do nível do alarme de falha no link de sinalização V5.
2.24.18 Alteração no comando MD_TRONCO.
Tornou-se configurável a utilização de CRC4 em E1 através do comando "MD TRONCO

TRONCO=X, PLACA=XX-XX, TIP=E1, FRM={CRC4,NCRC4}".
2.24.19 Inclusão de sinalização QSIG.
Alterações do CSR em função do QSIG:

Comandos CR-ASS e IT-ASS - inclusão do mnemônico QSIG para o parâmetro SNL para
assinantes alocados em acesso primário.
CR-ROTA e IT-ROTA -inclusão do mnemônico RRC para o parâmetro TIP.
Inclusão dos comandos CR-IRC, IT-IRC e SU-IRC para a criação, verificação e supressão do
parâmetro IRC(Identificador de rede corporativa).
MD-TER e IT-TER , possibilidade de atribuir pré-dígito para uma interface QSIG alocada para
um dado TER=uni-pla-cir.
MD-ORI - o parâmetro ROT1, passa a considerar as indicações de índices de início e partida.
2.25.1 Placa JDT00012A - NT 01/063.
Resolução de problemas relacionados com a placa JDT00012A, tais como alinhamento e

bloqueio.
2.25.2 BINA em MPS-B.
Resolvida a falha da placa MPS-B que não estava enviando os dígitos para o BINA.
2.26.1 Falha de detecção MFC.
Resolução de falha de detecção de MFC quando está sendo utilizado equipamento de

compressão de E1.

ATTACHMENT
2.27.1 Respondedor automático.
Habilitado o respondedor automático para atender chamadas efetuadas através do comando

AT-TSTCHA.
2.28.1 Sinalização de linha R2MFC e registro R2 para as Filipinas.
Adaptação na sinalização de linha R2 digital e de registro para as Filipinas. Foi criado o

parâmetro EN0, alterado através do comando MD-SNLR2, que configura o sinal MFC que
deve ser interpretado como “Requisição de último dígito (n)”.
2.28.2 Novos códigos de país.
Criação de novos códigos de país (UA) relativo à Ucrânia e (PHI) relativo às FILIPINAS.
Afetando os comandos do CSR MD-PAIS e IT-PAIS.
2.28.3 Registro de alarme de limiar de bilhetes.
Manter o alarme presente de indicação que o limiar de bilhetes foi atingido.
2.28.4 Novo formato de bilhete de RDC.
Criação de bilhete RDC para chamadas de entrada quando o usuário possui o serviço
suplementar de RDC habilitado.
2.28.5 RDC para chamada de entrada.
Criação de bilhete RDC para chamadas de entrada quando o usuário possui o serviço
suplementar de RDC habilitado.
2.28.6 Liberação de placa MPSC com 2 enlaces.
Suportada placa MPSC com 2 enlaces possibilitando 4 conferências com 3 participantes, 9

enviadores DTMF/FSK, 20 detectores DTMF, 24 transceptores MFC, geração/detecção de
500Hz, geração de tons NAR acrescidos as funcionalidades da MPSC anterior.
2.28.7 Erro na criação de acesso MAP.
Corrigido problema relativo a criação de acessos MAP quando utilizadas mais de uma placa.

ATTACHMENT
2.28.8 Linha executiva.
O serviço suplementar de linha executiva foi alterado para se comportar como linha direta
quando sua temporização for configurada igual a zero.
2.28.9 Valores-padrão de tons.
Os valores-padrão para os tons foram alterados os valores antigos. (anteriores à resolução

252)
2.28.10 V5 Problema de perda de tom.
Problema de perda de tom no assinante originador da chamada (Lado AN) quando a interface
V5 caía.
2.28.11 Atualização do estado dos links V5.
Atualização do estado dos links de uma interface V5 durante o shutdown.
2.28.12 Atualização do Status dos enlaces V5 no CSR.
Após o switch over ou após desabilitarmos um link o status demonstrado no CSR estará
compatível com o AN.
2.28.13 Novas mensagens tratadas no estado Switch over recover.
Tratamento das novas mensagens:

PROT_MDU_RESET_SN_COM,
PROT_MDU_RESET_SN_ACK,
PROT_MDU_RESET_SN_IND
2.28.14 Desprogramação de MSN.
Corrigida falha que inibia a desprogramação de serviço suplementar de MSN.
2.28.15 Teste de continuidade ISUP.
O teste de continuidade para placa MPS-C não funcionava por falha na detecção de tom de
2100 Hz. Problema solucionado com a troca do firmware da placa.

ATTACHMENT
2.29.1 Novo formato de bilhete RDC para chamadas de entrada.
Criado novo formato de bilhete RDC para chamadas de entrada com código identificador igual
a três (3). Basicamente a única diferença deste formato para o bilhete RDC de chamadas
originadas, formato (2), é a seguinte:
formato 2 … | assA | Classe assA | assB | Classe assB | …
formato 3 … | assB | Classe assB | assA | Classe assA | …
2.29.2 Melhoria no procedimento de identificação de link durante o startup da

interface V5 (lado LE).
Foi melhorado o procedimento de identificação de link durante o startup da interface V5 (lado

LE)
2.30 VERSÃO SOF98119G1 – 31/01/2002 – ARTUR M. CABRAL
2.30.1 Acesso indevido a contadores de juntores.
A central estava resetando ao tentar acessar contadores de juntores em posições inexistentes.
2.30.2 Registro do número de Assinante A para chamadas de entrada aumentado.
Para chamadas de entrada o registro detalhado de chamadas (RDC) armazena agora o

número do assinante A com até 16 dígitos.
2.30.3 Geração de freqüência pela placa MMC-C.
A placa MMC-C passa a gerar freqüência de 12 KHz ou 16 KHz caso não esteja presente na
sua unidade nenhuma placa MPS. Caso uma MPS seja instalada automaticamente a MMC-C
interrompe a sua geração de freqüência. A opção entre 12 ou 16 KHz é feita via CSR através
do já utilizado comando MD-CENPOP.
2.30.4 Criação de comando DT-INST .
Criado o comando do CSR DT-INST UNI=XX que prepara o sistema operacional da unidade de
bilhetagem para ser desligado.
2.30.5 Novas mensagens de erro para o comando MD-TRONCO
Novas mensagens de erro de consistência de parâmetros passados no comando MD-

TRONCO: “Tipo do tronco inválido” e “Tipo do quadro inválido ”

ATTACHMENT
2.30.6 Tratamento das sinalizações DP1, DP2 e MF-Shuttle (Ucrânia)
Tratamento das sinalizações DP1, DP2 e MF-Shuttle, associadas ao juntor. Os comandos do

CSR são:
CR JUN ..... SNL=DP1

CR JUN ..... SNL=DP2
CR JUN ..... SNL=MFSH
2.30.7 Tratamento dos protocolos RTR, RTL, SL, SLM e ZSL(Ucrânia)
Tratamento dos protocolos RTR, RTL, SL, SLM e ZSL, associados à rota. Os comandos do
CSR são:
CR ROTA ..... TIP=RTR

CR ROTA ..... TIP=RTL
CR ROTA ..... TIP=SL
CR ROTA ..... TIP=SLM
CR ROTA ..... TIP=ZSL
2.30.8 Tratamento da identificação do Assinante A (Ucrânia)
Tratamento da identificação de A (ANI procedure) após a ocupação do juntor, associada à rota.

O comando do CSR é:
CR ROTA .... ANI=0
Obs.: a ausência do parâmetro ANI é tratada como ANI após a ocupação, sendo assim,
esta programação não é obrigatória.
Tratamento da identificação de A (ANI procedure) durante a discagem. O comando do CSR é:
CR ROTA .... ANI=x (onde x tem que ser diferente de ZERO)
2.30.9 Envio do segundo tom de discar (Ucrânia)
Envio do segundo tom de discar (gerado pela própria central BZ5000) para TODOS os
assinantes quando o primeiro dígito discado é o dígito 8. Esta facilidade é ativada com a
combinação de TODOS os comandos do CSR abaixo:
MD PAIS PAIS=UA
MD CENPOP POP=SEGTOM
MD DIGESP CHEX=8
Obs.: o dígito 8 deve ser inserido para análise no plano de encaminhamento, independente

ATTACHMENT
de ser ou não discado pela central BZ5000.
Envio do segundo tom de discar pelo juntor de entrada. O envio deste tom só ocorrerá quando
a chamada tem tratamento ANI, sendo que ele será enviado após o tratamento ANI, isto é,
após o envio do sinal ANI-WITHDRAW. Esta facilidade é associada à rota e é configurada via
comando do CSR abaixo:
MD ROTA ..... POP=SEGTOM

Obs.: a programação acima deve ser feita para a rota de saída que receberá o tom de
discara, como forma de orientação ao programa controlador que o áudio deve ser comutado
após o tratamento ANI.
2.30.10 Ocupação do juntor após a discagem do dígito 8 (Ucrânia)
Ocupação do juntor após a discagem do dígito 8, sem o envio deste dígito, isto é, sem a
discagem deste dígito. Esta facilidade é ativada com a combinação de TODOS os comandos
abaixo:
MD PAIS PAIS=UA
MD DIGESP CHEX=8
CR ROTA ROTA=rota.....POP=SEGTOM
MD ORI SEQ=8 ..... ROT1=rota-1-1
2.30.11 Chamada R2 trânsito para a Argentina.
Quando o país configurado no programa controlador for a Argentina o programa foi alterado
para repassar o sinal mfc de fim de número I-15 ou I-12 ao invés de sempre enviar I-15(Brasil).
2.30.12 Alteração do envio da categoria de B para chamadas transferidas para a

Argentina.
Quando o país configurado no programa controlador for a Argentina e a chamada for

transferida via siga-me, o controlador passa a enviar a própria categoria de B e não a
categoria 11 como ocorre para o Brasil.
2.31.1 Criação de NOCO=TR para a Bolívia.
Quando configurado o parâmetro NOCO=TR no SSU MSN não valida o número de A que
chega no SETUP do acesso e passa transparentemente para as centrais à frente.
2.31.2 Correções na interface PRI
O canal 16 (de sinalização) estava sendo alocado como canal B e correção de reset da

ATTACHMENT
unidade que ocorria quando havia falha de transmissão na interface PRI com o PABX HICOM.
2.31.3 Conversor PRI/ISUP Avaya.
Incorporada a funcionalidade da central se comportar como conversora PRI/ISUP. Quando a

central se encontra em modo “Configuração” pode-se, através do comando MD-CENPOP
POP=CONV, ativar esta funcionalidade e para desativá-la deve-se, também em modo
“Configuração”, utilizar o comando MD_CENPOP POP=NPOP. Funcionando com o parâmetro
de operação CONV a central associa as placas MAP que somente podem ser criadas nas
posições 1, 3, 5 e 7 às correspondente JTS nas posições 9, 11, 13 e 15 respectivamente. Para
esclarecer o funcionamento prático temos que chamadas advindas de uma MAP que se
encontre na posição 5 de uma dada unidade somente serão encaminhadas a uma JTS que
esteja na posição 13 da mesma unidade e vice-versa.
2.31.4 Correção de reset de unidade.
Estava ocorrendo reset da unidade quando uma placa JDL configurada para V5 estava
instalada no momento do power on.
2.31.5 Falha na ATT.
Acesso ISDN atendendo a uma chamada de entrada muito rápido, fazendo com que o BZ
enviasse para trás fim de seleção duplicado. A chamada podia ser perdida pela central atrás
2.31.6 Problema na sinalização 5S.
Controlador passa a enviar a identificação de A para a central à frente também quando a

tarifação for MMTR (multimedição na trânsito).
2.32.1 Criação de novos mnemônicos para modo Conversor PRI/ISUP .
Criados dois novos mnemônicos para serem usados com o comando MD-CENPOP e
parâmetro POP, CONV1 e CONV2, que vêm substituir o antigo CONV. Agora quando a central
se encontra em modo “Configuração” pode-se, através do comando MD-CENPOP POP=
CONV1 ou CONV2, ativar a funcionalidade de conversor PRI/ISUP. Sendo a única diferença
em termos funcionais que com o parâmetro CONV2 a central não espera receber os dígitos
CID (identificadores da chamada) antes do número do assinante chamado.
2.32.2 Reset na central quando executados comandos relacionados a enlace. CR-

ENL, SU-ENL, MD-ENL e IT-ENL.

ATTACHMENT
A central estava resetando quando o operador utilizava os comandos CR-ENL, SU-ENL, MD-
ENL ou IT-ENL com formato incorreto.
2.32.3 Resolução de problema de desativação do led de ocupação de placas de

juntores JTS, JDT mesmo com algum juntor ocupado.
Quando duas chamadas estavam em curso, passando por uma mesma placa de juntores,
estava ocorrendo o desligamento do led de ocupação quando apenas uma das chamadas era
finalizada e a outra continuava em curso. Isto porque o contador de ocupação da placa estava
sendo decrementado mais de uma vez para um mesmo juntor.
2.32.4 Paramêtro de rota ANIREQ indicador de envio de INR para trás.
Caso o parâmetro de operação de rota ANIREQ esteja ativado, não será enviado o sinal INR
para trás.
2.32.5 Reset da central quando assinante A não identificado no IAM.
O IAM sem identificação de assinante A, quando o número chamado tinha BINA, estava
ocasionando o reset da central por inconsistência no tamanho do número de A.
2.32.6 Envio de UUI no modo conversor PRI/ISUP.
No modo conversor PRI/ISUP está sendo enviado o UUI recebido, ao final dos dados que já
estavam sendo enviados no IAM.
2.32.7 Problema no conversor PRI/ISUP com NOCO relevante do SSU MSN.
Para a central no modo conversor PRI/ISUP, quando configurado o parâmetro NOCO do

serviço suplementar MSN como não obrigatório ou obrigatório, as chamadas não se
realizavam ou ficavam associadas sempre a mesma placa de juntores dependendo da última
chamada efetuada em sentido contrário. Resolvido o problema com a correta identificação do
terminal de origem da chamada.
3 OBSERVAÇÕES
3.1 VERSÃO SOF98119D1

O software SOF98119D1 utiliza um novo esquema de armazenamento dos contadores de
tarifação, que não é compatível com as versões de software anteriores. Para evitar a perda
dos contadores no processo de atualização do software, deve ser seguido o procedimento
descrito
no Boletim Informativo 005.
3.2 VERSÃO SOF98119E1

ATTACHMENT
A central deve ser reconfigurada quando estiver utilizando versão anterior a E1 e for atualizada
versão E1 ou superior.

versão E4 ou superior.

para versão E6 ou superior.
3.5 VERSÃO SOF98119F1

A central deve ser reconfigurada quando estiver utilizando versão anterior a F1 e for atualizada
para versão F1 ou superior.
3.6 VERSÃO SOF98119F5

A central deve ser reconfigurada quando estiver utilizando versão anterior a F5 e for atualizada
para versão F5 ou superior.
3.7 VERSÃO SOF98119G1

A central deve ser reconfigurada quando estiver utilizando versão anterior a G1 e for
atualizada para versão G1 ou superior.
4 COMPATIBILIDADE DE HARDWARE E SOFTWARE
As questões de compatibilidade de hardware e software devem ser obtidas no documento

específico, denominado Relatório de Compatibilidade entre os Produtos da Família
ELCOM (090008).
5 TESTES DE VALIDAÇÃO
Este programa foi testado e aprovado em testes de laboratório.

019-SW

Uploaded by

Copyright:

Available Formats

You might also like

019-SW

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

019-SW

Uploaded by

Copyright:

Available Formats

LUCENT TECHNOLOGIES - BRASIL

BZ5000 LOCAL EXCHANGE SOFTWARE FOR UCP96058C AND

Approved by: Eugênio Lopes Daher 06/29/06

Lucent Technologies – Proprietary

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 1/1

2. PRODUCT HISTORY INFORMATION..................................................................................................11

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 3/3

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 4/4

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 7/7

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 10/10

2. Product History Information

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 11/11

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 12/12

2.1.1.2 DR 4385 – Time stamp on alarms

2.1.1.4 DR 4080 - Corrections in ANI procedure used in Ukraine

2.1.1.5 DR 4080 - Corrections in internetworking for Ukraine signaling

2.1.1.9 DR 4430 - Call Forward Problems

2.1.1.10 DR 4176 - DDC blocking for PRI/ISDN subscribers

2.1.1.13 DR 4176 - Updated Trillium stack

2.1.1.14 DR 4176 - Corrections in call release for ISDN subscribers

2.1.1.15 DR 4176 - Decreased time for MAP initialization

2.1.1.17 Corrections in command for trunk creation

2.1.1.19 Fixed problems in query command for synchronism clock

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 14/14

2.1.1.20 New country: Greece

2.1.1.21 Corrections in failures supervision for trunks

2.1.1.22 Changes in default values of synchronism mesh parameters

2.1.1.24 Increased the kernel heap memory

2.1.1.25 PR13700 – SS password managed by the subscriber

2.1.1.26 PR15000 – EBT service 102

2.2 Revision: 001 – Software Update : 001

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 15/15

2.3.1.2 DR 4473 - Problems on calls with subscribers on busy state – Bolivia

2.3.1.3 Semi-Permanent Switching

2.3.1.4 DR4000 - ISDN for interface V5.2 (PR 8200)

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 16/16

Some characteristics about the feature:

2.3.1.6 DR 4472 - Switch continuously reset

2.4 Revision: 002 – Software Update : 001

SRL-05001-GSW-V11-R01-BZ5000-LE-LPN109253856 LPN: REV 019 Sheet: 17/17

2.5 Revision: 002 – Software Update : 002

2.6 Revision: 003 – Software Update : -

2.6.1.2 DR 4456 - Alarm in SS7 signaling route

2.6.1.3 DR 4000 - ISDN for interface V5.2

2.6.1.4 DR 4000 - Problems in programming MSN for remote BRI subscribers

2.6.1.5 DR 4529 – Increasing the number of Direct Line Supplementary Service

2.6.1.7 DR 4484 – DDI calls routing problem

2.6.1.8 DR 4496 – ISDN Incoming calls in overlap mode (PR 19000)

MD-ORI SEQ = XXX, ROT=XX-XX-XX,……….;

2.6.1.10 New CDR format for the Philippines

2.6.1.11 DR 4475 - New country: Guatemala

Changes in the CSR commands were implemented:

Changes in the CSR commands were implemented:

ISUP Release message with the Signalling Point Code parameter.

Changes in the CSR commands were implemented:

2.6.1.14 DR 4483 – Line hunting group provisioning problem

2.6.1.15 Problems in V5 audio terminal creation