http://wiki.integrics.com/api.php?action=feedcontributions&feedformat=atom&user=Dcunningham 2026-05-06T21:46:31Z User contributions MediaWiki 1.31.7 http://wiki.integrics.com/index.php?title=SELinux_building_module&diff=395 2025-08-29T04:29:24Z

<p>Dcunningham: </p> <hr /> <div>To check for SELinux audit entries:<br /> &lt;pre&gt;<br /> audit2allow -a -b<br /> &lt;/pre&gt;<br /> <br /> To turn SELinux audit entries into a new SELinux module:<br /> &lt;pre&gt;<br /> audit2allow -a -b -M enswitch<br /> &lt;/pre&gt;<br /> <br /> To compile the SELinux module for Enswitch:<br /> &lt;pre&gt;<br /> cd /opt/enswitch/current/etc/selinux<br /> checkmodule -M -m -o enswitch.mod enswitch.te<br /> semodule_package -o enswitch.pp -m enswitch.mod<br /> semodule -i enswitch.pp<br /> rm enswitch.mod<br /> &lt;/pre&gt;<br /> <br /> To check the SELinux module for Enswitch is installed:<br /> &lt;pre&gt;<br /> semodule -l | grep enswitch<br /> &lt;/pre&gt;<br /> <br /> To remove the installed SELinux module for Enswitch:<br /> &lt;pre&gt;<br /> semodule -r enswitch<br /> &lt;/pre&gt;<br /> <br /> To list the contents of the .pp file:<br /> &lt;pre&gt;<br /> /usr/libexec/selinux/hll/pp /opt/enswitch/etc/selinux/enswitch.pp<br /> &lt;/pre&gt;</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=392 2025-05-30T00:09:13Z

<p>Dcunningham: </p> <hr /> <div>=== Check what's installed ===<br /> <br /> To check what version might already be installed run &lt;code&gt;go version&lt;/code&gt;. If the version is less than 1.20 you should definitely upgrade.<br /> <br /> Compiling messaged on a system with a newer version of GLIBC can mean that it won't run on systems with an older version, so it's better to compile messaged on older versions. Voisonics uses dev-4-2 for this.<br /> <br /> === Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Getting the source code ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;<br /> <br /> Then &lt;code&gt;cd&lt;/code&gt; into the root directory of the git clone.<br /> <br /> === Compiling messaged in 3.15 and below ===<br /> <br /> You should be able to run &lt;code&gt;go build&lt;/code&gt;, but it may not work with recent versions of Go.<br /> <br /> === Compiling messaged in 4.0 and above ===<br /> <br /> Run: &lt;code&gt;make&lt;/code&gt;<br /> <br /> If subsequent runs of make don't do anything, delete the compiled &lt;code&gt;messaged&lt;/code&gt; first and then try again.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Compiling_AngularJS_interface&diff=377 2024-09-20T02:36:38Z

<p>Dcunningham: Replaced content with &quot;You should follow the instructions in web/README.md on the Enswitch server.&quot;</p> <hr /> <div>You should follow the instructions in web/README.md on the Enswitch server.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Sharing_features_between_customers&diff=376 2024-08-27T03:51:03Z

<p>Dcunningham: </p> <hr /> <div>Normally features within one Enswitch customer cannot be accessed by another customer, except by calling a Number.<br /> <br /> However, sometimes you may want to create a customer with branch offices as sub-customers, and allow internal access between the sub-customers. For example, one customer may need to be able to dial feature codes within a sibling customer. This can be done with &quot;common routing&quot;. To use it:<br /> <br /> # Set System -&gt; Configuration -&gt; &quot;Enable common routing between customers&quot; to Yes.<br /> # For each sub-customer set &quot;Share features with parent&quot; to Yes.<br /> <br /> The logic then used is:<br /> <br /> # Call is made in customer with &quot;Share features with parent&quot; enabled.<br /> # Routing engine looks at the calling customer's parent customer to see if it has &quot;Share features with parent&quot; enabled, and if so check it's parent, and so on until the highest level customer with &quot;Share features with parent&quot; enabled is found.<br /> # Routing engine then looks in all sub-customers of that highest level customer, checks if the sub-customer has &quot;Share features with parent&quot; enabled, and if it does then looks in that customer for a number or feature code which matches the destination dialled.<br /> <br /> For an example refer to the following customer tree:<br /> <br /> &lt;pre&gt;<br /> a<br /> |<br /> -------<br /> | | |<br /> b c D<br /> | |<br /> e -------<br /> | |<br /> F G<br /> |<br /> H<br /> &lt;/pre&gt;<br /> <br /> All upper case customers have &quot;Share features with parent&quot; enabled, and all lower case customers do not.<br /> <br /> # Customer H makes call. No number in H itself matches the number dialled, so the routing engine recurses upwards until it finds the highest level customer with &quot;Share features with parent&quot; enabled, which is D.<br /> # The routing engine then recurses downwards from D until it finds that customer F contains a feature code matching the number dialled. The call routes to the destination which that feature code in customer F points to.<br /> # Customers a, b, c, and e were not checked because D's parent did not have &quot;Share features with parent&quot; enabled, so D's parent and D's siblings were not checked for a matching number.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Sharing_features_between_customers&diff=375 2024-08-27T03:50:39Z

