Vous êtes sur la page 1sur 8

BugFix

Analog/ISDN/GeoCENTREX
Malicious Call Identication (MCI)

Availability
Analog Subscriber GeoCENTREX subscriber X X ISDN X X

Benefits ... for the operator fast identication of malicious or nuisance callers ... for the subscriber improved protection against malicious callers

Description of the Feature


For situations where a subscriber is being harassed by another subscriber, EWSD offers the following features for identifying the source of such calls: Malicious Call Identication (MCI) This feature is used to identify malicious callers and nuisance ringers. Subscriber Online Observation (SOB) This feature makes it possible to monitor a subscriber line. Transit Exchange based Subscriber Observation (TxOB) This feature allows the operator of a transit, gateway or international exchange to identify the subscribers who have dialed a particular subscriber of a different exchange. All three features are based on call data recording. For further processing the data records can be printed out, displayed on-screen or forwarded to the operation and maintenance center (OMC).

Use and effect The following table shows whether the feature can be used by the calling or called subscriber and on which side of the connection the feature takes effect.
Calling subscriber MCI use MCI effect SOB use SOB effect TxOB use TXOB effect
*)

Called subscriber X X --X --X

Operator

--X --X --X

--X X *) --X *) ---

Justified instance

Interactions For interaction with other features, see Feature Interactions. Standards The feature is based on the following standards: ETS 300 130

Mode of operation
Malicious Call Identification Three variants of the feature Malicious Call Identification (MCI) can be activated: MCI on request (MCI1) The feature can be activated during a call by subscriber controlled input. MCI at subscriber answer (MCI2) Malicious Call Identication is activated automatically when the subscriber answers the call. MCI immediate at subscriber ringing (MCI3) Malicious Call Identication is activated automatically for each call. This detects nuisance ringers as well. In all three forms of activation, when MCI is activated an operator can additionally be included in the connection by means of subscriber-controlled input. This is done on the basis of a Three-Party Call or Three-Party Conference. For this feature option the directory number for MCI with operator assistance must be created in the network node. This directory number can only be assigned once in each network node. If several operators are to be available in the same network node, the pilot number of a PBX has to be created.

Data recorded When MCI is activated for a subscriber, data records are generated in the following cases: as soon as MCI is activated for a subscriber, regardless of the available data, or when one of the following conditions is fullled: the directory number of the calling subscriber is available, or the trunk is being held The second of these two conditions is the default setting and can be set via an APS parameter. In the case of external calls the record is generated both in the originating network node and in the destination network node. The following data are recorded for MCI: for an internal connection date and time calling directory number calling party category called directory number for an external connection in the terminating exchange date and time calling directory number calling party category called directory number incoming trunk group incoming line number (and circuit identication code for CCS7 trunks)

MCI1 Activation by subscriber controlled input

MCI2 Automatic activation on answer


EWSD

MCI3 Activation on call delivery

Date, Time Data recorded: Calling directory number Calling party category Called directory number Incoming trunk group number Incoming line number

optional

Operator

in the originating exchange date and time calling directory number calling party category called directory number outgoing trunk group outgoing line number (and circuit identication code for CCS7 trunks) The MCI data that is collected is logged in a buffer area. This enables the operator to display records from this buffer afterwards. Data records can be selected on the basis of the subscriber directory number, the trunk group ID, or a specific date or period of time, for example. All records are forwarded to a file and/or an output device. The MCI messages can also be sent to a remote operation and maintenance center (OMC) via FTAM and X25 protocol. Additional feature options The following feature options are available in connection with the feature MCI: Call Forwarding If a call is forwarded to a subscriber who has activated the MCI feature, the connection is considered in two sections: from the calling subscriber to the forwarding subscriber (A-->B). MCI records for the connection from A to B are supplemented by the number of the subscriber to whom the call was forwarded, i.e. the number of the subscriber who was actually reached (subscriber C). from the forwarding subscriber to the subscriber to whom the call was forwarded (B-->C). MCI records for the connection from B to C are supplemented by the number that was originally dialed and by the number of the subscriber to whom the call was forwarded (i.e. the number of the subscriber with call forwarding). The identication/holding of malicious calls and the logging of the recorded data are carried out separately for the sections A-->B and B-->C. When the calling party goes on hook and the identication data has been recorded at the forwarding point, the forwarding original called party (B-subscriber) is released. The sub-connections are still held, if the lines are trunks and if holding is requested.

