Zeck Audio STAC Force180 Guia de Instalação Página 26

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 41
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 25
Rev. 1.00 12-02-13 26/41
Registration nat-traversal mode: nortel (no change)
This is the nat-traversal method to use together with certain Nortel devices. The discovery of the global IP
address and port is done by sending a PING request and examining the answer to that. After that a
REGISTER request with the global IP address in the contact header is sent for registration. Once
registered the keep-alive is achieved with sending PING requests.
Mode: registration outbound
Command
Purpose
Step 1
[node](regout)# nat-traversal nortel
[keepalive-interval <seconds>]
Activate nat-traversal the Nortel way.
Default keepalive-interval: 55 seconds.
Registration nat-traversal mode: keep-alive (enhanced)
Up until now this mode always used OPTIONS requests for achieving the keep-alive. In addition
SmartWare supports PING requests for the same purpose. OPTIONS is still the default when not
explicitly specified otherwise in the command.
This nat-traversal method executes the same procedure for registration as the minimal mode. After that
either OPTIONS or PING requests are sent periodically for keeping the NAT open and detect changes.
Mode: registration outbound
Command
Purpose
Step 1
[node](regout)# nat-traversal keep-alive
[options | ping] [keepalive-interval
<seconds>]
Activate nat-traversal with OPTIONS or
PING as keep-alive. Default keepalive-
interval: 55 seconds.
Registration nat-traversal mode: flows (new)
When nat-traversal flows is selected then most of the „User Agent Procedures‟ described in RFC5626 are
executed for outbound registrations. Each sip gateway maintains its unique instance ID which is used on
the registrar to distinguish between flows for different gateways or devices. For each registration the
destination IP address is determined by the normal procedure. If a flow already exists for that destination,
then the REGISTER request is sent through that flow. Otherwise a new flow to that destination is created
before sending the request.
SmartWare currently does not support creating multiple flows for the same registered identity. Therefore
the „reg-id‟ parameter always is „1‟. If a REGISTER request receives a successful answer SmartWare
checks the „received‟ and „rport‟ parameters for correctness of the registered contact. If they do not
Vista de página 25
1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 40 41

Comentários a estes Manuais

Sem comentários