48554709 Resolviing Subsciber Related Problem OSS

Procedure ManualTITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Resolving Subscriber Related Problems (BGw & OSS) APPROVAL: ____________________ Max Maxted (Network Group Operations Manager) : ________________________________ Ray Mutlu (System Support Manager) Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 1 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Table of Contents Document History ...........................................................................................3 DISTRIBUTION..................................................................................................3 PROCEDURE ACTORS....................................................................................3 1 Introduction....................................................................................................3 2 PROCEDURES ..............................................................................................5 3 Terminology..................................................................................................12 4. APPENDIX..................................................................................................13 14 Data...............................................................................................................14 SUBSCRIBER DATA........................................................................................................................................14 2.1 RESOLVING SUBSCRIBER RELATED PROBLEM ........................................................................................................5 1.1 OBJECTIVE .................................................................................................................................................4 1.2 PRE-REQUISITES.................................................................................................................................4 1.3 OVERVIEW............................................................................................................................................4 Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 2 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 DOCUMENT HISTORY Edition Version 1.0 Date Nov 2003 Details DISTRIBUTION DEPARTMENT NWG Operations – Billing Gateway/OSS NWG Quality Assurance PROCEDURE ACTORS NAME Ray Mutlu Dolapo Lawrence Banke Osunsanya DESIGNATION System Support Manager BGw/OSS Engineer ISO/Process Engineer SIGNATURE 1 INTRODUCTION Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 3 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 1.1 OBJECTIVE This manual describes the commands used by BGw/OSS Engineers for sorting out customer related problems on the network. 1.2 PRE-REQUISITES It is assumed that the user of this Guide would have been familiar with: • • • Basic Unix Basic Telecommunication. ALEX library Software • TMOS or Winfiol Terminal 1.3 OVERVIEW This document is simply a guide for the Engineers that will be dealing with switch related subscriber data. Full explanations and command data can be found in Ericsson’s ALEX server and documentation software. This guide is in no way intended to replace or nullify the Ericsson ALEX documentation. Most of the data in this document has been taken from the Ericsson Alex documentation and is to be used as a guide only. This procedure applies to all BGw/OSS, switch, NMC and HLS team members. Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 4 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 2 PROCEDURES 2.1 RESOLVING SUBSCRIBER RELATED PROBLEM This section introduces and explains the detailed general commands in the Ericsson GSM platform for resolving subscriber related problem. Step No 1.0 Step Details Current NE with HLR functionality ABMSC1 = / HLR / AUC / FNR / MSC / LGHLR1 = / HLR / AUC /FNR / LGHLR2 = / HLR / AUC /FNR / PHHLR1 = / HLR / AUC /FNR / Reference 2.0 FNR Commands The data on all the FNR’s must be identical. The FNR is used to determine which HLR the MSISDN is registered on. As at the 1/09/2002 this is the FNR look-up table. ABMSC1 (HLR) = 6213001100… LGHLR1 (HLR) = 6213000100… LGHLR2 (HLR) = 6213000105 PHHLR1 (HLR) = 6213002100… When a call is made the MSISDN is sent to the FNR, the FNR then looks up what IMSI is linked for that MSISDN and then routes the call to the appropriate HLR (VLR) node so that the right subscriber checks can be done. 2.1 FGNTC:MSISDN={msisdn},IMSI={imsi}; • • • Change an already existing MSISDN to IMSI map on the FNR. This is command is normally sent when a sim swap is done. The IMSI linked to the MSISDN in this command must be the same as the IMSI linked to the MSISDN on the HLR. (see HGSDP) 2.2 FGNTE:MSISDN={msisdn}; • • This command will remove the MSISDN and IMSI from the FNR The command is sent when an MSISDN is to be deactivated Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 5 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Step No 2.3 Step Details FGNTI:MSISDN={msisdn}, IMSI={imsi}; • • This command will add the MSISDN and IMSI to the FNR. The IMSI linked to the MSISDN in this command must be the same as the IMSI linked to the MSISDN on the HLR. (see HGSDP) Reference 2.4 FGNTP:MSISDN={msisdn}; • • • This command will print the MSISDN and IMSI from the FNR. You will then be able to determine which HLR to check for the subscriber’s profile. If the FNR data is incorrect according to the data on the HLR then it could mean that the subscriber can’t receive calls. 3.0 AUC Commands The AUC is used for subscriber authentication. And this is done before the call is routed anywhere else. If the data in the AUC is incorrect then the subscriber will not have access to the network and the phone will normally display “No Access”. Each HLR node has it’s own AUC which contains IMSI details of only the IMSI’s registered on that HLR. IMSI’s should never be re-used that is why they have a huge range. When a subscriber has a SIM swap then the old IMSI must be removed from the relevant AUC and the new IMSI and related data must be registered on the correct AUC for that IMSI range. 3.1 AGSUE:IMSI={imsi}; • • This command will remove the IMSI and related data from the AUC. The command is sent when an MSISDN is to be deactivated or there is a SIM swap. 3.2 AGSUI:IMSI={imsi},EKI={Eki}, KIND={kind value},A4IND=0; • The provision command that adds the IMSI, Eki (Encrypted key), Kind (Key indicator) and Algorithm indicator data to the AUC. • • • The Eki is a 32 bit Hexadecimal number that is encrypted. The A4IND set to zero (0). In the Auc10, Ericsson AUC, there are five different decryption keys that you can use at once and the one for that range is indicated by the “KIND” value which is determined as follows: Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 6 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Step No Step Details ABMSC1, 621300110000000, 621300110030004,1,15 ABMSC1, 621300110030005, 621300110999999,2,15 LGHLR1, 621300010000000, 621300010120004,1,14 LGHLR1, 621300010120005, 621300010499999,2,14 LGHLR1, 621300011500000, 621300011999999,2,14 LGHLR2, 621300010500000, 621300011499999,2,14 PHHLR1, 621300210000000, 621300210050004,1,16 PHHLR1, 621300210050005, 621300210999999,2,16 Reference 3.3 AGSUP:IMSIS={imsi}; • This command will print the IMSI, Eki, KIND and A4IND values from the AUC. • Make sure that the kind value is correct for that range. If any of the data is incorrect for that IMSI then the subscriber will not be able to make use the GSM network. 4.0 4.1 HLR Commands HGICI:MSISDN={msisdn},NIMSI={new imsi}; The command is used to do sim swap on the same HLR. The Profile will stay the same just the IMSI will change. 4.2 HGMCI:MSISDNS={all or specify range},SUD={sud}, NEWSUD={newsud},UPDATENET; • The command will initiate a mass subscriber profile changes on all MSISDN’s within the range specified and those meeting the specification in the {sud} area. NOTE: Exercise extreme caution when issuing this command. 4.3 HGSDC: MSISDN={msisdn},SUD={sud}-{flag}; HGSDC:MSISDN={msisdn},PROFILE={profile no}; • • • The command is used to make “permanent subscriber data” changes. These changes go into a little more depth at “permanent data”. The second command will be used when trying to migrate a subscriber from one profile to another, the subscriber will then assume permanent Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 7 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Step No Step Details subscriber settings as laid out in the profile. Individual flag change will need to be made if necessary. Reference 4.4 HGSDP:MSISDN={msisdn},{ all/suda/loc }; OR HGSDP:IMSI={imsi}, { all/suda/loc }; • This command will print out the subscriber profile data as chosen in the {} parenthesis. • More detail on these subscriber flags are covered below, at “permanent data 4.5 HGSLR:MSISDN={msisdn}; • This will reset the subscriber address on the VLR, the subscriber will then need to logon to the network again by switching off and switching on their handset. 4.6 HGSPC:PROFILE={profile no},NEWSUD={sud}-{flag}&&{sud}-{flag}…..; • When a subscriber is activated for the first time they are assigned a standard profile (Template) that is already created on the switch. • Use this command to make changes to the individual templates; they are numbered from 1 –256. • Current profile templates are: PROFILE 30 = Post-Paid subscribers PROFILE 40 = Data only subscribers PROFILE 50 = Pre-Paid subscribers PROFILE 51 = Pre-Paid subscribers Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 8 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Step No 4.7 Step Details HGSPP:PROFILE={profile no}; • This command merely prints the data that has been set-up for the profile template. A profile is a template that one can activate to the subscriber individual profile instead of setting all the flags individually. • Changes made to the profile will not affect already provisioned subscribers. The change in the template will only affect subscriber that are provisioned using the amended template. Reference 4.8 HGSSE: MSISDN={msisdn},BSG={bsg},SS={ss}; • This command will cancel the selected supplementary service that is seen as “ACTIVE” when issuing a HGSDP(all) command. • BSG = Bearer service group: BS20 = Data service (Asynchronous) TS10 = Voice service TS20 = SMS service TS60 = Fax service • SS = Supplementary Service Eg. BOIC, BAIC, BAOC, CFU, CFNRY, CFNRC, etc. 4.9 HGSSI: MSISDN={msisdn},BSG={bsg},SS={ss},FNUM={number},TIME={sec}; HGSSI: MSISDN={msisdn},BSG={bsg},SS={ss},FNUM={number}; HGSSI: MSISDN={msisdn},BSG={bsg},SS={ss}; HGSSI: MSISDN={msisdn},SS={ss}; • This command will activate (initiate) the selected supplementary service and change its state to “ACTIVE”. • In the case of Call Forwarding the FNUM (Forwarding number) is supplied in a printout of the HGSDP(all) command. • It’s best to use the BSG portion to specify a change to particular Bearer Service Group otherwise changes will be made to all Bearer Service Groups that contain that supplementary service . Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 9 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Step No 4.10 Step Details HGSUE: MSISDN={msisdn}; • This command will deactivate the specified MSISDN from the HLR only. • Exercise extreme caution when issuing this command. HGSUI: MSISDN={msisdn},IMSI={imsi},PROFILE={profile no}; • This will provision the specified MSISDN and IMSI to the HLR function of the AXE node. • The profile will set all pre-defined flags for that subscriber. It is therefore of utmost importance that when this command is issued the correct profile must be chosen. • The IMSI will need to be provisioned in that HLR’s AUC before this command will execute. • Take note of the IMSI and make sure that the IMSI range is correct for that HLR Reference 4.11 5.0 ADDITIONAL FLAGS AUTHD: Indicate if the subscriber IMSI is/was provisioned on the AUC. DCF: Default Call Forwarding can be set by the operator. Please see notes on DCF below and take note of the different SOSDCF settings. MPTY: Multi-party service needs to be active for the conference calling option. OBA: This flag is not visible but, if it is set to “1” then the subscriber will be suspended (OBO-1 & OBI-1) and vice-versa when set to “0”. Take note that un-suspending a subscriber will result in their international call bar still being active (OBO-2 & OBI-0). OBI: Is for barring of incoming calls. OBO: Is for barring of outgoing calls. OFA: Is for Call forwarding analysis. In a nutshell it is used to determine which Voice-mail the subscribers’ diverts must be set to. OICK: Originating Intelligent Network Category Key. This value indicates which Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 10 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Step No Step Details SDP platform the pre-paid subscriber is active on. If this is set incorrectly the subscriber will experience a break in service. Please consult the prepaid team if this is encountered. OSB3: Operator Specific Barring OSB4: STYPE: Subscriber type, this is purely for billing purposes. If the number end with at “1” then the subscriber is active on the pre-paid billing platform and if it ends with a “2” then the subscriber is on the post-paid billing platform. TICK: Terminating Intelligent Network Category Key. This value is “1” digit up from it’s corresponding OICK value. BS2F, BS2G, BS3F and BS3G need to be set to a value other than “0” (like “1”) for HSCSD to be working on the subscribers’ profile. Reference Please take the time to go through the example below and used the hyperlinks supplied. At the “detail” text you can click on the hyperlink and come back to the original example portion. For those who would like to get to know subscriber data even better, go through the notes below and familiarize yourself with the individual settings and meanings. 5.0 END Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 11 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 3 TERMINOLOGY Term/Abbreviation BGw OSS GSM IMSI MSISDN BAIC BAOC CFU DCF SPN BOIC TMOS VLR FNR AUC HLR HGSDP BSC BSG CFNRC CFNRY MSC STP Explanation Billing Gateway Operation Support System Global System for Mobile Communication International Mobile Subscriber Identity Mobile Station ISDN number Barring of All Incoming Calls Barring of All Outgoing Calls Call Forwarding Unconditional Default Call Forwarding Single Personal Number Barring of All Outgoing International Calls Telecommunication Management Operating System Visitor Location Register Flexible Numbering Register Authentication Centre Home Location Register HLR Subscriber Data Print Base Station Controller Basic Service Group Call Forwarding Not Reachable Call Forwarding No Reply Mobile Switching Centre Signalling Transfer Point Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 12 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 4. APPENDIX REQUIRED DOCUMENTS The following documents are required: <HGSDP:MSISDN=2348032001773,ALL; HLR SUBSCRIBER DATA SUBSCRIBER IDENTITY MSISDN IMSI STATE AUTHD 2348032001773 621300010003919 CONNECTED PERMANENT SUBSCRIBER DATA SUD CAT-10 DBSG-1 STYPE-2 OBR-2 BS26-1 TS11-1 TS21-1 TS22-1 TS62-1 OFA-1 PWD-0000 CFU-1 CFB-1 CFNRY-1 CFNRC-1 BAOC-1 BOIC-1 BOIEXH-1 BAIC-1 BICRO-1 CAW-1 SOCFB-0 SOCFRY-1 SOCFRC-0 SOCFU-0 SOCB-1 SOCLIP-0 SOCLIR-2 HOLD-1 CLIP-1 CLIR-1 AMSISDN NONE BS BC AVAILABLE SUPPLEMENTARY SERVICE DATA BSG TS10 SS STATUS FNUM SADD BAIC NOT ACTIVE BAOC NOT ACTIVE BICRO NOT ACTIVE BOIC NOT ACTIVE BOIEXH NOT ACTIVE CAW NOT ACTIVE CFU NOT ACTIVE CFB NOT ACTIVE CFNRY NOT ACTIVE CFNRC NOT ACTIVE BSG TS20 SS STATUS FNUM SADD BAIC NOT ACTIVE BAOC NOT ACTIVE BICRO NOT ACTIVE BOIC NOT ACTIVE BOIEXH NOT ACTIVE BSG TS60 SS STATUS FNUM SADD BAIC NOT ACTIVE BAOC NOT ACTIVE BICRO NOT ACTIVE BOIC NOT ACTIVE TIME TIME TIME Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 13 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 BOIEXH NOT ACTIVE CAW NOT ACTIVE CFU NOT ACTIVE CFB NOT ACTIVE CFNRY NOT ACTIVE CFNRC NOT ACTIVE BSG BS20 SS STATUS FNUM SADD BAIC NOT ACTIVE BAOC NOT ACTIVE BICRO NOT ACTIVE BOIC NOT ACTIVE BOIEXH NOT ACTIVE CAW NOT ACTIVE CFU NOT ACTIVE CFB NOT ACTIVE CFNRY NOT ACTIVE CFNRC NOT ACTIVE LOCATION DATA VLR ADDRESS MSRN 4-2348030000120 END Date Issued: Date Effective: November, 2003 December, 2003 TIME MSC NUMBER 2348030000120 LMSID DATA SUBSCRIBER DATA Parameter Description IMSI International Mobile Subscriber Identity (IMSI) Digit string 6 ~ 15 digits Each digit is 0-9. NIMSI New IMSI number Digit string 6 ~ 15 digits Each digit is 0-9. MSISDN Mobile Station ISDN number (MSISDN) Digit string 5 ~ 15 digits Each digit is 0-9. AMSISDN Additional MSISDN Digit string 5 ~ 15 digits Each digit is 0-9. SS Supplementary Service (SS) Identifier 2 ~ 6 characters Allowed SS identifiers are shown in Table 1. For information on which Basic Service Groups are applied by a SS, see Table 9. SS identifier ALLSS BAC BAIC BAOC BIC BICRO BOC BOIC BOIEXH CAW CCFS Description ALL SUPPLEMENTARY SERVICES ALL CALL RESTRICTION SERVICES BARRING OF ALL INCOMING CALLS BARRING OF ALL OUTGOING CALLS BARRING OF INCOMING CALLS BARRING OF ALL INCOMING CALLS WHEN ROAMING OUTSIDE THE HOME PLMN COUNTRY BARRING OF OUTGOING CALLS BARRING OF ALL OUTGOING INTERNATIONAL CALLS BARRING OF ALL OUTGOING INTERNATIONAL CALLS EXCEPT THOSE DIRECTED TO THE HOME PLMN COUNTRY CALL WAITING ALL CONDITIONAL FORWARDING SERVICES Action D D A/D/P A/D/P D A/D/P D A/D/P A/D/P A/D/P R/A/E/D Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 14 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 CFB CFNRC CFNRY CFS CFU DCF SPN Action Identifier R A E D P SUD Date Issued: Date Effective: November, 2003 December, 2003 CALL FORWARDING ON MOBILE SUBSCRIBER BUSY CALL FORWARDING ON MOBILE SUBSCRIBER NOT REACHABLE CALL FORWARDING ON NO REPLY ALL FORWARDING SERVICES CALL FORWARDING UNCONDITIONAL DEFAULT CALL FORWARDING SINGLE PERSONAL NUMBER Description This string can be used in the command HGSSI to register a Supplementary Service. This string can be used in the command HGSSI to activate a Supplementary Service This string can be used in the command HGSSE to erase a Supplementary Service This string can be used in the command HGSSE to deactivate a Supplementary Service. R/A/E/D/P R/A/E/D/P R/A/E/D/P R/A/E/D R/A/E/D/P R/E/P R/E/P This string can appear in the printout initiated by command HGSDP (SUPPLEMENTARY SERVICE DATA ) Subscriber Data (SUD) Expressed as a-b where: a SUD code Identifier 2 ~ 6 characters b SUD value Numeral 0 ~ 65535 Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 15 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 SUD Code Description ACC ACCOUNT CODES 0 = not provided 1 = provided and mandatory 2 = provided and optional Date Issued: Date Effective: November, 2003 December, 2003 SUD Value 0-2 Action L/P/S/D The availability of this parameter value depends on commercial agreements. AOC ADVICE OF CHARGE 0 = Advice of charge not provided 1 = Advice of charge information provided 2 = Advice of charge charging provided BAIC BARRING OF ALL INCOMING CALLS 0 = not provided 1 = provided BAOC BARRING OF ALL OUTGOING CALLS 0 = not provided 1 = provided BICRO BARRING OF ALL INCOMING CALLS WHEN ROAMING OUTSIDE THE HOME PLMN COUNTRY 0 = not provided 1 = provided BOIC BARRING OF ALL OUTGOING INTERNATIONAL CALLS 0 = not provided 1 = provided BOIEXH BARRING OF ALL OUTGOING INTERNATIONAL CALLS EXCEPT THOSE DIRECTED TO THE HOME PLMN COUNTRY 0 = not provided 1 = provided BS21 BEARER SERVICE "DATA CIRCUIT ASYNCHRONOUS 300 b/s" 0 = not subscribed 1 = subscribed Incompatible with BS2G when both SUD's are entered in commands HGMCI (parameter NEWSUD) or HGSPC (parameter SUD), and their values are different from zero. Incompatible with BS2F when both SUD's are entered in commands HGMCI (parameter NEWSUD) or HGSPC (parameter SUD), and their values are different from zero. BS22 BEARER SERVICE "DATA CIRCUIT ASYNCHRONOUS 1200 b/s" 0 = not subscribed 1 = subscribed Incompatible with BS2G when both SUD's are entered in commands HGMCI (parameter NEWSUD) or HGSPC (parameter SUD), and their values are different from zero. Incompatible with BS2F when both SUD's are entered in commands HGMCI (parameter NEWSUD) or HGSPC (parameter SUD), and their values are different from zero. BS23 BEARER SERVICE "DATA CIRCUIT ASYNCHRONOUS 1200-75 b/s" 0 = not subscribed 1 = subscribed Incompatible with BS2G when both SUD's are entered in commands HGMCI (parameter NEWSUD) or HGSPC (parameter SUD), and their values are different from zero. Incompatible with BS2F when both SUD's are entered in commands HGMCI (parameter NEWSUD) or HGSPC (parameter SUD), and their values are different from zero. BS24 BEARER SERVICE "DATA CIRCUIT ASYNCHRONOUS 2400 b/s" 0 = not subscribed 1 = subscribed Incompatible with BS2G when both SUD's are entered in commands HGMCI (parameter NEWSUD) or HGSPC (parameter SUD), and their values are different from zero. 0-1 L/P/S/D 0-1 L/P/S/D 0-1 L/P/S/D 0-1 L/P/S/D 0-1 L/P/S/D 0-1 L/P/S/D 0-1 L/P/S/D 0-1 L/P/S/D 0-1 L/P/S/D 0-2 L/P/S/D Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 16 of 17 Procedure Manual TITLE: OSS Procedure Resolving Subscriber Related Problems Document Number: MTNN0-NWG-NDD-PRO025 Document Revision: Version 1.0 Date Issued: Date Effective: November, 2003 December, 2003 Last changed on 10/12/2003 Last changed by: Banke Osunsanaya Page 17 of 17