Page History
Add_workflow_for_techpubs
| Include Page | ||||
|---|---|---|---|---|
|
Transparency flags are provisioned on IP Signaling Profiles associated with egress SIP Trunk Groups, and indicate whether specific SIP headers are transparently copied from the ingress SIP message to the egress SIP message. Transparency flags include:
acceptContactHeader | acceptHeader | alertInformationHeader | authcodeHeaders |
callInfoHeader | contactHeader | errorInfo | fromHeader |
geolocation | geolocationError | geolocationRouting | historyInfo |
maxForwardsHeader | mwiBody | pAccessNetworkInfoHeader | pCalledPartyID |
pChargingVectorHeader | pEarlyMedia | pVisitedNetworkIDHeader | passCompleteContactHeader |
pathHeader | qsigBody | reasonHeader | referredByHeader |
requestURI | routeHeader | serviceRouteHeader | sipBody |
sipfragBody | toHeader | toneBody | unknownBody |
unknownHeader | userToUserHeader | viaHeader |
|
To enable a transparency flag, use the following CLI syntax:
| Code Block |
|---|
% set profiles signaling ipSignalingProfile DEFAULT_SIP commonIpAttributes transparencyFlags <transparencyFlag_name> enable |
| Include Page | ||||
|---|---|---|---|---|
|
For configuration details, see:
- CLI: Common IP Attributes - SIP - CLI
- EMA: Common Ip Attributes - Transparency Flags, Common Ip Attributes - Transparency Flags - Profile Management
| Pagebreak |
|---|
Overview
Content Tools