A malicious call can only be identied/held across the forwarding point if the feature MCI before ANSWER was activated and if the APS parameter for malicious call identication across the forwarding point is set. For ISDN subscribers, holding across the forwarding point is only possible in the following cases: The following list shows the options that can be applied for MCI in section A-->B:
Call forwarding unconditional (CFU) Call forwarding netw. det. user busy (CFNDUB) Call forwarding no reply (CFNR) no MCI preparation no MCI preparation MCI preparation call identification if MCI immediate MCI preparation *) call identification if MCI on request and no reception of the CF condition or if MCI through the diversion point Call forwarding user det.user busy (CFUDUB) MCI preparation *) MCI if CF unsuccessful or if MCI through the diversion point

*) The MCI preparation is cancelled if the APS parameter 'malicious call identification through the diversion point' is not set.

An MCI ticket for B1 ISDN subscriber and B2 subscriber is generated in the following configuration: A-->B (with MCI immediate) B-->C (with MCI immediate/on request) Two additional APS parameters must be set ('MCI beyond the DIV exchange and MCI data recording in DIV exchange) MCI and Number Portability In the case of ported subscribers on the calling and/or called side, both numbers (routing number/ported number) of the calling and/or called subscriber are collected in the MCI records, as long as they are signaled and available in the exchange.

Subscriber Online Observation The feature Subscriber Online Observation (SOB) can be created for incoming and/or outgoing calls of a subscriber line. Observation of the incoming and/or outgoing line can be restricted to one or more directory numbers by means of a screening list. In this case the system checks whether the calling subscriber (SOB incoming) or the called subscriber (SOB outgoing) has been entered in the screening list before the actual observation is started. The same type of identification and recording is used as for MCI. For a subscriber who is under observation, a data record is generated and an alarm is sent as soon as the connection has been registered. The recorded data is logged in the same buffer as for MCI. Data records are selected on the basis of input parameters such as subscriber number, trunk group ID, specific dates and time periods. Recorded data The data recorded for SOB is only generated in the network node in which observation has been created. The following data is recorded: Incoming connection date and time calling directory number calling party category called directory number number of the incoming trunk group (only for external trafc) number of the incoming line (only for external trafc) Outgoing connection date and time calling directory number calling party category called directory number number of the outgoing trunk group (only for external trafc) number of the outgoing line (only for external trafc) The SOB data that is collected is logged in a buffer area. This enables the operator to display records from this buffer afterwards. Data records can be selected on the basis of the subscriber number, trunk group ID, or a specific date or time period, for example. All records are forwarded to a file and/or an output device. The SOB messages can also be sent to a remote operation and maintenance center (OMC) via FTAM and X25 protocol.

Additional functions The following feature options are available in connection with the feature SOB: SOB with Screening If the subscriber with SOB (originating or terminating) has been assigned a screening list for SOB, then the calling party number (for terminating SOB) or called party number (for originating SOB) is checked against the entries in the screening list. If the numbers match, the call data is recorded. It should be noted that the entries in the screening list must exactly match the directory numbers that are to be screened. If the entry in the SOB screening list only contains two digits, all numbers that begin with these digits are considered a match! SOB and Number Portability In the case of ported subscribers on the calling and/or called side, both numbers (routing number/ported number) of the calling and/or called subscriber are collected in the SOB records, as long as they are signaled and available in the exchange. Transit Exchange based Subscriber Observation The feature Transit Exchange based Subscriber Observation, TxOB can be used on outgoing connections. To activate observation, the operator enters a directory number in the TxOB screening list. To deactivate observation, the operator removes the directory number from the TxOB screening list. For each exchange, only a limited number of subscriber directory numbers can be entered in the TxOB screening list. The specified directory numbers can also be partially qualified. If the number of a subscriber who is under observation is dialed, the calling subscriber can be identified on the basis of the directory number. Calls to a subscriber who is under observation result in a data record in connection with an alarm, as in the case of MCI and SOB. The same type of identification and recording is used as for MCI and SOB.

Recorded data The data recorded for TxOB is only generated in the network node in which the TxOB screening list has been created. The following data is recorded for each observed call: date and time calling directory number calling party category called directory number number of the incoming trunk group number of the incoming line number of the outgoing trunk group number of the outgoing line The TxOB data that is collected is logged in a buffer area. This enables the operator to display records from this buffer afterwards. Data records can be selected on the basis of the subscriber directory number, trunk ID, or a specific date or time period, for example. All records are forwarded to a file and/or an output device. The TxOB messages can also be sent to a remote operation and maintenance center (OMC) via FTAM and X25 protocol. Additional feature options The following feature option is available in connection with the feature TxOB: TxOB and Number Portability In the case of ported subscribers on the calling and/or called side, both numbers (routing number/ported number) of the calling and/or called subscriber are collected in the TxOB records, as long as they are signaled and available in the exchange.

Subscriber controlled input


Subscriber controlled input is not possible for the Subscriber Online Observation (SOB) and Transit Exchange based Subscriber Observation (TxOB) features. The Malicious Call Identification (MCI) feature can be administrated and used by subscriber controlled input.
Subscriber controlled input functions Signaling method Analog Pulse DTMF Keypad X X ----------X X ----ISDN Functional protocol X X ----------X X -----

Activate Deactivate Enter data Delete data Enter data and activate Delete data and deactivate Activate with/without data Feature use Status request Data request Status request with/without data

X X ----------X X -----

X X ----------X X -----

Examples of input procedures The input procedures shown here are for ISDN lines. For analog lines, entry of MSN and BC does not apply. The meaning of the pictograms and abbreviations is explained in the overview in the section on subscriber controlled input, as well as the differences in the procedure for pulse dialing. Activate DT (( ( ( ) SC PIN) MSN) BC) IND optional optional optional

Deactivate DT (( ( ( ) SC PIN) MSN) BC) IND optional optional optional

Feature use with ISDN MCI 1 without operator assist function Keypad protocol A-B n Connection Start MCI 1

Function protocol with function key A-B Connection FK MCI

Interrogate state FK DT (( ( ( ) PIN) MSN) BC) IND FK Feature use for analog subscribers MCI 1 without operator assist function A-B Connection Start MCI 1 MCI 1 with operator assist function A-B Connection Start MCI 1 RDT B - Op n Operator request Connection DT B - Op MCI 2 with operator assist function Start MCI 2 A-B RDT B - Op n Connection 1st ring Operator request Answer Connection A-B MCI 3 with operator assist function 1st ring Start MCI 3 Answer A-B RDT B - Op
6

SC optional optional optional FK FK MCI FK HOLD SC B - Op Operator request Connection MCI 1 with operator assist function Function protocol with function key A-B Connection

DT

MCI 2 with operator assist function Function protocol with function key Start MCI 2 A-B FK SC Connection FK HOLD Operator request Connection

MCI 3 with operator assist function Function protocol with function key Start MCI 3

Connection FK HOLD SC Operator request Connection

FK DT B - Op

Connection n Operator request Connection

Call charge registration


For detailed information on call charge registration, please refer to the section on call charges in the overview. Charges for feature input and feature usage
Action Activate Deactivate Enter data Delete data Assign authorization Remove authorization Assign authorization to modify Remove authorization to modify Status request, data request Use FAIO --------X X --------FAIS X X ------------X --FAU ------------------X

Subscriber access types The feature can be used with the following types of subscriber access:
Type Subscriber Analog Main station Basic access PBX PBX with BA and/or PA PBX line PBX line with Direct Dialing In (DDI) PBX line, connected like a subscriber Coinbox Emergency call station MLHG line Basic attendant console X --X ------X ----------ISDN --X --X ----------------GeoCENTREX Analog X --X ------X ----------ISDN --X --X -----------------

Call charges for connections With MCI the call charges are the same as for a normal call.

MAC attendant console

I SDN basic services The allocation and usage of the feature are service specific. The basic code may be different, depending on the individual project.
Basis service All services Circuit mode: speech Circuit mode: 64 kbit/s unrestricted Circuit mode: 3.1 kHz audio Circuit mode: 7 kHz audio Telephony 3.1 kHz Teletex 64 kbit/s Fax group 4 Videotex Video telephony Fax group 2/3 Telephony 7 kHz Basis code 00 01 02 03 04 32 33 34 35 36 37 38

Administration
The operator can perform all administration functions on the NetManager by means of user-friendly applications or MML commands. Feature authorization The network operator assigns authorization for the MCI feature when requested by the subscriber. Authorization for the features SOB and TxOB is requested by a legitimated authority and created by the operator without the subscribers knowledge.

Call charge registration For more information, please refer to OMN:EXCH-TA. System administration The following feature data can be administrated in the network node: options for subscriber controlled input display and modication of network node options creation of announcements recording by means of trafc measurement For more information, please refer to OMN:EXCH-SY. Subscriber administration For more information, please refer to OMN:EXCH-SU. GeoCENTREX administration For more information, please refer to OMN:EXCH-CTX.

Requirements
Hardware UI-LTG with OCANEQ speech equipment and INDAS for: acknowledging subscriber controlled input Signaling Signaling between the network nodes Signaling system no. 7 (SS7) ISDN user part (ISUP) Telephony user part (TUP) Subscriber signaling Analog Dual-tone multi-frequency (DTMF) Pulse dialing ISDN Digital subscriber signaling system no.1 (DSS1) Subscriber interfaces The following interfaces for subscriber access are required: DLU LTG V5.1 interface V5.2 interface

Copyright (C) Siemens AG 2002 Issued by Information and Communications Group Hofmannstrae 51 D-81359 Mnchen Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract. Order Number: A30828-X1160-B616-1-7629 Visit our Website at: http://www.siemens.com