Zeck Audio STAC Force180 Guida di Installazione Pagina 31

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 41
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 30
Rev. 1.00 12-02-13 31/41
1000Base-SX => configure for Gigabit Ethernet Fiber/Copper module
100Base-FX => configure for Fast Ethernet Fiber module
The medium is not configurable and always uses auto-negotiation.
Limit packets to prevent SIP overload condition
First appeared in build series: 2012-09-17
It is possible to limit the maximum amount of incoming SIP packets which are stored to be handled and
processed later on. This guarantees a responsive system even in an overload condition. It handles and
parses still as much requests as possible but the excess is simply discarded.
When more SIP requests are arriving than SmartWare can handle, the overall system performance
decreases. This is because internal resources are occupied for requests which cannot be handled in
time. This causes re-transmissions of these requests and adds additional overhead to the system. In
order to avoid such a condition where no successful processing of requests is possible anymore, it is
better to drop packets early in the processing queue.
Best overall performance in processing the highest number of successful call attempts with a
continuously overloaded system was reached by setting this queue limit to a value of 8.
Mode: sip
Command
Purpose
Step 1
[node](sip)#[no] max-queued-packets
<number of packets>
Limits the internal SIP queue to discard
any packets when the configured
number of packets is reached.
Suggested: 8
FXO caller-ID checksum verification
First appeared in build series: 2012-07-18
This configuration only has an influence when the caller-ID format is either „etsi‟ or „bell‟. These are the
two formats which provide a checksum. All of the caller-ID formats with DTMF are not affected because
they have no checksum at all.
Enabled (old default behavior)
Until now SmartWare accepted a caller-ID only if it had a valid checksum. A caller-ID without checksum
or with an invalid checksum was discarded. The user can establish the old behavior with enabling the
caller-ID verification.
Disabled (new default behavior)
The default behavior is changed now that the caller-ID verification is disabled. Here the calling e164 is
filled with the received caller-ID data no matter if a checksum is valid or present at all.
Vedere la pagina 30
1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 40 41

Commenti su questo manuale

Nessun commento