Deprecated API

Contents

• Deprecated Classes
• Deprecated Methods

Deprecated Classes

org.mobicents.csapi.jr.slee.ui.ReportNotificationEvent
This event is deprecated and replaced by reportEventNotification(). It will be removed in a later release. This method notifies the application of an occurred network event which matches the criteria installed by the createNotification method.

Deprecated Methods

org.mobicents.csapi.jr.slee.IpServiceConnection.closeConnection()
No need to invoke this method. It will be removed from the API. Close this Connection . Any further invocations with throw an Exception It is imperative that close() is called before this is reference goes out of scope for efficient connection pooling

org.mobicents.csapi.jr.slee.dsc.IpDataSessionControlManagerConnection.createNotification(TpDataSessionEventCriteria)
This method is deprecated and will be removed in a later release. It is replaced with createNotifications(). This method is used to enable data session notifications so that events can be sent to the application. This is the first step an application has to do to get initial notifications of data session happening in the network. When such an event happens, the application will be informed by reportNotification(). In case the application is interested in other events during the context of a particular data session it has to use the connectReq() method on the data session object. The application will get access to the data session object when it receives the reportNotification(). The createNotification method is purely intended for applications to indicate their interest to be notified when certain data session events take place. It is possible to subscribe to a certain event for a whole range of addresses, e.g. the application can indicate it wishes to be informed when a data session is setup to any number starting with 800. If some application already requested notifications with criteria that overlap the specified criteria or the specified criteria overlap with criteria already present in the network (when provisioned from within the network), the request is refused with P_INVALID_CRITERIA. The criteria are said to overlap if both originating and terminating ranges overlap and the same number plan is used. If a notification is requested by an application with monitor mode set to notify, then there is no need to check the rest of the criteria for overlapping with any existing request as the notify mode does not give control of a data session. Only one application can place an interrupt request if the criteria overlaps. If the same application requests two notifications with exactly the same criteria but different callback references, the second callback will be treated as an additional callback. Both notifications will share the same assignmentID. The gateway will always use the most recent callback. In case this most recent callback fails the second most recent is used. In case the createNotification contains no callback, at the moment the application needs to be informed the gateway will use as callback the callback that has been registered by setCallback().

org.mobicents.csapi.jr.slee.cc.mpccs.IpMultiPartyCallControlManagerConnection.getNotification()
This method is deprecated and replaced by getNextNotification(). It will be removed in a later release. This method is used by the application to query the event criteria set with createNotification or changeNotification.

org.mobicents.csapi.jr.slee.dsc.IpDataSessionControlManagerConnection.getNotification()
This method is deprecated and its use is discouraged. It will be removed in a later release. It is replaced with getNotifications. This method is used by the application to query the event criteria set with createNotification or changeNotification.