Most SIP user agents will automatically try to register when they start up, by sending a REGISTER request.
This updates the Registrar with the user agent’s contact address. SIP registrations are not permanent, so the user agent will periodically refresh its registration with the Registrar. When the user agent shuts down, it will send another request to un-register its contact address.
The registration process is defined in RFC3261 section 10. When registering, refreshing or un-registering, the user agent sends a REGISTER request and expects to receive a 200 OK response, indicating that the operation succeeded:
User Agent Registrar
| |
| REGISTER |
|------------------>|
| 200 OK |
|<------------------|
| |
|
You can enable tracing in Rhino to see the messages received by the Registrar service. |
