AudioCodes Mediant 4000 SBC - HTTP-Based Proxy Services

CHAPTER16 Services
Mediant 4000 SBC | User's Manual
Contact: <sip:1000@10.7.2.15>
Supported: em,100rel,timer,replaces
Allow:
REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO
,SUBSCRIBE
User-Agent: Sip Message Generator V1.0.0.5
2. Outgoing HTTP GET:
Header=GET /v3/phone/15551234567?account_sid=SID&auth_token=TOKEN
HTTP/1.1
Content-Type: html/text
Host: 52.7.189.114
Connection: keep-alive
Content-Length: 0
Cache-Control: no-cache
User-Agent: 1
3. Incoming HTTP response:
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Cache-Control: max-age=0
Content-Type: text/html
Date: Thu, 07 Dec 2017 14:35:21 GMT
Server: nginx/1.8.1
Content-Length: 6
Connection: keep-alive
Alice
4. Outgoing SIP message:
INVITE sip:2000@10.7.7.246;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.7.7.246:5060;branch=z9hG4bKac1693897511
Max-Forwards: 70
From: Alice <sip:+15551234567@10.7.2.15;user=phone>;tag=1c1900944531
To: <sip:2000@10.7.7.246;user=phone>
Call-ID: 17651812441120101654@10.7.7.246
CSeq: 1 INVITE
Contact: <sip:1000@10.7.7.246:5060>
Supported: em,100rel,timer,replaces,sdp-anat
HTTP-based Proxy Services
The device can be configured as an HTTP Proxy (or a non-HTTP Proxy) to intermediate between
clients (e.g., HTTP requests) and servers (hosts). The client sends an HTTP GET request
specifying the destination (URL), and the device (acting as an HTTP Proxy), forwards it to the host,
and vice versa.
- 260 -