SIP Stack (sipStack)
Configuration for the SIP stack
Attribute name | Data type | Default value | Description |
---|---|---|---|
acceptNonUtf8Bytes | boolean | false | Accept byte sequences that are not encoded in UTF-8. |
auto100OnInvite | boolean | true | The SIP container automatically sends a 100 response code when an INVITE request is received. |
auto482OnMergedRequests | boolean | false | The SIP container automatically sends a 482 response code when a merged request is received. This behavior is defined in the SIP RFC 3261 Section 8.2.2.2. |
compactHeaders |
|
MtuExceeds | Defines when the SIP stack uses compact headers when encoding a message.
|
forceConnectionReuse | boolean | true | Connections are reused in subsequent requests even if the alias parameter exists in the via header. |
hideMessageBody | boolean | false | Hide message content in the SIP container logs. |
hideMessageReqUri | boolean | false | Hide the message request URI in the SIP container logs. |
networkAddressCacheTtl | string | The amount of time that the SIP container keeps a cached InetAddress entry and does not resolve it again. | |
pathMtu | int | 1500 | The maximum transmission unit (MTU) for outbound UDP requests, as defined in RFC 3261-18.1.1. |
timerA | A period of time with millisecond precision | 500ms | The initial INVITE request retransmit interval for UDP only, in milliseconds, as defined in RFC 3261. The default value equals T1. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerB | A period of time with millisecond precision | 32000ms | The INVITE client transaction timeout timer, in milliseconds, as defined in RFC 3261. The default value equals 64*T1. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerD | A period of time with millisecond precision | 32000ms | The wait time for INVITE response retransmits, in milliseconds, as defined in RFC 3261. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerE | A period of time with millisecond precision | 500ms | The initial non-INVITE request retransmit interval for UDP only, in milliseconds, as defined in RFC 3261. The default value equals T1. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerF | A period of time with millisecond precision | 32000ms | The non-INVITE transaction timeout timer, in milliseconds, as defined in RFC 3261. The default value equals 64*T1. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerG | A period of time with millisecond precision | 500ms | The initial INVITE response retransmit interval, in milliseconds, as defined in RFC 3261. The default value equals T1. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerH | A period of time with millisecond precision | 32000ms | The wait time for ACK receipts, in milliseconds, as defined in RFC 3261. The default value equals 64*T1. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerI | A period of time with millisecond precision | 5000ms | The wait time for ACK retransmits, in milliseconds, as defined in RFC 3261. The default value equals T4. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerJ | A period of time with millisecond precision | 32000ms | The wait time for non-INVITE request retransmits, in milliseconds, as defined in RFC 3261. The default value equals 64*T1. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerK | A period of time with millisecond precision | 5000ms | The wait time for non-INVITE response retransmits, in milliseconds, as defined in RFC 3261. The default value equals T4. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerT1 | A period of time with millisecond precision | 500ms | The round-trip time (RTT) estimate, in milliseconds, as defined in RFC 3261. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerT2 | A period of time with millisecond precision | 4000ms | The maximum retransmit interval, in milliseconds, for non-INVITE requests and INVITE responses, as defined in RFC 3261. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
timerT4 | A period of time with millisecond precision | 5000ms | The maximum duration that a message remains in the network in milliseconds, as defined in RFC 3261. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), seconds (s), or milliseconds (ms). For example, specify 500 milliseconds as 500ms. You can include multiple values in a single entry. For example, 1s500ms is equivalent to 1.5 seconds. |
- commaSeparatedHeaders
Description: A list of header fields that should be comma-separated. If there are multiple values of the same header, the headers are not duplicated and the value will be in the same header separated by a comma.Required: falseData type: string