How to create tar.gz?
You can create tar.gz file with the following command.DO NOT ENTER / after the directory name.
tar -cvzf test.tar.gz test
You can create tar.gz file with the following command.DO NOT ENTER / after the directory name.
tar -cvzf test.tar.gz test
“fs.file-max = 65536″
adding this one in sysctl.conf
and then “sysctl -p”
switch to /etc/securitty/limits.conf and add ther following lines
* hard nofile 65536
* soft nofile 16384
switch 2 user for which u need to increase the file-max for, with this the default for all users will be 16384,
u can increase with ulimit -n XXXX now
In the var_config.cfg file, you can now turn on a feature to block incoming
H323 calls. Set the following two lines:
H323Q931PortFlag 1
H323Q931PortNum 1788 or some other number for listening port (other than 0)”
Save as var_config.cfg and upload via FTP.
From the root prompt on your server, invoke the CPAN shell:
#perl -MCPAN -e shell
Once the Perl interpreter has loaded (and been configured), you can install modules with: install .MODULENAME
The first thing you should do is upgrade your CPAN:
cpan>install Bundle::CPAN
Once it is completed, type:
cpan>reload cpan
Now, enter the following command to retrieve all of the required modules:
cpan> install DateTime
Note
Be aware that after freshly installing make / gcc, your perl installation will not necessarily detect it. This means module installation will still fail during the 'make' stage. You may need to invoke the CPAN shell and run the setup routine again, to point to the location of make:
# perl -MCPAN -e shell CPAN
cpan> o conf make /usr/bin/make
cpan> o conf commit
execute this in your shell before you start Application
ulimit -c unlimited
ulimit -d unlimited
ulimit -f unlimited
ulimit -i unlimited
ulimit -n 999999
ulimit -q unlimited
ulimit -u unlimited
ulimit -v unlimited
ulimit -x unlimited
ulimit -s 244
ulimit -l unlimited
Incoming call-limit can be controlled in FreeSWITCH from user directory for example:
<document type=”freeswitch/xml”>
<section name=”directory”>
<domain name=”192.168.0.2″>
<user id=”some_user”>
<params>
<param name=”password” value=”some_password”/>
</params>
<variables>
<variable name=”accountcode” value=”315″/>
<variable name=”user_context” value=”default”/>
<variable name=”vm_extension” value=”315″/>
<variable name=”max_calls” value=”1″/>
</variables>
</user>
</domain>
</section>
</document>
The following channel variables are set when mod_limit is called.
These channel variables are used at hang up to remove the record. More specifically, the delete is limited by uuid, hostname, realm and id.
<extension name=”Outbound Limit”>
<condition field=”destination_number” expression=”^00″/>
<action application=”limit” data=”$${domain} gw_PROVIDER PROVIDER_CHANNEL_LIMIT nextgw1″/>
<action application=”bridge” data=”sofia/gateway/PROVIDER/1$1″/>
<action application=”transfer” data=”nextgw1″/>
</condition>
</extension>
The following example shows how a DID can bridge to multiple extensions or gateways sequentially in a hunt pattern. In Asterisk, this feature is called FollowMe. If none of the bridges are successful the caller is sent to voicemail for example.
<extension name=”12531234567″>
<condition field=”destination_number” expression=”12531234567″>
<action application=”set” data=”hangup_after_bridge=true”/>
<action application=”set” data=”continue_on_fail=true”/>
<action application=”set” data=”ignore_early_media=true”/>
<action application=”set” data=”call_timeout=10″/>
<action application=”bridge” data=”sofia/$${domain}/1001″/>
<action application=”set” data=”call_timeout=13″/>
<action application=”bridge” data=”sofia/gateway/isoftswitch/123456789″ />
<!– No answer, transfer to voicemail –>
<action application=”answer”/>
<action application=”sleep” data=”1000″/>
<action application=”voicemail” data=”default $${domain} 1001″/>
</condition>
</extension>
Forked dial is when you want to attempt to ring 2 destinations at the same time. Freeswitch will attempt to call both bridge options simultaneously. The first bridge leg that replies with a 183 (session progress) message will win the call, and the other bridge leg is dropped. This only will work if you enable inbound-late-negotiation in the profile this recipe is executing under ( not in the bridged-to profile ).
an example is:
<extension name="dialoutpstn">
<condition field="destination_number" expression="^((00).*)$">
<action application="set" data="hangup_after_bridge=true"/>
<action application="set" data="ignore_early_media=true"/>
<action application="bridge" data="sofia/gateway/gatewayA/$1@1.2.3.4,sofia/gateway/gatewayB/$1@4.5.6.7"/>
</condition>
</extension>