Interconnect two XiVO directly

Situation diagram
Interconnecting two XiVO will allow you to send and receive calls between the users configured on both sides.
The steps to configure the interconnections are:
Establish the trunk between the two XiVO, that is the SIP connection between the two servers
Configure outgoing calls on the server(s) used to emit calls
Configure incoming calls on the server(s) used to receive calls
For now, only SIP interconnections have been tested.
Establish the trunk
The settings below allow a trunk to be used in both directions, so it doesn’t matter which server is A and which is B.
Consider XiVO A wants to establish a trunk with XiVO B.
On XiVO B, go on page
, and create a SIP trunk:Name : xivo-trunk
Username: xivo-trunk
Password: pass
Connection type: Friend
IP addressing type: Dynamic
Context: <see below>
Media server: MDS Main
Note
For the moment, Name and Username need to be the same string.
The Context
field will determine which extensions will be reachable by the
other side of the trunk:
If
Context
is set todefault
, then every user, group, conf room, queue, etc. that have an extension if thedefault
context will be reachable directly by the other end of the trunk. This setting can ease configuration if you manage both ends of the trunk.If you are establishing a trunk with a provider, you probably don’t want everything to be available to everyone else, so you can set the
Context
field toIncalls
. By default, there is no extension available in this context, so we will be able to configure which extension are reachable by the other end. This is the role of the incoming calls: making bridges from theIncalls
context to other contexts.
On XiVO A, create the other end of the SIP trunk on the
:Name: xivo-trunk
Username: xivo-trunk
Password: pass
Identified by: Friend
Connection type: Static
Address: <XiVO B IP address or hostname>
Context: Incalls
Media server: MDS Main
Register tab:
Register: checked
Transport: udp
Username: xivo-trunk
Password: pass
Remote server: <XiVO B IP address or hostname>
On both XiVO, activate some codecs, Signaling
:
Enabled codecs: at least GSM (audio)
Warning
Without customizing the codecs, problems with sound quality or one-way sound may occur.
At that point, the Asterisk command sip show registry
on XiVO B should print
a line showing that XiVO A is registered, meaning your trunk is established.
Set the outgoing calls
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
and add a route.Tab General:
Trunks: xivo-trunk
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
prefix).
The most useful special characters to match extensions are:
. (period): will match one or more characters
X: will match only one character
You can find more details about pattern matching in Asterisk (hence in XiVO) on the Asterisk wiki.
Set the incoming calls
Now that we have calls going out from a XiVO, we need to route incoming calls on the XiVO destination.
Note
This step is only necessary if the trunk is linked to an Incoming calls context.
To route an incoming call to the right destination in the right context, we will create an incoming call in
.Tab General:
DID: 101
Context: Incalls
Destination: User
Redirect to: someone
This will tell XiVO: if you receive an incoming call to the extension 101
in
the context Incalls
, then route it to the user someone
. The destination
context will be found automatically, depending on the context of the line of the
given user.
So, with the outgoing call set earlier on XiVO A, and with the incoming call
above set on XiVO B, a user on XiVO A will dial **99101
, and the user
someone
will ring on XiVO B.