Version 2.0 of the protocol, known as 'SIP2', is a de facto standard for library self-service applications. SIP version 1.0 was published by 3M in 1993. The first version of the protocol supported basic check in and check out operations, but had minimal support for more advanced operations. Version 2.0 of the protocol was published in. PHP GPL-2.0 46 65 9 (1 issue needs help) 4 Updated Sep 8, 2020 opensips-cli OpenSIPS CLI tool - an interactive command line tool that can be used to control and monitor OpenSIPS servers.
-->Sip 103
Specifies Microsoft extensions to the Session InitiationProtocol (SIP), as specified in [RFC3261], which is used by terminals toestablish, modify, and terminate multimedia sessions or calls. The SIPextensions add support for privacy features and for subscription requests foroffline end nodes to the SIP extensions for presence.
This page and associated content may beupdated frequently. We recommend you subscribe to the RSSfeed to receive update notifications.
Published Version
Date | Protocol Revision | Revision Class | Downloads |
---|---|---|---|
6/1/2017 | 8.0 | None | PDF | DOCX | Diff |
Previous Versions
Date | Protocol Revision | Revision Class | Downloads |
---|---|---|---|
7/14/2016 | 8.0 | None | PDF | DOCX | Diff |
10/16/2015 | 8.0 | None | PDF | DOCX |
6/30/2015 | 8.0 | None | PDF | DOCX |
5/15/2014 | 8.0 | Major | PDF | DOCX |
2/13/2014 | 7.0 | None | PDF | DOCX |
11/14/2013 | 7.0 | None | PDF | DOCX |
8/8/2013 | 7.0 | None | PDF | DOCX |
1/31/2013 | 7.0 | None | |
10/25/2012 | 7.0 | None | |
7/12/2012 | 7.0 | None | |
3/30/2012 | 7.0 | Major | |
12/16/2011 | 6.2 | None | |
9/23/2011 | 6.2 | None | |
6/17/2011 | 6.2 | Minor | |
5/6/2011 | 6.1 | River 2 77. Minor | |
3/25/2011 | 6.0.3 | None | |
2/11/2011 | 6.0.3 | None | |
1/7/2011 | 6.0.3 | None | |
11/19/2010 | 6.0.3 | Geekbench 4 v4 4 1. None | |
10/8/2010 | 6.0.3 | None | |
8/27/2010 | 6.0.3 | None | |
7/16/2010 | 6.0.3 | None | |
6/4/2010 | 6.0.3 | Editorial | |
4/23/2010 | 6.0.2 | Editorial | |
3/12/2010 | 6.0.1 | Editorial | |
1/29/2010 | 6.0 | ||
12/18/2009 | 5.1.2 | Editorial | |
11/6/2009 | 5.1.1 | Editorial | |
9/25/2009 | 5.1 | Minor | |
8/14/2009 | 5.0.4 | Editorial | |
7/2/2009 | 5.0.3 | Editorial | |
5/22/2009 | 5.0.2 | Editorial | |
4/10/2009 | 5.0.1 | Editorial | |
2/27/2009 | 5.0 | Major | |
1/16/2009 | 4.0 | Major | |
12/5/2008 | 3.0 | Major | |
10/24/2008 | 2.1 | Minor | |
8/29/2008 | 2.0.2 | Editorial | |
7/25/2008 | 2.0.1 | Editorial | |
6/20/2008 | 2.0 | Major | |
5/16/2008 | 1.0.3 | Editorial | |
3/14/2008 | 1.0.2 | Editorial | |
1/25/2008 | 1.0.1 | Editorial | |
11/30/2007 | 1.0 | Major | |
10/23/2007 | 0.4 | Minor | |
9/28/2007 | 0.3 | Minor | |
8/10/2007 | 0.2 | Minor | |
5/11/2007 | 0.1 | New |
Preview Versions
From time to time, Microsoft maypublish a preview, or pre-release, version of an Open Specifications technicaldocument for community review and feedback. To submit feedback for a previewversion of a technical document, please follow any instructions specified forthat document. If no instructions are indicated for the document, pleaseprovide feedback by using the OpenSpecification Forums.
The preview period for a technical document varies.Additionally, not every technical document will be published for preview.
A preview version of this document may beavailable on the WindowsProtocols - Preview Documents page. After the preview period, themost current version of the document is available on this page.
Development Resources
Findresources for creating interoperable solutions for Microsoft software,services, hardware, and non-Microsoft products:
Plugfestsand Events, Test Tools,DevelopmentSupport, and Open SpecificationsDev Center.
Sip 100
Intellectual Property Rights Notice for Open Specifications Documentation
Sip 102 Bye
- Technical Documentation. Microsoft publishes OpenSpecifications documentation (“this documentation”) for protocols, fileformats, data portability, computer languages, and standards support.Additionally, overview documents cover inter-protocol relationships andinteractions.
- Copyrights. This documentation is covered by Microsoftcopyrights. Regardless of any other terms that are contained in the terms ofuse for the Microsoft website that hosts this documentation, you can makecopies of it in order to develop implementations of the technologies that aredescribed in this documentation and can distribute portions of it in yourimplementations that use these technologies or in your documentation asnecessary to properly document the implementation. You can also distribute inyour implementation, with or without modification, any schemas, IDLs, or codesamples that are included in the documentation. This permission also applies toany documents that are referenced in the Open Specifications documentation.
- No Trade Secrets. Microsoft does not claim any tradesecret rights in this documentation.
- Patents. Microsoft has patents that might cover yourimplementations of the technologies described in the Open Specificationsdocumentation. Neither this notice nor Microsoft's delivery of thisdocumentation grants any licenses under those patents or any other Microsoftpatents. However, a given Open Specifications document might be covered by theMicrosoft Open Specifications Promiseor the Microsoft CommunityPromise. If you would prefer a written license, or if thetechnologies described in this documentation are not covered by the OpenSpecifications Promise or Community Promise, as applicable, patent licenses areavailable by contacting [email protected].
- License Programs. To see all of the protocols in scopeunder a specific license program and the associated patents, visit the Patent Map.
- Trademarks. The names of companies and products containedin this documentation might be covered by trademarks or similar intellectualproperty rights. This notice does not grant any licenses under those rights.For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
- Fictitious Names. The example companies, organizations,products, domain names, email addresses, logos, people, places, and events thatare depicted in this documentation are fictitious. No association with any realcompany, organization, product, domain name, email address, logo, person,place, or event is intended or should be inferred.
Reservation of Rights. All otherrights are reserved, and this notice does not grant any rights other than asspecifically described above, whether by implication, estoppel, or otherwise.
Tools.The Open Specifications documentation does not require the use of Microsoftprogramming tools or programming environments in order for you to develop animplementation. If you have access to Microsoft programming tools andenvironments, you are free to take advantage of them. Certain OpenSpecifications documents are intended for use in conjunction with publiclyavailable standards specifications and network programming art and, as such,assume that the reader either is familiar with the aforementioned material orhas immediate access to it.
Support.For questions and support, please contact [email protected].
This section explains how to configure SIP roaming. SIP roaming lets subscribers move from one active SIP device to another (at the same site or multiple sites) and retain service at the last registering device.
Overview
The Oracle Communications Session Border Controller supports multiple active registrations for the same user. The softswitch makes decisions regarding the current location of the user and the handling of requests from devices that are not currently identified as the user location. When there are multiple NATs, the Oracle Communications Session Border Controller is still required to let the softswitch be able to differentiate it.
The Oracle Communications Session Border Controller’s SIP roaming ability supports the following features:
- Multiple active registrations from the same user can be cached, allowing subscribers to move from one active SIP device to another (at the same site or multiple sites) and still retain service at the last registering device. With the SIP roaming feature, one person, using multiple devices, can be contacted at all of the devices. These multiple devices (with their unique contact information) register to indicate that they are available for anyone that wants to contact that one person.
- The Oracle Communications Session Border Controller can also inform network devices (such as softswitches) of private SIP device IPv4 addresses (endpoints) and the public firewall address of the user location.
Process Overview
Caller 1 wants to contact Person A. Caller 1 sends a message to [email protected], but Person A has configured more than one SIP-enabled device to accept messages sent to that address. These devices have unique addresses of [email protected] and [email protected]. Person A has [email protected] and [email protected] registered with the Oracle Communications Session Border Controller for anything addressed to [email protected].
With the SIP roaming feature, the Oracle Communications Session Border Controller accepts and stores both registrations for [email protected]. That way, when someone wants to get in touch with Person A, the messages are sent to both devices ([email protected] and [email protected]) until Person A answers one of them. You do not need to configure your Oracle Communications Session Border Controller for this functionality; your Oracle Communications Session Border Controller automatically provides it.
Using Private IPv4 Addresses
In addition to supporting multiple registries, the Oracle Communications Session Border Controller (OCSBC) can also distinguish user locations by their private IPv4 address and the IPv4 address of the public firewall. Using this information, the OCSBC adds private endpoint and public firewall information to Contact headers.
For example, entering this information causes a Contact header that formerly appeared as the following:
to subsequently appear as the following:
The OCSBC SIP proxy reads this information and populates the contact-endpoint and contact-firewall fields with the appropriate values.
Example 1 With a NAT Firewall
The Oracle Communications Session Border Controller (OCSBC) SIP proxy is configured with the following changeable parameters:
- endpoint= IP address of the SIP UA
- useradd= IP address of the Firewall Public IP address or the source layer 3 IP address of Register message
- userport= IP address port number of the Firewall Public IP address or the source layer 3 IP address port of Register message
- OCSBC address=63.67.143.217
- firewall public address=10.1.10.21
- firewall public address port=10000
- SIP endpoint behind firewall=192.168.1.10
SIP message Contact header:
Example 2 Without a NAT Firewall
The Oracle Communications Session Border Controller SIP proxy is configured with the following changeable parameters:
Sip 101
- useradd= IP address of the SIP UA or the source layer 3 IP address of Register message
- userport= IP address port number of the SIP UA or the source layer 3 IP address port of Register message
- Oracle Communications Session Border Controller address=63.67.143.217
- SIP endpoint=192.168.1.10
- SIP endpoint IP address port=5060
SIP message Contact header:
For SIP, the softswitch responsibility is that the URI SD put in the Contact of the REGISTER message should be reflected in the 200-OK response to the REGISTER request. The Contact header of the response should have an expires header parameter indicating the lifetime of the registration.
The following example shows a Oracle Communications Session Border Controller Send:
The following examples shows the softswitch Respond:
The contact field for endpoint and firewall parameters only appear in the following:
- Contact header of a REGISTER request sent from the Oracle Communications Session Border Controller to the softswitch server
- Contact header of a REGISTER response sent from the softwitch server to the Oracle Communications Session Border Controller
- Request-URI of an initial INVITE sent from the UT CSA server to the Oracle Communications Session Border Controller
An active endpoint is deleted when it does not register within the registration-interval setting or receives a 401 Unauthorized.
Sip 1 0 83
SIP Roaming Configuration
You can configure the SIP configuration’s options parameter to indicate that you want to use the private IP address of the SIP device that the user is using and/or the public firewall address that identifies the location of the device. If defined, these options will be added as parameters to all Contact headers.
You can identify the endpoint and/or firewall information using the following options:
- contact-endpoint=<value> where <value> is the endpoint address or label
- contact-firewall=<value> where <value> is the firewall address or label
- In Superuser mode, type configure terminal and press Enter.
- Type session-router and press Enter to access the system-level configuration elements.
- Type sip-config and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters. From this point, you can configure SIP config parameters. To view all SIP config parameters, enter a ? at the system prompt.
- Type options followed by a Space.
- After the Space, type the information for an endpoint or a firewall, or both:
- Press Enter. For example, if you want your Oracle Communications Session Border Controller to add private endpoint and public firewall information to Contact headers, and you want to label this information as ep and fw, you would enter the following information in the ACLI.