S.4 SIP

26.1143GPPIP Multimedia Subsystem (IMS)Media handling and interactionMultimedia telephonyRelease 18TS

S.4.1 MSMTSI client in terminal

An MSMTSI client in terminal shall, when connecting to a remote party that included the "isFocus" tag in any of its SIP headers, subscribe to SIP conference events, as described in [147]. The MSMTSI client in terminal shall be able to receive and handle conference event notifications, resulting from the subscription. The MSMTSI client in terminal shall be capable of parsing all conference event information elements, shall be capable of receiving partial conference event information, and shall be capable of presenting conference event information to the user of the MSMTSI client in terminal, either automatically or on explicit user request. The MSMTSI client in terminal shall be capable of presenting at least the values of the conference event information elements indicated in bold below to the user of the MSMTSI client in the terminal, and shall be capable to use the conference event information elements indicated in italics below for endpoint and media identification, as defined by [147] and [148] (here also indicating relevant parts of the XML document hierarchy, for information):

– <conference-info>

– <conference-description>

– <display-text>

– <subject>

– <users>

– <user>

– <display-text>

– <associated-aors>

– <entry>

– <uri>

– <endpoint>

– <media>

– <src-id>

Values for other conference event information elements may optionally be made available to the user of the MSMTSI client in the terminal.

S.4.2 MSMTSI MRF

An MSMTSI MRF shall include the "isFocus" tag in all of its outgoing SIP headers that support inserting that tag. It shall be capable of handling subscriptions and unsubscriptions for conference event information, as specified in [147].