AudioCodes Mediant 4000 SBC User Manual page 549

Session border controllers
Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

CHAPTER 22    SBC Overview
2.
When the user wants to register with the device or make a call, the client application (e.g., Web
browser for the WebRTC application) through which the user communicates with the device,
sends a SIP REGISTER or INVITE request that includes the user's Access Token in the SIP
Authorization header ("Bearer" value), as shown in the following REGISTER message
example:
REGISTER sip:server.com SIP/2.0
Via: SIP/2.0/WSS 9rihbeck4vat.invalid;branch=z9hG4bK2426139
Max-Forwards: 69
To: <sip:alice@example.com>
From: "alice" <sip:alice@example.com>;tag=mstg4hpof6
Call-ID: 0il6hahess4ndc1pdlleqj
CSeq: 1 REGISTER
Authorization: Bearer
eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJUdDl1TF9Ya0hSampFR2N
UZFRlYXZ0dmxTc0pXYWplRHhIR1MzLXlVazhZIn0.eyJqdGkiOiIwOTgzOGNhZi1m
YTg0LTRjNzQtODkyMi1kNDQzNzI3ZjYzNTYiLCJleHAiOjE1MzI1MTI1NTAsIm5iZiI
6MCwiaWF0IjoxNTMyNTExOTUwLCJpc3MiOiJodHRwczovL3dlYnJ0Y29hdXRoLm
F1ZGlvY29kZXMuY29tL2F1dGgvcmVhbG1zL2RlbW8iLCJhdWQiOiJXZWJSVENEZ
W1vIiwic3ViIjoiMjQxZjlkNWEtMzhhNC00Y2Q1LTlhOWItYzBhYjIxNzJkZDZiIiwidHl
wIjoiQmVhcmVyIiwiYXpwIjoiV2ViUlRDRGVtbyIsIm5vbmNlIjoiMDEyMjg4ZmQtMzA
yNy00OWU3LTgyZGEtYTIxMGE1MzZkNmUyIiwiYXV0aF90aW1lIjoxNTMyNTExOT
Q5LCJzZXNzaW9uX3N0YXRlIjoiNTY1MjBkZjItMzUyMy00NjNhLWExY2ItMTgzMz
A5YzlhNzBjIiwiYWNyIjoiMSIsImFsbG93ZWQtb3JpZ2lucyI6WyIqIl0sInJlYWxtX2FjY
2VzcyI6eyJyb2xlcyI6WyJ1bWFfYXV0aG9yaXphdGlvbiJdfSwicmVzb3VyY2VfYWNj
ZXNzIjp7ImFjY291bnQiOnsicm9sZXMiOlsibWFuYWdlLWFjY291bnQiLCJtYW5hZ2U
tYWNjb3VudC1saW5rcyIsInZpZXctcHJvZmlsZSJdfX0sIm5hbWUiOiJIYWlmYTEgV
XNlcjEiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJoYWlmYXVzZXIxIiwiZ2l2ZW5fbm
FtZSI6IkhhaWZhMSIsImZhbWlseV9uYW1lIjoiVXNlcjEiLCJlbWFpbCI6ImhhaWZhdX
NlcjFAZXhhbXBsZS5jb20ifQ.aDoFsyt-KGN3kHkT7IZvHya0kf03xrfFzOBGgz_
X2w5mrRmLI18iRF0HqanWH3MJXJh0le3CRRN5O1F_Jx_
YxMH7Ue8864xP9CIN5X4g9eeQKuZxeppvBtf1BPjaKX6KQIbTN2IRPTj21hzUNvJO
6zWMIAiOWKQlHEBtk4upgsIBhkWs0fTLxpgFPlL0gx2pciN1yE9x_
SprisCxFhpatxYpBKejZqw12TYeyuInTWCtYaBu2tLdEIowLM7kEuwJsF5enN5a9Xgv
PfltYufoEn9bKriezYLcQoUlvDZ4Oq7bK5C4aWkTUu6eMgkqIC50fCb3oyiYzLbbMmZ
06JA
Contact: <sip:lnumvv6i@9rihbeck4vat.invalid;transport=ws>;+sip.ice;reg-
id=1;+sip.instance="<urn:uuid:1007ed30-98a3-492e-966f
67b6f6eb99c5>";expires=600
Expires: 600
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER,INFO
Supported: path,gruu,outbound
User-Agent: Example WebRTC phone
Content-Length: 0
3.
The device authenticates the SIP request, by sending (HTTP POST) an HTTP Introspection
request with the user's Access Token to the OAuth Authorization server, as shown in the
following example:
POST /auth/realms/demo/protocol/openid-connect/token/introspect HTTP/1.1
Host: authorizationhost.com
Content-Type: application/x-www-form-urlencoded
- 516 -
Mediant 4000 SBC | User's Manual

Advertisement

Table of Contents
loading

Table of Contents