HTTP Contact

With this approach, a remote application first creates a subscription by issuing an HTTP(S) POST message to a specific URL.

The subscription sent by a remote application specifies the subscription target. This target is typically a subscriber hosted in BroadWorks.

The subscription also specifies an HTTP contact and an event package. The contact represents the HTTP callback, which is a location at which Xsi-Events can send back notifications. The event package corresponds to various types of notifications that are asynchronously sent by BroadWorks back to the subscribing client or application.

When successful, Xsi-Events respond to the HTTP POST with an HTTP 200 OK.

After sending this response, BroadWorks sends an event that allows the remote application to know the initial state of the target. Note that if the subscription target is a collection of subscriber (for example, a group), then no such event is sent.

Then at various points in the life of a subscription, Xsi-Events send events to the remote client application.

Notifications are HTTP(S) POST methods issued by BroadWorks on the contact URL identified in a subscription. A client application is expected to respond to this POST with a 200 OK.

***** Where are my events?

For a POST to be transmitted from our servers to yours, we have to add your IP Address/Domain Name to our ACL (access control list).

Both & (ect.) XSP servers must be allowed.

Request Help

Have more questions? Submit a request


Powered by Zendesk