џWPCL ћџ2BJ|xа АH аа АА X аг.га ХА6p&А6p&Х аеЮ† а Hр аааУ Уб cмˆ4 PŽТ б Fascicle VI.8 Р-Р Rec. Q.730 Ф ФPAGE45У Уб cмˆ4 PŽТ б ЮееЃ† а HH аааб cмˆ4 PŽТ бPAGE46У Уб cмˆ4 PŽТ б Fascicle VI.8 Р-Р Rec. Q.730 Ѓеа HH ааЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџHpи P Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаа X  аСр8OСб cмˆ4 PŽТ бANNEX A Ср8FСб cмˆ4 PŽТ б(to Recommendation Q.730) аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџH јP Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСр89Сб cмˆ4 PŽТ бУ УSignalling procedure for the explicit invocation of Ср8=СuserР-РtoР-Рuser signalling services 1, 2 and 3Ф Ф аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџHpи P Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаб cмˆ4 PŽТ бA.1Тh  ТУУUserР-РtoР-Рuser signalling serviceЦЦ Та ТС€ HСФФA.1.1С СУУGeneral description of userР-РtoР-Рuser serviceЦЦ ФФС СSee РSРS 2.1 and 2.2. а H аA.2Тh  ТУУProcedures for userР-РtoР-Рuser signalling associated with circuit switched callsЦЦ аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџH јP Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаТX  ТТX јТС€  СС€ HСФФA.2.1С јСб cмˆ4 PŽТ бУУUserР-РtoР-Рuser signalling, Service 1ЦЦ аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџHpи P Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаТа ТС€ HСФФб cмˆ4 PŽТ бA.2.1.1СpСУУGeneral characteristicsЦЦ ФФС СService 1 allows users to communicate with userР-РtoР-Рuser signalling by transferring userР-РtoР-Рuser information within ISDN user part messages during the call setР-Рup and clearing phases. The userР-РtoР-Рuser signalling service provided is not a guaranteed service. If for any reason the combination of the basic plus supplementary service information causes the overall maximum length of the message to be exceeded then if the UserР-РtoР-Рuser Signalling Service 1 is included the service should be rejected. Та ТС€ HСA.2.1.2СpСУУUserР-РtoР-Рuser signalling, Service 1 Р-Р Explicit service requestЦЦ а H аФФС СProcedures for call setР-Рup are as described in Recommendation Q.764, РSР 2 with the following changes: а H аС СOn call setР-Рup, the Initial Address Message will contain the userР-РtoР-Рuser indicators parameter with Service 1 indicated as Р"Рrequested essential/not essentialР"Р and Service 2 and 3 indicated as Р"Рno informationР"Р. The service request will be received from call control at the originating exchange and will be passed to the call control at the terminating exchange. а H аС СIf the called user or network can support the transfer of userР-РtoР-Рuser, a Service 1 acceptance will be returned to the originating exchange in an Address Complete or Call Progress Message for the pointР-РtoР-Рpoint case or the Answer or Connect Message in the pointР-РtoР-Рmultipoint case with the indication Р"РService 1 providedР"Р in the userР-РtoР-Рuser indicators parameter. Services 2 and 3 will be indicated as Р"Рno informationР"Р in the userР-РtoР-Рuser indicators parameter. These explicit indications shall be forwarded to the call control at the originating exchange. а H аС СUserР-РtoР-Рuser information may be contained in any of the messages that may be transferred in the call setР-Рup phase. Та ТС€ HСA.2.1.3СpСУУInterworkingЦЦ а H аФФС СIn the case of interworking with a nonР-РISDN network, the Р"РinterworkingР"Р protocol control information will be returned to the originating exchange in the first appropriate message, e.g., and Address Complete Message. Two ISDN networks that interwork may have to retain knowledge of the service request until it is clear whether both can support the service. Та ТС€ HСA.2.1.4СpСУУRejection of explicit service requestsЦЦ а H аФФС СIf the called user or network does not understand the Service 1 request then the Address Complete or Call Progress Message returned to the originating exchange shall not include either a Service 1 acceptance or rejection. This type of response will be taken as an implicit rejection of Service 1. (УУNoteФФ Р-Р The Study Group XVIII service description does not allow this implicit rejection.) С СIf the network or called user cannot support Service 1, and it was requested with a nonР-Рessential indication, a Service 1 rejection indication is returned in the Address Complete or Call Progress Message with the indication Р"РService 1 not providedР"Р in the userР-РtoР-Рuser indicators parameter. а H аС СIf the Service 1 request is indicated as essential and the called user or network cannot support it a Release Message is sent with cause code 50, Р"Рrequested facility not subscribedР"Р, cause code 29, Р"Рfacility rejected by the networkР"Р or cause code 69, Р"Рrequested facility not implementedР"Р and the diagnostic containing the userР-РtoР-Рuser indicators parameter. Та ТС€ HСA.2.1.5СpСУУUserР-РtoР-Рuser signalling in the call clearing phaseЦЦ ФФС СA userР-РtoР-Рuser information parameter may be included in the Release Message. The userР-РtoР-Рuser information parameter received at the distant exchange in the Release Message is passed to the call control for the remote user. In the case of simultaneous clearing of the call the Release Message may not reach the distant local exchange and the userР-РtoР-Рuser information will be lost. аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџH јP Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаТX  ТТX јТС€  СС€ HСA.2.2С јСб cмˆ4 PŽТ бУУUserР-РtoР-Рuser signalling, Service 2ЦЦ аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџHpи P Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаТа ТС€ HСФФб cмˆ4 PŽТ бA.2.2.1СpСУУGeneral characteristicsЦЦ а H аФФС СService 2 allows the users to communicate with userР-РtoР-Рuser signalling by transferring up to two userР-РtoР-Рuser information messages in each direction during the call setup phase. As a network option, userР-РtoР-Рuser information may de delivered to the called party after the call is answered to accommodate situations where the information was sent at approximately the same time as the call was answered. This service allows either an implicit or explicit rejection. а H аС СService 2 is only applicable when a pointР-РtoР-Рpoint configuration exists at the userР-Рnetwork interface at the terminating exchange. Та ТС€ HСAУУ.2.2.2СpСCall setР-РupЦЦ а H аФФС СProcedures for call setР-Рup are as described in Recommendation Q.764, РSР 2 with the following changes: а H аС СOn call setР-Рup the Initial Address Message will contain the userР-РtoР-Рuser indicators parameter with Service 2 indicated as Р"Рrequested essential/not essentialР"Р and Services 1 and 2 indicated as Р"Рno informationР"РУУб cмˆ4 PŽТ б1жя  а HH ааа1)б cмˆ4 PŽТ бФФThe Connection Request parameter will be included if COР-РSCCP method is selected, or the call reference parameter if CLР-РSCCP method is selected. яж)ФФб cмˆ4 PŽТ б. The service request will be received from call control. The service request will be passed to call control at the terminating exchange. а H аС СIf the called user or network can support the transfer of userР-РtoР-Рuser information, a Service 2 acceptance will be returned to the originating exchange in an Address Complete or Call Progress Message with the indication Р"РService 2 providedР"Р in the userР-РtoР-Рuser indicators parameterУУб cмˆ4 PŽТ б2жЏ†а H ааа2)б cмˆ4 PŽТ бФФThe SCCP connection confirm message will be returned if COР-РSCCP method is selected. Џж)ФФб cмˆ4 PŽТ б. Services 1 and 3 will be indicated as Р"Рno informationР"Р in the userР-РtoР-Рuser indicators parameter. These explicit indications shall be forwarded to the call control at the originating exchange. Та ТС€ HСA.2.2.3СpСУУService rejectionЦЦ Та ТС€ HСФФA.2.2.3.1СpСУУPointР-РtoР-Рpoint callsЦЦ а H аФФС СIf the called user or network does not understand the Service 2 request then the Address Complete or Call Progress Message returned to the originating exchange shall not include either a Service 2 acceptance or rejection. This type of response will be taken as an implicit rejection of Service 2. С СIf the network or called user cannot support Service 2, and it was requested with a nonР-Рessential indication, a Service 2 rejection indication is returned in the Address Complete or Call Progress Message with the а H аindication Р"РService 2 not providedР"Р in the userР-РtoР-Рuser indicators parameterУУб cмˆ4 PŽТ б3жЏ†а H ааа3)б cмˆ4 PŽТ бФФThe SCCP connection refused message will be returned if COР-РSCCP method is selected. Џж)ФФб cмˆ4 PŽТ б. (УУNoteФФ Р-Р The Study Group XVIII service description does not allow this implicit rejection.) а H аС СIf the Service 2 request is indicated as essential and the called user or network cannot support it a Release Message is sent with cause code 50, Р"Рrequested facility not subscribedР"Р cause code 29, Р"Рfacility rejected by the networkР"Р or cause code 69, Р"Рrequested facility not implementedР"Р and the diagnostic containing the userР-РtoР-Рuser indicators parameter. Та ТС€ HСA.2.2.3.2СpСУУPointР-РtoР-Рmultipoint callsЦЦ а H аФФС СIf the call is pointР-РtoР-Рmultipoint then Service 2 cannot be provided at the called party because the user is not identified until the user is connected. Consequently, Service 2 must be rejected using the pointР-РtoР-Рpoint procedures. The cause value in this case is code 88, Р"Рincompatible destinationР"Р. Та ТС€ HСA.2.2.4СpСУУInterworkingЦЦ а H аФФС СIn the case of interworking with a nonР-РISDN network, the Р"РinterworkingР"Р protocol control information will be returned to the originating exchange in the appropriate message, e.g., an Address Completed Message. Two ISDN networks that interwork may have to retain knowledge of the service request until it is clear whether both can support the service. Та ТС€ HСA.2.2.5СpСУУTransfer of messages containing userР-РtoР-Рuser informationЦЦ а H аФФС СOnce acceptance of Service 2 has been transmitted across the network, both of the involved users can transfer userР-РtoР-Рuser information between themselves. Within the network the userР-РtoР-Рuser information parameter will be carried in a UserР-РtoР-Рuser Information Message. The network provides for the transfer of these messages from the calling to the called side and vice versa. С СThe UserР-РtoР-Рuser Information Message format can be found in Table 20/Q.763. а H аС СIf the Service 2 is provided, no more than two UserР-РtoР-Рuser Information Messages carrying userР-РtoР-Рuser information parameters may be transmitted in each direction during the call setР-Рup phase. If more than two messages are received during call setР-Рup, the additional messages are discarded. If only Service 2 has been requested, one of the messages may also be received and passed after the answer state has been reached. а H аС СNo transfer of userР-РtoР-Рuser information can occur until the service is acknowledged. аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџH јP Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаТX  ТТX јТС€  СС€ HСA.2.3С јСб cмˆ4 PŽТ бУУUserР-РtoР-Рuser signalling, Service 3ЦЦ аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџHpи P Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаТа ТС€ HСФФб cмˆ4 PŽТ бA.2.3.1СpСУУGeneral characteristicsЦЦ а H аФФС СService 3 allows the users to communicate with userР-РtoР-Рuser signalling by transferring UserР-РtoР-Рuser Information Messages in each direction during the active phase of the call. This service allows either an implicit or explicit rejection. а H аС СService 3 allows the service to be requested either during call setР-Рup or after call setР-Рup. However, Service 3 should not be requested after call setР-Рup if it has been rejected during the call setР-Рup phase. Та ТС€ HСA.2.3.2СpСУУService 3 requested during call setР-РupЦЦ а H аФФС СProcedures for call setР-Рup are as described in Recommendation Q.764, РSР 2 with the following changes: а H аС СOn call setР-Рup the Initial Address Message will contain the userР-РtoР-Рuser indicators parameter with Service 3 indicated as Р"Рrequested essential/not essentialР"Р and Services 1 and 2 indicated as Р"Рno informationР"РУУб cмˆ4 PŽТ б4жюIа H ааа4)б cмˆ4 PŽТ бФФThe Connection Request parameter will be included if COР-РSCCP method is selected, or the call reference parameter if CLР-РSCCP method is selected. юж)ФФб cмˆ4 PŽТ б. The serviceд S%д request will be received from call control at the originating exchange. The service request will be passed to the call control at the terminating exchange. а H аС СIf the called user or network can support the transfer of userР-РtoР-Рuser information, a Service 3 Acceptance will be returned to the originating exchange in an Answer or Connect Message with the indication Р"РService 3 providedР"Р in the userР-РtoР-Рuser indicators parameterУУб cмˆ4 PŽТ б5жЏ†а H ааа5)б cмˆ4 PŽТ бФФThe SCCP connection confirm message will be returned if COР-РSCCP method is selected. Џж)ФФб cмˆ4 PŽТ б. Services 1 and 2 will be indicated as Р"Рno informationР"Р in the userР-РtoР-Рuser indicators parameter. These explicit indications shall be forwarded to the call control at the originating exchange. а Hh аТа ТA.2.3.3СP СУУRejection of Service 3 when requested during call setР-РupЦЦ а H аФФС СIf the called user or network does not understand the Service 3 request then the Address Complete Call Progress Message, Answer or Connect Message, returned to the originating exchange shall not include either a Service 3 acceptance or rejection. This type of response will be taken as an implicit rejection of Service 3. С СIf the network or called user cannot support Service 3, and it was requested with a nonР-Рessential indication, a Service 3 rejection indication is returned in the Address Complete, Call Progress Message, Answer or Connect with the indication Р"РService 3 not providedР"Р in the userР-РtoР-Рuser indicators parameterУУб cмˆ4 PŽТ б6жЏ†а H ааа6)б cмˆ4 PŽТ бФФThe SCCP connection refused message will be returned if COР-РSCCP method is selected. Џж)ФФб cмˆ4 PŽТ б. (УУNoteФФ Р-Р The Study Group XVIII service description does not allow this implicit rejection.) а H аС СIf the Service 3 request is indicated as essential and the called user or network cannot support it a Release Message is sent with cause code 50, Р"Рrequested facility not subscribedР"Р, cause code 29, Р"Рfacility rejected by the networkР"Р or cause code 69, Р"Рrequested facility not implementedР"Р and the diagnostic containing the userР-РtoР-Рuser indicators parameter. Та ТС€ HСA.2.3.4СpСУУService 3 requested after call setР-РupЦЦ а H аФФС СAfter call setР-Рup has been completed either the calling or called party may request to transfer Service 3 information. On reception of the request from call control the ISDN User Part sends a Facility Request Message containing the facility indicator parameter indicating userР-РtoР-Рuser service and a userР-РtoР-Рuser indicators parameter requesting Service 3 to the distant local exchange using the appropriate transport method. The facility request will contain the userР-РtoР-Рuser indicators parameter with Service 3 indicated as Р"Рrequested essential/not essentialР"Р and Services 1 and 2 indicated as Р"Рno informationР"РУУб cмˆ4 PŽТ б7жюIа H ааа7)б cмˆ4 PŽТ бФФThe Connection Request parameter will be included if COР-РSCCP method is selected, or the call reference parameter if CLР-РSCCP method is selected. юж)ФФб cмˆ4 PŽТ б. On receipt of the Facility message at the distant exchange call control will be notified which will then notify the remote user. If the user wishes to support Service 3 during the active phase, a Service 3 acceptance will be returned to call control. On notification of the acceptance by call control the ISDN User Part will generate a Facility Accepted Message with the indication Р"РService 3 providedР"Р in the userР-РtoР-Рuser indicators parameterУУб cмˆ4 PŽТ б8жЏ†а H ааа8)б cмˆ4 PŽТ бФФThe SCCP connection confirm message will be returned if COР-РSCCP method is selected. Џж)ФФб cмˆ4 PŽТ б. Services 1 and 2 will be indicated as Р"Рno informationР"Р in the userР-РtoР-Рuser indicators parameter. On the receipt of the message this explicit acceptance indication shall be forwarded to call control which will then notify the requesting user. Та ТС€ HСA.2.3.5СpСУУRejection of Service 3 when requested after call setР-РupЦЦ а H аФФС СIf the requested user or network does not understand the Service 3 request then no message is returned. This response shall be taken as an implicit rejection of the service request. С СIf the network or requested user cannot support Service 3, and it was requested with a nonР-Рessential indication, a Service 3 rejection indication is returned in the Facility Reject Message with the indication Р"РService 3 not providedР"Р in the userР-РtoР-Рuser indicators parameter. а H аС СIf the call control does not indicate acceptance or rejection the network shall not return any explicit rejection to the exchange. С СУУNote 1ФФ Р-Р The Stage 1 service description does not allow this implicit rejection. а H аС СУУNote 2ФФ Р-Р The handling of essential/non essential Service 3 request is not yet consistent with the State 1 service description. Та ТA.2.3.6СP СУУInterworkingЦЦ а H аФФС СIn the case of interworking with a nonР-РISDN network an Р"РinterworkingР"Р protocol control indicator will be returned to the originating exchange in the first appropriate messageУУб cмˆ4 PŽТ б9)б cмˆ4 PŽТ бФФ. If Service 3 was requested after call setР-Рup, a Facility Reject Message is returnedУУб cмˆ4 PŽТ б9жЏ†а H ааа9)б cмˆ4 PŽТ бФФThe SCCP connection refused message will be returned if COР-РSCCP method is selected. Џж)ФФб cмˆ4 PŽТ б. Two ISDN networks that interwork may have to retain knowledge of the service request until it is clear whether both can support the service. Та ТС€ HСA.2.3.7СpСУУTransfer of messages containing userР-РtoР-Рuser informationЦЦ а H аФФС СOnce acceptance of Service 3 has been transmitted across the network, both of the involved users can transfer userР-РtoР-Рuser information between themselves. Within the network the userР-РtoР-Рuser information parameter will be carried in a UserР-РtoР-Рuser Information Message. The network provides for the transfer of these messages from the calling to the called side and vice versa. С СThe UserР-РtoР-Рuser Information Message format can be found in Table 20/Q.763. Та ТС€ HСA.2.4С СУУRequesting userР-РtoР-Рuser signalling Services 1, 2 and 3ЦЦ ФФС СThis section describes procedures for requesting Services 1, 2 and 3. а H аС СУУNoteФФ Р-Р UserР-РtoР-Рuser Service 1 implicit request/response procedures are also found in РSР 2.2.1. Only explicit Service 1 requests may follow the procedure in this section. Та ТС€ HСA.2.4.1СpСУУCall establishmentЦЦ а H аФФС СProcedures for call establishment are described in РSРS A.2.1.2, A.2.2 and A.2.3.2 with the following modifications: а H аС СOn service request one userР-РtoР-Рuser indicators parameter will be sent with each service being indicated as Р"Рrequested, essential/non essentialР"Р. С СIf the called user can support the indicated services, then all three services will be indicated as Р"РprovidedР"Р in the userР-РtoР-Рuser indicators parameter in the Address Complete or Call Progress Message. Alternatively, the Address Complete or Call Progress Message may indicate Р"РService 3, no informationР"Р and Р"РService 3 providedР"Р in the Answer or Connect Message as provided in РSР A.2.3.2. In the case that the call is to multiР-Рpoint users, the acknowledgement of Services 1 and 3 shall be delayed until the Answer or Connect Message is sent. Та ТС€ HСA.2.4.2СpСУУService rejectionЦЦ а H аФФС СIf the called user or network does not understand the service requested, then the Address Complete, Call Progress, Answer or Connect Messages returned will not include either service(s) acceptance or rejection. This type of response will be taken as an implicit rejection of all services. С СIf the called user or network does not understand a specific service request, that specific service is implicitly rejected following the procedures of РSРS A.2.1.4, A.2.2.3 and A.2.3.3. Alternatively, if the network or called user cannot support one or more service requests and the service requests were indicated as nonР-Рessential, then the rejection may be provided in the Address Complete or Call Progress Messages. (In the case of a call to multiР-Рpoint users only Service 2 may be rejected in this way, Service 1 and 3 must be rejected in the Answer or Connect Message if the called user is furnishing the rejection.) The services may also be rejected following the procedures of РSРS A.2.1.4, A.2.2.3 and A.2.3.3. а H аС СIf any or all of the services requested is indicated as essential and the called user or network cannot support one or more of the services, a а H аRelease Message is sent with cause code 29, Р"Рfacility rejected by the networkР"Р, cause code 50, Р"Рrequested facility not subscribedР"Р, or cause code 69, Р"Рrequested facility not implementedР"Р and the diagnostic containing the userР-РtoР-Рuser indicators parameter. С СIf the call control does not indicate Service 1, 2 or 3 acceptance or rejection prior to the sending of the Address Complete, Call Progress, Answer or Connect Message, then no indication of service acceptance or rejection shall be returned for the specific service(s). Та ТС€ HСA.2.4.3СpСУУInterworkingЦЦ а H аФФС СIn the case of interworking with a nonР-РISDN network, the Р"РinterworkingР"Р protocol information will be returned to the originating exchange in the first appropriate message, e.g., an Address Complete Message. Two ISDN networks that interwork may have to retain knowledge of the service request until it is clear whether both can support the services. Та ТС€ HСA.2.4.4СpСУУTransfer of UserР-РtoР-Рuser Information MessagesЦЦ а H аФФС СThe procedures for the transfer of UserР-РtoР-Рuser Information Messages is covered in РSРS A.2.2.5 and A.2.3.7. Та ТС€ HСA.2.5С СУУUserР-РtoР-Рuser information transport methods for Services 2 and 3ЦЦ ФФС СThe Transport methods for Services 2 and 3 may be found in РSР 3 of Recommendation Q.764. Та ТС€ HСA.2.6С СУУMessage flow diagramsЦЦ а H аФФС СThe message flow diagrams are shown in Figures AР-Р1/Q.730 to AР-Р7/Q.730. а H аС СFor UserР-РtoР-Рuser Signalling Service 2 and 3 the figures only show ISDN user part messages required for basic call control and userР-РtoР-Рuser signalling and are not meant to imply any particular transfer method. The parameters and indicators shown are for the UserР-РtoР-Рuser Signalling Service only, i.e. any parameters or message associated with the various transport methods are not shown. С СThe following notes apply to Figures AР-Р1/Q.730 to AР-Р7/Q.730: С СУУNote 1ФФ Р-Р In cases where an ALERTING indication is carried by a Call Progress Message the userР-РtoР-Рuser indicators parameter and/or the а H аuserР-РtoР-Рuser information parameter may also be transported in the Call Progress Message. С СУУNote 2ФФ Р-Р In cases where the called user is an automatic answering terminal, userР-РtoР-Рuser indicators parameter and/or the userР-РtoР-Рuser information parameter may be transported in a Connect Message. а H аС СFigure AР-Р1/Q.730 shows a successful use of userР-РtoР-Рuser Signalling Service 1 when explicitly requested in a pointР-РtoР-Рpoint configuration. С СFigure AР-Р2/Q.730 shows both the successful and unsuccessful use of userР-РtoР-Рuser Signalling Service 2 in a pointР-РtoР-Рpoint configuration. С СFigure AР-Р3/Q.730 shows an unsuccessful use of userР-РtoР-Рuser Signalling Service 2 in a pointР-РtoР-Рmultipoint configuration. This unsuccessful case is shown because the network reactions will be the same in all similar cases. С СFigure AР-Р4/Q.730 shows both successful and unsuccessful cases for userР-РtoР-Рuser Signalling Service 3 when the service is nonР-Рessential in a pointР-РtoР-Рpoint configuration. а H аС СFigure AР-Р5/Q.730 shows a successful use of userР-РtoР-Рuser Signalling Service 3 after the call is active in a pointР-РtoР-Рpoint configuration. С СFigure AР-Р6/Q.730 shows a successful use of userР-РtoР-Рuser signalling Services 1, 2 and 3 and where all services are nonР-Рessential in a pointР-РtoР-Рpoint configuration. а H аС СFigure AР-Р7/Q.730 shows successful use of userР-РtoР-Рuser signalling Services 1 and 3 and unsuccessful use of Service 2 in a pointР-РtoР-Рmultipoint configuration. It should be noted again that Service 2 will not work in a pointР-РtoР-Рmultipoint configuration. С СThe following abbreviations are used in the figures: б cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџHpи и џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа‚Ср SСааб cмˆ4 PŽТ бAbbreviations аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџH ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСр JС UserР-РtoР-Рuser Indicator Values а Ш И ааЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРOСб cмˆ4 PŽТ б ni аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа no information а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б rne аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа requested, non essential а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРOСб cмˆ4 PŽТ б re аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа requested, essential а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРOСб cмˆ4 PŽТ б p аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа provided а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРOСб cмˆ4 PŽТ б np аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа not provided а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРIСб cмˆ4 PŽТ б Abbreviations аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Parameter name а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б UUI аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа userР-РtoР-Рuser information а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРLСб cмˆ4 PŽТ б UUI ind. аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа userР-РtoР-Рuser indicators а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРIСб cмˆ4 PŽТ б Abbreviations аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Message name а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б ACM аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Address Complete а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б ANM аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Answer а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б FAR аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Facility Request а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б FAA аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Facility Accepted а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б IAM аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Initial Address а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б REL аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Release а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б RLC аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа Release Complete а Ш И аб cмˆ4 PŽТ бˆа Ш И аб cмˆ4 PŽТ бвЦ‚Hи Ш ИЦв‡аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџpи и Ш џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаСрРNСб cмˆ4 PŽТ б USR аЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџШ ˆ№Xа(€иИџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬа UserР-РtoР-Рuser Information а Ш И аб cмˆ4 PŽТ бˆ а H ааЬџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџHpи P Ј XА`ИhР!(#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЬаС СThe messages shown with dashed lines are not part of the ISDN User Part protocol and are for information only. For detailed information on the access protocol userР-РtoР-Рuser procedures the ISDN access protocol Recommendation Q.931 should be examined. ‚Ср JСб cмˆ4 PŽТ бFigure AР-Р1/Q.730 Љ T1115880Љ88 б cмˆ4 PŽТ б Ср JСб cмˆ4 PŽТ бFigure AР-Р2/Q.730 Љ T1115890Љ88 б cмˆ4 PŽТ б Ср JСб cмˆ4 PŽТ бFigure AР-Р3/Q.730 Љ T1115900Љ88 б cмˆ4 PŽТ б Ср JСб cмˆ4 PŽТ бFigure AР-Р4/Q.730 Љ T1115910Љ88 б cмˆ4 PŽТ б Ср JСб cмˆ4 PŽТ бFigure AР-Р5/Q.730 Љ T1115920Љ88 б cмˆ4 PŽТ б Ср JСб cмˆ4 PŽТ бFigure AР-Р6/Q.730 Љ T1115930Љ88 б cмˆ4 PŽТ б Ср JСб cмˆ4 PŽТ бFigure AР-Р7/Q.730 Љ T1115940Љ88 б cмˆ4 PŽТ б Та ТС€ HСA.2.7С СУУInteraction with other supplementary servicesЦЦ Та ТС€ HСФФA.2.7.1СpСУУCall forwarding servicesЦЦ ФФС СInteractions with the call forwarding services are shown in the call forwarding protocol sections. Та ТС€ HСA.2.7.2СpСУУCall waiting serviceЦЦ а H аФФС СInteractions with the call waiting service are shown in the call waiting protocol sections. (Call waiting is for further study.) Та ТС€ HСA.2.7.3СpСУУOther servicesЦЦ а H аФФС СThere are no known interactions with services other than those listed. Та ТС€ HСA.2.8С СУУState transition diagramsЦЦ а H аФФС СThe state transition diagrams may be found in the Stage 2 description of the UserР-РtoР-Рuser Service.