SIST ETS 300 365 E1:2005
(Main)Private Telecommunication Network (PTN); Specification, functional models and information flows; Call completion supplementary services
Private Telecommunication Network (PTN); Specification, functional models and information flows; Call completion supplementary services
Contains stage 1 and stage 2 description of the (CCBS) sup service and the(CCNR) supplementary service. See ECMA DTR/ECMA-0002 (ECMA-TR/SVC) for a description of these supplementary services. See ENV 41 005 for definition of stages 1 and 2.
Zasebno telekomunikacijsko omrežje (PTN) – Specifikacija, funkcijski model in informacijski pretoki - Dopolnilna storitev: dokončanje klica
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Private Telecommunication Network (PTN); Specification, functional models and information flows; Call completion supplementary services33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:ETS 300 365 Edition 1SIST ETS 300 365 E1:2005en01-maj-2005SIST ETS 300 365 E1:2005SLOVENSKI
STANDARD
SIST ETS 300 365 E1:2005
EUROPEANETS 300 365TELECOMMUNICATIONJuly 1994STANDARDSource: ETSI TC-ECMAReference: DE/ECMA-00007ICS:33.080Key words:PTN, ECMA-185, CCSDPrivate Telecommunication Network (PTN);Specification, functional model and information flowsCall completion supplementary servicesETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1994. All rights reserved.SIST ETS 300 365 E1:2005New presentation - see History box
Page 2ETS 300 365:1994Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to "ETSI Editingand Committee Support Dept." at the address shown on the title page.SIST ETS 300 365 E1:2005
Page 3ETS 300 365:1994Table of contentsForeword71Scope92Conformance93References94Definitions104.1External definitions104.2Additional Network Feature114.3Busy114.4Call, Basic call114.5Call Completion114.6Originating Number114.7Path reservation114.8Service retention114.9SS-CC Recall114.10User A114.11User B115List of Acronyms126SS-CCBS stage 1 specification136.1Description136.1.1General Description136.1.2Qualifications on Applicability to Telecommunication Services136.2Procedures136.2.1Provision/Withdrawal136.2.2Normal Procedures146.2.2.1Activation, Deactivation, Registration and Interrogation146.2.2.2Invocation and Operation146.2.2.3Cancellation156.2.3Exceptional Procedures156.2.3.1Activation, Deactivation, Registration and Interrogation156.2.3.2Invocation and Operation156.2.3.2.1Rejection of SS-CCBS Service request156.2.3.2.2User A is busy on SS-CC recall166.2.3.2.3Network congestion166.2.3.2.4User B becomes busy after successful SS-CC recall166.2.3.2.5User B becomes busy during path reservation166.2.3.2.6Duplicate SS-CCBS requests176.2.3.2.7Other Failure Situations176.2.3.3Cancellation176.3Interactions with other Supplementary Services176.3.1Calling Line Identification Presentation (SS-CLIP)176.3.2Calling/Connected Line Identification Restriction (SS-CLIR)176.3.3Connected Line Identification Presentation (SS-COLP)176.3.4Calling Name Identification Presentation (SS-CNIP)17SIST ETS 300 365 E1:2005
Page 4ETS 300 365:19946.3.5Calling/Connected Name Identification Restriction (SS-CNIR)176.3.6Connected Name Identification Presentation (SS-CONP)176.3.7Call Forwarding Unconditional (SS-CFU)186.3.8Call Forwarding Busy (SS-CFB)186.3.9Call Forwarding on No Reply (SS-CFNR)186.3.10Call Transfer (SS-CT)186.3.11Completion of Calls on No Reply (SS-CCNR)186.3.12Path Replacement (ANF-PR)186.4Interworking considerations196.5SS-CCBS Overall SDL197SS-CCNR stage 1 description237.1Description237.1.1General description237.1.2Qualifications on applicability to telecommunication services237.2Procedures237.2.1Provision/Withdrawal237.2.2Normal Procedures247.2.2.1Activation/Deactivation/Registration/Interrogation247.2.2.2Invocation and Operation247.2.2.3Cancellation247.2.3Exceptional Procedures257.2.3.1Activation/Deactivation/Registration/Interrogation257.2.3.2Invocation and Operation257.2.3.2.1Rejection of SS-CCNR Service request257.2.3.2.2User A is busy on SS-CC recall257.2.3.2.3Network Congestion257.2.3.2.4User B becomes busy after successful SS-CC recall257.2.3.2.5User B becomes busy during path reservation257.2.3.2.6Duplicate SS-CCNR requests257.2.3.2.7Other Failure Situations267.2.3.3Cancellation267.3Interaction with other Supplementary Services267.3.1Calling Line Identification Presentation (SS-CLIP)267.3.2Calling/Connected Line Identification Restriction (SS-CLIR)267.3.3Connected Line Identification Presentation (SS-COLP)267.3.4Calling Name Identification Presentation (SS-CNIP)267.3.5Calling/Connected Name Identification Restriction (SS-CNIR)267.3.6Connected Name Identification Presentation (SS-CONP)267.3.7Call Forwarding Unconditional (SS-CFU)267.3.8Call Forwarding Busy (SS-CFB)277.3.9Call Forwarding on No Reply (SS-CFNR)277.3.10Call Transfer (SS-CT)277.3.11Completion of Calls to Busy Subscribers (SS-CCBS)277.3.12Path Replacement (ANF-PR)277.4Interworking considerations277.5SS-CCNR Overall SDL278SS-CC stage 2 specification29SIST ETS 300 365 E1:2005
Page 5ETS 300 365:19948.1Functional model298.1.1Functional Model Description298.1.2Description of the functional entities298.1.2.1Originating SS-CC Agent FE, FE1298.1.2.2Originating SS-CC Controlling FE, FE2298.1.2.3Terminating SS-CC Controlling FE, FE3298.1.2.4Terminating SS-CC Agent FE, FE4298.1.3Relationship to basic call functional model308.2Information Flows308.2.1Definition of information flows308.2.1.1ra_CC_cancellation_access308.2.1.2ra_CC_cancelled318.2.1.3ra_CC_failed318.2.1.4ra_CC_list328.2.1.5ra_CC_recall_accept328.2.1.6ra_CC_rem_user_free338.2.1.7ra_CC_request338.2.1.8ra_CC_status_req348.2.1.9ra_CC_stop_recall348.2.1.10ra_CC_user_B_free358.2.1.11rb_CC_call358.2.1.12rb_CC_call_reject358.2.1.13rb_CC_cancellation358.2.1.14rb_CC_free_notification368.2.1.15rb_CC_monitor368.2.1.16rb_CC_path_reserve378.2.1.17rb_CC_resume_completion378.2.1.18rb_CC_suspend_completion378.2.1.19rc_CC_status_req388.2.2Relationship of Information Flows to Basic Call Information Flows388.2.3Information flow sequences408.2.3.1Successful invocation of SS-CC408.2.3.1.1Successful Invocation of SS-CCBS408.2.3.1.2Successful Invocation of SS-CCNR408.2.3.2Status request procedure, User A418.2.3.3Status request procedure, User B428.2.3.4Cancellation of previously invoked SS-CC request by User A428.2.3.5Remote cancellation of previously invoked SS-CC request for servicereasons438.2.3.6Local cancellation of previously invoked SS-CC request for service reasons438.2.3.7Listing of SS-CC requests448.2.3.8Successful completion of SS-CC without path reservation448.2.3.9Successful completion of SS-CC with path reservation458.2.3.10Local rejection of SS-CC by PTN468.2.3.11Remote rejection of SS-CC by PTN468.2.3.12User A busy when User B becomes not busy, without path reservation478.2.3.13User A busy when User B becomes not busy, with path reservation488.2.3.14No response by User A to SS-CC Recall, without path reservation49SIST ETS 300 365 E1:2005
Page 6ETS 300 365:19948.2.3.15No response by User A to SS-CC Recall, with path reservation508.2.3.16User B busy when SS-CC Recall accepted, without path reservation518.2.3.17User B busy on SS-CC Recall, with path reservation518.2.3.18No path to User B when User A accepts SS-CC Recall, without pathreservation528.2.3.19Failure of path reservation due to network congestion538.2.3.20Failure of path reservation due to busy User B538.3Functional entity actions548.3.1Functional entity actions of FE1548.3.2Functional entity actions of FE2548.3.3Functional entity actions of FE3568.3.4Functional entity actions of FE4578.4Functional entity behaviour578.4.1Behaviour of FE1578.4.2Behaviour of FE2628.4.3Behaviour of FE3698.4.4Behaviour of FE4738.5Allocation of Functional entities to Physical Locations748.6Interworking considerations74Annex A (informative):Relationship to corresponding public ISDN standards75Annex B (informative):Bibliography76History77SIST ETS 300 365 E1:2005
Page 7ETS 300 365:1994ForewordThis European Telecommunication Standard (ETS) has been produced by the European Computer ManufacturersAssociation (ECMA) on behalf of its members and those of the European Telecommunications Standards Institute(ETSI).This ETS is one of a series of standards defining services and signalling protocols applicable to PrivateTelecommunication Networks (PTNs) incorporating one or more interconnected nodes. The series uses the IntegratedServices Digital Network (ISDN) concepts as developed by CCITT and is also within the framework of standards foropen systems interconnection as defined by ISO.This ETS specifies the Call Completion to Busy Subscriber and Call Completion on No Reply Supplementary Services.The ETS is based upon the practical experience of ECMA member companies and the results of their active andcontinuous participation in the work of ISO, CCITT, ETSI and other international and national standardisation bodies.It represents a pragmatic and widely based consensus.The services specified are compatible with the equivalent services specified by ETSI for public ISDNs. The referencesfor the ETSI specifications of the Completion of Calls to Busy Subscriber Supplementary Service are contained in theBibliography (Annex B) of this ETS. ETSI currently does not define the Call Completion on No Reply SupplementaryService (SS-CCNR).This ETS was produced by ECMA using the ECMA guidelines for the production of standards and using the ECMAstylesheet. In order to avoid undue delays in the voting process for this ETS it has been agreed that this ETS will not beconverted to the ETSI stylesheet.SIST ETS 300 365 E1:2005
Page 8ETS 300 365:1994Blank pageSIST ETS 300 365 E1:2005
Page 9ETS 300 365:19941ScopeThis European Telecommunication Standard (ETS) specifies Supplementary Services Call Completion(SS-CC), which are applicable to various basic services supported by Private Telecommunication Networks(PTN). Basic services are specified in ETS 300 171.SS-CC consists of two Supplementary services: the Completion of Calls to Busy Subscribers SupplementaryService (SS-CCBS) and the Completion of Calls on No Reply Supplementary Service (SS-CCNR). SS-CCBSenables a calling User A, encountering a busy destination User B, to have the call completed when User Bbecomes not busy, without having to make a new call attempt. SS-CCNR enables a calling User A,encountering a destination User B that, though alerted, does not answer, to have the call completed when UserB becomes not busy again after a period of activity, without having to make a new call attempt.Service specifications are produced in three stages, according to the method described in ENV 41005. ThisETS specifies the stage 1 and stage 2 specifications of SS-CC. The stage 1 specifications (Clauses 6 and 7)specify the supplementary services as seen by the users of PTNs. The stage 2 specification (Clause 8) specifiesthe functional entities involved in the supplementary services and the information flows between them.2ConformanceIn order to conform to this ETS, a Stage 3 Standard shall specify signalling protocols and equipment behaviourthat are capable of being used in a PTN which supports the supplementary services specified in this ETS. Thismeans that, to claim conformance, a Stage 3 Standard is required to be adequate for the support of thoseaspects of Clauses 6 and 7 (stage 1) and Clause 8 (stage 2) which are relevant to the interface or equipment towhich the Stage 3 Standard applies.The stage 1 and stage 2 clauses which a stage 3 standard for the Call Completion of Calls to Busy Subscribersupplementary service is required to support are Clauses 6 and 8 respectively.The stage 1 and stage 2 clauses which a stage 3 standard for the Call Completion of Calls on No Replysupplementary service is required to support are Clauses 7 and 8 respectively.3ReferencesETS 300 171:Private Telecommunication Network (PTN); Specification, functionalmodels and information flows; Control aspects of circuit mode basicservices (1992)CCITT Recommendation I.112:Vocabulary of terms for ISDNs (1988)CCITT Recommendation I.210:Principles of telecommunications services supported by an ISDN and themeans to describe them (1988)CCITT Recommendation I.221:Common specific characteristics of services (1988)CCITT Recommendation Z.100:Specification and description language (SDL) (1988)ENV 41005:Method for the specification of basic and supplementary services ofprivate telecommunication networks (1989)ENV 41007-1:Definition of terms in private telecommunication networks (1989)SIST ETS 300 365 E1:2005
Page 10ETS 300 365:19944DefinitionsFor the purposes of this ETS the following definitions shall apply.4.1External definitionsThis ETS uses the following terms defined in other documents:Basic Service(CCITT Recommendation I.210)Connection(ENV 41007-1)Network determined user busy(CCITT Recommendation I.221)Private(ENV 41007-1)Private Telecommunication Network Exchange (PTNX)(ENV 41007-1)Public(ENV 41007-1)Public ISDN(ENV 41007-1)Service(CCITT Recommendation I.112)Signalling(CCITT Recommendation I.112)Supplementary Service(CCITT Recommendation I.210)Telecommunication Network(ENV 41007-1)Terminal, Terminal Equipment(ENV 41007-1)User(ETS 300 171)User determined user busy(CCITT Recommendation I.221)This ETS refers to the following basic call functional entity (FEs) defined in ETS 300 171:-Call Control (CC)-Call Control Agent (CCA)This ETS refers to the following basic call inter-FE relationships defined in ETS 300 171:-r1-r2-r3This ETS refers to the following basic call information flows defined in ETS 300 171:-r1_setup request/indication/response/confirmation-r1_report request/indication-r1_disconnect request/indication-r2_setup request/indication/response/confirmation-r2_report request/indication-r2_release request/indication-r3_setup request/indication/response/confirmation-r3_setup_reject request/indication-r3_report request/indication-r3_disconnect request/indicationSIST ETS 300 365 E1:2005
Page 11ETS 300 365:1994This ETS refers to the following basic call information flow elements defined in ETS 300 171:-Connection Type (CT)-Destination Number (DN)-Originating Subaddress (OS)-Destination Subaddress (DS)4.2Additional Network FeatureA capability, over and above that of a basic service, provided by a PTN, but not directly to a User.4.3BusyA property of a User for whom either a Network determined user busy or User determined user busycondition exists.4.4Call, Basic callAn instance of the use of a basic service.4.5Call CompletionThe successful presentation of a previously unsuccessful Call to a destination user (User B) which occurswhen the call has entered an alerting phase or has been answered.4.6Originating NumberElement Originating Number is as defined in Standard ETS 300 171 with the exception that Screeningindicator does not apply.4.7Path reservationThe reservation of resources prior to SS-CC Recall in order that a connection path through the PTN isavailable when User A accepts the SS-CC Recall.Note 1Path Reservation does not guarantee that User B will be not busy when User A accepts the SS-CC Recall.4.8Service retentionThe capability to continue with a SS-CC request after the call resulting from acceptance of a SS-CC recallfails due to User B being busy again.4.9SS-CC RecallAn indication informing User A that User B is no longer busy (in the case of SS-CCBS) or has justcompleted a period of activity (in the case of SS-CCNR). Acceptance of this indication by User A will causethe call to be completed by the PTN.4.10User AThe specific User that originated the call and requested the supplementary service.4.11User BThe User that was initially addressed in the original call set up.SIST ETS 300 365 E1:2005
Page 12ETS 300 365:19945List of AcronymsANFAdditional Network FeatureCCCall Control (functional entity)CCACall Control Agent (functional entity)CCICC IdentifierCRCancellation ReasonDNDestination NumberFCFailure CauseFEFunctional EntityFEAFunctional Entity ActionISDNIntegrated Services Digital NetworkNDUBNetwork Determined User BusyNPRNo Path ReservationPTNPrivate Telecommunication NetworkPTNXPrivate Telecommunication Network ExchangeRCReject CauseRLRequest ListRMRequest MaintainedSDLSpecification and Description LanguageSIStatus IndicatorSRService RetentionSS-CCSupplementary Service Call CompletionNOTE 2This is a generic term, used to describe aspects common to both SS-CCBS and SS-CCNR.SS-CCBSSupplementary Service Call Completion to Busy SubscriberSS-CCNRSupplementary Service Call Completion on No ReplyTETerminal EquipmentUDUBUser Determined User BusySIST ETS 300 365 E1:2005
Page 13ETS 300 365:19946SS-CCBS stage 1 specification6.1Description6.1.1General DescriptionCompletion of Call to Busy Subscriber (SS-CCBS) is a supplementary service which is offered to acalling User A. On encountering a busy called User B, it allows User A to request that the PTN monitorsUser B and notifies User A when User B becomes not busy. On response by User A to that notification,the PTN will attempt to complete the call to User B.6.1.2Qualifications on Applicability to Telecommunication ServicesSS-CCBS is applicable to all circuit-mode basic services defined in ETS 300 171.6.2Procedures6.2.1Provision/WithdrawalSS-CCBS may be provided after pre-arrangement with the service provider (by means of service profilecontrol), or may be available generally to all Users. SS-CCBS may be withdrawn on request of the Useror for administrative reasons.The subscription parameters and values offered by a PTN shall be an implementation matter. A PTN mayoffer more or less parameters and values than those specified below.Possible subscription options are summarised in Table 1.Table 1 - SS-CCBS Subscription parametersSubscription optionValues:Recall mode-SS-CC Recall offered to all compatible terminals(Note 3)-SS-CC Recall offered to the terminal which hasinvoked SS-CCBSNote 3If the user has more than one compatible terminal (e.g. passive bus arrangement), this option will result inSS-CC Recall being offered simultaneously to all those terminals, thereby allowing acceptance by any one ofthose terminals.SIST ETS 300 365 E1:2005
Page 14ETS 300 365:19946.2.2Normal Procedures6.2.2.1Activation, Deactivation, Registration and InterrogationSS-CCBS is permanently activated. No information needs to be registered with the PTN for thissupplementary service, and therefore interrogation is not applicable.6.2.2.2Invocation and OperationWhen a call from User A fails because the destination User, User B, is busy, the PTN shall retain thecall information provided by User A, as described in subclause 9.2.1 of ETS 300 171, for a periodduring which User A shall be able to request SS-CCBS. On receipt of a request for SS-CCBS duringthat period, the PTN shall check whether it is possible to initiate the service, and if so shall send anacknowledgement to User A, start monitoring User B and start the SS-CCBS Service Duration Timer.The acknowledgement means that User A can expect to receive a SS-CC Recall if User B becomes notbusy within the period of the SS-CCBS Service Duration Timer.Note 4The fact that User B is already being monitored, as a result of a call completion request from another user,need not cause rejection of the request from User A. The handling of multiple requests against the same UserB is an implementation matter, typically involving some sort of queue arranged in chronological or priorityorder.Note 5The fact that User A has already invoked call completion against another user need not cause rejection ofany further requests for call completion from User A. The handling of multiple requests by the same User A isan implementation matter.Note 6The period during which SS-CCBS can be invoked and the value of the SS-CCBS Service Duration timer areimplementation specific.After the SS-CCBS request has been acknowledged, User A shall be able to receive and initiate othercalls.A PTN may provide User A with the ability to request a list of outstanding SS-CC requests that User Ahas invoked. If the Recall mode is "SS-CC Recall offered to all compatible terminals", details of allrequests made by that user should be provided. If the Recall mode is "SS-CC Recall offered to theterminal which has invoked SS-CCBS", only details of requests made by the user from that terminalshould be provided. The list will be empty if there are no outstanding SS-CC requests.When the monitoring of User B indicates that User B has become not busy, and if User A is also notbusy, the PTN shall provide SS-CC Recall, and start the SS-CC Recall timer. The value of this timershall not exceed 30 seconds. Optionally, path reservation may be employed before providing SS-CCrecall.If User A accepts the SS-CC Recall, the PTN shall attempt to complete the call between User A andUser B. In the case of SS-CC recall offered to all compatible terminals, the PTN shall instruct otherterminals to stop SS-CC recall. If the call is successfully presented to User B and enters an alertingphase or is answered, SS-CCBS shall be regarded as complete.SIST ETS 300 365 E1:2005
Page 15ETS 300 365:19946.2.2.3CancellationThe PTN shall provide User A with the ability to request cancellation of at least one of the following:-all outstanding SS-CC requests for which a SS-CC Recall is still expected;-the most recent SS-CC request for which a SS-CC Recall is still expected; and,-a specific SS-CC request for which a SS-CC Recall is still expected.If the Recall mode is "SS-CC Recall offered to all compatible terminals", requests made by that usershould be cancellable. If the Recall mode is "SS-CC Recall offered to the terminal which has invokedSS-CCBS", requests made by the user from that terminal should be cancellable.User A shall be informed of successful cancellation.6.2.3Exceptional Procedures6.2.3.1Activation, Deactivation, Registration and InterrogationNot applicable.6.2.3.2Invocation and Operation6.2.3.2.1Rejection of SS-CCBS Service requestIf User A is not permitted to request SS-CCBS, the PTN shall reject the SS-CCBS request with anindication of whether denial is short or long term.Short term denial shall be used for temporary conditions where a later request for SS-CCBS mightbe successful. Examples of conditions that may result in a short term denial are:-limit of requests by User A already reached;-no call information retained;-limit of requests against User B already reached; or,-duplicate request (see subclause 6.2.3.2.6).Long term denial shall be used when later requests will also be rejected. Examples of conditions thatmay result in a long term denial are:-SS-CCBS not provided to User A;-interworking with a network which does not support SS-CCBS; or-SS-CCBS not allowed against User B (Note 7).Note 7This is an implementation option that can apply to certain classes of user.SIST ETS 300 365 E1:2005
Page 16ETS 300 365:19946.2.3.2.2User A is busy on SS-CC recallIf User A is found to be busy when User B becomes not busy, the PTN shall wait for both Users tobecome not busy before providing SS-CC Recall and starting the SS-CC Recall timer. The PTN shallnotify User A that the PTN is attempting to complete a call. If a path has been reserved, the pathshall be released until User A has become not busy. As an option, the PTN may allow a short timefor User A to become not busy before releasing the reserved path.Note 8On receipt of such a notification, User A can either:-ignore the notification, thereby causing the SS-CC Recall to be delayed;-cancel the SS-CCBS request; or,-free resources by disposing of an existing call, thereby allowing the SS-CC Recall to proceed.6.2.3.2.3Network congestionIf path reservation is used by the PTN, network congestion can delay the SS-CC Recall, which shallnot occur until a path has been reserved and both Users are not busy. A PTN may cancel SS-CC andinform User A if unable to reserve a path.If the PTN does not use path reservation, or interworks with a network which does not allow pathreservation, the call completion attempt can fail after User A has accepted the SS-CC Recall becauseof network congestion. In this case, User A shall be informed of the failure and SS-CCBS shall becancelled.6.2.3.2.4User B becomes busy after successful SS-CC recallIf User B is busy when User A accepts the SS-CC Recall, the PTN shall either:-abandon SS-CCBS indicating the reason for the failure to User A and that the SS-CCBS requesthas been cancelled. In such a case the PTN may allow User A, as an implementation option, thepossibility of re-invoking SS-CCBS if call completion to User B is still required; or,Note 9The method used in the PTN to allow User A to re-invoke SS-CCBS is outside the scope of this ETS.-resume monitoring of User B, indicating the reason for the failure to User A and that theSS-CCBS request has been maintained (service retention). In such a case, User A may, as a Useroption, request cancellation of the SS-CCBS request, if call completion to User B is no longerrequired.6.2.3.2.5User B becomes busy during path reservationIf User B is found to be busy when path reservation is performed, the path shall be released and thePTN shall wait for User B to become not busy before re-attempting path reservation.SIST ETS 300 365 E1:2005
Page 17ETS 300 365:19946.2.3.2.6Duplicate SS-CCBS requestsIf User A has already requested SS-CCBS on User B for a particular Basic service, and is awaitingrecall, any subsequent request from User A to invoke SS-CCBS on User B, for the same Basicservice, shall cause the PTN to either:-reject the request as a duplicate request; or,-accept the request as valid.Note 10In the case that the PTN accepts the duplicate SS-CCBS request, User A can receive one or more SS-CCRecalls dependent on the treatment of the duplicate request by the PTN.6.2.3.2.7Other Failure SituationsA particular request for the service shall be automatically cancelled by the PTN, and User A shall benotified if:-User B and/or User A is still busy after the SS-CCBS Service Duration Timer expires;-User A does not accept the SS-CC Recall before the SS-CC Recall timer expires;-User B invokes or activates a service that conflicts with the existing SS-CCBS invocation; or-for any reason, the PTN is unable to continue with the CCBS invocation.6.2.3.3CancellationA cancellation request shall be rejected if there are no SS-CC requests for User A or if the request is tocancel a specific SS-CC request which does not exist.6.3Interactions with other Supplementary ServicesInteractions with other supplementary services and ANFs for which PTN Standards were available at thetime of publication of this ETS are specified below.6.3.1Calling Line Identification Presentation (SS-CLIP)No interaction.6.3.2Calling/Connected Line Identification Restriction (SS-CLIR)If User A requests override of the SS-CLIR default value for a call, and the call encounters a busy User B,the request to override the default value shall be retained by the network and shall apply to a call resultingfrom the use of SS-CCBS.6.3.3Connected Line Identification Presentation (SS-COLP)No interaction.6.3.4Calling Name Identification Presentation (SS-CNIP)No interaction.6.3.5Calling/Connected Name Identification Restriction (SS-CNIR)If User A requests override of the SS-CNIR default value for a call, and the call encounters a busy UserB, the request to override the default value shall be retained by the network and shall apply to a callresulting from the use of SS-CCBS.6.3.6Connected Name Identification Presentation (SS-CONP)No interaction.SIST ETS 300 365 E1:2005
Page 18ETS 300 365:19946.3.7Call Forwarding Unconditional (SS-CFU)If the call to User B is diverted to User C by SS-CFU and User C is busy, then a SS-CCBS request fromUser A shall be applied to the diverted-to User C.If User B activates SS-CFU after User A has requested SS-CCBS and whilst the SS-CC Recall has not yetbeen accepted by User A, the SS-CCBS request shall either continue to be applied to User B or becancelled.If User A invokes SS-CCBS whilst SS-CFU is activated, or User A invokes SS-CCBS and subsequentlyactivates SS-CFU, SS-CC Recall shall still be given to User A.6.3.8Call Forwarding Busy (SS-CFB)If the call from User A to User B is diverted to User C by SS-CFB and User C is busy, then a SS-CCBSrequest made by User A shall be applied either to the diverted-to User C or to the originally called UserB.If User B activates SS-CFB after User A has requested SS-CCBS and whilst the SS-CC Recall has not yetbeen accepted by User A, the SS-CCBS request shall continue to be applied to User B.If User A invokes SS-CCBS whilst SS-CFB is activated, or User A invokes SS-CCBS and subsequentlyactivates SS-CFB, this shall not affect the provision of the SS-CC Recall to User A6.3.9Call Forwarding on No Reply (SS-CFNR)If User B activates SS-CFNR after User A has requested SS-CCBS and whilst the SS-CC Recall has notyet been accepted by User A, then the SS-CCBS request shall continue to be applied to User B.Note 11In such a case, the call resulting from successful completion of SS-CCBS can be subject to SS-CFNR if notanswered.If User A invokes SS-CCBS whilst SS-CFNR is activated, or User A invokes SS-CCBS and subsequentlyactivates SS-CFNR, this shall not affect the provision of the SS-CC Recall to User A.6.3.10Call Transfer (SS-CT)No interaction.6.3.11Completion of Calls on No Reply (SS-CCNR)If User A has SS-CCNR activated on User B, and User A requests SS-CCBS on User B, this request shallbe treated as a duplicate SS-CCBS request in accordance with subclause 6.2.3.2.6.Note 12When User B is busy (the pre-requisite for invocation of SS-CCBS by User A) before SS-CC Recall has beenstarted relating to a previous SS-CCNR request, the pending SS-CCNR request has effectively become anSS-CCBS request, as it is awaiting a not busy User B in order to recall User A. If an SS-CCBS request is thenreceived from User A, relating to User B,
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.