Commit 7aef244b authored by Etienne Allovon's avatar Etienne Allovon

1403 - add precision in documentation and link from RN to doc section and...

1403 - add precision in documentation and link from RN to doc section and behavior change note in RN
parent bb5f4415
......@@ -113,42 +113,57 @@ caller ID in different places. Each way to configure a caller ID has it's own us
The format for a caller ID is the following ``"My Name" <9999>`` If you don't set the number part of
the caller ID, the dialplan's number will be used instead. This might not be a good option in most
cases.
If you only need to set a *number* as an outgoing caller ID, you just have to put the number in the caller ID field like ``0123456789``.
.. _outgoing_call_callerid:
Outgoing call caller ID
=======================
When you create an outgoing call, it's possible to set the it to internal, using the check box in
the outgoing call configuration menu. When this option is activated, the caller's caller ID will be
There are several behavior for the outgoing caller ID.
Use internal caller ID
----------------------
When you create an outgoing call, it's possible to set it to internal, using the check box in
the outgoing call configuration menu. When this option is activated, the internal caller's caller ID will be
forwarded to the trunk. This option is useful when the other side of the trunk can reach the user
with it's caller ID number.
.. figure:: images/outgoing_call_internal.png
:scale: 85%
When the caller's caller ID is not usable to the called party, the outgoing call's caller id can
Use outgoing caller ID
----------------------
When the internal caller's caller ID is not usable to the called party, the outgoing call's caller id can
be fixed to a given value that is more useful to the outside world. Giving the public number here
might be a good idea.
.. figure:: images/outgoing_call_callerid.png
:scale: 85%
A user can also have a forced caller ID for outgoing calls. This can be useful for someone who has
his own public number. This option can be set in the user's configuration page. To enable editing it,
The Outgoing Caller ID id option must be set to Customize.
A user can also have a forced caller ID for outgoing calls. This can be useful for a user who has
his own public number (DID number). This option can be set in the user's configuration page. For this,
the *Outgoing Caller ID* option must be set to Customize.
.. figure:: images/user_custom_callerid.png
:scale: 85%
The user can also set his outgoing caller ID to Anonymous. Before anonymizing caller ID, it is
recommended to set the Send the Remote-Party-ID option of the SIP protocol to PAI.
It can be set from two places:
The user can also set his outgoing caller ID to Anonymous.
If you use a SIP operator trunk, and if your operator supports the RFC3325 for Anonymous calls, you have
to set the Send the Remote-Party-ID option of your SIP trunk to **PAI**:
* :menuselection:`Services --> IPBX --> General settings --> SIP Protocol --> Default`
* :menuselection:`Services --> Trunk management --> SIP Protocol --> Edit --> tab Advanced`
#. :menuselection:`Services --> Trunk management --> SIP Protocol --> Edit --> tab Advanced`
#. set parameter *Send the Remote-Party-ID* to **PAI**
This option will keep the protocol compliant with the RFC 3325 standard, and the caller ID will be anonymized
only for the called party and untrusted parties but not for the trusted SIP peers.
With this option anonymous calls will be sent to your SIP operator with the RFC 3325 standard.
Note that in this case, the *P-Asserted-Identity* SIP Header will contain the Outgoing caller ID number if set. Otherwise it
will use the user's internal caller id, which not a good idea. So you should configure a default caller ID in the outgoing call.
Order of precedence
......@@ -158,5 +173,5 @@ The order of precedence when setting the caller ID in multiple places is the fol
#. Internal
#. User's outgoing caller ID
#. Outgoing call
#. Outgoing call caller ID
#. Default caller ID
......@@ -49,6 +49,13 @@ Consult the `2017.11 Roadmap <https://projects.xivo.solutions/versions/53>`_ for
* `#1394 <https://projects.xivo.solutions/issues/1394>`_ - Documentation: Configuration of new switchboard queue has changed
* `#1403 <https://projects.xivo.solutions/issues/1403>`_ - Change trust_id_outbound default value to yes (anonymous calls with RFC3325)
.. note::
**Behavior change** :
With this change, if your SIP trunk has *Send the Remote-Party-ID* set to *PAI*, anonymous calls will be sent according to
RFC 3325.
See :ref:`outgoing_call_callerid`.
**XiVO Provisioning**
* `#1012 <https://projects.xivo.solutions/issues/1012>`_ - Bug Directory Mitel 6865i 6869i (fixed with Aastra/Mitel firmware update
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment