ANSI T1.610-1998 pdf download Generic Procedures for the Control of ISDN Supplementary Services
4.5.2.4 Network Initiated Service Activation or Deactivation
It may be necessary for the network to either activate a supplementary service for a user, or to deactivate a service that had previously been activated. For example, a network may provide service activation for a user at a specified time of day or a supplementary service that is active may need to be deactivated by the network for such reasons as: .
a.by prior arrangement with the user, deactivation is to occur at a specified time of day;
b.an active service’s timer expires, requiring service deactivation; .
C.an action or operation by a user requires that a service be deactivated;
d.an interaction with another supplementary service causes deactivation; that is, another service takes precedence over an active service causing it to be deactivated.
If the network needs to activate or deactivate a supplementary service and the Keypad protocol applies to the served user’s interface, then the network may send an appropriate message (e.g.,. INFORMATION message) to the user that includes a Display text information element containing an appropriate indication that a supplementary service has been activated or deactivated. Networks supporting both the Keypad and the Feature key management protocols per access, in the network-to-user direction, may choose to send to the user a Feature indication information element in an INFORMATION message that identifies the feature and whether it is being activated or deactivated. Additional indications may be provided to the user via the Display text information element in appropriate messages.
10) The following shall be added after the third paragraph of 6.2.1:
Enhancements to the procedures may be required for users requesting that no B-Channel be reserved or that the reserved B-Channel be released on a per call basis.
11) The following shall be added to 6.2.1.1:
Auxillary states v and vi are not supported.
12) The following shall be added to 6.2.2.1 at the end of the second paragraph (i.e.,immediately after the line “Active (U10), (N10)”):
The Hold function is not applicable to call termination states other than the active state.
13) Subclause 6.3.2.1 and its subclauses shall be replaced with the following text: For supplementary service procedures independent of an active call, the initiating side must first establish a reliable data link connection between the network and the user according to the data link services described in ANSI T1. 602. Once the data link connection is established, the user or the network starts the establishment of the signalling connection by transferring a REGISTER message across the user-network interface. This signalling connection is identified by the call reference associated with the REGISTER message. The requested supplementary service is identified by the operation value within the Facility information element. This signalling connection may be released by the exchange of return result, return error or reject component types contained in the Facility information element within a RELEASE COMPLETE message. Alternatively, the Networked Call Independent, Connection Oriented procedures of Annex E may be used. The choice of signaling mechanisms is network and application dependent.