Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 17
- Page / 136
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
ServerIron ADX Advanced Server Load Balancing Guide 5
53-1002435-01
SIP Overview
1
SIP message headers
This section describes SIP message headers that you might find useful when making decisions
about SIP Server Load Balancing.
CALL-ID
The call-ID is a header field that appears in all SIP requests and responses. This header field acts
as a unique identifier to group together a series of messages. It must be the same for all requests
and responses sent by either UAC or UAS in a dialog.
Call-ID is generated by the combination of a random string and the host name or IP address of a
particular UAC. There is no length restriction on call-ID. in the first implementation, real server is
selected based on hash value of call ID (stateless mode) or value of call ID (stateful mode).
Record-Route
The Record-Route header field is inserted by a proxy in a request to force future requests in the
dialog to be routed through the proxy.For example, Record-Route: <sip: server10.Biloxi.com; 1r>
From
The From header field indicates the LOGICAL identity of the initiator of the request. It contains a URI
and, optionally, a display name. This field MUST contain a "tag" parameter, chosen by the UAC.
IP addresses of the host on which the UA is running should not be used as "from" URIs, as these are
not logical names.
For example,
From: "Alice" <sip: [email protected]> ; tag=a48s or From: "Alice" <sip: al[email protected]> ; tag=a48s
To
The To header field specifies the desired logical recipient of the request. This might not be the
ultimate recipient of the request. Normally, the initial To field is set to be the value of the
Request-URI. One exception is the REGISTER method.
To: Alice <sip: ali[email protected] > or To: Alice <sip: [email protected] >
Via
The Via header field indicates the path taken by the request so far and indicates the path that
should be followed in routing responses. A Via header field value contains the transport protocol
used to send the message, the client's host name or network address, and possibly the port
number at which it wishes to receive responses. It is a mandatory field for the UAC or UAS SIP
proxies, and guarantees that the responses traverse through the same route as the requests.
For example, Via: SIP/2.0/UDP erlang.bell-telephone.com:5060; branch=z9hGbK87asdks7
The branch ID parameter in the Via header field values serve as a transaction identifier, and is
used by proxies to detect loops.
- ServerIron ADX 1
- Document History 2
- Contents 5
- About This Document 9
- Command syntax conventions 10
- Notice to the reader 11
- Related publications 11
- Web access 12
- E-mail and telephone access 12
- SIP Server Load Balancing 13
- SIP terminology 16
- SIP message headers 17
- Max-Forwards 18
- Sample deployment topologies 19
- RINGING F4 21
- Configuring SIP SLB 23
- Configuring health check 26
- Example 29
- Load Balancing SIP over TCP 31
- Call-ID3 33
- Call-ID1 34
- Rehashing the SIP hash table 38
- Debug commands 40
- SIP SLB command reference 42
- Sample configuration 43
- Transparent Cache Switching 45
- Stateful caching 47
- Sample Deployment Topologies 48
- TCS with spoofing 49
- TCS with destination NAT 49
- TCS with Source NAT 50
- VIPs with reverse proxy 51
- Configuring TCS 52
- Defining a cache server 53
- Enabling TCS 56
- Other TCS options 57
- Cache Route Optimization 58
- Enabling Destination NAT 62
- Configuring Source NAT 62
- Examples 64
- Distribution algorithm 66
- • Maximum connection rate 72
- Enabling FastCache 73
- Enabling remote cache 73
- Shutting down a cache server 74
- Passive FTP for TCS 75
- Traffic flow of passive FTP 76
- Topologies supported 76
- High availability support 77
- ServerIron ADX 2 78
- Policy based caching 79
- Show commands 81
- Content aware cache switching 82
- Setting up the CSW policies 84
- Configuring the cache servers 85
- This field... Displays 91
- Displaying cache information 95
- TCS information (Continued) 96
- Sample configurations 98
- Applying IP policies 99
- Defining the caches 99
- Defining the cache groups 100
- 53-1002435-01 101
- Policy-based caching 102
- Asymmetric TCS (FastCache) 103
- Policy-based cache failover 105
- TCS with reverse proxy 107
- Layer 3 TCS 109
- Basic TCS configuration 110
- Commands for ServerIron ADX A 111
- Commands for ServerIron ADX B 112
- Internet 114
- 10.10.20.104 114
- 10.10.20.102 114
- Router NI1 117
- Router NI2 117
- OSPF Area 0 117
- Commands for Router NI2 121
- Active-standby TCS 125
- Configuring Router R1 126
- Configuring ServerIron ADX A 126
- Configuring ServerIron ADX B 127
- NetCache servers 128
- NetCache C720 cache server 128
- TABLE 9 Hashing methods 130
- Parsing the host string 133
- Force rehash 136
Related products and manuals for Network switches Brocade Communications Systems ServerIron ADX 12.4.00
(30 pages)© 2020, manymanuals.com. All rights reserved. | 0.740 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals