About SIP headers

Message headers, which comply with the SIP standard, are automatically added when you add Send requests and responses. Message headers that are generated at runtime are displayed as <<Auto>>, and the actual values are visible in the log file.

The following table lists the headers that are automatically generated with a Send request. If a subsequent Send request uses the same context as a previous Send request, the message headers are automatically copied to the new request. The exceptions are Content-Type, which is copied only if the current request contains body contents, and Content-Length and Call-ID, whose values are generated during runtime and appear in the log file.

Header Generated with Default value
Call-ID All methods <<Auto>>. Cannot be modified.
Contact Subscribe, Invite, Update, Notify, Refer <<local-host>>:local-port. The default local port is 5555.
Content-Length All methods <<Auto>>.
CSeq All methods Numbered sequentially for each context. For example, the first Invite CSeq that uses context x is 1 INVITE, the next Invite CSeq that uses context x is 2 INVITE, but the next CSeq, which uses context y (a new context), is 1 INVITE.
Event Publish, Subscribe, Notify none
From All methods none
Max-Forwards All methods 70
RAck Prack none
Refer-To Refer ""<SIP:refer-to-url>
Subscription-State Notify none
To All methods none
Via All methods <<local-host>>:local-port

The following table lists the headers that are automatically generated with a Send response. The actual values are generated during runtime and are visible in the log file.

Header Default value
Call-ID <<Auto>>. Cannot be modified.
Contact Generated for Invite, Subscribe, Refer, and Update methods when the response is 200 OK:<<local-host>>:local-port
Content-Length <<Auto>>
CSeq <<Auto>>
From <<Auto>>
To <<Auto>>
Via <<Auto>>


Related

  • SIP test editor overview
  • Add SIP contexts
  • Add sequence patterns to SIP tests


    Related tasks

  • Configure background registration
  • Configure a test to use the TLS transport
  • Create a SIP counterpart test
  • Run tests on computers with multiple network addresses
  • Configure different ports for a SIP location
  • Verify expected behavior