IMS / SIP Requests

This page groups the SIP request methods most often seen in IMS traces. The goal is simple: identify what the endpoint or network is trying to do before you dive into headers, SDP, authentication, or policy details.

In practice, request methods fall into a few repeatable jobs: session setup, session maintenance, registration, service control, subscription handling, and messaging.

Request Message Pages

Open the individual IMS / SIP request references below.

Core Session Control

These methods create, confirm, modify, or end the SIP session itself.

INVITE

Starts a dialog or changes session parameters when the dialog already exists. This is the main call-setup method in IMS voice traces.

ACK

Confirms the final response to an INVITE transaction. In traces, it tells you the INVITE exchange really closed successfully.

BYE

Ends an existing dialog. Use it when reading call release or session teardown.

CANCEL

Stops an INVITE transaction before a final response is received.

UPDATE

Changes session parameters inside an existing dialog without ending it.

PRACK

Acknowledges a reliable provisional response, usually when early-session handling matters.

Registration and Capability

These methods matter most when the UE or network is establishing service reachability rather than an active voice session.

REGISTER

Registers the UE contact and service reachability with the IMS core. This is the anchor request in IMS registration procedures.

OPTIONS

Queries capabilities or liveness without starting a full session.

PUBLISH

Publishes presence-related state toward the service layer when that feature is in use.

Messaging and Mid-Call Service Control

These methods carry application or service information without behaving like the main session-setup request.

MESSAGE

Carries standalone SIP message content.

INFO

Transfers mid-session service information inside an existing dialog.

REFER

Requests call transfer or related redirection behavior.

Subscription and Event Signaling

These methods are common when IMS services depend on event packages or notification-based state updates.

SUBSCRIBE

Creates or refreshes a subscription to an event package.

NOTIFY

Carries state change notifications for an active subscription.