Zeck Audio STAC Force180 Guide d'installation Page 27
- Page / 41
- Table des matières
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
Rev. 1.00 12-02-13 27/41
match, a new REGISTER request with corrected values is sent out. This can happen over the same flow
as the previous one or over a newly created flow depending on the destination IP address resolution.
Once a correct contact is successfully registered, the configured keep-alive mechanism is started for the
flow of that successful request. When a failure of a flow is detected through the keep-alive mechanism, all
registrations associated with that flow are discarded and the registration procedure is started anew.
Flows created for requests which were not successful and which are not used by other active calls or
registrations are terminated after 120 seconds of idle time.
Flows can be used for other outgoing requests, depending on the configuration. Incoming requests
through flows are treated the same was as if they were received through the listening socket of the sip
gateway. This ensures that the registrar server can forward calls through NAT to the registered user.
For flows the following keep-alive mechanisms can be configured:
no-keep-alive: Register through flows, but do not start a keep-alive mechanism. This could be
the case when the registrar server has such a mechanism, the NAT does not need such or the
registration lifetime is short enough that the keep-alive is made with the REGISTER requests.
CRLF: Start the CRLF keep-alive mechanism on TCP flows as described in FRC5626. For UDP
flows no keep-alive is started with that configuration.
options: Send OPTIONS request in periodic intervals over that flow to keep it active and detect
failure or changes.
ping: Send a PING request in periodic intervals over that flow to keep it active and detect failure
or changes
Mode: registration outbound
Command
Purpose
Step 1
[node](regout)# nat-traversal flows (no-keep-
alive | CRLF | options | ping) [keepalive-
interval <seconds>]
Activate nat-traversal with flows. Default
keepalive-interval: 55 seconds.
Calls using flows (new)
The concept of flows can be used for calls to. When flows are opened by registrations these are re-used
for outgoing calls as well, but only if the target resolution procedures for calls are resulting in an IP
address which a flow already exists for. Otherwise new flow is created for the duration of the call.
This does not affect incoming calls. Incoming calls are accepted through flows or outside of flows in the
same way.
Mode: call outbound
- SmartWare R6.T Release Notes 1
- About this Release 2
- Supported Products 2
- History of Solved CTS Cases 3
- Build Series 2012-12-03 4
- 1.00 12-02-13 5/41 5
- Build Series 2012-09-17 6
- 1.00 12-02-13 7/41 7
- Build Series 2012-07-18 8
- 1.00 12-02-13 9/41 9
- Build Series 2012-05-23 10
- 1.00 12-02-13 11/41 11
- 1.00 12-02-13 12/41 12
- 1.00 12-02-13 13/41 13
- Build Series 2012-03-15 14
- 1.00 12-02-13 15/41 15
- 1.00 12-02-13 16/41 16
- 1.00 12-02-13 17/41 17
- Build Series 2012-01-26 18
- Build Series 2011-11-18 18
- Build Series 2011-09-15 19
- Caveat - Known Limitations 20
- 1.00 12-02-13 21/41 21
- 1.00 12-02-13 22/41 22
- General Notes 23
- New Configuration Commands 24
- 1.00 12-02-13 25/41 25
- 1.00 12-02-13 26/41 26
- 1.00 12-02-13 27/41 27
- SIP AOC (Advice of Charge) 28
- 1.00 12-02-13 29/41 29
- Set SFP mode 30
- 1.00 12-02-13 31/41 31
- 1.00 12-02-13 32/41 32
- 1.00 12-02-13 33/41 33
- 1.00 12-02-13 34/41 34
- Using PVC channel with IPoA 35
- Using PVC channel with PPPoA 35
- Set G.S power backoff 36
- 1.00 12-02-13 37/41 37
- Documentation 38
- How to Upgrade 39
- 1.00 12-02-13 40/41 40
- 1.00 12-02-13 41/41 41
Elinchrom Taschenlampen Benutzerhandbücher
Beginnend mit D
Commentaires sur ces manuels