hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.2 J.istp: Availability and Performance Requirements | NOTE: This clause is called "Network Reliability" in ISTP and is at the backend of the J.istp specification. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.2.1 Distribution model Background | • Fundamental to understanding ISTP, but moved to back end of ITU spec from IPCablecom. • Elements, also known as IPCablecom components, or software components, represent "clusters" of one to many computers sharing a common function (software code) and text-based domain address; note that the model allows multiple call... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.2.2 Distribution Model | MGC(0) SS7/IP Signalling Gateway Node Signalling Points (SCP) SS7 Managed IP networks MGC(1) MGCN (a) MGCN (b) MGCN (z) MGC(q) CMS(j) CMNS (a) CMNS CMNS (z) CMS(k) CMNS (a) CMNS (b) CMNS (z) SS7/IP Signalling Gateway Node SS7/IP Signalling Gateway Node SGIP (0) SGIP (1) SGIP (p) Signalling Points (SCP) MGCN (a) MGCN (b... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.2.3 Availability | • The architecture model must support a network availability equal to that of the PSTN or higher (0,9999+) in a highly scalable fashion to allow for growth and replacement. Operators may implement lower availability targets in order to reduce costs in some markets. • Meeting this availability objective may require serv... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.2.4 Call Availability and Recovery | • Stable calls must be preserved over software replacement, and, where possible, may be preserved in the event of a failure. • Calls in a set up or tear down state may not be preserved. • Billing issues are not addressed in J.istp recovery. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.2.5 Call Performance | • It must meet relevant ITU recommendations on the PSTN. This means a IPCablecom connection has the same performance requirements as a PSTN call. While the issue of performance is complex in a pure SS7 network, the mixture of IP and SS7, and the vendor-dependent breakdown of performance budget makes performance a diffi... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.2.6 Traffic Performance | • The SG should scale up to a "reasonable size", which is one that does not compromise the reliability of the network by putting to many critical calls over a single component. The actual maximum size is determined by the operator based on their own network goals and implementation, so this area is left deliberately va... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3 J.istp: Distribution model requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.1 Bi-directional mapping among components | • It must forward incoming ISUP messages to the ISTP-User element (ex: MGC) controlling the MG associated with the circuit identity in the message. Conversely, it must forward IPCablecom outgoing messages from a ISTP-User to the SG: - The mapping between the SG TCAP-User element (ex: CMS) for TCAP messages is much more... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.2 Numbering: MGC name to IP address | • IPCablecom elements must be identified by their domain name, not their IP network addresses. • Several IP addresses may be associated with a domain name. • If a message cannot be forwarded to one of the network addresses, implementations must retry the transmission using another address. • It must support transparent... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.3 Numbering: circuits and transactions | • It must map SS7 identities (CIC, OPC, and DPC) to the internal identity of the IPCablecom network (MGC, MG, and domain name). • Transaction numbering to the SS7 network must adhere to SS7 transaction numbering recommendations. • Transaction numbering must be dynamically allocated on demand. • Transaction identities m... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.4 Message distribution | • ISUP messages must be routed from the SS7 network to IPCablecom components (MGC) by mapping the circuit identity to an IP address associated with the corresponding element that handles the MG that handles the unique circuit identity. • Outgoing TCAP queries from the CMS or MGC must be routed by mapping a transaction ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.5 Alternate mapping on failure | • It must re-map to redundant or alternate paths upon detection of communication failures. On failures or communication timeouts: - if a MGC/CMS IP communication fails, it must look up alternate IP addresses first for that MGC/CMS element; - if a SG IP communication fails, the MGC/CMS must look up alternate IP addresse... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.6 Relationships | • It must provide mechanisms to manage mapping databases and tables, which map combinational parameters from SS7 messages to target IPCablecom elements and nodes. • It must provide mechanisms to manage other databases and relational parameters not addressed in this specification. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.7 Initialization | • It must support a complete "cold start" initialization of all elements, communications, and dynamic data in all the nodes of the IPCablecom network, and the start up of SS7 stack and links as well. • It must support a CMS, MGC or SG element initialization, which initializes all IP physical and logical communications ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.8 Recovery | • Given the PSTN-like or higher availability requirements, the ISTP must recover from failures quickly and robustly. • ISTP must handle fully distributed n+k node architectures, as well as interfaces to the various SS7 highly reliable network configurations: - at the physical level, the ISTP must manage two or more net... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.9 Dynamic provisioning updates | • The ISTP internal configuration mapping relationships must be dynamically updated without a network restart. It may store information in a local database, or require a central distribution of data on node recovery: this is an implementation option. • Changing a mapping relationships must be done in a graceful and con... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.10 Administration | • ISTP defines some semi-permanent objects and relationship (e.g. timers) that must be administered by the service provider's operations staff. The mechanisms and processes used to administer this data and behaviour are currently beyond the scope of the present document. • The operational support system for the ISTP mu... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.11 ISTP Security | • ISTP Message authentication must use current state of the art Intranet technology to ensure safe and secure transport of IP messaging. • Further security required at ISTP and higher level is currently under study. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.12 Maintenance | • ISTP must manage the IP communications owned by the particular MGC, SG, or CMS, so it can proactively skip failed IP addresses when searching for a target IP without waiting for a timeout. It must support the following procedures: - enable IP, which places the IP connect in service and allows traffic; - disable IP, w... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.13 Measurement | Operational measurements will be collected. The details on these issues are currently beyond the scope of this protocol Recommendation. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.14 Alarms | • At a minimum the ISTP should generate alarms whenever an IP connection fails and whenever an ISTP node restarts. • Other alarms may be generated, including SS7 related alarms. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.15 Congestion | • Congestion on the SS7 network must be handled as per SS7 Recommendations the interfacing PSTN network. • The CMS and the MGC must handle congestion messages from the SG and meet the SS7 requirements in this area. The ISTP will only pass congestion messages to the CMS and MGC; the SG itself must only take SCCP/MTP lev... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.3.16 SG management notification | • When the status of lower layer objects, such as IP nodes, network clusters, or subsystems, change, SG must report the changes to MGC; the MGC may take autonomous recovery actions in the IPCablecom network and may notify operators of the change event. • The MGC must respond to the status changes according to the SS7 R... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4 J.istp: SS7 related protocol requirements | NOTE: Much, but not all, of this clause can be replaced by M3UA and SUA if they eventually become mature RFCs. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.1 ISTP protocol requirements | • ISTP must provide a message distribution function that distributes ISUP and TCAP messages to/from distributed signalling components on the IP network. • ISTP must provide an encoding schema for the transport of SS7 messages over a reliable IP-based protocol. • ISTP must provide a set of messages and procedures for dy... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.2 ISTP connection requirements | • ISTP must establish a reliable communication path. • ISTP must guarantee the prompt and sequenced delivery of the messages. • ISTP must provide information about the origination of incoming messages. • ISTP must retransmit messages in case of errors or timeouts. • ISTP must promptly detect failures in the communicati... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.3 ISTP SS7 encoding requirements | • ISTP must support "raw" ISUP and TCAP messages; it may support messages normalized to ITU or ANSI (note: not supported by IETF Internet-Drafts M3UA v.6 and SUA v.7 (see bibliography)). |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.4 ISTP load-sharing and sequencing | • The SG must assign the SLS value based on the CIC or the Transaction ID for outgoing messages in order to ensure optimal SS7 performance. The MTP Level 3 uses this value to distribute the traffic evenly between available signalling link, and the SG must supply an even distribution of the SLS values in order to achiev... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.5 Circuit registration and activation | • The SG must accept requests to register ISUP circuits. • Once an MGC is successfully registered, it must activate the entries in order for them to take effect and bring them into traffic: - It must allow a "a forced exclusive circuit activation" to override existing activation abruptly. - It must support a "new work ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.6 Transaction subsystem registration | • In order to exchange TCAP messages with nodes in the SS7 network, the TCAP-User components must properly register with the SG as a TCAP subsystem to properly distribute messages received from the SS7 network and provide some validation of the message to the SS7 network to minimize CMS/CA conflicts. • Once an applicat... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.7 Message failure detection and handling | The following failures must be detected and recovered: • The inability of the SG to transfer a message received from the MGC or a CMS onto the SS7 network. • The inability of the SG to transfer a message received from the SS7 network to an MGC or a CMS. • The loss of connectivity of the SG to the SS7 network. • The los... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.8 Heartbeat | • ISTP must validate its own and the application level operation with a query response type "heartbeat" message. • All ISTP nodes must send heartbeat requests on a periodic basis, and must respond to incoming heartbeat requests as soon as they are received. • The detailed steps taken upon delayed or missing heartbeat r... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.9 Signalling gateway accessibility procedures | • The SG can lose access to one or more SS7 signalling points due to local SS7 link failures, remote routing failures, or maintenance activities, and it can recover or gain access as well: - It must support notification of all registered IPCablecom components when a signalling point becomes inaccessible or accessible. ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.10 SG congestion handling | • If the SG detects the congestion of a signalling point by receiving a SS7 network message, it must notify all registered IPCablecom nodes with the congestion level that was received; the SG should provide a mechanism for detection of the end of congestion. • If the SG autonomously detects congestion of the local SS7 ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.11 IPCablecom component management procedures | IPCablecom components (ex: MGC, CMS) must support SS7 recommendations and standards by taking appropriate actions and sending required MTP3 messages to handle: • signalling point inaccessible/accessible. • SS7 network inaccessible/accessible. • SG inaccessible/accessible. • SS7 Network congestion/decongestion. • IP Net... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.4.12 IP usage | • Either SCTP or TCP must be used as an underlying transport mechanism. • The underlying transport mechanism must be configured to avoid blocking, mis-sequencing, IP network congestion and sending delay. • The underlying physically network must support redundancy sufficient to meet network reliability goals, which are ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.5 J.istp: Future work | • ISTP is currently focused on ANSI; it is not planned to upgrade the SS7 protocols requirements clause 5 and call flows to ITU. • Instead, clause 5 and the call flows would be replaced by M3UA and SUA based text, using a fixed draft version of the IETF specification, and the other clauses upgraded to handle M3UA and S... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7 Requirements obtained from J.tgcp | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1 Overview | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1.1 Scope | This clause describes the requirements obtained from reverse engineering the ITU-T J.tgcp document (J.171 [3]). The source document used has been written by the Study Group 9 of the ITU-T. The title of this file is "Revised Draft New Recommendation J.tgcp - IPCablecom Trunking Gateway Control Protocol (TGCP)", as of De... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1.2 What is J.tgcp? | J.tgcp (or J.171 [3]) is a globalized ITU-T version of the Trunking Gateway Control Protocol (TGCP) released in 1999 by Cablelabs. TGCP has been adapted by the ITU in draft J.171. It includes the following characteristics: • It defines an API and a text based protocol in the IPCablecom Framework Architecture. • TGCP su... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1.2.1 Note on MG, MGC, TGCP and MGCI | • They are not quite the same thing: - The media gateway (MG) is a logical component (a set of software and hardware) that is the single point of interface for bearer channel trunks to the PSTN; the MGC is a logical component (a set of software running on a computer) that manages trunk calls. - TGCP is a protocol imple... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1.2.2 TGCP in the protocol stack | The TGCP protocol is highlighted in figure 6. MGCI (TGCP API) TGCP stack UDP IP MGC TGCP MGCI (TGCP API) TGCP stack UDP IP MG (trunking gateway) Figure 6: TGCP in the protocol stack |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1.2.3 J.tgcp Trunking Gateway Document | The J.tgcp document contains: • Presentation of example APIs with the name of the command, the parameters it can take and return, and the semantics of these. • TGCP encoding of the commands and parameter based on text formats. • Annexes for endpoint event packages. • Appendices for: - Connection mode. - Example Command... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1.2.4 First level decomposition of a Managed IP Network | See figure 1 for the first level decomposition. ETSI ETSI TR 102 019 V1.1.1 (2002-02) 45 |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.1.2.5 Areas beyond the scope of J.tgcp | The following areas are out of the scope of the TGCP: • Address layer management (SNMP), security, and measurements covered in other IPCablecom Recommendations, but the MG must adhere to those requirements within the J.arch framework. • Implementation and vendor dependant issues, such as performance, functional distrib... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2 J.tgcp: Technical requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.1 J.tgcp: Framework and Architecture Requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.1.1 Support of J.arch framework service goals | It must support J.arch/J.nsc service goals including: • voice or other media content conversion; • call control signalling; • quality of service control; • call control signalling interoperability with the existing public network; • media interfaces to the existing public network; • data transactions to public database... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.1.2 High level control requirements | • It must provide: - Connection control. - Endpoint control. - Auditing. - Status reporting. • It must provide a common naming convention for using these functions. ETSI ETSI TR 102 019 V1.1.1 (2002-02) 46 • It must support text based control of devices, with ASCII endpoint and connection naming. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.1.3 High level IP side management requirements | It must support IP management procedures for: • Notification request - instruct the MG to look for a set of events. • Notify - notify the MGC when an looked for event occurs. • Create connection - instruct the MG to set up an IP connection. • Modify connection - change the nature of an existing connection. • Delete con... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.1.4 TGCP high level trunk side requirements | • It must provide control of clear channel SS7 trunk (circuits); there is no signalling information passed for these trunks. • It must support requirements for operator assisted calls using legacy MF trunks: - Information note: "the specification in this annex is used in North America", means that MF Operator Services ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.1.5 Other Trunking Gateway Requirements | Trunking Gateway must provide: • TGCP signalling to the MGC. • Support for OA&M. • Support for IPCablecom QoS. • Support for IPCablecom Security. • Static binding to a MGC component type; the MGC component may contain many MGC nodes, each with one or more IP addresses. • Dynamic binding using DNS to map the name of the... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.1.6 Distribution model | • A MG is physically connected to a trunk and thus is tied to the hardware. • Its association with a MGC is flexible; one MG over time can be controlled by different MGCs; this binding can be either provisioned, controlled by a DSN server, or autonomously changed by the MG in the event of a failure of a MGC. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2 J.tgcp: MGCI API requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.1 Model and naming convention | • It must adhere to the MGCP Connection Model: - MGCP assumes connection model where basic constructs are endpoints and connections participating (grouped) in a call. - Trunking gateways have one or more endpoints, e.g. one for each trunk. - Connections will be grouped in calls; one or more connections can belong to on... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.2 Endpoint name | • Endpoint names/identifiers must have two components: - Domain name of the gateway managing the endpoint. - A local endpoint name within that domain. • Domain name may be an IPv4 IP address in dotted decimal format represented as a text string, but this is discouraged. • Trunking gateways will have one or more endpoin... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.3 Trunk name | • Trunking gateways must support the following basic endpoint types: - DS-0 ISUP trunk (clear channel with out of band SS7 signalling). - DS-0 MF trunk (for MF Operator Services). • It must adhere to a conventions supporting hierarchical name support with/separation (for the DS-3, 1, 0), decimal channel numbers, wildca... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.4 Call and Connection names | • Calls should be identified uniquely by the MGC, with hexadecimal a number. • Call identifiers must be unique within the collection of MGCs that control the same gateways. • Multiple connections pertaining to the same call, must have the same call identifier, that can be used by accounting or management schemes. • The... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.5 MGC naming | • MGC must be named similar to endpoints name (domain name + local portion), and must be identified by its (logical) name not (physical) IP address for normal call handling. • One MGC must be able to have multiple IP network addresses; thus network addresses must not be used for identification. • For redundancy, one or... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.6 MGC name binding | • The "notified entity" of an endpoint is the MGC controlling that endpoint and represents a second level of name binding: - upon start-up, the notified entity must be set to a provisioned value; - MGC commands sent to the MG must contain the notified entity name for the endpoint invoked in the command; - the MG must s... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.7 Digit Maps | • None of the trunk types supported by the current version of the TGCP Recommendation have a need for digit maps, and digit maps therefore must not be part of the current TGCP Recommendation. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.8 Packages | • The concept of events and signals is central to TGCP. Events and signals must be grouped in packages sharing a common namespace (a set of unique names). • One or more packages may exist for a given endpoint-type; each endpoint-type must have a default package with which it is associated. • Each endpoint-type must hav... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.9 Experimental Packages | • Implementers may define experimental packages. • The package name of experimental packages must begin with the two characters "x-" or "X-". • IPCablecom must not register package names that start with these two characters. • A MG that receives a command referring to an unsupported package must return an error. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.10 Wildcard support | • Package names and event codes support one wildcard notation each. • The wildcard character "*" (asterisk) must be used to refer to all packages supported by the endpoint in question, and the event code "all" to all events in the package in question. • Consequently, the package name "*" must not be assigned to a packa... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.11 Events and Signals on connections | • Events and signals are by default detected and generated on endpoints, however some events and signals may be detected and generated on connections in addition to or instead of on an endpoint. • In order for an event or signal to be able to be detected or generated on a connection, the definition of the event/signal ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.12 Session Description Protocol | • The MGC must provide MGs with description of parameters (ex: IP addresses, UDP port, RTP profile) using SDP. • SDP descriptions must follow conventions as in Session Description protocol (SDP) in IETF RFC 2327 [11], however, Trunking gateways make certain simplifying assumptions: - SDP usage depends on type of sessio... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.2.13 Gateway control functions | • An API function must be defined for every MGCP command. • The MGCI function must take and return the same parameters as the corresponding MGCP command. • Functions may be implemented, but functions that are implemented, must conform to the semantics specified. • MGCI APIs must support connections handling and endpoin... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3 J.tgcp: Control Function Requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3.1 Commands | It must support commands to: • Allow the MGC to notify an MG of a service request (NotificationRequest). • Allow MGC to notify the MGC that it is ready for service (Notify). • Allow the MGC to request a connection (CreateConnection). • Allow the MGC to modify a connection (ModifyConnection). • Allow the MGC to delete a... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3.2 Calls | Connections are grouped into "calls". • Several connections, that may or may not belong to the same call, can terminate in the same endpoint. • Multiple calls may be active on the same endpoint. ETSI ETSI TR 102 019 V1.1.1 (2002-02) 51 |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3.3 Connection mode parameter | • Each connection must be qualified by a mode parameter: - Send only. - Receive only. - Send/Receive. - Inactive. - Loop back. - Continuity test. - Network loop back. - Network continuity test. • The mode parameter must define if the connection can send or receive packets; however, RTCP must be unaffected by the mode p... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3.4 Audio connection modes | • Audio signals received from the endpoint may be sent on any connection for that endpoint whose mode is either "send only", or "send/receive. • Handling of the audio signals received on these connections must also be determined by the mode parameters: - Audio signals received in data packets through connections in "in... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3.5 Loop-back and continuity testing | • It must support "loop-back" and "continuity test" modes to be used during maintenance and continuity test operations. • New and existing connections for the endpoint must not be affected by connections placed in "network loopback" or "network continuity test" mode. • Local resource constraints may limit the number of... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3.6 Continuity test (COT) | • It must support two variations of continuity test (COT): - One specified for general use: the loopback test. If the originating switch sees the same tone returned (the return tone), the COT has passed. If not, the COT has failed. - One used in several national networks, where the go and return tones are different. Wh... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.3.7 Audio requirements on testing | • When a connection for an endpoint is in "loop-back" or "continuity test" mode: - Audio signals received on any connection for the endpoint must not be sent to the endpoint. - Audio signals received on the endpoint must not be sent to any connection for the endpoint. • If the mode is set to "network loop-back", the au... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4 Requirements from notification request message and parameters | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.1 Notification request command | • This message must be used to notify a MG to be ready for service. • Command must be applied to a unique endpoint; wildcard commands must not be used. • Endpoint must support all signals; connections may support some signals, such as Continuity test and set-up MF OSS call: - On/off signals must be supported, and last ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.2 Media stream notification requirements | • If a signal applied to an endpoint results in the generation of a media stream (audio, video, etc.), the media stream must not be forwarded on any connection associated with that endpoint, regardless of the mode of the connection. For example, if a tone is applied to an endpoint involved in an active communication, o... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.3 Dynamic configuration of events | • It must support a dynamically configurable set of events on each endpoints and connection. • It must support a list of requested events that the gateway must detect on the endpoint. Unless otherwise specified, events are detected on the endpoint, however, some events can be detected on a connection. • For each event,... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.4 Default vs. dynamically set events | • It must support persistent and non-persistent events. • Persistent events are events that must always detected on an endpoint, even if a persistent event is not included in the list of requested events occurs, the event must be handled as if it were a requested event. • Persistent events must still be detected and no... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.5 Event requests | • It must return an error code to the MGCP if it receives a request with an invalid action or illegal combination of actions. • When multiple actions are specified (e.g. "Keep signal(s) active" and "Notify") the individual actions must be assumed to occur simultaneously. • The generation of all "Time Out" signals must ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.6 Event scripting | • If signal(s) are desired to start when a looked-for event occurs, an embedded notification request action may allow the MGC to set up a "mini-script" to be processed by the gateway immediately following the detection of the associated event. • If connection modes are desired to be changed when a looked-for event occu... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.7 Event request vs. signal request | • The specific definition of actions that are requested via signal Request is outside the scope of the core recommendation. • The requested events and signal requests generally refer to the same events. In one case, the gateway is asked to detect the occurrence of the event and, in the other case, it is asked to genera... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.4.8 Quarantine handling | • It must allow the MGC to specify whether quarantined events should be processed or discarded. • If the parameter is absent, the quarantined events must be processed. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.5 Requirements from Notify message and parameters | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.5.1 Notify requirements | • The endpoint identifier must be a fully qualified endpoint name, including the domain name of the gateway, and the local part of the name must not use the wildcard convention. • The notification must be sent to the current "notified entity" for the endpoint; the return message may identify the entity to which the not... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.6 Requirements from create connection message and parameters | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.6.1 Connection definition | • A connection is defined by its attributes and the endpoints it associates with. The MGC must provide all the data necessary to build one of the two endpoints "view" of a connection. • Call identities. • They must at a minimum be unique within the collection of MGCs that control the same gateways. • Connections that b... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.6.2 Local connection characteristics | • The MGC must instruct the endpoint on the send and receive characteristics of the media connection. • The MG must respond with an error if any of the local connection characteristics rules are violated. Some are dynamic, and some set by default, and all defaults must be modified by provisioning. • Encoding Method: A ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.6.3 Local connection options for IP security | • Secret: A seed value that may be used to derive end-to-end encryption keys for the RTP and RTCP security services. The secret should be encoded as clear-text if it only contains values in the ASCII character range 21H to 7EH. Otherwise, the secret must be encoded using base64 encoding. If no value is supplied, or the... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.6.4 Local connection LI requirements | • It must support Lawful Intercept: - Connections must support replication and forwarding to an Electronic Surveillance Delivery Function with Call Content Connection Identifier attached. - Media generated by signals applied to the connection must be replicated regardless of the connection mode. - Replicated packets mu... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.6.5 Remote connections | • The same media parameters must apply to a connection in both the send and receive direction. • If inconsistency is detected by a gateway between the local and the remote connection, the local must take precedence. • When codecs are changed during a communication, small periods of time may exist where the endpoints us... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.6.6 Local connection modes | • This must be the same as the notify modes. • If the command specifies a mode that the endpoint does not support, an error must be returned. • If a connection has not yet received a remote connection descriptor, an error must be returned if the connection is attempted to be placed in any of the modes "send only", or "... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.7 Requirements from Modify Connection message and parameters | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.7.1 Modify connection | • It must be able to modify the characteristics of a gateway's "view" of a connection dynamically. • It must modify information: - on the other "remote" end of the connection; - on the modes that activate or deactivate the connection; - on the local parameters of the connection. • RTP address information may be changed... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.7.2 Synchronized create and modify connection | • Detect events parameters may be used by the MGC to effectively include a modify request that is executed simultaneously with the creation of the connection. • The creation of the creation and the modification request must be synchronized, which means that they are both either accepted or refused. ETSI ETSI TR 102 019... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.8.1 Delete message usage | • It must support deletion (termination) of a connection. • In the general case where a connection has two ends, this command must be sent to both gateways involved in the connection. • After the connection has been deleted: - media streams previously supported by the connection must no longer be available; - any media... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 7.2.8.2 Return performance data | • It must return status data after a connection is terminated, including: - Number of packets sent. - Number of octets sent. - Number of packets received. - Number of octets received. - Number of packets lost. - Interarrival jitter. - Average transmission delay. - It may include other data. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.