This section provides the information about the protocol and error handling related to the SIP Profile API:
When you create a
When the
The profile data is transferred from the server to the client when a user retrieves a
When the client holds an instance of
Note: A
When the client deletes the
The profile must be active before a
All profiles are automatically registered when they are enabled. If a profile is not registered before being enabled, the registration status change is acknowledged through
When a profile is enabled and registered, the client can use it and the SIP Client API to create SIP sessions. An enabled profile cannot be removed from the system while it is used by the client.
When a profile is not needed by the client, it is disabled. When you delete an instance of the profile the profile is disabled.
The following illustration shows use of the SIP Profile API.
The errors are indicated by return codes, by functions leaving, or by calling callback functions. If an error occurs during a synchronous operation initiated by the client, the called function leaves with a correct error code.
If an error occurs during an asynchronous operation, the error is passed to the client through the callback function
This section provides the information about the protocol and error handling related to the SIP Profile API:
When you create a
When the
The profile data is transferred from the server to the client when a user retrieves a
When the client holds an instance of
Note: A
When the client deletes the
The profile must be active before a
All profiles are automatically registered when they are enabled. If a profile is not registered before being enabled, the registration status change is acknowledged through
When a profile is enabled and registered, the client can use it and the SIP Client API to create SIP sessions. An enabled profile cannot be removed from the system while it is used by the client.
When a profile is not needed by the client, it is disabled. When you delete an instance of the profile the profile is disabled.
The following illustration shows use of the SIP Profile API.
The errors are indicated by return codes, by functions leaving, or by calling callback functions. If an error occurs during a synchronous operation initiated by the client, the called function leaves with a correct error code.
If an error occurs during an asynchronous operation, the error is passed to the client through the callback function