Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sipInteropReplacesConfig",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"doNotUseReplaces",
"(",
"0",
")",
",",
"useReplacesWithRequire",
"(",
"1",
")",
",",
"useReplacesNoRequire",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Configures usage of the Replaces header mechanism used in a transfer. When supported by the target of the transfer, Replaces ensures a more seamless transfer by permitting the initiating party to effectively replace a current call by another instead of disconnecting the call to be replaced and creating a second call. doNotUseReplaces : The Replaces header is not used. useReplacesWithRequire : The Replaces header is used. It can be seen in the Refer-To header found in the REFER request sent by the transferor. It can also be seen in the INVITE sent by the transferee. The target that supports Replaces will use its information to merge the new INVITE with an existing call specified in the Replaces header. The transferee will require the use of the replaces extension for proper completion of the transfer. If the replaces extension is not supported by the target of the transfer, the unit will go into a fallback algorithm to retry the transfer using replaces, by reversing the roles of the target and the transferee (by resending the REFER to the initial target instead of the initial transferee). As a last resort (if none of the participants supports replaces), the transfer will be carried out without using the replaces extension. useReplacesNoRequire : The Replaces header is used. It can be seen in the Refer-To header found in the REFER request sent by the transferor. It can also be seen in the INVITE sent by the transferee. The target that supports Replaces will use its information to merge the new INVITE with an existing call specified in the Replaces header. This will disable the transfer fallback. The replaces information will still be present, but no check will be made that it is effectively used to complete the transfer.\"",
"DEFVAL",
"{",
"useReplacesWithRequire",
"}",
"::=",
"{",
"sipInteropMIBObjects",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"doNotUseReplaces",
0
],
[
"useReplacesWithRequire",
1
],
[
"useReplacesNoRequire",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Configures usage of the Replaces header mechanism used in a transfer. When supported by the target of the transfer, Replaces ensures a more seamless transfer by permitting the initiating party to effectively replace a current call by another instead of disconnecting the call to be replaced and creating a second call. doNotUseReplaces : The Replaces header is not used. useReplacesWithRequire : The Replaces header is used. It can be seen in the Refer-To header found in the REFER request sent by the transferor. It can also be seen in the INVITE sent by the transferee. The target that supports Replaces will use its information to merge the new INVITE with an existing call specified in the Replaces header. The transferee will require the use of the replaces extension for proper completion of the transfer. If the replaces extension is not supported by the target of the transfer, the unit will go into a fallback algorithm to retry the transfer using replaces, by reversing the roles of the target and the transferee (by resending the REFER to the initial target instead of the initial transferee). As a last resort (if none of the participants supports replaces), the transfer will be carried out without using the replaces extension. useReplacesNoRequire : The Replaces header is used. It can be seen in the Refer-To header found in the REFER request sent by the transferor. It can also be seen in the INVITE sent by the transferee. The target that supports Replaces will use its information to merge the new INVITE with an existing call specified in the Replaces header. This will disable the transfer fallback. The replaces information will still be present, but no check will be made that it is effectively used to complete the transfer."
],
null,
null,
null,
[
"DEFVAL",
"useReplacesWithRequire"
]
]
}