<p>Dcunningham: </p> <hr /> <div>Normally features within one Enswitch customer cannot be accessed by another customer, except by calling a Number.<br /> <br /> However, sometimes you may want to create a customer with branch offices as sub-customers, and allow internal access between the sub-customers. For example, one customer may need to be able to dial feature codes within a sibling customer. This can be done with &quot;common routing&quot;. To use it:<br /> <br /> # Set System -&gt; Configuration -&gt; &quot;Enable common routing between customers&quot; to Yes.<br /> # For each sub-customer set &quot;Share features with parent&quot; to Yes.<br /> <br /> The logic then used is:<br /> <br /> # Call is made in customer with &quot;Share features with parent&quot; enabled.<br /> # Routing engine looks at the calling customer's parent customer to see if it has &quot;Share features with parent&quot; enabled, and if so check it's parent, and so on until the highest level customer with &quot;Share features with parent&quot; enabled is found.<br /> # Routing engine then looks in all sub-customers of that highest level customer, checks if the sub-customer has &quot;Share features with parent&quot; enabled, and if it does then looks in that customer for a number or feature code which matches the destination dialled.<br /> <br /> For an example refer to the following customer tree:<br /> <br /> &lt;code&gt;<br /> a<br /> |<br /> -------<br /> | | |<br /> b c D<br /> | |<br /> e -------<br /> | |<br /> F G<br /> |<br /> H<br /> &lt;/code&gt;<br /> <br /> All upper case customers have &quot;Share features with parent&quot; enabled, and all lower case customers do not.<br /> <br /> # Customer H makes call. No number in H itself matches the number dialled, so the routing engine recurses upwards until it finds the highest level customer with &quot;Share features with parent&quot; enabled, which is D.<br /> # The routing engine then recurses downwards from D until it finds that customer F contains a feature code matching the number dialled. The call routes to the destination which that feature code in customer F points to.<br /> # Customers a, b, c, and e were not checked because D's parent did not have &quot;Share features with parent&quot; enabled, so D's parent and D's siblings were not checked for a matching number.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=371 2024-07-01T01:06:50Z

