Manuais
Documentação do Asterisk 22
Documentação do Asterisk 21
Documentação do Asterisk 20
Documentação do Asterisk 18
Documentação do Asterisk 17
Documentação do Asterisk 16
Documentação do Asterisk 15
Documentação do Asterisk 14
Documentação do Asterisk 13
Documentação do Asterisk 12
Documentação do Asterisk 11
Configuração de Módulos do Asterisk 20
Comando:
res_stir_shaken: STIR/SHAKEN module for Asterisk
Sinopse:
Since: 18.22.0, 20.7.0, 21.2.0 Must be a valid http, or https, URL. Since: 20.12.0, 21.7.0, 22.2.0 Normally if a callerid TN isn't configure
Descrição:
Since: 18.22.0, 20.7.0, 21.2.0 Must be a valid http, or https, URL. Since: 20.12.0, 21.7.0, 22.2.0 Normally if a callerid TN isn't configured in stir_shaken.conf no Identity header will be created. If this option is set, however, an Identity header will be sent using this attestation level. Since there's no TN object, you must ensure that a private_key_file and public_cert_url are configured in the attestation or profile objects for this to work. 18.22.0, 20.7.0, 21.2.0 Since: 18.22.0, 20.7.0, 21.2.0 Must be a valid http, or https, URL. 18.22.0, 20.7.0, 21.2.0 Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual CRLs must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 continue - If set to 'continue', continue and let the dialplan decide what action to take. reject_request - If set to 'reject_request', reject the incoming request with response codes defined in RFC8224. continue_return_reason - If set to 'return_reason', continue to the dialplan but add a 'Reason' header to the sender in the next provisional response. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. 18.22.0, 20.7.0, 21.2.0 Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual CRLs must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 off - Don't do any STIR/SHAKEN processing. attest - Attest on outgoing calls. verify - Verify incoming calls. on - Attest outgoing calls and verify incoming calls. Since: 18.22.0, 20.7.0, 21.2.0 continue - If set to 'continue', continue and let the dialplan decide what action to take. reject_request - If set to 'reject_request', reject the incoming request with response codes defined in RFC8224. continue_return_reason - If set to 'return_reason', continue to the dialplan but add a 'Reason' header to the sender in the next provisional response. Since: 18.22.0, 20.7.0, 21.2.0 Must be a valid http, or https, URL. Since: 20.12.0, 21.7.0, 22.2.0 Normally if a callerid TN isn't configured in stir_shaken.conf no Identity header will be created. If this option is set, however, an Identity header will be sent using this attestation level. Since there's no TN object, you must ensure that a private_key_file and public_cert_url are configured in the attestation or profile objects for this to work. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. This documentation was generated from Asterisk branch 20 using version GIT
Since: 18.22.0, 20.7.0, 21.2.0 Must be a valid http, or https, URL. Since: 20.12.0, 21.7.0, 22.2.0 Normally if a callerid TN isn't configured in stir_shaken.conf no Identity header will be created. If this option is set, however, an Identity header will be sent using this attestation level. Since there's no TN object, you must ensure that a private_key_file and public_cert_url are configured in the attestation or profile objects for this to work. 18.22.0, 20.7.0, 21.2.0 Since: 18.22.0, 20.7.0, 21.2.0 Must be a valid http, or https, URL. 18.22.0, 20.7.0, 21.2.0 Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual CRLs must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 continue - If set to 'continue', continue and let the dialplan decide what action to take. reject_request - If set to 'reject_request', reject the incoming request with response codes defined in RFC8224. continue_return_reason - If set to 'return_reason', continue to the dialplan but add a 'Reason' header to the sender in the next provisional response. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. 18.22.0, 20.7.0, 21.2.0 Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 These certs are used to verify the chain of trust for the certificate retrieved from the X5U Identity header parameter. This file must have the root CA certificate, the certificate of the issuer of the X5U certificate, and any intermediate certificates between them. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual CRLs must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 off - Don't do any STIR/SHAKEN processing. attest - Attest on outgoing calls. verify - Verify incoming calls. on - Attest outgoing calls and verify incoming calls. Since: 18.22.0, 20.7.0, 21.2.0 continue - If set to 'continue', continue and let the dialplan decide what action to take. reject_request - If set to 'reject_request', reject the incoming request with response codes defined in RFC8224. continue_return_reason - If set to 'return_reason', continue to the dialplan but add a 'Reason' header to the sender in the next provisional response. Since: 18.22.0, 20.7.0, 21.2.0 Must be a valid http, or https, URL. Since: 20.12.0, 21.7.0, 22.2.0 Normally if a callerid TN isn't configured in stir_shaken.conf no Identity header will be created. If this option is set, however, an Identity header will be sent using this attestation level. Since there's no TN object, you must ensure that a private_key_file and public_cert_url are configured in the attestation or profile objects for this to work. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. Since: 18.22.0, 20.7.0, 21.2.0 If you with to check if the certificate in the X5U Identity header parameter has been revoked, you'll need the certificate revocation list generated by the issuer. Unfortunately, sometimes the CRLs are signed by a different CA than the certificate being verified. In this case, you may need to provide the untrusted certificate to verify the CRL. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. For this option, the individual certificates must be placed in the directory specified and hashed using the 'openssl rehash' comando. See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information. This documentation was generated from Asterisk branch 20 using version GIT
Sintaxe:
Fonte: Asterisk Wiki
POR QUE A LOJAMUNDI É CONFIÁVEL?
ENTRE EM CONTATO COM A LOJAMUNDI.
Assine nossa Newsletter! É gratuito!
Cadastre seu nome e email para receber novidades e materiais gratuitos da Lojamundi.