name: PBX
full_form: Private Branch eXchange
context: Figure 6.1.2.2-1: How Originating IMS network invokes the signing on behalf of 3rd party (SIP trunk) 1. The 3rd party PBX sends a SIP INVITE that contains the IMS Identity of the calling UE and that may or may not contain the third party ID on behalf of 3rd party subscriber to IBCF. 2. The IBCF forwards the SIP request to the IMS subsystem entity. The IMS subsystems include I/S-CSCF, MMtel AS and etc. (details not shown in the figure) 3. The originating IMS subsystem checks whether the IMS subscription of the calling PBX is authorized to use 3P IDs. If the PBX is not authorized to use 3P IDs, then the originating IMS subsystem ignores the 3P ID within the SIP INVITE (if present) and do not execute the rest of 3P ID related steps during the call set-up. The call continues without presenting 3P ID to the called endpoint. If the PBX is authorized to use 3P IDs, the originating IMS subsystem gets Rich Call Data of 3rd party susbscriber from the Database based on the received IMS identity.
description: A Private Branch eXchange (PBX) is a telephone system within an enterprise that switches calls between users on local lines while also providing access to external telephone services. In the context of 3GPP TS 33.890, the PBX acts as a device connecting to the network and interacting with IMS subsystem entities for call setup and management.
explanation: The classification of PBX as a Device is based on its role in the provided context, where it is described as sending SIP requests and interacting with the IMS network, indicating its function as an endpoint or user equipment within the telecommunications infrastructure.
section_title: 6.1.2.2	How Originating IMS network invokes the signing on behalf of 3rd party (SIP trunk)
biotag_Context: O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,B-Network,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,B-Network,O,O,O,B-Network,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Parameter,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Network,O,O,B-Miscellaneous,I-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,B-Network,O
biotag_Description: O,B-Device,I-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O