<p>Dcunningham: </p> <hr /> <div>=== Check what's installed ===<br /> <br /> To check what version might already be installed run &lt;code&gt;go version&lt;/code&gt;. If the version is less than 1.20 you should definitely upgrade.<br /> <br /> === Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Getting the source code ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;<br /> <br /> Then &lt;code&gt;cd&lt;/code&gt; into the root directory of the git clone.<br /> <br /> === Compiling messaged in 3.15 and below ===<br /> <br /> You should be able to run &lt;code&gt;go build&lt;/code&gt;, but it may not work with recent versions of Go.<br /> <br /> === Compiling messaged in 4.0 and above ===<br /> <br /> Run: &lt;code&gt;make&lt;/code&gt;<br /> <br /> If subsequent runs of make don't do anything, delete the compiled &lt;code&gt;messaged&lt;/code&gt; first and then try again.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=370 2024-05-22T21:49:54Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are thousands of permutations to consider.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)<br /> * SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> * Take call feature prefix<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> * Transfer by party which did call pickup (using ** or *** and is really a calling but a user might think of as the called party)<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Queue event log (queue_events table)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=369 2024-05-22T21:49:25Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are thousands of permutations to consider.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)<br /> * SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> * Take call feature prefix<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> * Transfer by party which did call pickup (using ** or *** and is really a calling but a user might think of as the called party)<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Queue event log<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=362 2023-06-12T03:30:47Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are thousands of permutations to consider.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)<br /> * SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> * Take call feature prefix<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> * Transfer by party which did call pickup (using ** or *** and is really a calling but a user might think of as the called party)<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=361 2023-06-09T01:10:24Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Getting the source code ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;<br /> <br /> Then &lt;code&gt;cd&lt;/code&gt; into the root directory of the git clone.<br /> <br /> === Compiling messaged in 3.15 and below ===<br /> <br /> You should be able to run &lt;code&gt;go build&lt;/code&gt;, but it may not work with recent versions of Go.<br /> <br /> === Compiling messaged in 4.0 and above ===<br /> <br /> Run: &lt;code&gt;make&lt;/code&gt;<br /> <br /> If subsequent runs of make don't do anything, delete the compiled &lt;code&gt;messaged&lt;/code&gt; first and then try again.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=360 2023-06-09T01:03:37Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Getting the source code ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;<br /> <br /> Then &lt;code&gt;cd&lt;/code&gt; into the root directory of the git clone.<br /> <br /> === Compiling messaged in 3.15 and below ===<br /> <br /> You should be able to run &lt;code&gt;go build&lt;/code&gt;, but it may not work with recent versions of Go.<br /> <br /> === Compiling messaged in 4.0 and above ===<br /> <br /> Run: &lt;code&gt;make&lt;/code&gt;<br /> <br /> If subsequent runs of make don't do anything you can instead run: &lt;code&gt;go build cmd/messaged&lt;/code&gt;<br /> <br /> Note that the 4.1 code was copied to 4.0 in ticket #8215 to take advantage of the better compilation system.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=359 2023-06-07T03:08:48Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Getting the source code ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;<br /> <br /> Then &lt;code&gt;cd&lt;/code&gt; into the root directory of the git clone.<br /> <br /> === Compiling messaged in 4.0 and below ===<br /> <br /> You should be able to run &lt;code&gt;go build&lt;/code&gt;, but it may not work with recent versions of Go.<br /> <br /> === Compiling messaged in 4.1 and above ===<br /> <br /> Run: &lt;code&gt;make&lt;/code&gt;<br /> <br /> If subsequent runs of make don't do anything you can instead run: &lt;code&gt;go build cmd/messaged&lt;/code&gt;</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=358 2023-06-07T03:08:13Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Getting the source code ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;<br /> <br /> Then &lt;code&gt;cd&lt;/code&gt; into the root directory of the git clone.<br /> <br /> === Compiling messaged in 4.0 and below ===<br /> <br /> You should be able to run &lt;code&gt;go build&lt;/code&gt;, but it may not work with recent versions of Go.<br /> <br /> === Compiling messaged in 4.1 and above ===<br /> <br /> Run &lt;code&gt;make&lt;/code&gt;.<br /> <br /> If subsequent runs of &lt;code&gt;make&lt;/code&gt; don't do anything you can run &lt;code&gt;go build cmd/messaged&lt;/code&gt; instead.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=357 2023-06-07T03:08:01Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Getting the source code ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;.<br /> <br /> Then &lt;code&gt;cd&lt;/code&gt; into the root directory of the git clone.<br /> <br /> === Compiling messaged in 4.0 and below ===<br /> <br /> You should be able to run &lt;code&gt;go build&lt;/code&gt;, but it may not work with recent versions of Go.<br /> <br /> === Compiling messaged in 4.1 and above ===<br /> <br /> Run &lt;code&gt;make&lt;/code&gt;.<br /> <br /> If subsequent runs of &lt;code&gt;make&lt;/code&gt; don't do anything you can run &lt;code&gt;go build cmd/messaged&lt;/code&gt; instead.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=356 2023-06-06T00:02:52Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Compiling messaged ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;.<br /> <br /> Then from the root directory of the git clone you can run &lt;code&gt;make&lt;/code&gt;.<br /> <br /> If subsequent runs of &lt;code&gt;make&lt;/code&gt; don't do anything you can run &lt;code&gt;go build cmd/messaged&lt;/code&gt; instead.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=346 2023-05-24T02:17:51Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Compiling messaged ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 &lt;username&gt;@git.integrics.com:enswitch&lt;/code&gt;.<br /> <br /> Then from the root directory of the git clone you can run &lt;code&gt;make&lt;/code&gt;.<br /> <br /> If subsequent runs of &lt;code&gt;make&lt;/code&gt; don't do anything you can run &lt;code&gt;go build ./cmd/messaged&lt;/code&gt; instead.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=345 2023-05-24T01:47:34Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Compiling messaged ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout -b 4.2 git@git.integrics.com:enswitch&lt;/code&gt;.<br /> <br /> Then from the root directory of the git clone you can run &lt;code&gt;make&lt;/code&gt;.<br /> <br /> If subsequent runs of &lt;code&gt;make&lt;/code&gt; don't do anything you can run &lt;code&gt;go build ./cmd/messaged&lt;/code&gt; instead.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=344 2023-05-24T01:38:55Z

<p>Dcunningham: </p> <hr /> <div>=== Installing go ===<br /> <br /> Copy a download link for the latest .linux-amd64.tar.gz from: https://go.dev/dl/<br /> <br /> Download it on your development/build machine: &lt;code&gt;wget &lt;download url&gt;&lt;/code&gt;<br /> <br /> Install into /usr/local: &lt;code&gt;tar -C /usr/local -xvf &lt;file downloaded&gt;&lt;/code&gt;<br /> <br /> === Compiling messaged ===<br /> <br /> The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout 4.2&lt;/code&gt;.<br /> <br /> Then from the root directory of the git clone you can run &lt;code&gt;make&lt;/code&gt;.<br /> <br /> If subsequent runs of &lt;code&gt;make&lt;/code&gt; don't do anything you can run &lt;code&gt;go build ./cmd/messaged&lt;/code&gt; instead.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Messaged_compilation&diff=343 2023-05-03T23:45:51Z

<p>Dcunningham: Created page with &quot;The Enswitch messaged program is held in the git repository. Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout 4.2&lt;/code&gt;. The...&quot;</p> <hr /> <div>The Enswitch messaged program is held in the git repository.<br /> <br /> Check out the branch for the Enswitch version you're working on, for example: &lt;code&gt;git checkout 4.2&lt;/code&gt;.<br /> <br /> Then from the root directory of the git clone you can run &lt;code&gt;make&lt;/code&gt;.<br /> <br /> If subsequent runs of &lt;code&gt;make&lt;/code&gt; don't do anything you can run &lt;code&gt;go build ./cmd/messaged&lt;/code&gt; instead.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=295 2022-10-22T04:06:36Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are thousands of permutations to consider.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)<br /> * SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> * Transfer by party which did call pickup (using ** or *** and is really a calling but a user might think of as the called party)<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=294 2022-10-22T04:04:57Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,500 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)<br /> * SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> * Transfer by party which did call pickup (using ** or *** and is really a calling but a user might think of as the called party)<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enabling_Messages&diff=293 2022-08-03T03:23:38Z

