...
Panel |
---|
...
borderColor | green |
---|---|
bgColor | transparent |
borderWidth | 2 |
...
In this section:
|
...
Info |
---|
...
0 | series |
---|
...
Related articles: |
Spacevars | |
---|---|
|
...
|
...
the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
After accepting the MSRP offer, the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
After accepting the MSRP answer from egress UA, the
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
MSRP UAs when making an offer can include a “setup” attribute as per RFC 4145, TCP based media transport in the SDP. MSRP UAs may also assume a default setup role and not include this attribute which basically means the UA that initiates the MSRP offer assumes a TCP client role.
The setup attribute as defined in the RFC 4145 may contain one of the three possible values “actpass”, “active” or “passive”. UAs that offer “actpass” are capable of being either a client or a server and expect the answering UA to select a specific role for the TCP connection. UAs that offer “active” or “passive” have already decided on their TCP role and expect the peer UA to take up the opposite role of what has been offered.
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
When the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Upon completion of the offer/answer, if the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
If the negotiated role of the
Spacevars | ||
---|---|---|
|
When the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The
Spacevars | ||
---|---|---|
|
TCP connections are normally terminated along with the SIP sessions. UAs may close TCP connections prior to terminating the SIP session. In those scenarios, if the SBC was the TCP server, it simply goes back to the listening state on the same TCP port that was used prior to the connection being closed. This allows the UAs to reconnect with the same transport information and there is no need for a SIP reINVITE. Similarly, if the SBC is the TCP client and if the connection is torn down by the server, the
Spacevars | ||
---|---|---|
|
...
Caption | ||||
---|---|---|---|---|
|
...
Each MSRP session leg consists of a policer (also referred to as a microflow) that is installed once the TCP connections are established. The microflow is defined as a rule that contains the following configuration:
Spacevars | ||
---|---|---|
|
All incoming MSRP packets are checked against the above configuration.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
If incoming MSRP TCP packets match an ipAccessControlList with action "discard", the packets are discarded even though the packets match up with 1 through 3. |
Both conforming and non-conforming packets are subjected to another level of policer known as the Link Aggregate Policer. The configuration (see configuration section for Reserving Interface Bandwidth) of this policer is derived from the amount of bandwidth reserved for MSRP. Any available bandwidth out of the reserved bandwidth is first used for the conforming packets before using it for non-conforming packets. So based on the amount of reserved bandwidth, all MSRP packets are subjected to a best effort policy to be admitted into the
Spacevars | ||
---|---|---|
|
Refer to IP Interface Group - CLI or Ip Interface Group - Ip Interface (EMA) for configuring a bandwidth contingency to reserve interface bandwidth for this scenario.
Pagebreak |
---|