Panel |
---|
...
borderColor | green |
---|---|
bgColor | transparent |
borderWidth | 2 |
Noprint |
---|
In this section:
|
Info | ||
---|---|---|
| ||
Related articles |
...
:
|
...
style | h6 |
---|
Panel | ||||
---|---|---|---|---|
In this section:
|
This section provides details regarding various SIP headers supported by the
...
Spacevars | ||
---|---|---|
|
...
...
|
Include Page | ||||
---|---|---|---|---|
|
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The IP Signaling Profile flag "diversionHistoryInfoInterworking
" indicates to the egress side that the interworking is accomplished as per the RFC 6044. In addition, the existing Redirecting Info flag of Diversion and History-Info headers identifies the target interworking header to send out in egress INVITE message. The Diversion and History-Info headers received on the ingress side are transparently passed to the egress where
...
transparency profile configuration determine the corresponding header to use to pass on this information in outgoing INVITE.
This feature is supported across GW-GW with the
Spacevars | |
---|---|
|
...
|
The
Spacevars | ||
---|---|---|
|
Use following CLI syntax to configure an X-header Profile:
Code Block | ||
---|---|---|
| ||
% set profile signaling XHeaderProfile <XHeaderProfileName> X-HeaderExtensions <extension_type> RecvHeader <disable|enable> SendHeader <disable | enable>
% set profile signaling XHeaderProfile <XHeaderProfileName> X-Header-default-value
% set profile signaling XHeaderProfile <XHeaderProfileName> X-HeaderFlags |
Use the following CLI syntax to attach configured X-header and ISUP profile to trunk group:
Code Block |
---|
% set addressContext <addressCcontext_name> zone <zone_name> sipTrunkGroup <sipTrunkGroup_name> signaling X-Headers HeaderFlag <none | xHeaders> |
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
...
Refer to Common IP Attributes - SIP - CLI or
...
Signaling - Ip Signaling Profile - Common Ip Attributes (EMA) for configuration details.
For information on the 3GPP header support,
...
refer to P-Headers page.
In order to interoperate with Broadsoft, the
Spacevars | ||
---|---|---|
|
The SBC supports a header tag length of up to 256 characters.
P-DCS-LEAS header support is defined in RFC 3603 for PacketCable 2.0 Electronic Surveillance. The P-DCS-LAES extension contains the information needed to support Lawfully Authorized Electronic Surveillance. This header contains the address and port of an Electronic Surveillance Delivery Function for delivery of a duplicate stream of event messages related to a call. This header is only used between proxies and trusted User Agents. An example of this header is:
P-DCS-LAES: 10.252.139.180:1813; content=10.252.139.180:45006;
bcid=D0E4965A2020202020373035302D30353030303000423403; cccid=015E8061
If
Spacevars | ||
---|---|---|
|
Pagebreak |
---|