<p>Dcunningham: </p> <hr /> <div>SMS messages are sent using:<br /> * SIP SIMPLE messages when the destination is a phone registered with Enswitch.<br /> * A custom script for external destinations.<br /> <br /> Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics. In 3.15 and later inbound SMS messages can be send to the web API methods at:<br /> * /api/bandwidth/<br /> * /api/twilio/<br /> * Any custom-written API which then uses Integrics::Enswitch::Texts or the messages/text/send JSON API method.<br /> <br /> The outbound custom script:<br /> * Must be customised for each provider to match the protocol they use<br /> * Is located at: &lt;code&gt;/usr/local/sbin/enswitch_message_out&lt;/code&gt;<br /> * Must be on the same machines as enswitch_sipd.<br /> * Should be careful to properly escape characters in the message.<br /> <br /> Here is an [[SMS_Send_Script_Example|example]] enswitch_message_out script to send requests via HTTP.<br /> <br /> Besides customising this script, you need to:<br /> * In System -&gt; Configuration set &quot;Enable text messages&quot; (or &quot;Enable messaging&quot; in 3.13 and earlier) to Yes.<br /> * Restart enswitch_sipd.<br /> * In System -&gt; Roles set &quot;Actions » Send a message&quot; to &quot;Yes&quot; for desired roles.<br /> * In System -&gt; Routes create routes with the &quot;Media type&quot; set to &quot;Message&quot;.<br /> * In System -&gt; Peers for each peer which is used by a message route, edit the outbound costs and define the &quot;Cost to send a message&quot;.<br /> * In each Rate plan set:<br /> ** Features -&gt; &quot;Send SMS messages&quot; to &quot;Allow&quot;.<br /> ** Optionally, set relevant fields in &quot;Default markups&quot; and &quot;Included in rate plan&quot;.<br /> ** Optionally, set &quot;Outbound call cost exceptions&quot; -&gt; &quot;Cost to send message&quot;.<br /> We recommend your configuration is thoroughly tested prior to making it available to users.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enabling_Messages&diff=292 2022-08-03T03:23:02Z

<p>Dcunningham: </p> <hr /> <div>SMS messages are sent using:<br /> * SIP SIMPLE messages when the destination is a phone registered with Enswitch.<br /> * A custom script for external destinations.<br /> <br /> Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics. In 3.15 and later inbound SMS messages can be send to the web API methods at:<br /> * /api/bandwidth/<br /> * /api/twilio/<br /> * Any custom-written API which then uses Integrics::Enswitch::Texts or the messages/text/send JSON API method.<br /> <br /> The custom script:<br /> * Must be customised for each provider to match the protocol they use<br /> * Is located at: &lt;code&gt;/usr/local/sbin/enswitch_message_out&lt;/code&gt;<br /> * Must be on the same machines as enswitch_sipd.<br /> <br /> Here is an [[SMS_Send_Script_Example|example]] enswitch_message_out script to send requests via HTTP.<br /> <br /> Besides customising this script, you need to:<br /> * In System -&gt; Configuration set &quot;Enable text messages&quot; (or &quot;Enable messaging&quot; in 3.13 and earlier) to Yes.<br /> * Restart enswitch_sipd.<br /> * In System -&gt; Roles set &quot;Actions » Send a message&quot; to &quot;Yes&quot; for desired roles.<br /> * In System -&gt; Routes create routes with the &quot;Media type&quot; set to &quot;Message&quot;.<br /> * In System -&gt; Peers for each peer which is used by a message route, edit the outbound costs and define the &quot;Cost to send a message&quot;.<br /> * In each Rate plan set:<br /> ** Features -&gt; &quot;Send SMS messages&quot; to &quot;Allow&quot;.<br /> ** Optionally, set relevant fields in &quot;Default markups&quot; and &quot;Included in rate plan&quot;.<br /> ** Optionally, set &quot;Outbound call cost exceptions&quot; -&gt; &quot;Cost to send message&quot;.<br /> We recommend your configuration is thoroughly tested prior to making it available to users.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enabling_Messages&diff=287 2022-06-03T01:34:11Z

<p>Dcunningham: </p> <hr /> <div>SMS messages are sent using:<br /> * SIP SIMPLE messages when the destination is a phone registered with Enswitch.<br /> * A custom script for external destinations.<br /> <br /> Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics.<br /> <br /> The custom script:<br /> * Must be customised for each provider to match the protocol they use<br /> * Is located at: &lt;code&gt;/usr/local/sbin/enswitch_message_out&lt;/code&gt;<br /> * Must be on the same machines as enswitch_sipd.<br /> <br /> Here is an [[SMS_Send_Script_Example|example]] enswitch_message_out script to send requests via HTTP.<br /> <br /> Besides customising this script, you need to:<br /> * In System -&gt; Configuration set &quot;Enable text messages&quot; (or &quot;Enable messaging&quot; in 3.13 and earlier) to Yes.<br /> * Restart enswitch_sipd.<br /> * In System -&gt; Roles set &quot;Actions » Send a message&quot; to &quot;Yes&quot; for desired roles.<br /> * In System -&gt; Routes create routes with the &quot;Media type&quot; set to &quot;Message&quot;.<br /> * In System -&gt; Peers for each peer which is used by a message route, edit the outbound costs and define the &quot;Cost to send a message&quot;.<br /> * In each Rate plan set:<br /> ** Features -&gt; &quot;Send SMS messages&quot; to &quot;Allow&quot;.<br /> ** Optionally, set relevant fields in &quot;Default markups&quot; and &quot;Included in rate plan&quot;.<br /> ** Optionally, set &quot;Outbound call cost exceptions&quot; -&gt; &quot;Cost to send message&quot;.<br /> We recommend your configuration is thoroughly tested prior to making it available to users.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enabling_Messages&diff=286 2022-06-03T01:33:58Z

