Differenze tra le versioni di "AdminGuide:Service:SIPSettings/en"

Da Kalliope Wiki.
Jump to navigation Jump to search
(Creata pagina con "The duration is useful because if the central unit has to convert this DTMF, when sending it to the interlocutor in a format other than RFC 233, it should play it back for a c...")
 
(Creata pagina con "Thus, the use of ''in-band'' DTMF mode is discouraged because if the RTP stream suffers degradation due to losses or congestion, the tones, even using G.711 are distorted and...")
 
(Una versione intermedia di uno stesso utente non è mostrata)
Riga 50: Riga 50:
The setting in this panel applies to all SIP accounts defined in the "Internal and Accounts" panel and is used as the default setting for all incoming and outgoing lines.
The setting in this panel applies to all SIP accounts defined in the "Internal and Accounts" panel and is used as the default setting for all incoming and outgoing lines.


<div lang="it" dir="ltr" class="mw-content-ltr">
Unlike accounts, in the panel, there is no ability to go and change DTMFs: when you send a DTMF to an account, you send it with SIP settings, and the same occurs when a SIP account sends a DTMF.
A differenza degli account, nel pannello non c’è la possibilità di andare a cambiare i DTMF: quando si manda un DTMF verso un account lo si manda con le impostazioni SIP e lo stesso si verifica quando un account SIP manda un DTMF.
Instead, you can change the DTMF mode in the [[AdminGuide:BasicConcepts:Outbound_lines/en#Configuration|Inbound lines]] panel or leave it as default.
Invece, nel pannello delle [[AdminGuide:BasicConcepts:Outbound_lines#Configurazione_del_servizio|linee di ingresso e di uscita]] si può cambiare la modalità DTMF o lasciarla come di default.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
[[File:Cambio modalità.png|600px]]
[[File:Cambio modalità.png|600px]]
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
This mode is often referred to as AVB (Attribute Value Pair) on other equipment.
Questa modalità è spesso indicata come AVB (Attribute Value Pair) su altri apparati.
** '''SIP INFO''': is a mode that does not send RTP or RTP event messages, but an info type SIP message. The info is a type of SIP message that contains a payload containing the key and duration, is transmitted only once, and has a network path that follows that of the SIP signaling which is different from the path that the RTP flow takes.
** '''SIP INFO''': è una modalità che non manda messaggi RTP o RTP event, ma un messaggio SIP di tipo info. L’info è un tipo di messaggio SIP che contiene come payload contiene il tasto e la durata, viene trasmesso una sola volta e ha un percorso di rete che segue quello della segnalazione SIP che è diverso dal percorso che effettua il flusso RTP.
** '''In-band''': typed DTMF tones are sent as audio tones within the RTP stream.  
** '''In banda''': i toni DTMF digitati sono mandati sotto forma di toni audio all’interno del flusso RTP.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
If you analyze the tracks containing DTMF tones, you can find RTP only. So you cannot distinguish whether they are tones or not.
Infatti, se si analizzano le tracce che contengono toni DTMF si trovano solo RTP e non si può distinguere se siano toni o meno.
The problem with DTMF transmission under audio tones is that if codecs other than G.711 are used, they introduce compression into the audio and distortion of the tones.  
Il problema della trasmissione DTMF sotto toni audio è che se vengono utilizzati dei codec diversi dal G.711, questi introducono una compressione nell’audio e una deformazione dei toni.  
While a conversation is understandable, recognition of these tones may fail.  
Mentre una conversazione risulta comprensibile, il riconoscimento di questi toni potrebbe fallire.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
[[File:G711.png|700px]]
[[File:G711.png|700px]]
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
Thus, the use of ''in-band'' DTMF mode is discouraged because if the RTP stream suffers degradation due to losses or congestion, the tones, even using G.711 are distorted and may not be recognized.  
Quindi, l’utilizzo della modalità DTMF “in banda” è scoraggiato perché se il flusso RTP subisce un degrado per perdite o congestione, i toni, anche usando G.711 vengono deformati e possono non venire riconosciuti.  
Thus, the use of DTMF in audio is recommended only in conjunction with a compressed '''PCM a-low''' or '''PCM u-low''' codec, but it may still be error-prone.
Quindi l’utilizzo dei DTMF in audio è raccomandato solo in associazione ad un codec compresso '''PCM a-low''' o '''PCM u-low''', ma può comunque essere soggetto a errori.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
The most commonly used mode is RFC 2833.
La modalità più utilizzata è la RFC 2833.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
The following two fields are attributes that impact both SIP accounts and input and output lines; as in the case of DTMF mode, the next two are also modifiable from the default value in the input and output lines.
I successivi due campi sono due attributi che impattano sia gli account SIP che le linee di ingresso e uscita, come nel caso della modalità DTMF, anche i seguenti due sono modificabili rispetto al valore di default nelle linee di ingresso e di uscita.
* '''Enable RPID (Remote Party ID) acceptance''': enables COLP acceptance (named thus in the inbound and outbound lines).  
* '''Abilita accettazione RPID (Remote Party ID)''': abilita accettazione COLP (nominato così nelle linee di ingresso e uscita).
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
Enabling causes it to extract the caller's identity from the FROM it sends and the PAI, RPID, etc. headers.
L’abilitazione fa in modo che si estragga l’identità del chiamante non solo dal FROM che manda, ma dagli header PAI, RPID ecc.
This is a SIP header that carries additional information that identifies the caller.
Si tratta di un header SIP che trasporta un’informazione aggiuntiva che identifica il chiamante.
During a call, there are instances when the identifier of the person being talked to may change over time.
Durante una chiamata, ci sono dei casi in cui l’identificativo della persona con cui si parla possa cambiare nel tempo.
The COLP feature causes the exchange to notify that the caller has changed; there are some cases where it is necessary to provide this information to the caller, and others where it is not.
La funzionalità del COLP fa in modo che la centrale notifichi che l’interlocutore è cambiato, ci sono dei casi in cui è necessario fornire questa informazione all’interlocutore, e altri in cui non lo è.
This flag causes it to accept from telephones connected to the exchange, the caller ID present in the RPID or PAI (P-Asserted-Identity) header.
Questo flag fa sì che si accetti dai telefoni collegati alla centrale, l’identificativo chiamante presente nell’header RPID o PAI (P-Asserted-Identity).
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
'''N.B.''' At the output level, it is recommended that the entry be disabled since you do not want the pbx to change the identifier of the connected line.
'''N.B.''' A livello di uscita si raccomanda che la voce sia disabilitata poiché non si vuole che la centrale modifichi l’identificativo della linea connessa.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
* '''Send rpid mode''': Send COLP mode (named so in the input and output lines).  
* '''Send rpid mode''': Modalità invio COLP (nominato così nelle linee di ingresso e uscita).
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
It has three options: disabled / remote party ID / P-Asserted-Identity.
Ha tre opzioni: disabilitato / remote party ID / P-Asserted-Identity.
In this case, the setting that is used for telephones and that is recommended is sending PAI. This flag causes the pbx to warn that the interlocutor being communicated with has changed, it sends a message that updates the information via the PAI header.  
In questo caso, l’impostazione che viene utilizzata verso i telefoni e che si raccomanda è l’invio del PAI. Questo flag fa sì che la centrale avverta che l’interlocutore con cui si comunica è cambiato, manda un messaggio che aggiorna l’informazione tramite l’header PAI.  
The interlocutor change information is useful toward telephones, but generally, on an outgoing line it should be disabled.
L’informazione di cambio interlocutore è utile verso i telefoni, ma normalmente su una linea di uscita deve essere disabilitato.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
N.B. If you go to make a trunk to another exchange where you configure remote extensions, in this case the line is not an outgoing trunk to an operator, but it is the interconnection to another exchange on which it is helpful to activate the COLP update mode.
N.B. Se si va a fare un trunk verso un’altra centrale in cui configuro interni remoti, in questo caso la linea non è un trunk di uscita verso un operatore, ma è l’interconnessione con un’altra centrale sulla quale è utile attivare la modalità di aggiornamento del COLP.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
The following three fields set the quality-of-service parameters for the service leaving the exchange.
I tre campi successivi servono per impostare i parametri di qualità del servizio in uscita dalla centrale.
There are TOS hexadecimal values and priority codes in the network to decide which packets to make travel with priority over others in case of congestion. Thus, it ensures that audio and video streams receive priority over sending the mail.
Sono presenti i valori esadecimali del TOS e i codici di priorità che nella rete servono per decidere in caso di congestione, quali pacchetti far viaggiare con priorità rispetto agli altri. Quindi, garantisce che flussi audio e video abbiano trattamento privilegiato rispetto all’invio della mail.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
* '''TOS SIP'''
* '''TOS SIP'''
* '''TOS Audio'''
* '''TOS Audio'''
* '''TOS Video'''
* '''TOS Video'''
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
These values can be changed if the network in which the control panel is operating requires that different TOS values be used for audio, signaling, and/or video.
Questi valori possono essere cambiati se la rete in cui si trova a operare la centrale richiede che siano usati diversi valori di TOS per l’audio, la segnalazione e/o il video.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
* '''Enable Video''': to globally enable support for video calls.
* '''Abilita Video''': per abilitare a livello globale il supporto alle videochiamate
* '''Maximum bitrate for video calls''': attribute that applies only to video calls and determines the maximum bitrate that the exchange accepts and offers for video calls, by default it is 384 Kbps so as not to take up too much bandwidth. Often values can be raised to increase quality.  
* '''Bitrate massimo per le chiamate video''': attributo che vale solo per le chiamate video e determina il bitrate massimo che la centrale accetta e offre per le videochiamate, di default è 384 Kbps per non occupare troppa banda. Spesso i valori possono essere alzati per aumentare la qualità.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
* '''Enable RTP encryption support (SRTP)''': enables at the pbx level the ability to allow encryption of RTP streams that generally travel in the clear (anyone who can intercept the RTP stream of the call can listen to its contents).
* '''Abilita supporto alla cifratura RTP (SRTP)''': abilita a livello di centrale la possibilità di attivare l’encryption dei flussi RTP che normalmente viaggiano in chiaro (chiunque riesca a intercettare il flusso RTP della chiamata può ascoltarne il contenuto).
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
SRPT is a protocol that relies on the prior exchange of keys between the caller and called party; the flow is encrypted with a symmetric key cipher. The key is exchanged during call setup, and if a secure signaling transport protocol such as TLS is not used and TCP or UDP is used instead, it can be read in the cleartext on the SIP message. Enabling SRPT makes sense if coupled with a secure signaling protocol such as TLS.
SRPT è un protocollo che si basa sul preventivo scambio di chiavi tra chiamante e chiamato, il flusso è cifrato con un cifratore a chiave simmetrica. La chiave viene scambiata in fase di setup della chiamata e, se non si usa un protocollo di trasporto della segnalazione sicuro come TLS e si usa invece TCP o UDP, si può leggere in chiaro sul messaggio SIP. L’attivazione dell’SRPT ha senso se è accoppiata a un protocollo di segnalazione di tipo sicuro come TLS.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
'''WARNING''': Enabling SRTP in the SIP settings does not automatically enable the actual use of SRTP, but it does allow the module from SRPT support. You need to enable it in the ''Extensions and Accounts'' panel. Here, there is a checkmark ''"Enable SRPT"''': this way it can be inherited by all accounts that use that particular template.
'''ATTENZIONE''': L’abilitazione dell’SRTP nelle impostazioni SIP non abilita automaticamente l’effettivo utilizzo dell’SRTP, ma abilita il modulo da supporto SRPT. È necessario abilitarlo nel pannello degli “Interni e account”. Qui, è presente la spunta '''“Abilita SRPT”''': in questo modo può essere ereditato da tutti gli account che usano quel determinato template.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
[[File:Abilita SRPT interni.png|600px]]
[[File:Abilita SRPT interni.png|600px]]
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
The following two fields are not necessary to configure, except when you want to expose the service via WebRtc (via Web Socket) and specify a STUN server to acquire the information needed to shut down signaling properly and media.
I due campi successivi non sono necessari da configurare, se non quando si vuole esporre il servizio tramite WebRtc (tramite Web Socket) ed è necessario specificare un server STUN per acquisire l’informazione necessari aa far chiudere correttamente segnalazione e media.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
'''N.B.''' STUN is a protocol used to distribute the public IP information a client uses behind a NAT. It is used by rtc (web phone) web clients to ensure that the central station knows what IP address to send media streams.
'''N.B.''' STUN è un protocollo che serve per distribuire l’informazione dell’IP pubblico utilizzato da un client che si trova dietro un NAT. Viene usato dai client web rtc (telefono web) per fare in modo che la centrale sappia qual è l’indirizzo IP a cui spedire i flussi media.
It goes hand in hand with enabling transport (protocol for SIP signaling) via Web Socket. Once Secure Web Socket is allowed, there is a need to specify a STUN server, which the central office uses to learn which ports it will use for signaling and media.
Va di pari passo con l’abilitazione del trasporto (protocollo per le segnalazioni SIP) tramite Web Socket e, una volta attivato il Web Socket Sicuro, c’è necessità di specificare un server STUN, che la centrale usa pere imparare quali sono le porte che utilizzerà per la segnalazione e per il media.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
* '''STUN server address'''
* '''Indirizzo del server STUN'''
* '''STUN server mail'''
* '''Posta del server STUN'''
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
===NAT Helper===
===NAT Helper===
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
This section is especially important for making the station available in access from the public.
Questa sezione è particolarmente importante per rendere la centrale disponibile in accesso dal pubblico.
* External host: public IP address.
* Host esterno: indirizzo IP pubblico
* External host update period (sec.)
* Periodo di aggiornamento dell’host esterno (sec.)
* External UDP port
* Porta UDP esterna
* External TCP port
* Porta TCP esterna
* External TLS port
* Porta TLS esterna
* Local networks
* Reti locali
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
All messages sent to networks marked as local use their private address as routed, while what is outside local networks uses the IP address you specify in the external host.
Per tutti i messaggi inviati alle reti marcate come locali usa il proprio indirizzo privato come da routing, mentre ciò che è fuori dalle reti locali usa l’indirizzo IP che specificate nell’host esterno.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
===Predefined video codecs===
===Codec video predefiniti===
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
To enable video call support, check the above "Enable video" box and select which video codecs are supported by the central unit.
Per abilitare il supporto alle videochiamate si spunta la sopracitata casella “Abilita video” e selezionare quali codec video sono supportati dalla centrale.
</div>


<div lang="it" dir="ltr" class="mw-content-ltr">
===Codec audio===
===Codec audio===
Anche per l’audio si può selezionare quali codec sono supportati dalle centrale.
Also, for audio, you can select which codecs are supported by the power plants.
</div>

Versione attuale delle 13:48, 3 set 2022

Altre lingue:

Return to AdminGuide:Service

Description

The SIP settings panel contains the specification of telephone engine settings. The SIP protocol governs the communication between the exchange and the telephones and between the exchange and other gateways.

Configuration

PBX, impostazioni sip.png

The panel can be reached from the menu "PBX > SIP settings". In the case of a multitenant system, the panel is used by the PBX admin because even in a multitenant node, the SIP stack running on the machine is unique and shares settings among all tenants. The tenants, however, can independently perform the configuration of their own extensions/groups/queues/accounts.

  • Enable pedantic check of SIP messages: this causes a stricter check of the formal correctness of SIP messages sent to the pbx to be carried out, and if this legal check indicates malformations within the SIP packet, it discards it.

This is a security measure to prevent malformed SIP packets from arriving at the exchange, creating malfunctions or attacks on the machine itself. In cases where one interfaces with providers (gateways, telephones) that create SIP messages that are not formatted entirely correctly, it may be helpful to disable the flag. In this case, message parsing is relaxed and made acceptable.

  • DTMF mode: tones that can be sent during a telephone call to send commands or information to the other party. There are three modes provided in the SIP standard by which DTMFs sent by the other party or sent to the other party can be sent and acknowledged.
    • RFC 2833: can be considered side-by-side with 4733, which recalls and extends 2833.

This mode provides that DTMF tones are sent as RTP event packets within the RTP stream of a call. DTMF tones take the same path as the audio stream, but are not sent as tones, but as RTP event packets. These RTP event messages are sent by sending an initial packet (beginning of the tone). Then, with periodicity typical of VoIP, another packet is sent that lengthens the duration of the tone. These RTP event' messages contain the number of keys pressed and the symbols *#.

Example:

The DTMF tone sent in RFC 2833 mode by the 10.0.20.100 central unit to the PBX can be displayed:

Rtp event.png

This incoming RTP is passed back from the pbx to the interlocutor.

The audio packet is sent to a stream that has a source and destination port that contains the RTP stream. When the station sends a DTMF in RTP event mode within the same stream, the port extremes do not change (the same as in the audio packet), but the payload type changes.

Payload type.png

Payload type event.png

In the second case the payload type is 101 because the RTP event changes the payload type. Kalliope uses 101 by default for sending DTMFs.

The payload becomes explicit information of the key is pressed, the volume, and duration in samples.

UDP, in the case of a PBX with more than one network interface, causes VoIP service to be activated on all the interfaces in the PBX. A second network interface can be added, or VLAN tags can be added.

Event duration (campioni).png

The duration is useful because if the central unit has to convert this DTMF, when sending it to the interlocutor in a format other than RFC 233, it should play it back for a corresponding duration. The setting in this panel applies to all SIP accounts defined in the "Internal and Accounts" panel and is used as the default setting for all incoming and outgoing lines.

Unlike accounts, in the panel, there is no ability to go and change DTMFs: when you send a DTMF to an account, you send it with SIP settings, and the same occurs when a SIP account sends a DTMF. Instead, you can change the DTMF mode in the Inbound lines panel or leave it as default.

Cambio modalità.png

This mode is often referred to as AVB (Attribute Value Pair) on other equipment.

    • SIP INFO: is a mode that does not send RTP or RTP event messages, but an info type SIP message. The info is a type of SIP message that contains a payload containing the key and duration, is transmitted only once, and has a network path that follows that of the SIP signaling which is different from the path that the RTP flow takes.
    • In-band: typed DTMF tones are sent as audio tones within the RTP stream.

If you analyze the tracks containing DTMF tones, you can find RTP only. So you cannot distinguish whether they are tones or not. The problem with DTMF transmission under audio tones is that if codecs other than G.711 are used, they introduce compression into the audio and distortion of the tones. While a conversation is understandable, recognition of these tones may fail.

G711.png

Thus, the use of in-band DTMF mode is discouraged because if the RTP stream suffers degradation due to losses or congestion, the tones, even using G.711 are distorted and may not be recognized. Thus, the use of DTMF in audio is recommended only in conjunction with a compressed PCM a-low or PCM u-low codec, but it may still be error-prone.

The most commonly used mode is RFC 2833.

The following two fields are attributes that impact both SIP accounts and input and output lines; as in the case of DTMF mode, the next two are also modifiable from the default value in the input and output lines.

  • Enable RPID (Remote Party ID) acceptance: enables COLP acceptance (named thus in the inbound and outbound lines).

Enabling causes it to extract the caller's identity from the FROM it sends and the PAI, RPID, etc. headers. This is a SIP header that carries additional information that identifies the caller. During a call, there are instances when the identifier of the person being talked to may change over time. The COLP feature causes the exchange to notify that the caller has changed; there are some cases where it is necessary to provide this information to the caller, and others where it is not. This flag causes it to accept from telephones connected to the exchange, the caller ID present in the RPID or PAI (P-Asserted-Identity) header.

N.B. At the output level, it is recommended that the entry be disabled since you do not want the pbx to change the identifier of the connected line.

  • Send rpid mode: Send COLP mode (named so in the input and output lines).

It has three options: disabled / remote party ID / P-Asserted-Identity. In this case, the setting that is used for telephones and that is recommended is sending PAI. This flag causes the pbx to warn that the interlocutor being communicated with has changed, it sends a message that updates the information via the PAI header. The interlocutor change information is useful toward telephones, but generally, on an outgoing line it should be disabled.

N.B. If you go to make a trunk to another exchange where you configure remote extensions, in this case the line is not an outgoing trunk to an operator, but it is the interconnection to another exchange on which it is helpful to activate the COLP update mode.

The following three fields set the quality-of-service parameters for the service leaving the exchange. There are TOS hexadecimal values and priority codes in the network to decide which packets to make travel with priority over others in case of congestion. Thus, it ensures that audio and video streams receive priority over sending the mail.

  • TOS SIP
  • TOS Audio
  • TOS Video

These values can be changed if the network in which the control panel is operating requires that different TOS values be used for audio, signaling, and/or video.

  • Enable Video: to globally enable support for video calls.
  • Maximum bitrate for video calls: attribute that applies only to video calls and determines the maximum bitrate that the exchange accepts and offers for video calls, by default it is 384 Kbps so as not to take up too much bandwidth. Often values can be raised to increase quality.
  • Enable RTP encryption support (SRTP): enables at the pbx level the ability to allow encryption of RTP streams that generally travel in the clear (anyone who can intercept the RTP stream of the call can listen to its contents).

SRPT is a protocol that relies on the prior exchange of keys between the caller and called party; the flow is encrypted with a symmetric key cipher. The key is exchanged during call setup, and if a secure signaling transport protocol such as TLS is not used and TCP or UDP is used instead, it can be read in the cleartext on the SIP message. Enabling SRPT makes sense if coupled with a secure signaling protocol such as TLS.

'WARNING: Enabling SRTP in the SIP settings does not automatically enable the actual use of SRTP, but it does allow the module from SRPT support. You need to enable it in the Extensions and Accounts panel. Here, there is a checkmark "Enable SRPT": this way it can be inherited by all accounts that use that particular template.

Abilita SRPT interni.png

The following two fields are not necessary to configure, except when you want to expose the service via WebRtc (via Web Socket) and specify a STUN server to acquire the information needed to shut down signaling properly and media.

N.B. STUN is a protocol used to distribute the public IP information a client uses behind a NAT. It is used by rtc (web phone) web clients to ensure that the central station knows what IP address to send media streams. It goes hand in hand with enabling transport (protocol for SIP signaling) via Web Socket. Once Secure Web Socket is allowed, there is a need to specify a STUN server, which the central office uses to learn which ports it will use for signaling and media.

  • STUN server address
  • STUN server mail

NAT Helper

This section is especially important for making the station available in access from the public.

  • External host: public IP address.
  • External host update period (sec.)
  • External UDP port
  • External TCP port
  • External TLS port
  • Local networks

All messages sent to networks marked as local use their private address as routed, while what is outside local networks uses the IP address you specify in the external host.

Predefined video codecs

To enable video call support, check the above "Enable video" box and select which video codecs are supported by the central unit.

Codec audio

Also, for audio, you can select which codecs are supported by the power plants.

Estratto da "https://www.kalliope.com/wiki/index.php?title=AdminGuide:Service:SIPSettings/en&oldid=17488"