Posts Tagged ‘PRI’

Interconnection Elastix between Gateway Dinstar via PRI E1 (English Version)

octubre 18, 2015 2 comentarios

Sometimes they asked to perform some implementations a bit unusual. However, it is also a sign of how versatile it can be used software and hardware that comply with open standards in telephony and VoIP.

Thus, that this time we will see how to interconnect a Elastix with gateway E1 ports Dinstar brand model MTG1000

We will perform a different configuration, tailored to Elastix works as “operator” and the Gateway client as follows:

DINSTARIn this case the Elastix 1 functions as an “operator” will pri_net ie signaling and manage the clock (parameter 0 span configuration)

The tutorial will be divided into 4 steps:

1. Configuration of Elastix1
Configuration Dinstar Gateway
3. Verify that the E1 connection is built in both
4. Configuring the SIP Trunk between Dinstar and Elastix2
5. Creating inbound / outbound routes and testing

Let’s start:

1. Configuration of Elastix 1
In the detector hardware configure the  E1 as follows

DINSTARVerify that we have the timing to “0” because we have the clock.

If we go to “/etc/dahdi/system.conf” we find:
And in the “/etc/asterisk/dahdi-channels.conf” we have:

DINSTARAs you see in the signaling parameter we have as “pri_net” that simulate be the operator.

2. Configuration of Gateway Dinstar
We will: PSTN Group Config –> E1 / T1 PARAMETER where we define the behavior of E1 if you will be operator (local) or client (remote)

Then we have to change parameters for the port where we set the PRIMARIO E1 in this case will be the port 0 as follows:

DINSTARNow you need to create the SIP trunk with which the gateway will work, ie the server will send the call, in this case the Elastix 2, we‘ll SIP CONFIG –> SIP TRUNK and create our trunk as follows

DINSTARWhere IP is the IP address our Elastix 2 based on the scheme we are developing

Now let’s PRI CONFIG –> PRI TRUNK to give the final settings as follows.

DINSTARSwitch type Note in what we like “Use Slide” because it works as a client according to our scenario.

3. Verify that the E1 connection is built in both
At this point, after restarting the gateway or Elastix 1 inclusive, Connection E1 is raised

in the gateway E1 we have the following:

DINSTARIn Physis Status” have the correct status.

With this we ensure that both sides have good, ie the Elastix 1 and the gateway configured correctly via E1

4. Configuring the SIP Trunk between Dinstar and Elastix2

Now we will see how to configure the gateway against Elastix 2 by SIP.

Remember that we have created a trunk in the gateway that points to Elastix 2 now we have to create the trunk:

DINSTARIn the details of the peer we have to point to the IP gateway

Then we enter the gateway to the section and see what we have set the trunk as shown below.


5. Creating inbound / outbound routes and testing

Now in the Elastix 2 we have to create an incoming DID route with a test that will be sent from the Elastix 1


When the Elastix 1 call to 7073890 DID the gateway will meet and send the Elastix 2 and in this way we will see in the CLI of the latter:

The output of CLI Elastix 2


The call operation:

Thanks to my good friend Pedro Bustamante the BestSol which always has the willingness to lend to test hardware configurations like this.

I hope they serve
Juan Oliva



Categorías:Asterisk, Centos, Linux Etiquetas: , , , , ,