Managing Object Memory

Messages

When you have created messages and assigned values to the particular parameters, you must explicitly call the send() method. If the call succeeds, then the API frees the memory used by the sent message. If the call to send() fails, the message is returned to the application for further investigation.

On receiving a message from the SS7 stack, the API creates a message object for the application via the receive() method. This message object must be deleted by the application when it has finished manipulating the message. The message object can also be returned to the API via a subsequent call to send().

Parameter Values

As illustrated in “Accessors”, you are recommended to create parameter value objects using the ISUP::ParmValue object. These objects are used by the appropriate write accessor to set the parameter.

To get a parameter value using a read accessor, the API creates the parameter value objects.

In both cases, it is your responsibility to delete all parameter value objects.

Additional Information

Some primitives sent from the HP OpenCall SS7 ISUP library to the application contain additional information objects (see “Additional Information”). These objects are automatically created by the API.

If the application sends any primitives containing additional information, the API automatically deletes these objects when the call to send() is successful.

In the case send() fails, the additional information objects are returned to the application for further investigation. These objects must be deleted by the application or returned to the API in a subsequent send().

Return Status Values

Check the Return Status value for each method, as described in “Exception Handling ”. The creation and deletion of these return status objects is your responsibility: the API only assigns values to these objects.