AudioCodes Mediant 4000 SBC, User Manual

Page: 292 / 1037

CHAPTER 16 Services
Mediant 4000 SBC | User's Manual
c. Click Apply .
2. Open the Remote Web Services table (see Configuring Remote Web Services ), and then for
the Remote Web Service entry that you configured for the routing server, do the following:
a. From the 'Type' [HTTPRemoteServices_HTTPType] drop-down list, select QoS .
b. Click Apply .
3. Enable voice quality monitoring and RTCP XR, using the 'Enable RTCP XR' [VQMonEnable]
parameter (see
Configuring RTCP XR ).
Configuring an HTTP GET Web Service
You can query (HTTP GET) an HTTP server and use the response for various functionality such as
SIP message manipulations, tag-based classification and routing. To configure this, you need to
configure a Remote Web Service to represent the HTTP server and a Call Setup Rule to define the
search query and the action you want done based on the HTTP response. The following example
queries an HTTP server (at IP address 52.7.189.10) using the caller's (source) user name in the
server's path
/v3/phone . When a response is received from the HTTP server, the device adds the
value of the HTTP response body ("Alice") to the From header in the outgoing SIP message.
➢
To configure an HTTP GET operation:
1. Open the Remote Web Services table, and then configure a Remote Web Service for the
HTTP server:
● 'Name': MyHTTP
● 'Type': General
● 'Path': v3/phone
● 'Username': adminuser1
● 'Password': 1234
2. Open the HTTP Remote Hosts table of the Remote Web Service that you configured in Step 1,
and then configure the following:
● 'Name': MyHTTPHost
● 'Address': 52.7.189.10
3. Open the Call Setup Rules table, and then configure the following rule:
● 'Rule Set ID': 1
● 'Request Type': HTTP GET
● 'Request Target': MyHTTPHost
● 'Request Key': Param.Call.Src.User+'?account_sid=SID&auth_token=TOKEN'
● 'Action Subject': Param.Call.Src.Name
● 'Action Type': Modify
● 'Action Value': HTTP.Response.Body
4. Assign your Call Setup Rule to the relevant SIP Interface, for example.
An example of the HTTP and SIP messages of the above configuration is shown below:
1. Incoming SIP message:
INVITE sip:2000@10.7.7.246;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.7.2.15;branch=z9hG4bKLRGQTOQHILSSMGAQJQSU
From: <sip:
15551234567@10.7.2.15;user=phone>;tag=RJFNXMKDOHELDUMEWWGH
To: <sip:2000@10.7.7.246;user=phone>
Call-ID: UBBKFKBCXFPESMYOPDTB@10.7.2.15
CSeq: 1 INVITE
- 259 -