<p>Dcunningham: </p> <hr /> <div>SMS messages are sent using:<br /> * SIP SIMPLE messages when the destination is a phone registered with Enswitch.<br /> * A custom script for external destinations.<br /> <br /> Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics.<br /> <br /> The custom script:<br /> * Must be customised for each provider to match the protocol they use<br /> * Is located at: &lt;code&gt;/usr/local/sbin/enswitch_message_out&lt;/code&gt;<br /> * Must be on the same machines as enswitch_sipd.<br /> <br /> Here is an [[SMS_Send_Script_Example|example]] enswitch_message_out script to send requests via HTTP.<br /> <br /> Besides customising this script, you need to:<br /> * In System -&gt; Configuration set &quot;Enable text messages&quot; (or &quot;Enable messaging&quot; in 3.13 and earlier) to Yes.<br /> * Restart enswitch_sipd.<br /> <br /> In System -&gt; Roles set &quot;Actions » Send a message&quot; to &quot;Yes&quot; for desired roles.<br /> In System -&gt; Routes create routes with the &quot;Media type&quot; set to &quot;Message&quot;.<br /> In System -&gt; Peers for each peer which is used by a message route, edit the outbound costs and define the &quot;Cost to send a message&quot;.<br /> * In each Rate plan set:<br /> ** Features -&gt; &quot;Send SMS messages&quot; to &quot;Allow&quot;.<br /> ** Optionally, set relevant fields in &quot;Default markups&quot; and &quot;Included in rate plan&quot;.<br /> ** Optionally, set &quot;Outbound call cost exceptions&quot; -&gt; &quot;Cost to send message&quot;.<br /> We recommend your configuration is thoroughly tested prior to making it available to users.</div>

Dcunningham http://wiki.integrics.com/index.php?title=SELinux_building_module&diff=285 2022-05-05T00:02:07Z

