Mode
Wireless mode or Cable mode with the SMS:SMPP or SMS:XML function enabled.
Syntax
send http http_method notification to server with headers headers and content content
Parameters
- http_method
- String. The HTTP method for the request message. Supported methods are:
- POST — (default) a method for sending data for processing by the application specified by URL
- GET — a method for requesting the retrieval of data located at the specified URL
- PUT — a method for requesting the storage of the data at the specified URL
- DELETE — a method for deleting the data located at the specified URL
- server
- A list of the defined notification servers. Select the notification server from the list. See Managing Notification Servers for information about adding a notification server.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
- headers
- String. One or more HTTP message headers (up to a maximum of 20 headers) using the format: field-name:field-value. For example, Content-Type:text/xml, Content-Type:application/json, and Content-Type:text/plain. See the HTTP standard at http://www.ietf.org for details on valid message header fields and values. This field cannot be empty.
Note: MPE does not validate whether the field-value corresponds to the field-name.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
- content
- String. The message body content that supports any type of notification like JSON/XML/Text message. The content can use policy variable substitution and can contain up to 4000 characters.
Note: MPE does not validate whether the message headers correspond to particular content.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
Description
Enables PCRF to send a configurable HTTP request message using the Web services interface. These notification messages are sent to pre-configured destinations. After a notification message is sent, PCRF receives the response from the specified URL. In the event of a failure, PCRF does not attempt to re-send the message.
Examples
XML POST
send http POST notification to NS1 with headers
Content-Type:text/xml;charset=UTF-8 and content <?xml version="1.0" encoding="UTF-8"?> <subscriber> <msisdn>{User.MSISDN}</msisdn> <quota>{User.Quota.Foo.Volume}</quota> </subscriber>
JSON POST
send http POST notification to NS2 with
headers Content-Type: application/json and content
{"class":"Subscriber","entitlement":"Extended Service`,`msisdn`:`{User.MSISDN}`,`name`:`{User.name}`}`
HTTP GET with query parameters
send http GET notification to
NS3 with headers Content-Type:text/plain and content ``