Caption |
---|
0 | Table |
---|
1 | sipHeadersAndParameters Parameters |
---|
3 | sipHeadersAndParameters |
---|
| | Parameter | Description |
---|
callForwarding | This parameter is used to control the call forwarding data mapping method in egress SIP signaling. dataMapping – Use this parameter to define how to map the diversion or redirecting data. Options are:none – No Diversion information is egressed.
diversion – Diversion information is sent out as SIP Diversion Header.
pkHeaders – Diversion information is sent out as proprietary PK Headers.
diversionHeaderTransparency – When enabled, the ingress Diversion header is passed through unchanged. Call forwarding data mapping transparency applies to Diversion header onlydiversionHistoryInfoInterworking – Enable flag to allow interworking between Diversion and History-Info header as per RFC 6044. The supports up to 12 History-Info entries and 10 Diversion entries. When this flag is disabled, only the first and last entries are maintained when History-Info or diversion transparency is disabled.
|
|
Note |
---|
diversionHistoryInfoInterworking - NOTE: This flag is only visible when either Diversion or History-Info header is selected as the egress call forwarding header. Diversion and History-Info Transparency configuration controls are ignored when it is enabled. This parameter has precedence over the others.
historyInformation includeHistoryInformation – Use this parameter to specify how to treat call forwarding history information. Enable this flag to include History-Info in INVITE egress message.
disable (default)enable
causeParameterInRFC4458 – Enable this flag to include the History-Info cause value in egress message as per RFC 4458 recommendation. When the flag is enabled, the output is similar to the following example:
History-Info: < sip:1234567890@P1.interwork.com?Privacy=none>;index=1, <sip: last_diverting_target;cause=408>;index=1.1
reasonWithCauseValueAsPerRFC4244 – Enable this flag to include History-Info cause value with Reason Header as per RFC 4244 recommendation. When the flag is enabled, the output is similar to the following example:
History-Info: <sip:1234567890@P1.interwork.com?Privacy=none>;index=1, <sip: last_diverting_target?Reason=SIP%3Bcause%3D408>;index=1.1
| destinationTrunkGroupOptions | Use this parameter to specify destination trunk group options. includeDtg – Include the destination trunk group parameter in SIP headers sent over associated trunk group.includeNone (default) – Do not include any trunk group information.includeTgrpWithDomainName – Include trunk group with domain name.includeTgrpWithIpAddress – Include the destination trunk group, and include the trunk context as domain name.
| flags | Use this object to configure the SIP Headers and Parameters flags. endToEndAck – Enable flag to send the ACK towards egress for the initial invite after receiving it from the ingress (remote) entity. The application retransmits the 200 OK towards the ingress side based on the configuration, and terminates the call if no ACK is received for the corresponding 200 OK.includeCic – If enabled, the includes the Carrier Identification Code in a cic= parameter in outgoing INVITE messages.
|
|
enable includeCpcInformation – If enabled, the includes the Calling Party Category (CPC) parameter value in the From header of outgoing SIP INVITE messages.The CPC parameter characterizes the station used to originate a call, such as ordinary, priority, data, test, operator, pay phone, prison, hotel or unknown.
includeNpi – If enabled, the includes the Numbering Plan Indicator in a npi= parameter in outgoing INVITE messages.includeOlip – If enabled, the includes the Originating Line Information Parameter in a oli= parameter in outgoing INVITE messages.includePKAdn – When enabled, the includes the P-K-Adn header in egress SIP messages. When disabled, the does not include the P-K-Adn header. The P-K-Adn header is a customer-specific SIP header used for ISUP-to-SIP interworking and contains the Translation Source Number (TSN) used in Number to SIP URL translation via the Number Username Translation screen (Generic variant only).includePstnParameters – If enabled, the includes a set of specific PSTN parameters in a pstn-params= entry in outgoing INVITE messages. The PSTN parameters currently included in pstn-params are Screening Indicator, ISDN Indicator, and Transmission Medium Requirement (TMR).includeQvalue – If enabled, the ERE SIP proxy/redirector includes the qvalue parameter (for example, q=0.9) in the Contact header of outgoing 3xx messages.skipCSeqCheckInEarlyDialog – When enabled, the accepts multiple SIP requests in which the CSeq number in a later request is of a lesser value than the CSeq number received in earlier requests.transparencyForDestinationTrunkGroupParameter – When enabled, if ERE receives both tgrp parameter and trunk-context in an ingress INVITE Request-URI, ERE as proxy transparently passes the tgrp parameter and trunk-context in the egress INVITE Request-URI. Values selected for the "Destination Trunk Group Option" are ignored.
| generateCallIdUsing | Use this parameter to control ingress and egress Call-ID behavior. doNotUseIngressCallId – Generates egress Call-ID independent of ingress Call-ID.useIngressCallIdByAddingStaticString – Generates egress Call-ID using ingress Call-ID and a static string (egressCallIdStaticString ) configured in the SIP trunk group. Egress Call-ID is the aggregate of ingress Call-ID and static string.useIngressCallIdByPrepending – Generates egress Call-ID using ingress Call-ID and locally generated string. Egress Call-ID is the aggregate of ingress Call-ID and locally generated string.
| includeChargeInformation | Select the includePChargeInfo option to map charge information in a call setup message (i.e., the charge number parameter of an IAM) to egress P-Charge-Info header in INVITE message. If the ERE returns billing information in a policy response, the ensures that the egress P-Charge-Info header in INVITE message is populated with the indicated data. If the receives a SIP INVITE message for a call destined to the PSTN, the populates the charge number parameter of the outgoing IAM based on the egress P-Charge-Info header in INVITE message.includeNone (default)includePChargeInfo
| originatingTrunkGroupOptions | Use this parameter to specify originating trunk group options. includeNone (default) – Do not include any trunk group information.includeOtg – Include the originating trunk group parameter in SIP headers sent over the associated trunk group.includeTgrpWithDomainName – Include the originating trunk group, and include the trunk context as domain name.includeTgrpWithIpAddress – Include the originating trunk group, and include the trunk context as IP address
| sessionExpiresRefresher | Controls whether the refresher parameter is sent in the Session-Expires header and is enabled when the Customized Session Timer Behavior flag is selected. Options include: - notSend (default) – The Session-Expires refresher parameter is not sent in the initial outgoing INVITE message, re-INVITE message, and UPDATE message.
Uac – When selected, the parameter refresher uac (User-Agent Client) is sent in the Session-Expires header.- Uas – When selected, the parameter refresher uas (User-Agent Server) is sent in the Session-Expires header.
| sipToHeaderMapping
| This parameter indicates which number is mapped and returned in the outgoing SIP To header. Options include: calledNumber – The TO header is mapped using the called number.gapDialedNumber – The TO header is mapped using the Generic Address Parameter from mime, if applicable.none (default) – The TO header user part is mapped from the Original Called Number, if present. Otherwise, it is mapped from the Called Number. The Original Called Number may be taken from the Diversion or the History-Info header, if present, in a SIP Invite.originalCalledNumberOcn – The TO header is mapped using the redirecting original Called number OCN parameter. This is filled from the SIP Invite using the Diversion or the History-Info header, if present.
|
|
|