<p>Dcunningham: Created page with &quot;To check for SELinux audit entries: &lt;pre&gt; audit2allow -a -b &lt;/pre&gt; To turn SELinux audit entries into a new SELinux module: &lt;pre&gt; audit2allow -a -b -M enswitch &lt;/pre&gt; To com...&quot;</p> <hr /> <div>To check for SELinux audit entries:<br /> &lt;pre&gt;<br /> audit2allow -a -b<br /> &lt;/pre&gt;<br /> <br /> To turn SELinux audit entries into a new SELinux module:<br /> &lt;pre&gt;<br /> audit2allow -a -b -M enswitch<br /> &lt;/pre&gt;<br /> <br /> To compile the SELinux module for Enswitch:<br /> &lt;pre&gt;<br /> cd /opt/enswitch/current/etc/selinux<br /> checkmodule -M -m -o enswitch.mod enswitch.te<br /> semodule_package -o enswitch.pp -m enswitch.mod<br /> semodule -i enswitch.pp<br /> rm enswitch.mod<br /> &lt;/pre&gt;</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=284 2022-04-25T22:42:33Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,500 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)<br /> * SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> * Transfer by party which did call pickup (using ** or *** and is really a calling but should be treated as a called party)<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=283 2022-04-01T00:01:24Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,500 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second (first call's Call-ID is in the Refer-To data)<br /> * SIP REFER attended transfer, second calls transferred to first (second call's Call-ID is in the Refer-To data, used by Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=282 2022-03-31T23:59:50Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,500 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second<br /> * SIP REFER attended transfer, second calls transferred to first (Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Transferred call is direct to telephone line<br /> * Transferred call is via queue or hunt group (adds a Local dial)<br /> * Transferred call is to external destination<br /> * Transfer destination is direct to telephone line<br /> * Transfer destination is via queue or hunt group (adds a Local dial)<br /> * Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=281 2022-03-31T23:59:26Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,500 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second<br /> * SIP REFER attended transfer, second calls transferred to first (Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> - Transferred call is direct to telephone line<br /> - Transferred call is via queue or hunt group (adds a Local dial)<br /> - Transferred call is to external destination<br /> - Transfer destination is direct to telephone line<br /> - Transfer destination is via queue or hunt group (adds a Local dial)<br /> - Transfer destination is to external destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=280 2022-03-31T23:58:05Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,500 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second<br /> * SIP REFER attended transfer, second calls transferred to first (Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing (billed correctly)<br /> * Call recording (records all call legs with no duplicates)</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=279 2022-03-31T03:14:27Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,500 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second<br /> * SIP REFER attended transfer, second calls transferred to first (Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=278 2022-03-31T03:14:04Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,000 possible checks.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second<br /> * SIP REFER attended transfer, second calls transferred to first (Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=277 2022-03-31T03:13:18Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,000 possible items to check are working.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer, first call transferred to second<br /> * SIP REFER attended transfer, second calls transferred to first (Polycom)<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=276 2022-03-31T00:47:07Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations - over 2,000 possible items to check are working.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=275 2022-03-31T00:45:30Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=274 2022-03-31T00:45:10Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Servers:<br /> * Call legs on all same Asterisk server<br /> * Call legs across multiple Asterisk servers in cluster<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call<br /> * Ensure no calls legs are left stale in active table</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=273 2022-03-31T00:43:53Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transfer by calling party<br /> * Transfer by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call<br /> * Ensure no calls legs are left stale in active table</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=272 2022-03-31T00:43:14Z

<p>Dcunningham: </p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transferred by calling party<br /> * Transferred by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> * Transfer destination does not answer call<br /> * Call park times out and rings back parking party<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination<br /> <br /> Affected features:<br /> * Control panel (uses active table)<br /> * Busy lamps (uses active table)<br /> * Queue destinations (uses active and queue_destinations tables)<br /> * Billing of call<br /> * Ensure no calls legs are left stale in active table</div>

Dcunningham http://wiki.integrics.com/index.php?title=Transfer_types&diff=271 2022-03-31T00:38:58Z

<p>Dcunningham: Created page with &quot;The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations. Methods: * Features.conf attended transfer *...&quot;</p> <hr /> <div>The following are types of transfer in Enswitch. Taking in combination with each other, there are a lot of possible permutations.<br /> <br /> Methods:<br /> * Features.conf attended transfer<br /> * Features.conf blind transfer<br /> * SIP REFER attended transfer<br /> * SIP REFER blind transfer<br /> * SIP 302 redirection<br /> * Asterisk AMI redirect (eg web control panel)<br /> * Call park<br /> * Holding slots<br /> <br /> Party:<br /> * Transferred by calling party<br /> * Transferred by called party<br /> <br /> Call status:<br /> * Transferred call was answered when transfer starts<br /> * Transferred call was ringing when transfer starts<br /> * Transfer destination was answered when transfer completes<br /> * Transfer destination was ringing when transfer completes<br /> <br /> Features:<br /> * Direct to telephone line<br /> * To telephone via queue or hunt group (adds a Local dial)<br /> * External destination</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enabling_Messages&diff=270 2022-02-16T20:06:10Z

<p>Dcunningham: </p> <hr /> <div>SMS messages are sent using:<br /> * SIP SIMPLE messages when the destination is a phone registered with Enswitch.<br /> * A custom script for external destinations.<br /> <br /> Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics.<br /> <br /> The custom script:<br /> * Must be customised for each provider to match the protocol they use<br /> * Is located at: &lt;code&gt;/usr/local/sbin/enswitch_message_out&lt;/code&gt;<br /> * Must be on the same machines as enswitch_sipd.<br /> <br /> Here is an [[SMS_Send_Script_Example|example]] enswitch_message_out script to send requests via HTTP.<br /> <br /> Besides customising this script, you need to:<br /> * In System -&gt; Configuration set &quot;Enable text messages&quot; (or &quot;Enable messaging&quot; in 3.13 and earlier) to Yes.<br /> * Restart enswitch_sipd.<br /> * In System -&gt; Roles set &quot;Actions » Send a message&quot; to Yes for desired roles.<br /> * In each Peer used for messaging, in the outbound costs define the &quot;Cost to send a message&quot;.<br /> * In each Route used for messaging, define the &quot;Peer for messages&quot;.<br /> * In each Rate plan set:<br /> ** Features -&gt; &quot;Send SMS messages&quot; to &quot;Allow&quot;.<br /> ** Optionally, set relevant fields in &quot;Default markups&quot; and &quot;Included in rate plan&quot;.<br /> ** Optionally, set &quot;Outbound call cost exceptions&quot; -&gt; &quot;Cost to send message&quot;.<br /> We recommend your configuration is thoroughly tested prior to making it available to users.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Compiling_AngularJS_interface&diff=269 2022-02-15T20:48:08Z

<p>Dcunningham: </p> <hr /> <div><br /> === Current instructions ===<br /> <br /> You should follow the instructions in web/README.md on the Enswitch server.<br /> <br /> === Old instructions ===<br /> <br /> NodeJS version should be &gt;=12.0.0 and &lt;=12.14.1 (tested, but probably works on anything &gt;=12).<br /> <br /> As root:<br /> <br /> On Ubuntu:<br /> Install nodejs version 12 from: https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-ubuntu-18-04<br /> <br /> On Debian based systems:<br /> apt-get install nodejs<br /> <br /> On Redhat based systems:<br /> curl --silent --location https://rpm.nodesource.com/setup_6.x | bash -<br /> yum install nodejs<br /> <br /> Then:<br /> cd /opt/enswitch/current/web<br /> npm install<br /> npm install -g bower<br /> npm install -g gulp<br /> ln -s /usr/bin/nodejs /usr/local/bin/node<br /> bower --allow-root install<br /> gulp build<br /> <br /> Apache can now serve from /opt/enswitch/current/web/dist/.<br /> <br /> Alternatively you can run a development version using &quot;gulp serve&quot;. You should use the URL on port 3000, and allow access to it through the firewall.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Compiling_AngularJS_interface&diff=268 2022-02-15T03:00:11Z

<p>Dcunningham: </p> <hr /> <div>NodeJS version should be &gt;=12.0.0 and &lt;=12.14.1 (tested, but probably works on anything &gt;=12).<br /> <br /> As root:<br /> <br /> On Ubuntu:<br /> Install nodejs version 12 from: https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-ubuntu-18-04<br /> <br /> On Debian based systems:<br /> apt-get install nodejs<br /> <br /> On Redhat based systems:<br /> curl --silent --location https://rpm.nodesource.com/setup_6.x | bash -<br /> yum install nodejs<br /> <br /> Then:<br /> cd /opt/enswitch/current/web<br /> npm install<br /> npm install -g bower<br /> npm install -g gulp<br /> ln -s /usr/bin/nodejs /usr/local/bin/node<br /> bower --allow-root install<br /> gulp build<br /> <br /> Apache can now serve from /opt/enswitch/current/web/dist/.<br /> <br /> Alternatively you can run a development version using &quot;gulp serve&quot;. You should use the URL on port 3000, and allow access to it through the firewall.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Compiling_AngularJS_interface&diff=253 2021-04-13T21:19:16Z

<p>Dcunningham: </p> <hr /> <div>NodeJS version should be &gt;=12.0.0 and &lt;=12.14.1 (tested, but probably works on anything &gt;=12).<br /> <br /> As root:<br /> <br /> On Debian based systems:<br /> apt-get install nodejs<br /> <br /> On Redhat based systems:<br /> curl --silent --location https://rpm.nodesource.com/setup_6.x | bash -<br /> yum install nodejs<br /> <br /> Then:<br /> cd /opt/enswitch/current/web<br /> npm install<br /> npm install -g bower<br /> npm install -g gulp<br /> ln -s /usr/bin/nodejs /usr/local/bin/node<br /> bower --allow-root install<br /> gulp build<br /> <br /> Apache can now serve from /opt/enswitch/current/web/dist/.<br /> <br /> Alternatively you can run a development version using &quot;gulp serve&quot;. You should use the URL on port 3000, and allow access to it through the firewall.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enswitch_Client_apps&diff=251 2020-09-29T20:47:56Z

<p>Dcunningham: </p> <hr /> <div>Enswitch has client apps for:<br /> * Android: from Google Play<br /> * [[Enswitch Client for iOS|iOS]]: from App Store<br /> * Windows: from https://download.integrics.com/windows/enswitch_windows.msi</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enswitch_Client_apps&diff=250 2020-09-29T20:47:02Z

<p>Dcunningham: Created page with &quot;Enswitch has client apps for: * Android: from Google Play * iPhone: from App Store * Windows: from https://download.integrics.com/windows/enswitch_windows.msi&quot;</p> <hr /> <div>Enswitch has client apps for:<br /> * Android: from Google Play<br /> * iPhone: from App Store<br /> * Windows: from https://download.integrics.com/windows/enswitch_windows.msi</div>

Dcunningham http://wiki.integrics.com/index.php?title=Security_Considerations&diff=248 2020-09-08T03:52:42Z

<p>Dcunningham: </p> <hr /> <div>Technical:<br /> * Disallow routes to countries that customers don't need, especially high fraud countries. This is set in System -&gt; Routes.<br /> * Set a daily spending limit and maximum concurrent calls limit for all customers. This is set in customers and rate plan fields &quot;Maximum call spending per day&quot; and &quot;Maximum concurrent total calls&quot;.<br /> * Set phones and people to be locked out after too many failed login attempts. This is set in the &quot;Telephone line failed registrations lock&quot; and &quot;Person failed logins lock&quot; system configurations.<br /> * Require long password lengths for phones and people. This is set in the &quot;Person minimum password length&quot; and &quot;Telephone line minimum password length&quot; system configurations.<br /> * Change the SSH port from 22 to something non-standard.<br /> * Use iptables to lock out countries where you do not have customers.<br /> * Set Asterisk servers to use non default ports for SIP like 5065 instead of 5060.<br /> * Make sure all handsets have a username and password which are not the devices default.<br /> * Monitor servers with a tool like Zabbix, Nagios, or Cacti to alert if there are more calls than expected.<br /> * Use SIPSentry to automatically block brute-force attacks: http://sipsentry.com/<br /> <br /> Secure provisioning with a solution such as:<br /> * Use a provisioning password in Enswitch 4.1 and above. This is set in the &quot;Provision password global&quot; system configuration.<br /> * Restrict telephones to specific IP address(es). This is set in the &quot;Only allow from source IP address(es)&quot; field on the edit telephone line page.<br /> * Restrict access by user-agent, by customising the Apache configuration.<br /> * Restrict access to a private domain, by customising the Apache configuration.<br /> * Use HTTP basic authentication if supported by telephones, by customising the Apache configuration.<br /> * Use TFTP username and password authentication if supported by telephones, by customising the TFTP configuration.<br /> <br /> Non-technical:<br /> * Educate customers on choosing good passwords.<br /> * Have contracts to make sure the right person pays if they are hacked and run up a huge bill.</div>

Dcunningham http://wiki.integrics.com/index.php?title=Kamailio_patch_to_stop_crashes_with_TCP_traffic&diff=245 2020-05-26T00:54:54Z

<p>Dcunningham: </p> <hr /> <div>On some systems running Enswitch 3.14 or higher we've noticed Kamailio can crash if there is TCP traffic. The following patch was provided by Daniel-Constantin Mierla to fix it. Apparently the fix went into the 5.1 and 5.2 branches in October 2019. <br /> <br /> Replace the exiting functions unload_perl() and perl_reload() from modules/app_perl/app_perl_mod.c or src/modules/app_perl/app_perl_mod.c file with the next content:<br /> <br /> &lt;pre&gt;<br /> /*<br /> *<br /> */<br /> int unload_perl(PerlInterpreter *p) {<br /> /* clean and reset everything */<br /> PL_perl_destruct_level = 1;<br /> perl_destruct(p);<br /> perl_free(p);<br /> <br /> return 0;<br /> }<br /> <br /> <br /> /*<br /> * reload function.<br /> * Reinitializes the interpreter. Works, but execution for _all_<br /> * children is difficult.<br /> */<br /> int perl_reload(void)<br /> {<br /> if(my_perl) {<br /> unload_perl(my_perl);<br /> }<br /> my_perl = parser_init();<br /> <br /> #ifdef PERL_EXIT_DESTRUCT_END<br /> PL_exit_flags |= PERL_EXIT_DESTRUCT_END;<br /> #else<br /> #warning Perl 5.8.x should be used. Please upgrade.<br /> #warning This binary will be unsupported.<br /> PL_exit_flags |= PERL_EXIT_EXPECTED;<br /> #endif<br /> <br /> if(my_perl) {<br /> LM_DBG(&quot;new perl interpreter initialized\n&quot;);<br /> return 0;<br /> } else {<br /> LM_CRIT(&quot;failed to initialize a new perl interpreter - exiting\n&quot;);<br /> exit(-1);<br /> }<br /> }<br /> &lt;/pre&gt;</div>

Dcunningham http://wiki.integrics.com/index.php?title=Kamailio_patch_to_stop_crashes_with_TCP_traffic&diff=244 2020-05-25T07:01:27Z

<p>Dcunningham: </p> <hr /> <div>On some systems running Enswitch 3.14 or higher we've noticed Kamailio can crash if there is TCP traffic. The following patch was provided by Daniel-Constantin Mierla to fix it. Apparently the fix went into the 5.1 and 5.2 branches in October 2019. <br /> <br /> Replace the exiting functions unload_perl() and perl_reload() from modules/app_perl/app_perl_mod.c file with the next content:<br /> <br /> &lt;pre&gt;<br /> /*<br /> *<br /> */<br /> int unload_perl(PerlInterpreter *p) {<br /> /* clean and reset everything */<br /> PL_perl_destruct_level = 1;<br /> perl_destruct(p);<br /> perl_free(p);<br /> <br /> return 0;<br /> }<br /> <br /> <br /> /*<br /> * reload function.<br /> * Reinitializes the interpreter. Works, but execution for _all_<br /> * children is difficult.<br /> */<br /> int perl_reload(void)<br /> {<br /> if(my_perl) {<br /> unload_perl(my_perl);<br /> }<br /> my_perl = parser_init();<br /> <br /> #ifdef PERL_EXIT_DESTRUCT_END<br /> PL_exit_flags |= PERL_EXIT_DESTRUCT_END;<br /> #else<br /> #warning Perl 5.8.x should be used. Please upgrade.<br /> #warning This binary will be unsupported.<br /> PL_exit_flags |= PERL_EXIT_EXPECTED;<br /> #endif<br /> <br /> if(my_perl) {<br /> LM_DBG(&quot;new perl interpreter initialized\n&quot;);<br /> return 0;<br /> } else {<br /> LM_CRIT(&quot;failed to initialize a new perl interpreter - exiting\n&quot;);<br /> exit(-1);<br /> }<br /> }<br /> &lt;/pre&gt;</div>

Dcunningham http://wiki.integrics.com/index.php?title=Enswitch_SIP_Trunking&diff=243 2020-04-15T00:51:17Z

<p>Dcunningham: </p> <hr /> <div>Creating a SIP trunk with Enswitch can be done, as follows.<br /> <br /> ===Outbound calls===<br /> <br /> * The remote device can register as a normal telephone line. If the telephone line has caller ID set to &quot;Original&quot; then Enswitch will pass whatever the remote device sets as the caller ID.<br /> * You can set up a Remote Access account to allow calls from a fixed IP address. You need to set the type to &quot;Dial the called number&quot; and enter the source IP address. This means the remote device does not have to register with Enswitch to make outbound calls.<br /> <br /> ===Inbound calls===<br /> <br /> * If you're happy with having one destination number on the remote device, you can route a normal number to the telephone line the remote system registers with.<br /> * You can create multiple numbers routing to the same telephone line, and then set the telephone line option &quot;Send called number as request URI&quot; to Yes. This will send the call to &lt;dialled number&gt;@&lt;telephone line registered IP address&gt;.<br /> * If the remote device is not registered as a telephone line, you can send calls to a fixed address using the SIP URI destination type.</div>

Dcunningham