Commit 5d0ad792 authored by Laurent Meiller's avatar Laurent Meiller

Update references to previous outgoing calls to new route system

parent 54404f3f
......@@ -72,7 +72,7 @@ To use your DAHDI links you must create a customized interconnection.
.. warning:: if you use a BRI card you MUST use per-port dahdi groups.
You should not use a group like g0 which spans over several spans.
For example, add an interconnection to the menu :menuselection:`Services --> IPBX --> Trunk management --> Customized` ::
......@@ -115,16 +115,16 @@ Outgoing call caller ID
There are several behavior for the outgoing caller ID.
Use internal 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.
.. 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%
.. .. figure:: images/outgoing_call_internal.png
.. :scale: 85%
Use outgoing caller ID
......@@ -144,7 +144,7 @@ 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.
The user can also set his outgoing caller ID to Anonymous.
If you use a SIP provider trunk, and if your provider supports the RFC3325 for Anonymous calls, you have
to set the Send the Remote-Party-ID option of your SIP trunk to **PAI**:
......
......@@ -101,16 +101,14 @@ The outgoing calls configuration will allow XiVO to know which extensions will
be called through the trunk.
On the call emitting server(s), go on the page :menuselection:`Services
--> IPBX --> Call management --> Outgoing calls` and add an outgoing call.
--> IPBX --> Call management --> Outgoing calls` and add a route.
Tab General::
Trunks: xivo-trunk
Tab Exten::
Exten: **99. (note the period at the end)
Stripnum: 4
Extension: **99. (note the period at the end)
Target: \1
RegExp: .{4}(.*)
This will tell XiVO: if any extension begins with ``**99``, then try to dial it
on the trunk ``xivo-trunk``, after removing the 4 first characters (the ``**99``
......
......@@ -79,15 +79,12 @@ The outgoing calls configuration will allow XiVO to know which extensions will
be called through the trunk.
Go on the page :menuselection:`Services --> IPBX --> Call management -->
Outgoing calls` and add an outgoing call.
Outgoing calls` and add a route.
Tab General::
Trunks: provider_username
Tab Exten::
Exten: 418. (note the period at the end)
Extension: 418. (note the period at the end)
This will tell XiVO: if an internal user dials a number beginning with ``418``,
then try to dial it on the trunk ``provider_username``.
......
......@@ -237,29 +237,13 @@ management --> Outgoing calls` page :
1. Redirect calls to the PBX :
* Name : fsc-pabx
* Extension : XXXX
* Context : to-pabx
* Trunks : choose the *t2-pabx* interconnection
.. figure:: images/outgoing_call_general.png
:align: center
:scale: 80%
In the extensions tab :
* Exten : XXXX
.. figure:: images/outgoing_call_exten.png
:align: center
:scale: 75%
2. Create a rule "fsc-operateur":
* Name : fsc-operateur
* Extension = X.
* Context : to-extern
* Trunks : choose the "t2-operateur" interconnection
In the extensions tab::
exten = X.
......@@ -28,7 +28,7 @@ A route can define
* **Media server**: define the route only for specific media server.
* **Context**: define the route only for specific context.
Here some example of how you can take advantage of **RegExp** and **Target**:
Here some examples of how you can take advantage of **RegExp** and **Target**:
========== ======== ======================================================================================================================
Regexp Target Result
......
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