Asterisk - Eduguru - Page 15

Better SIP Security on Asterisk: How To Secure Asterisk

June 21, 2014April 28, 2018 eduguru 0 Comments again at least 12 characters with a complex mix of symbols, and a mix of upper and lowercase letters at least 12 digits long. 4) Block your AMI manager ports. Use “permit=” and “deny=” lines in manager.conf to reduce inbound connections to known hosts only. Us, and letters. 5) Allow only one or two calls at a time per SIP entity, asterisk-securitySeven Easy Steps to Better SIP Security on Asterisk: 1) Don’t accept SIP authentication requests from all IP addresses. Use the “permit=” and “deny=” lines in sip.conf to only allow a, Better SIP Security on Asterisk: How To Secure Asterisk, denying remote attackers the ability to detect existing extensions with brute-force guessing attacks. 3) Use STRONG passwords for SIP entities. This is probably the most important step you can take. D, for instance, limiting your exposure to toll fraud is a wise thing to do. This also limits your exposure when legitimate password holders on your system lose control of their passphrase – writing it on the bottom o, numbers, or some sort of combination of a common phrase + extension MD5 hash (example: from a shell prompt, this is an easy target for attackers to guess SIP authentication names. Use the MAC address of the device, try “md5 -s ThePassword5000″) 7) Ensure your [default] context is secure. Don’t allow unauthenticated callers to reach any contexts that allow toll calls. Permit only a limited number of active calls , where possible. At the worst, which allows extension information leakage. Setting this to “yes” will reject bad authentication requests on valid usernames with the same rejection information as with invalid usernames, which I’ve seen. 6) Make your SIP usernames different than your extensions. While it is convenient to have extension “1234″ map to SIP entry “1234″ which is also SIP user “1234″, you’d understand that trivial obfuscation like that is a minor hinderance to a modern CPU. Use symbols

Seven Easy Steps to Better SIP Security on Asterisk: 1) Don’t accept SIP authentication requests from all IP addresses. Use

Asterisk Databse mysql

ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/lib /mysql/mysql.sock’ (2)

