Differenze tra le versioni di "AdminGuide:BasicConcepts:Outbound lines/en"
Riga 14: | Riga 14: | ||
Calls to external numbers are not forwarded directly to the outbound lines, but are presented to the '''outbound routing''' engine. This engine decides whether the calling user/entity is authorized to perform the call (based on the destination number) and which outbound lines can be used. | Calls to external numbers are not forwarded directly to the outbound lines, but are presented to the '''outbound routing''' engine. This engine decides whether the calling user/entity is authorized to perform the call (based on the destination number) and which outbound lines can be used. | ||
Calls can reach the '''outbound routing''' engine from the ''' | Calls can reach the '''outbound routing''' engine from the '''numbering Plan''' or directly as a failover action of a previous destination (e.g. an incoming call to an extension can be forwarded to an external number in case of no answer). In both cases, the requested outbound call has two associated parameters, which are the '''outbound identity''' and the '''outbound routing class'''. | ||
=== Outbound identity === | === Outbound identity === |
Versione delle 11:25, 5 mar 2018
Return to AdminGuide:BasicConcepts
Outbound and inbound lines
"Outbound and inbound lines" are all the SIP lines through which the PBX can make and receive calls to and from external numbers, i.e. not an internal service or extension (local SIP account).
These lines are configured in the Gateway and VoIP Domains panel.
Calls to external numbers
Calls to external numbers are not forwarded directly to the outbound lines, but are presented to the outbound routing engine. This engine decides whether the calling user/entity is authorized to perform the call (based on the destination number) and which outbound lines can be used.
Calls can reach the outbound routing engine from the numbering Plan or directly as a failover action of a previous destination (e.g. an incoming call to an extension can be forwarded to an external number in case of no answer). In both cases, the requested outbound call has two associated parameters, which are the outbound identity and the outbound routing class.
Outbound identity
The outbound identity is the extension number which will be accounted for that call, and will be used to derive the CLID used in the outbound call (according to the corresponding calling number manipulation table). The Outbound Identity can be explicitly set in case of failover actions, whereas it is automatically assigned in case of calls performed by a SIP account or in case of calls transferred/forwarded:
- Calls made by a SIP account
- The outbound identity is set to the extension linked to the SIP Account.
- Calls forwarded by a device (telephone-driven call forwarding)
- Same as above.
- Calls forwarded using the KalliopePBX (unconditional) call forwarding service
- The outbound identity is set to the forwarding extension number.
- Transferred calls (using KalliopePBX star-codes or telephone functions)
- The outbound identity is set equal to the transferring extension number.
In all these cases, if the caller requests to present itself as anonymous (according to the different CLIR supported methods), the outbound identity retains the extension number throughout all the lifetime of the call, and actual calling number restriction is performed when placing the call to the outbound line (or to the destination SIP accounts, in case of internal calls).
Outbound routing class
The outbound routing class defines the actual handling of the call, i.e. whether it is allowed or not, and (in the former case) the sequence of outbound lines to be used to perform the call.
Except when explicitly set by a failover action, the choice of the Outbound Routing Class is automatically derived by the Outbound Identity.