Content-Type Clause Samples

Content-Type. The Content-Type header will contain the value application/registration+xml (from RFC 3680). The body of the NOTIFY request will contain a registration element for each non-barred public user identity (identified in the aor attribute of each <registration> element). The <uri> sub-element inside each <contact> sub-element of the <registration> element will contain the contact address provided by the respective UE. If the public user identity has been de-registered ⮚ The state attribute within the <registered> and <contact> elements is set to ‘terminated’. ⮚ The event attribute within each <contact> element to one of ‘deactivated’,’expired’,’unregistered’,’rejected; or ‘probation’ according to RFC3680. If the deregistration of the public user identity has already been indicated in an earlier NOTIFY and no new registration has occurred then the <registration> element for the deregistered public user identity is not included. If the public user identity has been registered ⮚ The state attribute within the <registered> and <contact> elements is set to ‘active’. ⮚ The event attribute within the <contact> element is set to ‘registered’ If the public user identity has been automatically registered ⮚ The state attribute within the <registration> and <contact> elements is set to ‘active’. ⮚ The event attribute within the <contact> element is set to ‘created’.
View Source
Content-Type. Support for the Content-Type header is mandatory for both UACs and UASs.
View Source
Content-Type. If Service Information is associated with the Application Server iFC for the REGISTER method then this SHOULD be included as an XML element in the message body of the REGISTER request. In this case then Content-Type header will include the MIME type application/3gpp-ims+xml as defined in section 7.6 in 3GPP TS 24.229 V7.2.0.
View Source

Related to Content-Type

  • Formatted Font: 12

  • Query a search query initiated from the Search Box or a Hyperlink, or a request for Matched Ads initiated by the Ad Code on an Ad Page. Results: Paid Search Results, Hyperlink Results, Domain Match Results, Web Search Results and/or Matched Ads, to the extent included in this Agreement and as appropriate to the context. Search Box: a graphical area in which a user can enter a Query. SO: the Service Order.

  • Keywords Price expiry date (to be in line with Review Dates)

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • End User This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.