SIP Registration Server
| Line 13: | Line 13: | ||
By changing some fields in the message the registration canceling is performed. Also interrogation of the server to identify contacts associated with a SIP url are made in the same way. | By changing some fields in the message the registration canceling is performed. Also interrogation of the server to identify contacts associated with a SIP url are made in the same way. | ||
| + | |||
| + | |||
| + | '''See also''' | ||
| + | |||
| + | * [[SIP in Yate]] | ||
Revision as of 13:13, 28 March 2013
The registration server’s functionality typically stands in setting up and tearing down functionality with a client by using the registration and invite requests as well as clearing and retrieving registrations from a SIP url.
Register notion
The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason? The answer is quite simple. It’s about locating individual users in case of a call, which is similar to an INVITE message sent to the server.
Message flow in registration of a SIP user agent on a registration server
The actual registration of a SIP user agent on a registration server is made using a pretty simple message flow like it follows.
- The user agent sends a REGISTER request to the server.
- The server sends back an acknowledgement message.
By changing some fields in the message the registration canceling is performed. Also interrogation of the server to identify contacts associated with a SIP url are made in the same way.
See also
