SIP Registration Server
| Line 8: | Line 8: | ||
===Message flow in registration of a SIP user agent on a registration 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 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 user agent sends a REGISTER request to the server. | ||
* The server sends back an acknowledgement message. | * 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. | 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. | ||
| + | |||
| + | === Yate as a SIP registrar === | ||
| + | |||
| + | The module used for configuring Yate are: | ||
| + | |||
| + | * regfile.conf | ||
| + | * register.conf | ||
| + | |||
| + | ==== Register file ==== | ||
| + | |||
| + | Module regfile used for autentication, registration, and routing of users from a file. | ||
| + | |||
| + | regfile.conf | ||
| + | |||
| + | [general] | ||
| + | ; auth setups the user.auth handler priority | ||
| + | auth=100 | ||
| + | ; register setups the user.register and user.unregister | ||
| + | ; handlers priority | ||
| + | register=100 | ||
| + | ; route setups the call.route handler priority | ||
| + | route=100 | ||
| + | ; file: string. An auxiliary conf file used to save and load from it autocreated and registered entries | ||
| + | ; If file don't exists the registered entities will be lost on reload | ||
| + | file=/path/filename | ||
| + | |||
| + | ====Register file ==== | ||
| + | |||
| + | Module register used for autentication, registration, and routing of users from database. | ||
| + | |||
| + | See more how to [[Register#Configuration| configure register]]. | ||
| Line 18: | Line 49: | ||
* [[SIP in Yate]] | * [[SIP in Yate]] | ||
| + | * [[Regfile|Regfile module]] | ||
| + | * [[Register| Register module]] | ||
Revision as of 16:07, 3 April 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.
Contents |
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.
Yate as a SIP registrar
The module used for configuring Yate are:
- regfile.conf
- register.conf
Register file
Module regfile used for autentication, registration, and routing of users from a file.
regfile.conf
[general]
- auth setups the user.auth handler priority
auth=100
- register setups the user.register and user.unregister
- handlers priority
register=100
- route setups the call.route handler priority
route=100
- file
- string. An auxiliary conf file used to save and load from it autocreated and registered entries
- If file don't exists the registered entities will be lost on reload
file=/path/filename
Register file
Module register used for autentication, registration, and routing of users from database.
See more how to configure register.
See also
