Parameter | Description |
|---|
acceptContactHeader | Set flag to allow P-CSCF to transparently pass the received Accept-Contact Header. |
acceptHeader | Use this flag to determine Accept header behavior.disable (default) – Accept header includes: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed information.enable – Accept header is transparently passed from ingress to egress.
|
acceptLanguageHeader | Enable to allow Accept-Language Header transparency.
|
alertInformationHeader | Set this flag to transparently copy the ALERT INFO header from the ingress SIP INVITE method to the egress SIP INVITE message. |
authcodeHeaders | Enable this flag to transparently copy the WWW Authentication header for SIP 401/407 response messages or SIP Authorization/Proxy Authorization headers.| Note |
|---|
| You must enable statusCode4xx6xx relay flag when using authcodeHeaders transparency. |
|
callInfoHeader | Set flag to transparently pass Call-Info header, if present, in the incoming message. |
contactHeader | Set flag to transparently pass the Contact Header Flag in egress leg with respect to the message direction. |
errorInfo | Enable this flag to transparently copy the Error-Info header from the ingress leg to the egress leg. |
externalBody | Enable to send message/external-body transparently.
|
fromHeader | Enable this flag to transparently copy the userinfo@host component of the FROM header from the ingress SIP INVITE message to the egress SIP INVITE message.| Note |
|---|
| Even when this flag is enabled, the IP port information is not included unless the "Include IP Ports in From and To Headers" flag, elsewhere in this IP Signaling Profile, is also enabled |
|
geolocation | Set flag to transparently pass Geolocation header, if present, in incoming message. |
geolocationError | Set flag to transparently pass Geolocation-Error header, if present, in incoming message. |
geolocationRouting | Set flag to transparently pass Geolocation-Routing header, if present, in incoming message. |
historyInfo | Controls History-info header transparency in SIP INVITE messages. When enabled, the passes the History-Info header transparently from the ingress message to the egress message. When disabled, the SBC does not copy the history-info. Provision this flag on the egress leg with respect to the message direction. |
maxForwardsHeader | Enable this flag to decrement the value in Max-Forwards header by 1 for requests traversing through the SBC. By default (disable), the SBC populates the Max-Forwards header with the value configured in maxFwdsDefault (default value is 70).
|
messageExternalBody | Enable flag to pass Message External Body transparently.
|
mwiBody | Enable flag to transparently copy the MWI body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision this flag on the egress leg with respect to message direction. |
pAccessNetworkInfoHeader | Enable flag to transparently pass the p-Access-Network-Info (PANI) header from ingress to egress.disable (default) – suppresses the PANI header towards egress messages when the incoming message contains PANI header.enable –
transparently passes PANI header from ingress to egress.
| Note |
|---|
| Enable this flag when is configured as P-CSCF node. |
|
pCalledPartyID
| Set flag to transparently pass the P-Called-Party-ID header from ingress to egress call leg. |
pChargingVectorHeader | When enabled, the transparently copies the P-Charging-Vector header from the ingress message to the egress message. When disabled, the does not copy the header. PCharging- Vector header transparency is supported in INVITE, REGISTER, SUBSCRIBE, OPTIONS, MESSAGE, PUBLISH, NOTIFY, REFER, and INFO messages. |
pEarlyMedia | Controls P-Early Media header transparency in INVITE or non-100 RESPONSE requests and their responses if they are relayed. When enabled, the SBC transparently copies the P-Early Media header from the incoming message to the outgoing message. When disabled, the PEarly- Media header is not copied to the egress leg. Provision this flag on egress leg with respect to message direction. |
pidfBody | Enable to send application/pidf+xml body transparently.
|
pidfDiffBody | Enable to send application/pidf-diff+xml body transparently.
|
pVisitedNetworkIDHeader | Enable flag to pass the P-Visited-Network-ID header transparently to the egress leg. |
passCompleteContactHeader | Enable flag at egress IPSP (with respect to message direction) to copy the Contact header and its parameters from the ingress message and insert in the egress message.
|
pathHeader | Enable flag to transparently copy the Path header from the ingress SIP message to the egress SIP message. |
qsigBody | Enable flag to transparently copy the QSIG body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision this flag on the egress leg with respect to message direction. |
reasonHeader | When enabled, the ingress Reason header value is passed through unchanged. |
referredByHeader | When enabled, transparently copies the Referred-By Header (in INVITE requests/responses) from the incoming message to the outgoing message. When cleared, the Referred-By Header is not copied. Provision this flag on the egress leg (with respect to the message direction). |
requestURI | Enable flag to transparently copy the Request URI from the incoming message to the outgoing message for INVITE, REGISTER, SUBSCRIBE/NOTIFY. Provision this flag on the egress leg (with respect to the message direction). |
resourceListBody | Enable to send application/resource-lists+xml body transparently.
|
resourcePriorityOptionTag | Enable to transparently pass 'resource-priority' option tag received in Require or Supported header of SIP messages.
|
rlmiBody | Enable to send application/rlmi+xml transparently.
|
routeHeader | Enable flag to transparently copy the Route header from the ingress SIP message to the egress SIP message. |
serverHeader | Enable to allow Server Header transparency.
|
serviceRouteHeader | Enable flag to transparently copy the Service-Route header from the ingress SIP message to the egress SIP message. |
simpleFilterBody | Enable to send application/simple-filter+xml content-type transparently.
|
sipBody | Enable flag to transparently copy the SIP body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE, if relayed. Provision this flag on the egress leg with respect to the message direction. |
sipfragBody | Enable flag to transparently copy the SIPFRAG body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction. |
toHeader | Enable flag to transparently copy the userinfo@host component of the TO header from the ingress SIP INVITE message to the egress SIP INVITE message. When flag is disabled, SBC generates its own TO header. | Note |
|---|
| Even when this flag is enabled, the IP port information is not included unless the "Include IP Ports in From and To Headers" flag, elsewhere in this IP Signaling Profile, is also enabled. |
|
toneBody | Enable flag to transparently copy the Tone body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction. |
unknownBody | Enable flag to transparently copy the Unknown body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction. |
unknownHeader | Enable flag to transparently copy the Unknown header from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction. |
userAgentHeader | Enable to allow User-Agent header transparency.
|
userToUserHeader | When the ingress INVITE contains the User-to-User header and this transparency flag is enabled, the User-to-User header passes through to the egress. |
viaHeader | Use this flag to specify the behavior of VIA header, the source address of the call originator.disable – (default) Default behavior where IP address on the VIA header is the local SIP signaling address.enable – Transparently pass all the VIA headers received in original INVITE or REGISTER. With only the transparency flag enabled, the SBC will still include the local SIP signaling address and port as the top most VIA header.
|
warningHeader | Enable to allow Warning Header transparency. |
watcherInfoBody | Enable to send application/watcherinfo+xml transparently. |