1 / 4

Jani.Hautakorpi@ericsson

Extending the SIP Reason Header with Warning Codes draft-hautakorpi-reason-header-for-warnings-00.txt. Jani.Hautakorpi@ericsson.com. The Main Idea. New protocol value for SIP Reason header field: Warning codes from RFC3261.

junius
Télécharger la présentation

Jani.Hautakorpi@ericsson

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extending the SIP Reason Header with Warning Codesdraft-hautakorpi-reason-header-for-warnings-00.txt Jani.Hautakorpi@ericsson.com

  2. The Main Idea • New protocol value for SIP Reason header field: • Warning codes from RFC3261. • Motivation: Ability to convey richer information about why a SIP request was generated. • Example: Reason: SIP-Warning; cause=304; text="Media type not available"

  3. Example Scenario A Controller B INVITE 200 OK ACK INVITE 480 Temp. Unavailable Warning: 399 pc2.example.org “Low battery” ACK BYE Reason: SIP; cause=480; text="Request Terminated" Reason: SIP-Warning; cause=399; text="Low battery" 200 OK

  4. Way Forward • One big open issue: RFC3261 only allows Warning codes that are related to the SDP. Should this be the case also in the future? • Comments?

More Related