creating cod for axe example4 T5MINAIEGIHXD7O272D573S7YG6323M6YTA5KTQ


Monitoring, Initiate ERICSSON ///  Example 305/1013-FCK 114 62 Uen, A COMMAND DESCRIPTION  Uppgjord - PreparedETXMALS Faktaansvarig - Subject responsibleEEI/SPH HAXE Nr - No1/190 82-CNT 123 9999 Uen Dokansv/Godk - Doc respons/ApprovedUAB/K/UEC (Henrik Almeida) Kontr - CheckedEEIGCN Datum - Date1996-11-14 RevA File  MONTIMonitoring, Initiate 1   Format 1.1   Command / \ |DEV=dev[,BCH=bch]| MONTI:+ + [,BNB=bnb]; |SNB=snb | \ / 1.2   Parameters BCH=bchB-channel identityThis parameter initiates monitoring on a specific B-channel for applications where one device corresponds to one access Numeral 1 - 30 BNB=bnbB-number for listening or making a speech connection to test position Digit string 1 - 16 digits Each digit is 0-9 or #10-#15. DEV=devDevice designation Expressed as dety-n where: detyDevice type Identifier 1 - 7 characters The value for this parameter is system defined. nDevice number Numeral 0 - 65535 The maximum value is defined by Size Alteration Event (SAE) 500 in the device-owning block. Alternative expressions can be found in the Application Information for block TRANand the relevant device block. SNB=snbSubscriber number Digit string 1 - 20 digits Each digit is 0 - 9 or #10 - #15. The maximum number of digits can be found in the Application Information for block TRAN. 1.3   Dialogue Parameters CON;This parameter executes trunk offering of the monitored object.This cannot be given if offering with speech facility has already been executed. END;This parameter disconnects the monitoring function and ends the dialogue command. NXT;This parameter initiates monitoring on the next channel of the monitored object.This can only be used if there is more than one channel for the monitored object and if parameter BCH has not been specified. It may only be given after a monitoring connection has been established. SON;This parameter executes trunk offering with the speech facility of the monitored object. 2   Function This command orders trunk offering, in dialogue with the function, in the group switch for monitoring of an established call. The command can only be ordered and executed from a defined test position in the exchange. The function can handle monitoring on successive channels of ISDN subscriber lines with more than one channel. Trunk offering is not permitted for certain subscriber categories. In applications where one device corresponds to one primary rate access, it is possible to initiate monitoring on a specific B-channel using parameter BCH. If parameter BCH is not specified, monitoring is performed on the first busy channel. If no linked task individual is found for the first B-channel in an ISDN basic access environment, the monitoring proceeds on the second B-channel and printout NO LINKED TASK INDIVIDUAL FOR B-CHAN 1 - CHECKING B-CHAN 2 is received. Checks are also made to determine whether the working state of the indicated device is BUSY and whether the established call is in a speech position. When a command has been analysed, a connection is first set up to the monitoring equipment. This connection is made possible by associating the Input/Output (IO) device of the test position from which the command was given) with a subscriber number that has been predefined for the test position by command. A number that has been predefined for another test position can also be indicated in the command using parameter BNB. This is used when no association to the IO device identity can be obtained, for example, due to switched IO channels when the test position is remote. The B-number of the test position is obtained from a table placed centrally in the system. If a device is specified in the command, and is not connected in the incoming group selector, the monitoring function may initiate tracing of the multiple point for the connection of the group selector. Tracing may also be initiated to determine whether the call is protected. A correctly entered command results in a speech connection to the telephone set at the test position. A ringing signal is received and when answered, a conference device is inserted into the call. If this is successful, printout READY FOR CONNECTION is received, verifying that all is correct. If a fault is detected in the command analysis, or in the above checks, a procedure printout is received with the relevant fault information. If there are no faults, the normal sequence may continue and parameter CON may be used to execute trunk offering of the established call, and printout MONITORING ESTABLISHED is received. If the operator wishes to enter the line with conversation about the monitored call, this can be done using parameter SON, which results in printout SPEECH MONITORING ESTABLISHED. It is not necessary to give parameter CON prior to parameter SON. For ISDN subscriber lines with more than one B-channel, parameter NXT may be used to prepare monitoring for the next busy channel once a monitoring connection has been successfully established. Disconnection of monitoring set up by the operator is performed using parameter END, or by the operator placing the phone on-hook, which also ends the established dialogue and the command function. Printout CONCLUSION OF COMMAND MONTI is received. Monitoring ends automatically after 4 minutes (or a multiple of 4 minutes) of dialogue time supervision. If limited time duration of monitoring is in operation, the monitoring function ends after the time set has expired, and printout MONITORING TIME-LIMIT EXCEEDED is received. The control character "commercial at" from the IO device makes it possible to park the established dialogue temporarily, which opens the IO device for new input. The operator can then request a status inquiry, relay operation, or take other actions towards the connected device. Returning to the parked dialogue is done by using the key for normal release of the IO device. Details of the monitored calls are presented in printout MONITORING REGISTRATION DETAILS, which can be received using command MONRP or automatically when the file containing the monitoring registrations is full. The order does not remain after system restart. 3   Examples 3.1   Example 2 (<)MONTI:SNB=9900220; (READY FOR CONNECTION) (:) CON; (MONITORING ESTABLISHED) (:) SON; (SPEECH MONITORING ESTABLISHED) (:) END; (CONCLUSION OF COMMAND MONTI) (END) The subscriber with number 9900220 is being monitored. Monitoring is initiated towards the connection. 3.2   Example 2 (<)MONTI:DEV=LIBA-0; (READY FOR CONNECTION) (:) CON; (MONITORING ESTABLISHED) (:) NXT; (READY FOR CONNECTION) (:) CON; (MONITORING ESTABLISHED) (:) END; (CONCLUSION OF COMMAND MONTI) (END) The subscriber connected to device LIBA-0 is being monitored. Monitoring is initiated towards the connection. Monitoring proceeds on the second channel of the device. 4   Printouts 4.1   Check Printout Not relevant. 4.2   Procedure Printouts NOT ACCEPTED fault type fault type FUNCTION BUSY         The function is busy. FORMAT ERRORdetails         The command or a parameter was incorrectly specified. UNREASONABLE VALUEdetails         The parameter was specified with an unreasonable value. FAULT CODE 3 B-CHANNEL NOT AVAILABLE details The B-channel is not available. FAULT CODE 4 INCORRECT DEVICE TYPE SPECIFIED details This is the incorrect block type for the test object. Monitoring is not allowed on devices that are only software. FAULT CODE 7 B-CHANNEL MONITORING NOT PERMITTED The specified device cannot handle parameter BCH. FAULT CODE 8 SPEECH EQUIPMENT AT TEST POSITION UNAVAILABLE Speech equipment is unavailable at the test position. Check whether the test position number is connected. FAULT CODE 9 NO IDLE TCON INDIVIDUAL No idle Test Connection individual is available. Wait for an idle Test Connection individual. FAULT CODE 10 TEST POSITION NOT DEFINED FROM THIS IO The test position is not defined. Monitoring may only be carried out at defined IO positions FAULT CODE 11 CONGESTION IN THE SUBSCRIBER STAGE Congestion occurred when setting up the speech connection. Wait and try again. FAULT CODE 12 TEST POSITION PHONE BUSY The speech equipment related to the test position is busy. Replace the receiver. FAULT CODE 13 SIGNALLING FAULT A signalling fault occurred during interface with the register functions. FAULT CODE 14 DIALOGUE PARAMETER UNKNOWN The dialogue parameter is unknown. Specify the correct parameter. FAULT CODE 15 DIALOGUE PARAMETER NOT CURRENTLY PERMITTED The dialogue parameter is not permitted during the applicable dialogue state, or in combination with the parameters in the main command. FAULT CODE 16 MULTIPLE POINT BUSY OR NOT DEFINED A multiple point for fixed speech connection is busy or not defined. Check whether the multiple point is defined for the test position using the test position print command. FAULT CODE 21 NO ANSWER AT THE TEST POSITION No answer is received from the operator test position phone, which rings when monitoring is established. FAULT CODE 24 LINE NOT CLEARLY INDICATED There is no clear indication of a subscriber line. Monitoring is not allowed on the group number. FAULT CODE 26 FAULT IN THE GROUP SWITCH, POSSIBLY HARDWARE A fault or congestion occurred in the group switch. Try again. FAULT CODE 29 SUBSCRIBER NUMBER VACANT The specified subscriber number is vacant. FAULT CODE 30 CALL PATH STATE PREVENTS MONITORING Monitoring is not allowed, the subscriber service activated during the call, or the monitored subscriber ended the call. FAULT CODE 31 OPERATOR SPEECH IS NOT ALLOWED Monitoring with operator speech is not allowed FAULT CODE 32 CALL NOT IN SPEECH POSITION The specified device is not linked in a speech position. FAULT CODE 33 NO MONITORING WITH SWITCHED SPEECH CONNECTION Monitoring is not allowed on the switched monitoring connection (the B-number was specified in the command). FAULT CODE 34 CONGESTION WHILE SEIZING MJ OR CCD Congestion occurred while attempting to seize a Multi Junctor (MJ) or a Cross Connect Device CCD). FAULT CODE 35 MONITORING NOT ALLOWED ON SUBSCRIBER LINE Monitoring is not allowed on the specified subscriber line because of the subscriber category. FAULT CODE 40 B-CHANNEL OR DEVICE NOT BUSY MARKED The specified device is not busy-marked. Determine whether or not the indicated device is busy using the device state print command. If parameter BCH has been specified, the device state can be checked using the call path tracing command. FAULT CODE 41 DEVICE NOT CONNECTED TO GROUP SWITCH The specified device is not connected to the group switch. Connect the device to the group switch. FAULT CODE 42 NO MORE (BUSY) CHANNELS PER DEVICE There are no more channels, or no more busy channels on this device. Print the device details using command STDDP on the device for more details. FAULT CODE 44 NO LINKED TASK INDIVIDUAL LOCATED No linked task individual was located. There are no busy B-channels for the specified access FAULT CODE 49 CALL IS PROTECTED - MONITORING NOT ALLOWED Monitoring is not allowed on protected calls. FAULT CODE 50 SUBSCRIBER SERVICE PREVENTS MONITORING Monitoring is not possible because the subscriber service activated in the call. FAULT CODE 51 NO MARKING INDIVIDUAL ALLOWED Monitoring is not possible because marking of busy channels is not allowed. FAULT CODE 52 MONITORING OBJECT NOT DEFINED FOR DEVICE TYPE Monitoring is not possible because no monitoring object exists for the device. FAULT CODE 53 SUBSCRIBER LINE INFORMATION TEMPORARILY INACCESSIBLE Monitoring is not possible because the function cannot access the required information for the subscriber line. FAULT CODE 311 CONGESTION IN EVENT SUBSCRIPTION TABLE The event subscription table is controlled by SAE 608 in block OBMAN1. FAULT CODE 312 CONGESTION IN EVENT IDENTIFIER TABLE The event identifier table is controlled by SAE 607 in block OBMAN1. 4.3   Answer Printouts CONCLUSION OF COMMAND MONTI Command MONTI has been ended. MONITORING ESTABLISHED A monitoring connection has been established. MONITORING TIME-LIMIT EXCEEDED The maximum period for monitoring has been exceeded. NO LINKED TASK INDIVIDUAL FOR B-CHAN 1 - CHECKING B-CHAN 2 No linked task individual was fetched for the first B-channel. The remaining channel is checked automatically. READY FOR CONNECTION The command has been analysed and accepted. Dialogue parameters can be entered. SPEECH MONITORING ESTABLISHED A monitoring connection with speech capability has been established. 4.4   Result Printouts MONITORING REGISTRATION DETAILS 5   Logging Not relevant. 6   Command Category Group Recommended value 48 (H'30). 7   Command Receiving Block MFMONT 8   Glossary CCD Cross Connect Device IO Input/Output MJ Multi Junctor SAE Size Alteration Event 9   References 10   Command Descriptions MONRP Monitoring Registrations, Print STDDP Device State Digital Line Details, Print 11   Printout Descriptions MONITORING REGISTRATION DETAILS 12   Application Information OBMAN1 TRAN

Wyszukiwarka

Podobne podstrony:
creating cod for axe example3
creating cod for axe example5
creating cod for axe example5
creating cod for axe example1
creating cod for axe example2
creating pod for axe example2
creating pod for axe example4
creating cod for axe
creating pod for axe example1
creating pod for axe example3
creating pod for axe
phrases for giving examples practice game
creating customers for life
drugs for youth via internet and the example of mephedrone tox lett 2011 j toxlet 2010 12 014
2001 08 Creating Boot Cds for a Quick Recovery
How to Write a Brief for a Creative Advertising Agency
Managing brands for value creation
Brandy Corvin Howling for the Vampire

więcej podobnych podstron