Sip Session Id - Cisco 8800 Series Manual
Hide thumbs
Also See for 8800 Series:
- Administration manual (406 pages) ,
- User manual (218 pages) ,
- Hardware installation manual (140 pages)
Table of Contents
Advertisement
Cisco IP Phone Configuration
Attribute
Oct
CiscoTxVm.TxCodec
CiscoTxVm.TxBw
CiscoTxVm.TxReso
CiscoTxVm.TxFrameRate
CiscoRxVm.rtpBitRate
CiscoTxVm.rtcpBitRate
SIP Session ID
The Multiplatform phones now support "Session Identifier". This feature helps to overcome the limitations
with the existing call-identifiers and allows end-to-end tracking of a SIP session in IP-based multimedia
communication systems in compliance with RFC 7989. To support session identifier, "Session-ID" header is
added in the SIP request and response messages.
"Session Identifier" refers to the value of the identifier, whereas "Session-ID" refers to the header field used
to convey the identifier.
• When a user initiates the call, the phone while sending SIP INVITE message, generates the local-UUID.
• When the UAS receives the SIP-INVITE, the phone picks up the local UUIDs with the incoming messages
• The same UUIDs are maintained in all the SIP messages of a particular session.
• The phone maintains the same local-UUID during other features, such as conference or transfer.
• This header is implemented in REGISTER method, the local-UUID remains same for all the REGISTER
The Session-ID comprises of Universally Unique Identifier (UUID) for each user agent participating in a call.
Each call consists of two UUID known as local UUID and remote UUID. Local UUID is the UUID generated
from the originating user agent and remote UUID is generated from the terminating user agent. The UUID
values are presented as strings of lower-case hexadecimal characters, with the most significant octet of the
UUID appearing first. Session Identifier comprises of 32 characters and remains same for the entire session.
Session ID format
Components will implement Session-ID which is global session ID ready.
A sample current session ID passed in http header by phones (dashes are just included for clarity) is
00000000-0000-0000-0000-5ca48a65079a.
A session-ID format: UUUUUUUUSSSS5000y000DDDDDDDDDDDD where,
Description
Number of octets transmitted
Video codec used for the transmitted video stream
Negotiated bandwidth for the transmitted video stream
Resolution of the transmitted video stream
Frame rate for the transmitted video stream
RTP bit rate in seconds (including any FEC, retransmits etc.).
Used to estimate bandwidth usage (bits/sec).
RTCP bit rate in seconds (including any FEC, retransmits etc.).
Used to estimate bandwidth usage (bits/sec).
and appends it to the received Session-ID header and sends the header in reponses.
messages till the phone fails to REGISTER.
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
SIP Session ID
Mandatory
Yes
Yes
No
Yes
Yes
Yes
Yes
219
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