June 10, 2014February 24, 2016 eduguru 0 Comments [SOLVED] CentOS 6.5 - MySQL Daemon failed to start., 000 results (0.23 seconds) Search Results MySQL Daemon Failed to Start - centos 6 - Stack Overflow stackoverflow.com/questions/.../mysql-daemon-failed-to-start-centos-6 Dec 1, 2010 - 15 posts - ‎2 authors I'm really not sure what I'm doing wrong. I'm attempting to start mysql Code: [root@bebop-test /]# /etc/init.d/mysqld restart Stopping mysqld: [ OK ] MySQL Daemon failed t, 2013 - [root@sacroiliac log]# service mysqld start MySQL Daemon failed to start. Starting mysqld: [FAILED] [root@sacroiliac log]# service mysql start ... centos - Cent OS - MySQL Daemon failed to star, 2013 - 12 posts - ‎1 author Starting mysqld: [FAILED] Does anyone know what could be happening here? How to repeat: Run a yum update -y on a centos 6.4, 2013 - EDIT: Look at the checkmarked answer comments to get your issue .... The most likely cause for this error is that your mysql server is not running. You've visited this page 2 times. Last visit:, 2013 - Recently I started working on a very basic Drupal website for a friend, 2013 - Symptoms This article applies if you face any of the following symptoms: MySQL starts/stops properly when started/stopped with the mysqld ... startup - mysql server start failed - Ask Ubuntu as, 2014 - 10 posts - ‎2 authors 140115 17:21:35 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql ... chcon: failed to change context of `mysql' to ... MySQL Daemon Failed to Start af, 2014 - But mysqld.sock file doesn't exist inside /var/run/mysqld folder. On executing ps aux | grep mysql command, 2014 - Now I have restarted mysqld and it wont start. It has just stopped. I really need to get this up and running now. Its highly urgent for me. Below is ... Cannot start/stop/restart service: MySQL, 2014 - When trying restart mysqld service I'm getting this erroe: Cannot start/stop/restart service: MySQL Daemon failed to start. Anybody have idea ... MySQL Daemon failed to start. | DigitalOcean ht, and change its value to the database server host machine's IP address. For me, by doing that it sadly seems that it has overloaded mysql. Can it really be ... MySQL Daemon failed to start. - LinuxQuestions.org www.linuxquestions.org › Forums › Linux Forums › Linux - Software Nov, Can't connect to local MySQL server through socket, check the ... rhel - Problem Starting MySQL on new Centos 6 build - Unix ... unix.stackexchange.com/.../problem-starting-mysql-on-new-centos-6-bui... Dec 10, ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib /mysql/mysql.sock' (2), I realized that mysql server was not ... MySQL Bugs: #71086: Starting Mysql service on CentOS6.5 bugs.mysql.com/bug.php?id=71086 Dec 5, I tried the following steps: Log in as super user or use sudo Open /etc/mysql/my.cnf using gedit Check the all the configuration Find bind-address, it was localhost or 127.0.0.1 Save and close the file. Come back to terminal and execute sudo service mysql start And it worked for me., MySQL Daemon Failed to Start - centos 6, Searches related to mysql daemon failed to start. mysql daemon failed to start. starting mysqld failed mysql daemon failed to start. starting mysqld mysql daemon failed to start. starting mysqld cento

I tried the following steps: Log in as super user or use sudo Open /etc/mysql/my.cnf using gedit Check the all

ISDN hangup cause codes

June 10, 2014 eduguru 0 Comments (similar to cause 88). Some part of the format being used is not understood by either the remote side equipment or the switching equipment between the source and destination of the call. Code No. 97 -, a physical layer or data link layer failure at the remote party or user equipment off-line. Code No. 28 - invalid number format (address incomplete). This cause indicates that the called party cannot , all Telcos have their own system for programming the number formats that the switches will recognize. Some systems want to see 7 digits, although the number is in a valid format, and cause 100. Code No. l - Unallocated (unassigned) number. This cause indicates that the destination requested by the calling user cannot be reached because, and others 11. Code No. 52 - outgoing calls barred. Code No. 53 - outgoing calls barred within CUG. This cause indicates that although the calling party is a member of the CUG for the outgoing CUG cal, as defined in Recommendation X.213. cannot be provided (e.g., as it is invalid. 3. On long distance calls, but at this time they are proprietary in nature. The PRI equipment vendors are the most likely to use these codes as they have been using proprietary messages in the facilities data link for some time, but if it doesn't happen in the time allotted by the switch programming, but the reasons for it could be: 1. Bad username or password 2. Router's settings do not match what is expected by the remote end. 3. Telephone line problems. 4. Hung session on remote end. Code No. 1, but this call identify does not. This cause indicates that a call resume has been attempted with a call identity which differs from that in use for any presently suspended call(s). Code No. 84 - call , cause 88, Code No. 1, data rate) which cannot be accommodated. What it means: 1. This usually means that the Number To Dial in the Connection Profile is in the wrong format. You may need to dial a 10 or 11 digit number, dialing at 64K when only 56K is supported. Code No. 66 - channel type not implemented. This cause indicates that the equipment sending this cause does not support the channel type requested. Code No. , for example, giving a SPID failure in the router logs. 2. The ISDN phone number being dialed by the router is invalid and the telco switch cannot locate the number to complete the call, high layer compatibility or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic. Code No. 44 - req, if a user has subscribed to those channels on a primary rate interface numbered from l to 12 and the user equipment or the network attempts to use channels 3 through 23, if the equipment sending this cause is an intermediate point, immediately re-attempting the call is not likely to be successful. Code No. 39 - permanent frame mode connection out-of-service. This cause is included in a STATUS message to indicate that a permanent, indicating that the call was cleared due to a supplementary service constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection. What i, ISDN hangup cause codes, ISDN hangup cause codes provide information as to why a call has been terminated. The list of hangup cause codes below provides detailed information as to the underlying cause behind a call hangup: Co, it is not currently assigned (allocated). What it usually means: 1. The SPIDS may be incorrectly entered in the router or the Telco switch, low layer compatibility, one or more of the fields in the information element are coded in such a way which has not been implemented by the equipment sending this cause. What it means: Like cause 1 and cause 88, or a call will fail with this cause. Code No. 101 - message not compatible with call state. This cause indicates that a message has been received which is incompatible with the call state. Code No. 10, or a misconfiguration on the equipment being called. Code No. 22 - number changed. This cause is returned to a calling party when the called party number indicated by the calling party is no longer as, or a STATUS message was received indicating an incompatible call state. Code No. 99 - Information element / parameter non-existent or not implemented. This cause indicates that the equipment sending t, or dial a 9 in front of the number if it is a Centrex line. 2. This problem may also give a Cause 111. 3. Dialing at the wrong line speed can also give this Cause. Code No. 90 - non-existent CUG. This, some 10, the call cannot be properly routed to its destination. Code No. 2 - No route to specified transit network (national use). This cause indicates that the equipment sending this cause has received a requ, the call should be placed properly. There are no standards for this, the call will not ring through and will be discarded by the switch. Code No. 103 - parameter non-existent or not implemented - passed on (national use). This cause indicates that the equipment sending, the information element is not required to be present in the message in order for the equipment sending the cause to process the message. Code No. 100 - Invalid information element contents. This caus, the number being called is not an ISDN number but an analog destination. 2. The equipment is dialing at a faster rate than the circuitry allows, the router relinquishes the second channel, the Telco switch operates a timer. For example, the user may wish to try another call attempt almost immediately. What it means: This means that there is a temporary failure at the physical layer on the ISDN network. If you remove the ISDN cable fr, then this cause indicates that the parameter(s) were passed unchanged. Code No. 110 - message with unrecognized parameter discarded. This cause indicates that the equipment sending this cause has disc, this cause is generated. Code No. 83 - a suspended call exists, this usually indicates that the ISDN number being dialed is in a format that is not understood by the equipment processing the call. SPIDs will sometimes fail to initialize with a Cause 100, throughput of transit delay cannot be supported). Code No. 50 - requested facility not subscribed. This cause indicates that the user has requested a supplementary service which is implemented by the , unallocated (unassigned) number shall be used. Code No. 26 - non-selected user clearing. This cause indicates that the user has not been awarded the incoming call. Code No. 27 - destination out of ord, unspecified. This cause indicates that an interworking call (usually a call to 5W56 service) has ended. Notes about Cause Codes over 128 Cause code values of 128 and higher aren't sent over the networ, unspecified. This cause is used to report a protocol error event only when no other cause in the protocol error class applies. Code No. 127 - Intel-working, unspecified. This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies. Code No. 49 - Quality of Service not available. This cause is, unspecified. This cause is used to report an invalid message event only when no other cause in the invalid message class applies. Code No. 96 - mandatory information element is missing. This cause ind, user-to-user information, when an analog call is placed to a Netopia router that has two B Data Channels in place, which can be caused by a bad switch translation, you would see this. It's usually temporary. Code No. 42 - switching equipment congestion. This cause indicates that the switching equipment generating this cause is experiencing a period of high traff

ISDN hangup cause codes provide information as to why a call has been terminated. The list of hangup cause codes

Asterisk Dialplan varriable

June 10, 2014June 10, 2014 eduguru 0 Comments %d%m%Y-%H:%M:%S)}) ${DIALEDPEERNAME}: Name of the called party. Broken for now, %Y%m%d-%H%M%S)}) ${TRANSFERCAPABILITY}: Type of Channel ${TXTCIDNAME}: Result of application TXTCIDName (see below) ${UNIQUEID}: Current call unique identifier ${TOUCH_MONITOR}: used for "one touch re, 1, 2, 3, and wW dial flags). If is set on either side of the call then that var contains the app_args for app_monitor otherwise the default of WAV||m is used ${TOUCH_MONITOR_PREFIX}: used for "one touch record, and wW dial flags). This set Prefix to ${TOUCH_MONITOR} default: auto "New in 1.8" Application-specific variables Some applications take extra input or provide output using channel variables. AgentCal, are case sensitive. Note: Several of these builtin variables have been converted to functions in 1.2, Asterisk Dialplan varriable, Caller ID that redirected the call. Limitations apply, DIALSTATUS seems to have been removed. Now you should use the DEVSTATE function. Try in astersisk console "core show function DEVSTATE" for more informations) ${DNID}: Dialed Number Identifier. Limita, exten => 100, extra channel variables are available. ${ARG1}: The first argument passed to the macro ${ARG2}: The second argument passed to the macro (and so on) ${MACRO_CONTEXT}: The context of the extension that , for example) should be aware of this). ${CALLINGPRES}: PRI Call ID Presentation variable for incoming calls (See callingpres ) ${CHANNEL}: Current channel name ${CONTEXT}: The name of the current cont, if specified - see Asterisk billing (DEPRECATED in 1.2.0 and removed in 1.4. Use ${CDR(accountcode)} ${ANSWEREDTIME}: This is the amount of time(in seconds) for actual call. ${BLINDTRANSFER}: The acti, in contrast to user-defined variables, instead use :${STRFTIME(${EPOCH}, it was DEPRECATED in 1.2.0 and removed in 1.4. (Note: this is not necessarily numeric as the name would indicate and can legitimately contain the space character. Commands acting on this variable (suc, it was DEPRECATED in 1.2.0 and removed in 1.4. ${CALLERID(num)}: The current Caller ID number - ${CALLERIDNUM} was used in versions of Asterisk prior to 1.2.0, MixMonitor(${filename}) Predefined Channel Variables There are some channel variables set by Asterisk that you can refer to in your dialplan definitions. Asterisk-defined variables, NoOp(${LEN(${Fruit})}) The first NoOp would show a value of 5 (the length of the string "fruit"). The second NoOp would show a value of 4 (the length of the string "pear"). This is an excellent way to, NoOp(${LEN(Fruit)}) exten => 100, see DIALEDPEERNAME ${DIALEDPEERNUMBER}: Number of the called party. Broken for now, see DIALEDPEERNUMBER ${DIALEDTIME}: Time since the number was dialed (only works when dialed party answers the line?!) ${DIALSTATUS}: Status of the call. See DIALSTATUS (note: In the current SVN relea, see DNID ${EPOCH}: The current UNIX-style epoch (number of seconds since 1 Jan 1970) ${EXTEN}: The current extension - cannot be modified with the set command- just use the GoTo to change the EXTEN va, see RDNIS ${SIPDOMAIN}: SIP destination domain of an inbound call (if appropriate) ${SIP_CODEC}: Set the SIP codec for the inbound (=first) call leg (see channelvariables.txt or README.variables in 1., Set(filename=${EVAL(${MY_VAR})}) exten => 104, Set(Fruit=pear) exten => 100, this is the errormessage Dial returns ${DIALSTATUS}: Text code returning status of last dial attempt. Dial takes input from ${TRANSFER_CONTEXT}: If this variable exists, to allow setting their values. ${ACCOUNTCODE}: Account code, Using $ If you want to set a global variable containing the another variable name in the [globals] category of extensions.conf you have to do something like this: [globals] SS=$ MY_VAR=${SS}{EPOCH}-${, when a #transfer is executed it goes to the selected extension on this context. EnumLookup returns ${ENUM}: The result of the lookup Hangup reads the ${PRI_CAUSE} variable for setting PRI return codes

Using $ If you want to set a global variable containing the another variable name in the [globals] category of extensions.conf you

Asterisk DialStatus Channel Varriable

June 7, 2014 eduguru 1 Comment ${ARG3}, ${ARG4}) exten => s, 1, 1) exten => s-CANCEL, 1) exten => s-NOANSWER, 2, arg2, Asterisk channel variable DIALSTATUS Contains a text string signifying result of the last dial attempt: ANSWER: Call is answered. A successful dial. The caller reached the callee. BUSY: Busy signal. T, Asterisk DialStatus Channel Varriable, Busy exten => s-CHANUNAVAIL, callee chose to send caller to torture menu INVALIDARGS: Error parsing Dial command arguments (added for Asterisk 1.4.1, callee rejected the call TORTURE: Privacy mode, Congestion exten => _s-., Congestion exten => s-, Congestion exten => s-CANCEL, Congestion The following is an example of a local Zap channel callout with SIP failover (ex. Zap channel is in use) [macro-localcallout] exten => s, Dial() returns DIALSTATUS=CONGESTION for pretty much every call setup problem. The reason for this is that Dial() is used for multiple protocols (Zap, Dial(${ARG1}, Dial(${ZAP/1/${ARG1}, Dial(SIP/sippeer/${LOCALAREACODE}${ARG1}, g, Goto(s-${DIALSTATUS}, GotoIf($["${DIALEDTIME}" = "0"]?here) exten => s-NOANSWER, GotoIf($["${DTIME}" = "0"]?here) exten => s-NOANSWER, Hangup exten => s-BUSY, Hangup exten => s-CONGESTION, Hangup exten => s-NOANSWER, IAX etc.) and so it is limited to the lowest common denominator and is unable to return the protocol specific information (e.g., in sip.conf or iax.conf). CONGESTION "Congestion" is somewhat misleading. Unfortunately at this time (2007-05-17), n, n(here), Need failover for "${ARG1}") exten => s-BUSY, Need failover for "${ARG1}") exten => s-CONGESTION, next line is not perfect! ;exten => s-NOANSWER, NoOp( Dial Status: ${DIALSTATUS}) exten => s, peer may not be registered. DONTCALL: Privacy mode, see example in goto documentation. Note: To obtain useful DIALSTATUS information when dialing a peer the peer's definition must contain qualify=yes (e.g., Set(DIALSTART=${EPOCH}) ;exten => s, Set(DTIME=$[${EPOCH} - ${DIALSTART}]) watch out DIALEDTIME can also be empty, SetCallerId(${CALLERIDNUM}) exten => s-CHANUNAVAIL, sip, SIP 404 response) ., SVN r53135-53136) The dial status may be used in the dialplan to control program flow, T), T) exten => s, the number rang for too long, then the dial timed out. CANCEL: Call is cancelled. The dial command reached its number but the caller hung up before the callee picked up. CONGESTION: Congestion. This status is usually a sign that t, This macro is an example of how failover for two or more outgoing trunks can be managed [macro-safedial] exten => s, Verbose(1

Asterisk channel variable DIALSTATUS Contains a text string signifying result of the last dial attempt: ANSWER: Call is answered. A

Asterisk Databse

Asterisk cmd MYSQL

June 6, 2014 eduguru 0 Comments '10', '9', ), ) & backtick (\`). Asterisk 1.4.xyz does need to have these characters escaped. exten => 888, ${EXTEN}) exten => _X., ${fetchid} is set to 0 and ${var1}, ${fetchid} is set to 1 and a single row is fetched from a result set contained in ${resultid}. The return fields are assigned to ${var1}, ${var2} ... ${varN} remain unchanged. MYSQL(Nextresult resultid ${connid}) (New in Asterisk 1.8) If last query returned more than one result set, ${var2} ... ${varN} respectively. If no rows are left to select, 1, 1) exten => 888, 2, 3, 4, 5, 6, 7, 8, 8) exten => _X., AGI(${AGIScript}, AGI(${DefaultAGIScript}, and backslash (\\).Note: This is apparently no longer necessary as of Asterisk 1.8. After upgrading two development servers, and flexibility? Using exec and a shell script, as this was the original behavior. autoclear=yes Check this page and Asterisk Queue Callback for background. These two sets of statements accomplish the same thing: exten => 1, Asterisk cmd MYSQL, autoclear will destroy allocated statement and connection resources when the channel ends. For most usage of the MYSQL app, backtick (\`), both free to download and use. There is some fee to keep it but you do not need to keep it, but it's conceivable that somebody is sharing MYSQL connections across multiple channels, callback=1\, callbacknum=${CALLERID:-11:11}) exten => 2, callbacknum=${CALLERID:-11:11}\ WHERE\ uniqueid=${UNIQUEID}) Notice that in extension 2 the resultid value didn't need to be cleared. These two sets of statements accomplish the same thing: exten =>, clean up connections in the 'h' extension. - R. Mills Be sure to close connections and handle clean up in the h extension. This will ensure that on hangup connections do not persist. - R.Mills Just to, comma (, commas (\, connections will persist and overload MySQL. The only way to undo this is to shutdown Asterisk and restart it, Goto(_X., Goto(fetchrow) ; continue loop if row found exten => 888, GotoIf($["${connid}" = ""]?error, GotoIf($["${foundRow}" = "1"]?done) ; leave loop if no row found exten => 888, GotoIf($[${AGIScript} = NULL]?5:7) exten => _X., GotoIf($[${fetchid}]?7:9) exten => _X., Hangup exten => _X., Hangup In the above example, Hangup Notice in this case, Hangup Please note the corrections to MYSQL(Fetch). ${fetchid} does not necessarily return 1 if there are more available rows, I am clearing and disconnecting after the Fetch. This ensures that before we even reach the AGI script to do a task, I discovered that I could define my querystring and return variables without the escape character The fields returned are assigned to the variables in the same order that they are returned by MySQL. I, if the user hangs up at either priority 5 or priority 7, if you are working with a TimeStamp column, in Asterisk 1.8 the addons have been integrated back into Asterisk. MYSQL(): Basic MYSQL Database Functionality (note that the help information returned from 'show application MYSQL' is a little misle, in order to use the MYSQL() delete in stead of the System delete you'll have to clear the resultid value between queries: exten => 2, in this case the following will work: exten => _X., in which case, install and use to develop your dial plan and then uninstall it, is not installed by default and must be downloaded and installed with the asterisk-addons package. However, it returns 1 if there was a row available during that call to MYSQL(Fetch). This appears to have been inaccurately explained since the creation of this page. I have corrected this above and in the exa, it stores the next result set in ${resultid}. It's useful with stored procedures. MYSQL(Clear ${resultid}) Frees memory and data structures associated with result set. MYSQL(Disconnect ${connid}) Disc, like I did. Here is how it looks like., MySQL will not allow anymore connections. (Depending on the limit set in the mysql conf file). Therefore, MYSQL(Clear ${resultid}) exten => _X., MYSQL(Clear ${resultid}) exten => 2, MYSQL(Clear ${resultid}) exten => 888, MYSQL(Clear...) and MYSQL(Disconnect....) will never be executed. This will constantly create connections over and over again as calls progressively increase. Eventually, MYSQL(Connect connid localhost asterisk dbpass asterisk) exten => _X., MYSQL(Connect connid localhost dbuser dbpass dbname) exten => _X., MYSQL(Connect connid localhost dbuser dbpass dbname) exten => 888, MYSQL(Disconnect ${connid}) exten => _X., MYSQL(Disconnect ${connid}) exten => error, MYSQL(Fetch fetchid ${resultid} AGIScript) exten => _X., MYSQL(Fetch fetchid ${resultid} cbn) exten => 2, MYSQL(Fetch foundRow ${resultid} number) ; fetch row exten => 888, MYSQL(Query resultid ${connid} DELETE\ FROM\ callers\ WHERE\ callbacknum=${cbn}) exten => 2, MYSQL(Query resultid ${connid} DELETE\ FROM\ callers\ WHERE\ callbacknum=${cbn}) Moreover, MYSQL(Query resultid ${connid} INSERT\ INTO\ callers\ SET\ uniqueid=${UNIQUEID}) exten => 2, MYSQL(Query resultid ${connid} INSERT\ INTO\ callers\ SET\ uniqueid=${UNIQUEID}\, MYSQL(Query resultid ${connid} SELECT\ `number`\ FROM\ `phones`\ WHERE\ `channel`=\'${chan}\') exten => 888, MYSQL(Query resultid ${connid} SELECT\ callbacknum\ FROM\ callers\ WHERE\ callbacknum=${CALLERID:-11:11}) exten => 2, MYSQL(Query resultid ${connid} SELECT\ called+0\ FROM\ callers\ WHERE\ callbacknum=${CALLERID(num):-11:11}) This returns datetime yyyymmddhhmmss. I find it easier to just disconnect and clear in the h, MYSQL(Query resultid ${connid} SELECT\ scriptname\ from\ mac2pin\ where\ userid=${CALLERIDNAME}) exten => _X., MYSQL(Query resultid ${connid} UPDATE\ callers\ SET\ callback=1\, n, n(done), n(fetchrow), no problems. Q: What is a better way to do it then in terms of performance, NoOp(${number}) exten => 888, NoOp(Connection error - do whatever we have to do to crash nicely!) exten => error, not needed for numbers. Eg. MYSQL(Query db_result ${db_connid} SELECT name from table WHERE phone=${callerid}) works fine. -Baji autoclear: Configuration file for app_addon_sql_mysql If set, or agi or something else? A: Setup extconfig to have realtime access to the database/table you want to pull info from, or use mytop and kill the processes that are hung. To avoid this, same is likely true for quotes (\' & \"), security, System(mysql -u acd -h 127.0.0.1 -e "DELETE FROM callers WHERE callbacknum=${cbn}" --password=acdpass acd) Now, then ${connid} == "". MYSQL(Query resultid ${connid} query-string) Executes standard MySQL query contained in query-string using established connection identified by ${connid}. Result of query is stor, then in the dialplan use the app Realtime. Use the RealTime config handler system to read data into channel variables: RealTime(||[|]) All unique column names will be set as channel variables with opt, This is an ADD-ON of asterisk, this is what you want, this should be set to 'no'. Defaults to 'no', we ensure that Clearing and Disconnecting takes place unless the call is hungup after the connection and before the disconnect. The best way to handle this situation is to clear connections in the 'h', works great and decreases the number of priority routines within an extension. There is alternative solution to easily work with almost all databases in Asterisk using drag-and-drop environment but yo, you can retrieve values without the delimiters by appending a '+0' to the column name: exten => 1, you can simply download

This is an ADD-ON of asterisk, is not installed by default and must be downloaded and installed with the asterisk-addons

Asterisk queue callback

June 6, 2014February 24, 2016 eduguru 4 Comments `callback` int(3) NOT NULL default '0', `callbacknum` varchar(15) NOT NULL default '', `callbacknum`) VALUES (1, `queueid` smallint(6) NOT NULL default '8', `queuename` varchar(20) default NULL, `queuename` varchar(20) NOT NULL default '', '/dev/null' or die "Can't read /dev/null: $!"; open STDOUT, '>>/dev/null' or die "Can't write to /dev/null: $!"; defined(my $pid = fork) or die "Can't fork: $!"; exit if $pid; setsid or die "Can't start a new session: $!"; umask 0; }, '>>/dev/null' or die "Can't write to /dev/null: $!"; defined(my $pid = fork) or die "Can't fork: $!"; exit if $pid; setsid or die "Can't start a new session: $!"; umask 0; } Expanded Queue Callb, '>>/dev/null' or die "Can't write to /dev/null: $!"; open STDERR, '311'), '911'), ">>/tmp/cb$row->{uniqueid}.call"; print CALLFILE "Channel: $outchan/$row->{callbacknum}"; print CALLFILE "MaxRetries: 3\n"; print CALLFILE "RetryTime: 60\n"; print CALLFILE "WaitTime: 30\n, "+>>/tmp/cb$row->{uniqueid}.call"; print CALLFILE "Channel: $outchan/$row->{callbacknum}\n"; print CALLFILE "MaxRetries: 3\n"; print CALLFILE "RetryTime: 60\n"; print CALLFILE "WaitTime: 3, "$calldir/$row->{uniqueid}.call"); } } # end main loop ############################################################################## sub daemonize { chdir '/' or die "Can't chdir to /: $!"; open S, "$calldir/$row->{uniqueid}.call"); } # end main loop sub daemonize { chdir '/' or die "Can't chdir to /: $!"; open STDIN, "$dbpass") or die $DBI::errstr; my $qql = "SELECT queuename FROM queuename"; my $aryRef = $dbh->selectall_arrayref($qql); my @queuename = map { $aryRef->[$_][0]} 0..$#{$aryRef}; while (1) { # be, "$dbpass") or die $DBI::errstr; while (1) { # begin main loop sleep($sleepsec); my $q1 = "SELECT uniqueid, "$dbuser", ${queueid}, ${VM_PREFIX}5857, 1, 1) [set-callback] exten => 9, 1) Queue Example An example of one of our queues, 2, 2) Perl Daemon (callbackd) !/usr/bin/perl use strict; use DBI; use POSIX; my $calldir = "/var/spool/asterisk/outgoing"; my $sleepsec = 20; # How often do we check for callbacks? my $outchan = "Zap/G2", and update privileges at a minimum to the database. CREATE TABLE `bit_blacklist` ( `uniqueid` int(11) NOT NULL auto_increment, Answer ;exten => s, Answer exten => 1, Asterisk queue callback, callback numbers are checked against a blacklist which is stored in a MySQL database. The number of calls allowed into all queues are set by a global variable as well as variable that sets the minimum, CALLBACKANNOUNCETHRES to set the total number of calls you will allow in all queues and how many calls must be in the queues before a caller hears about this option. A custom announcement must be reco, callbacknum, callbacknum FROM callers " . "ORDER BY uniqueid LIMIT 1"; my $row = $dbh->selectrow_hashref( $q1 ); if (!$row->{callbacknum}) { next; } open CALLFILE, callbacknum=\'${CALLBACKNUM}\'\, callbacknum=${CALLBACKNUM} WHERE\ uniqueid\=${UNIQUEID}) exten => 1, CREATE, CREATE TABLE `bit_callers` ( `uniqueid` varchar(15) NOT NULL default '', delte, GoTo(1) exten => 9, GoTo(Add9) exten => 9, Goto(ext-local, Goto(ext-queues-custom, GoTo(StoreNum) exten => 9, Goto(support-queue, GoToIf($["${CALLBACKNUM:0:3}"="210"]?:Not210) exten => 9, GotoIf($["${CORRECT}"="1"]?:1) exten => 9, GotoIf($["${f}"="1"]?:GoodNum) exten => 9, GotoIf($["${LEN(${CALLBACKNUM})}"="10"]?TenDigits) exten => 9, GotoIf($["${LEN(${CALLBACKNUM})}"="10"|"${LEN(${CALLBACKNUM})}"="7"]?GoodNumDigit) exten => 9, GoToIf($[${COUNT} >= ${CALLBACKANNOUNCETHRES}]?:EnterQueue) exten => 1, GotoIf($[${COUNT} >= ${QUEUESIZE}]?Queuevm) exten => 1, GotoIf($[${QUEUE_PRIO}=10]?EnterQueue) exten => 1, Hangup exten => h, INSERT, KEY `callback` (`callback`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; CREATE TABLE `bit_queuename` ( `id` int(11) NOT NULL auto_increment, KEY `callback` (`callback`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; Dialplan Additions [support-queue] exten => s, KEY `callbacknum` (`callbacknum`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COMMENT='Collection of numbers not allowed for customer callback' AUTO_INCREMENT=8 ; INSERT INTO `bit_blacklist` (`uniqueid`, KEY `queuename` (`queuename`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=13 Dialplan Additions If you are using Trixbox two variables should be set in globals_custom.conf - QUEUESIZE, MYSQL(Clear ${r1}) exten => 1, MYSQL(Connect connid 127.0.0.1 acd acd acd) exten => 1, MYSQL(Connect connid 127.0.0.1 acd acd acd) exten => 9, MYSQL(Connect connid 127.0.0.1 acd acd acd) exten => h, MYSQL(Connect connid 127.0.0.1 acd acdpass acd) exten => 1, MYSQL(Connect connid 127.0.0.1 acd acdpass acd) exten => h, MYSQL(Connect connid 127.0.0.1 acd acdpass acd) exten => s, MYSQL(Disconnect ${connid}) [callback] exten => s, MYSQL(Disconnect ${connid}) exten => 1, MYSQL(Disconnect ${connid}) exten => 9, MYSQL(Disconnect ${connid}) exten => s, MYSQL(Fetch f ${r} CALLBACKNUM) exten => 9, MYSQL(Fetch fetchid ${r1} COUNT) exten => 1, MYSQL(Query r ${connid} DELETE\ FROM\ callers\ where\ uniqueid=${UNIQUEID}\ AND\ callback=0) exten => h, MYSQL(Query r ${connid} INSERT\ INTO\ callers\ set\ uniqueid=\'${UNIQUEID}\'\, MYSQL(Query r ${connid} INSERT\ INTO\ callers\ set\ uniqueid=${UNIQUEID}) exten => s, MYSQL(Query r ${connid} SELECT\ callbacknum\ FROM\ blacklist\ WHERE\ callbacknum=${CALLBACKNUM}) exten => 9, MYSQL(Query r ${connid} UPDATE\ callers\ SET\ callback=1\, MYSQL(Query r1 ${connid} SELECT\ COUNT(*)\ FROM\ callers\) exten => 1, n, n(Add9), n(EnterQueue), n(GoodNum), n(GoodNumDigit), n(Not210), n(Queuevm), n(StoreNum), n(TenDigits), NoOp(${CALLBACKNUM}) exten => 9, NoOp(${CALLERID}) exten => 9, NoOp(${LEN(${CALLBACKNUM})}) exten => 9, placed in /etc/asterisk/queues_custom.conf. You may need to tweek these parameters to fit your requirements. [Spanish] wrapuptime=0 timeout=15 strategy=rrmemory retry=5 queue-youarenext=queue-youarene, Playback(after-the-tone) exten => 9, Playback(custom/queue-callback-msg) exten => 1, Playback(enter-phone-number10) exten => 9, Playback(goodbye) exten => 1, Playback(goodbye) exten => 9, Playback(if-this-is-correct) exten => 9, Playback(if-this-is-not-correct) exten => 9, Playback(pls-try-again) exten => 9, Playback(press-1) exten => 9, Playback(press-2) exten => 9, Playback(wrong-try-again-smarty) exten => 9, Playback(you-dialed-wrong-number) exten => 9, Playback(you-entered) exten => 9, PRIMARY KEY (`uniqueid`), put the following table into a database called 'acd'. CREATE TABLE `bit_callers` ( `uniqueid` varchar(15) NOT NULL default '', Queue(${QUEUENAME}|tT) exten => 1, Queue(support|t) exten => 1, queueid FROM callers WHERE queuename='".$queue."' ". "ORDER BY uniqueid LIMIT 1"; my $row = $dbh->selectrow_hashref( $q1 ); if (!$row->{callbacknum}) { next; } open CALLFILE, queueid=\'${QUEUEID}\'\, queueid=\'${queueid}\'\ WHERE\ uniqueid=${UNIQUEID}) exten => 9, queuename=\'${QUEUENAME}\') exten => 1, Read(CALLBACKNUM|beep|10) ; This is where you request the CallBack Number from your customer. Put your own prompts or whatever here. exten => 1, Read(CALLBACKNUM|beep|10||2|5) ; This is where you request the CallBack Number from your customer. Put your own prompts or whatever here. exten => 9, Read(CORRECT|beep|1||2|5) exten => 9, s, SayDigits(${CALLBACKNUM}) exten => 9, Set(CALLBACKNUM=${CALLBACKNUM:3:7}) exten => 9, Set(CALLBACKNUM=9${CALLBACKNUM}) exten => 9, Set(CALLBACKNUM=91${CALLBACKNUM}) exten => 9, Set(QUEUE_PRIO=10) exten => s, Set(QUEUEID=1) exten => 1, Set(QUEUENAME=Spanish) exten => 1, SQL Table Structure If using the dialplan below, Texas). You will need to change the code at label TenDigits for your area code(s). [ext-queues-custom] exten => 1, UNIQUE KEY `id` (`id`), Wait(1) ;exten => s, Wait(1) exten => 1, Wait(1) exten => 9, we are in San Antono, we give them text names so both the name of the queue and the queueid (the number a called presses when selecting a queue) is stored. The callback Perl script uses this information to make sure that w, yet. Functionality is there but there may be a bug or two laying around. I welcome suggestions on how to further enhance it. SQL Table Structure Three tables are used. Blacklist to hold the phone numb

SQL Table Structure If using the dialplan below, put the following table into a database called ‘acd‘. CREATE TABLE `bit_callers`

Asterisk : queues.conf

June 6, 2014February 24, 2016 eduguru 0 Comments ; MEMBERLASTCALL is the last time the member took a call. ; MEMBERPENALTY is the penalty of the member ; MEMBERDYNAMIC indicates if a member is dynamic or not ; MEMBERREALTIME indicates if a member is, 'no', 1 ; Any agent in group 1, 2004): Introduced right after the v1.0 release ; If you wish to remove callers from the queue when new callers cannot join, 2005 CVS HEAD) Periodic announcements are available in queues using the new periodic-announce and periodic-announce-frequency options. This allows a message like "Thank you for holding, 2005): Gives queues a 'weight' option, achieve circular call distribution by using round robin mode and putting a different penalty on each agent, AGI, and a member with penalty 1 will have a metric between 0 and 2000, and a member with penalty 2 will have a metric between 0 and 3000. ; Please note, and starts with the next agent in the list. If you have three agents, and the dial plan can determine what to do next. ; This setting controls whether callers can join a queue with no members. ; There are three choices: ; ; yes - callers can join a queue with no members, and the last agent logs out, and the Queue() call will return, and then also change monitor-type for individual queues within queue by using the same configuration parameter within a queue configuration block. ; If you do not specify or comment out this option, and they are then connected with the next available member and all available members and waiting callers waits while this happens. ; The new behavior, and you are not recording while people are listening to MOH. ; To enable monitoring, announceoverride, app_queue will now use the new MixMonitor application instead of Monitor so the concept of "joining/mixing" the in/out files now goes away when this is enabled. ; You can set the default type for all , asterisk inbound configuration, Asterisk will considered the Queue in-use, but consider with penalty Some notes about roundrobin and rrmemory roundrobin is not to be confused with "circular call distribution", but paused queue members do not count as unavailable (new in 1.6) ; ; joinempty = yes Asterisk 1.8: ; paused - a member is not considered available if he is paused ; penalty - a member is not consider, but rrmemory mode will move past them. You can, but the timeout is set to 60 seconds, but uses the agent's penalty as a weight (new in 1.6) ; rings random interface, but uses the member's penalty as a weight when calculating their metric. ; So a member with penalty 0 will have a metric somewhere between 0 and 1000, by kpfleming. round robin mode remembers the last agent it _started_ with for a new call, call 1 arrives and is queued. Call 2 arrives ten seconds later and is queued. After twenty seconds, call 1 is played the periodic announce message. Exactly one second after call 1 starts hearing the message an agent becomes free. Since call 1 is tied up with announcements, call 2 is successfully offered to the agent. Call 1 remains on hold and yet a call which arrived later has been serviced. Wrapuptime This setting can be in agents or in the queue. But it needs to be i, each member will be automatically read into their recorded queues. Default is 'yes'. ; persistentmembers = yes Keep Stats ; Keep queue statistics during a reload. Default is 'no' ; keepstats = no Auto, enabled by setting autofill=yes makes sure that when the waiting callers are connecting with available members in a parallel fashion until there are no more available members or no more waiting caller, estimated hold time ('announce-holdtime') and the thank you file ('queue-thankyou') are played. 'min-announce-frequency' defines a minimum time which must pass between position/holdtime announcements., etc. For the first call, etc. NOTE that this does not apply to 1.4.13 (an possibly earlier versions). There is no 'roundrobin' strategy any more and 'rrmemory' will continue to try the lowest priority handset(s) - there is no, etc. rrmemory mode remembers the last agent it tried to _call_, general ; ; Global settings for call queues Persistent Members ; Store each dynamic member in each queue in the astdb so that when asterisk is restarted, gosub, here in detail it's how it works, higher weights get first shot at available channels when the same channel is included in more than one queue. ; ;weight=0 weight = expects an integer value This option may cause a queue deadlock - ple, how long to wait before sending a potentially ; free member another call (default is 0, however, if agent 2 answered it in round robin mode, If leavewhenempty" is set to "strict". "joinempty" set to "strict" will keep incoming callers from being placed in queues where there are no agents to take calls. The Queue() application will return, if using this strategy, if you want announcements every 20 seconds, in the order you wish them to be called. app_queue will always try all agents with no penalty, in which if the user types a SINGLE digit extension while they are in the queue, infact even using roundrobin without memory subsequent calls are circulated between agent, it will default to no to keep backward compatibility with the old behavior. ; autofill = yes Autopause ; Autopause will pause a queue member if they fail to answer a call ; ;autopause=yes Maxlen ; Max, it will default to the old 'Monitor' behavior to keep backward compatibility. ; monitor-type = MixMonitor UpdateCDR behavior. ; This option is implemented to mimic chan_agents behavior of populating C, it will not record calls. ; ; monitor-format = gsm|wav|wav49 Monitor Type ; By setting monitor-type = MixMonitor, just prior to the caller being bridged with a queue member ; the following variables will be set: ; QEHOLDTIME callers hold time ; QEORIGINALPOS original position of the caller in the queue ; ;setqueu, just prior to the caller being bridged with a queue member the following variables will be set ; MEMBERINTERFACE is the interface name (eg. Agent/1234) ; MEMBERNAME is the member name (eg. Joe Soap) ;, leave them out e.g.: ;queue-thankyou=yoursoundfile ; ; Note that a timeout to fail out of a queue may be passed as part of application call ; from extensions.conf: ; Queue(queuename|[options]|[optiona, macro, no-answer) this also causes the queue to move to the next agent in a round robin) ;timeoutrestart = yes Strategy Calls are distributed among the members handling a queue with one of several strategies, not in the language of the originating channel. Notes The penalty parameter: You can have agents that are less likely to take calls (e.g. imagine a sales queue, only successful calls are ; recorded, only the holdtime will be announced (as configured in announce-holdtime) (1.6.X default=no) 'announce-position' = yes | no 'announce-frequency' controls how often the queue position (if 'announce-posi, options, or no delay) ; ;wrapuptime=15 Memberdelay This sets a delay period between the time that the member answers the call and when it is connected. ; If you wish to have a delay before the member is connec, or only once; hold time will not be announced if <1 minute ; ;announce-holdtime = yes|no|once ; ; Use these sound files in making position/holdtime announcements. The ; defaults are as listed below, press "1" to leave a message Default Rule ; If you wish to implement a rule defined in queuerules.conf (see configs/queuerules.conf.sample from the asterisk source directory for more information about, queue.conf, regardless of whether any Agents are logged in or not. AddQueueMember() on the other hand will dynamically add and remove the interface from the queue... and these options will work properly. Event Me, regardless of who it started with, remember where we left off last ring pass linear: Rings interfaces in the order they are listed in the configuration file. Dynamic members will be rung in the order in which they were added. (new in 1, rule)'). Note that the announcement is played in the language set on the answering device, run this macro when connected to the queue member ; you can override this macro by setting the macro option on ; the queue application ; ; membermacro=somemacro Monitor Format ; Calls may be recorded , set this setting to one of the same choices for 'joinempty' ; ; leavewhenempty = yes ;If you are using CVS-HEAD and agents the queue app sees the agents as queue members always thus breaking this try:, set this to the number of seconds to delay. ;memberdelay = 5 timeoutrestart ; If timeoutrestart is set to yes, set this to yes. ; ; reportholdtime = no Ring Inuse ; If you want the queue to avoid sending calls to members whose devices are ; known to be 'in use' (via the channel driver supporting that device st, simply specify "monitor-format"; it will be disabled ; otherwise. ; ; monitor-format = gsm|wav|wav49 ; How often to announce queue position and/or estimated holdtime to caller (0=off) ; ;announce-freq, simply specify "monitor-format"; it will be disabled ; otherwise. ; ; You can specify the monitor filename with by calling ; Set(MONITOR_FILENAME=foo) ; Otherwise it will use MONITOR_FILENAME=${UNIQUE, so that the next call will go the agent after the last one who answered. If you have three agents and the first call rings 1->2 (and is answered), starting recording ; when the call is actually picked up; thus, the first call will go to agent 1->2->3, the following manager events will be generated: ; QueueMemberStatus ; (may generate a WHOLE LOT of extra manager events) ; ; eventmemberstatus = no Report Hold Time ; If you wish to report the caller', the following variables will be set just prior to the caller being bridged with a queue member and just prior to the caller leaving the queue ; QUEUENAME name of the queue ; QUEUEMAX maximum number of, the member penalty is not the same as when using other queue strategies. ; It is ONLY used as a weight for calculating metric. ;strategy=rrmemory Timeout ; How long do we let the phone ring before we , the next call will go to 2->3->1, the next call will go to 3->2->1, the remaining incoming callers will immediately be removed from the queue, the timeout/retry period is effectively ignored (i.e. you can consider the queue to always be in this state) and announcements will be played as per your setting of the announce-frequency and periodic, the timeout/retry timeouts become critical. For example, then do not consider the member to be available ; invalid - Do not consider a member to be available if he has an "invalid" device state. This generally is caused by an error condition in the member's, then the next call will ring 2->3->1, then the next call will ring 3->1 (and is answered), then the ones with penalty 1, then the time out for an agent to answer is reset if a BUSY or CONGESTION is received. ; This can be useful if agents are able to cancel a call with reject or similar. ;(I found that when agents retur, they will be taken out of the queue and sent to that extension in this context. context= This is the context that is used to allow the caller to exit with a key for further action. For example, they would still be the first agent for the next call, timeout, to ensure calls waiting in a higher priority queue will deliver its calls first. Only delays the lower weight queue's call if the member is also in the higher weight queue. Thanks to k3v for this opti, URL, use rrmemory) leastrecent: ring interface which was least recently called by this queue fewestcalls: ring the one with fewest completed calls from this queue random: ring random interface rrmemory: ro, wait for first available, when a queue member is ringing, when specifying monitor-format to enable recording of queue member conversations, which you can set at the login time with AddQueueMember membername parameter. ; ; updatecdr = no Shared lastcall ; shared_lastcall will make the lastcall and calls received be the same in members logg, you may specify this by setting defaultrule to the rule's name ; ; defaultrule = myrule announce The "announce = XXX" option in queues.conf makes Asterisk play the XXX announcement to the member of th, you might have the receptionists with a penalty of 1 and us propeller heads in technical support with a penalty of 2). The technical support people would only be offered a call from the sales queue if, you must use Asterisk cmd AddQueueMember instead of Asterisk cmd AgentCallbackLogin or Asterisk cmd AgentLogin if you want the options leavewhenempty and joinempty to work properly. If you have any st, you will only ever get announcements every 60 seconds. ; Queue position announce? ; Either yes or no. If turned off, you will want to enable this behavior. ; If you do not specify or comment out this option, you'd have the sales people with no penalty, your call is important to us." to be played at regular intervals while a caller is in the queue. e.g: periodic-announce = thank-you-message periodic-announce-frequency = 60 ; every 60 seconds Weight N

general ; ; Global settings for call queues Persistent Members ; Store each dynamic member in each queue in the

MySQL Cluster

Asterisk linux php-mysql

Backup and Restore Mysql database table

May 29, 2014February 11, 2017 eduguru 0 Comments Backup and Restore Mysql database table, Backup and Restore MySQL Database Using mysqldump, Dump and restore from .sql Dump mysqldump db_name table_name > table_name.sql Restore mysql -u -p db_name mysql> source /table_name.sql or in one line mysql -u username -p db_name table_name.sq, How to Back Up and Restore a MySQL Database, so that it only backups the given tables. mysqldump -u -p yourdb yourtable > c:\backups\backup.sql

Dump and restore from .sql Dump mysqldump db_name table_name > table_name.sql Restore mysql -u <user_name> -p db_name mysql> source <full_path>/table_name.sql

Asterisk dial command

Setting to Limit SIP channels

May 26, 2014May 26, 2014 eduguru 0 Comments 1, adding to the number of calls on SIP that way it keeps a count of how many SIP channels are going out that direction. I think theres another way but the variable should work. exten => s, and basically you have 6 calls going on... Now when you hang up the do hang up, one thing you could probably do is set a variable before DIAL and then set it again after dial, Setting to Limit SIP channels, SetVar(SIPCOUNT=$[${SIPCOUNT} - 1]) then you would need a gotoif statement even before the increment if you post the context that shows your dial statement, SetVar(SIPCOUNT=$[${SIPCOUNT} + 1]) ; increment and exten => s, they dont get stuck right? So you have 6 different peopel on the line and when 7 hits they block you and essentially your phone system is dead....? Ok, v, You have the 6 channels

You have the 6 channels, and basically you have 6 calls going on… Now when you hang up the do