This event indicates that the network has detected that the overload has ceased and has automatically removed any load controls on calls requested to a particular address range or calls made to a particular destination within the call control service.
This event indicates that the network has detected that the overload has ceased and has automatically removed any load controls on calls requested to a particular address range or calls made to a particular destination within the call control service.
This event indicates that the network has detected overload and may have automatically imposed load control on calls requested to a particular address range or calls made to a particular destination within the call control service.
This event indicates that the network has detected overload and may have automatically imposed load control on calls requested to a particular address range or calls made to a particular destination within the call control service.
Deprecated.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
This asynchronous event indicates that the request to connect a data session with the destination party was unsuccessful, e.g, an error detected in the network or the data session was abandoned.
This asynchronous event indicates that the request to connect a data session with the destination party was successful, and indicates the response of the destination party (e.g, connected, disconnected).
This asynchronous event indicates that the request to route the call leg to the destination party was unsuccessful - the call leg could not be routed to the destination party (for example, the network was unable to route the call leg, the parameters were incorrect, the request was refused, etc.).
This method creates an instance of the IpChargingSession interface to handle the charging events related to the specified user and to the application invoking this method.
Deprecated.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().
This method creates an instance of the IpChargingSession interface to handle the charging events related to the specified users and to the application invoking this method.
This method is used to create a new user interaction object for non-call related purposes
Results: userInteraction
Specifies the interface and sessionID of the user interaction created.
This method is used to create a new virtual provisioned pipe, which includes the pipe QoS information, the provisioned QoS information, the SLA ID, and the selected pairs of SAP/Sites.
This event indicates to the application that a fault in the network has been detected which cannot be communicated by a network event, e.g., when the user aborts before any establishment method is called by the application.
This method will detach the call leg from its call, i.e., this will prevent transmission on any associated bearer connections or media streams to and from other parties in the call.
This method is used to indicate that the application is not able to receive notifications for which the provisioning has been done from within the network.
This method is used to indicate that the application is not able to receive notifications for which the provisioning has been done from within the network.
This method is used to indicate that the application is not able to receive notifications for which the provisioning has been done from within the network.
This method is used to indicate that the application is not able to receive notifications for which the provisioning has been done from within the network.
This method is used to indicate that the application is able to receive which are provisioned from within the network (i.e. these notifications are NOT set using createNotification() but via, for instance, a network management system).
This method is used to indicate that the application is able to receive notifications which are provisioned from within the network (i.e. these notifications are NOT set using createNotification() but via, for instance, a network management system).
This method is used to indicate that the application is able to receive which are provisioned from within the network (i.e. these notifications are NOT set using createNotification() but via, for instance, a network management system).
This method is used to indicate that the application is able to receive notifications which are provisioned from within the network (i.e. these notifications are NOT set using createNotification() but via, for instance, a network management system).
This asynchronous event indicates that the request to manage call leg event reports was unsuccessful, and the reason (for example, the parameters were incorrect, the request was refused, etc.).
This asynchronous event reports that an event has occurred that was requested to be reported (for example, a mid-call event, the party has requested to disconnect, etc.).
This asynchronous event reports time information of the finished call or call attempt as well as release cause depending on which information has been requested by getCallInfoReq.
This method returns the conference address that specifies the address with which the conference can be addressed in case parties are allowed to join the conference.
This method is used to get a handle to the enterprise network interface, which holds information regarding network services that are already provisioned for the enterprise network in the provider network.
This asynchronous method requests information associated with the call leg to be provided at the appropriate time (for example, to calculate charging).
Deprecated.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.
Deprecated.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.
This method is used to get pipe QoS information consisting of load parameters, direction of the traffic, and the endpoint (SAP or site) of a virtual provisioned pipe offered by this template.
This method is used to get the list of SAP IDs of the enterprise VPN (i.e., on the provider network) that have previously been established for this site with the provider network.
This method is used to get the ID of the service level agreement (SLA) if such was associated with the virtual provisioned pipe at the provisioning of the VPrP.
The generic Call provides the possibility to control the call routing, to request information from the call, control the charging of the call, to release the call and to supervise the call.
This interface stores enterprise network information maintained by the provider as it relates to the virtual private network service and the virtual provisioned network service that the enterprise had already established with the service provider network.
The Multi-Party Call provides the possibility to control the call routing, to request information from the call, control the charging of the call, to release the call and to supervise the call.
The Call User Interaction Service Interface provides functions to send information to, or gather information from the user (or call party) to which a call leg is connected.
This interface is the 'service manager' interface for the Generic User Interaction Service and provides the management functions to the Generic User Interaction Service.
The virtual provisioned pipe interface provides information on a VPrP whose status can be in one of the following states: - Active: a previously established VPrP, which indicates that a previous request to create the VPrP was granted by the provider.
This event indicates to the application that event notifications and method invocations have been temporarily interrupted (for example, due to network resources unavailable).
This method is used to merge two subconferences, i.e., move all our legs from this subconference to the other subconference followed by a release of this subconference.
Deprecated.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.
This asynchronous event indicates that the request to route the call to the destination party was unsuccessful - the call could not be routed to the destination party (for example, the network was unable to route the call, the parameters were incorrect, the request was refused, etc.).
This asynchronous event indicates that the request to route the call leg to the destination party was unsuccessful - the call leg could not be routed to the destination party (for example, the network was unable to route the call leg, the parameters were incorrect, the request was refused, etc.).
This asynchronous event indicates that the request to route the call to the destination was successful, and indicates the response of the destination party (for example, the call was answered, not answered, refused due to busy, etc.).
This method is used to request pipe QoS parameters consisting of load parameters, direction of the traffic, and the endpoint (SAP or site) of the virtual provisioned pipe, as selected by the operator from the set of values offered by the provider.
Request for user location reports, containing mobile related information, when the location is changed (the report is triggered by the location change).
This terminal capability report is issued when the capabilities of the terminal have changed in the way specified by the criteria parameter in the previously invoked triggeredTerminalCapabilityStartReq () event.
Request for terminal capability reports when the capabilities change or when the application obviously does not have the current terminal capability information when this method is invoked.