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 18
Comando:
res_pjsip_outbound_registration: SIP resource for outbound registrations
Sinopse:
If this option is enabled and an authentication challenge fails, registration will not be attempted again until the configuration is reloade
Descrição:
If this option is enabled and an authentication challenge fails, registration will not be attempted again until the configuration is reloaded. This is the address-of-record for the outbound registration (i.e. the URI in the To header of the REGISTER). For registration with an ITSP, the client SIP URI may need to consist of an account name or number and the provider's hostname for their registrar, e.g. client_uri=1234567890@example.com. This may differ between providers. For registration to generic registrars, the client SIP URI will depend on networking specifics and configuration of the registrar. When line support is enabled this configured endpoint name is used for incoming calls that are related to the outbound registration. If a fatal response is received, chan_pjsip will wait fatal_retry_interval seconds before attempting registration again. If 0 is specified, chan_pjsip will not retry after receiving a fatal (non-temporary 4xx, 5xx, 6xx) response. Setting this to a non-zero value may go against a "SHOULD NOT" in RFC3261, but can be used to work around buggy registrars. Note if also set the forbidden_retry_interval takes precedence over this one when a 403 is received. Also, if auth_rejection_permanent equals 'yes' then a 401 and 407 become subject to this retry interval. If a 403 Forbidden is received, chan_pjsip will wait forbidden_retry_interval seconds before attempting registration again. If 0 is specified, chan_pjsip will not retry after receiving a 403 Forbidden response. Setting this to a non-zero value goes against a "SHOULD NOT" in RFC3261, but can be used to work around buggy registrars. When enabled this option will cause a 'line' parameter to be added to the Contact header placed into the outgoing registration request. If the remote server sends a call this line parameter will be used to establish a relationship to the outbound registration, ultimately causing the configured endpoint to be used. By default, registrations are randomly delayed by a small amount to prevent too many registrations from being made simultaneously. Depending on your system usage, it may be desirable to set this to a smaller or larger value to have fine grained control over the size of this random delay. This sets the maximum number of registration attempts that are made before stopping any further attempts. If set to 0 then upon failure no further attempts are made. This is a comma-delimited list of auth sections defined in pjsip.conf used to respond to outbound authentication challenges. Note Using the same auth section for inbound and outbound authentication is not recommended. There is a difference in meaning for an empty realm setting between inbound and outbound authentication uses. See the auth realm description for details. This is a comma-delimited list of security mechanisms to use. Each security mechanism must be in the form defined by RFC 3329 section 2.2. no mediasec This is the URI at which to find the registrar to send the outbound REGISTER. This URI is used as the request URI of the outbound REGISTER request from Asterisk. For registration with an ITSP, the setting may often be just the domain of the registrar, e.g. sip:sip.example.com. When this option is enabled, outbound REGISTER requests will advertise support for Path headers so that intervening proxies can add to the Path header as necessary. Note A transport configured in 'pjsip.conf'. As with other 'res_pjsip' modules, this will use the first available transport of the appropriate type if unconfigured. This documentation was generated from Asterisk branch 18 using version GIT
If this option is enabled and an authentication challenge fails, registration will not be attempted again until the configuration is reloaded. This is the address-of-record for the outbound registration (i.e. the URI in the To header of the REGISTER). For registration with an ITSP, the client SIP URI may need to consist of an account name or number and the provider's hostname for their registrar, e.g. client_uri=1234567890@example.com. This may differ between providers. For registration to generic registrars, the client SIP URI will depend on networking specifics and configuration of the registrar. When line support is enabled this configured endpoint name is used for incoming calls that are related to the outbound registration. If a fatal response is received, chan_pjsip will wait fatal_retry_interval seconds before attempting registration again. If 0 is specified, chan_pjsip will not retry after receiving a fatal (non-temporary 4xx, 5xx, 6xx) response. Setting this to a non-zero value may go against a "SHOULD NOT" in RFC3261, but can be used to work around buggy registrars. Note if also set the forbidden_retry_interval takes precedence over this one when a 403 is received. Also, if auth_rejection_permanent equals 'yes' then a 401 and 407 become subject to this retry interval. If a 403 Forbidden is received, chan_pjsip will wait forbidden_retry_interval seconds before attempting registration again. If 0 is specified, chan_pjsip will not retry after receiving a 403 Forbidden response. Setting this to a non-zero value goes against a "SHOULD NOT" in RFC3261, but can be used to work around buggy registrars. When enabled this option will cause a 'line' parameter to be added to the Contact header placed into the outgoing registration request. If the remote server sends a call this line parameter will be used to establish a relationship to the outbound registration, ultimately causing the configured endpoint to be used. By default, registrations are randomly delayed by a small amount to prevent too many registrations from being made simultaneously. Depending on your system usage, it may be desirable to set this to a smaller or larger value to have fine grained control over the size of this random delay. This sets the maximum number of registration attempts that are made before stopping any further attempts. If set to 0 then upon failure no further attempts are made. This is a comma-delimited list of auth sections defined in pjsip.conf used to respond to outbound authentication challenges. Note Using the same auth section for inbound and outbound authentication is not recommended. There is a difference in meaning for an empty realm setting between inbound and outbound authentication uses. See the auth realm description for details. This is a comma-delimited list of security mechanisms to use. Each security mechanism must be in the form defined by RFC 3329 section 2.2. no mediasec This is the URI at which to find the registrar to send the outbound REGISTER. This URI is used as the request URI of the outbound REGISTER request from Asterisk. For registration with an ITSP, the setting may often be just the domain of the registrar, e.g. sip:sip.example.com. When this option is enabled, outbound REGISTER requests will advertise support for Path headers so that intervening proxies can add to the Path header as necessary. Note A transport configured in 'pjsip.conf'. As with other 'res_pjsip' modules, this will use the first available transport of the appropriate type if unconfigured. This documentation was generated from Asterisk branch 18 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.