Manually Editing Dial-Plan Logic in .NET Drawer barcode 3 of 9 in .NET Manually Editing Dial-Plan Logic

How to generate, print barcode using .NET, Java sdk library control with example project source code free download:
Manually Editing Dial-Plan Logic using .net vs 2010 toconnect code 39 extended for web,windows application QR Code Features CAUTION! The Code 3 of 9 for .NET following section is for advanced users only! If you are not familiar with programming languages, at this point, please skip to the next chapter. Additional information about Asterisk configuration files While this book deals with AsteriskNOW aimed to provide a simple, fast solution for managing the Asterisk Open Source PBX it does so without getting into the inner workings of Asterisk"s configuration files.

Additional information about the configuration files, their format, usage, and various available options is available at the voip-info wiki, located at: Asterisk+config+files.

. [ 79 ]. Tentacles of the PBX The Calling Rules Tables Manually edi ting AsteriskNOW dial-plan files isn"t recommended; however, in some extreme situations it can"t be avoided (especially while creating special applications with AsteriskNOW). For this specific reason, AsteriskNOW includes a facility to edit the configuration files manually. Click the File Editor menu option; the following screen should appear:.

[ 80 ]. 5 . The extensio visual .net Code 39 Extended ns.conf file should interest you.

Using the drop-down file selector, select the extensions.conf file for editing. The following screen should be observed:.

Now, if you were to click one of the lightly-shaded areas (light green on your screen); a text editing box will open to enable you to edit the file.. [ 81 ]. Tentacles of the PBX The Calling Rules Tables You"re proba .net vs 2010 barcode code39 bly wondering at this point "where is routing logic located " Scroll down the file and seek the section designated as numberplan-custom-1, which designates your DialPlan1 dial plan. If you were to create an additional dial plan using the GUI, its designation in the extensions.

conf file would be numberplan-custom-2. Examine the following section:. In the above section lines indicated by the exten directive, indicate a dial-plan activity. The exten directive is then followed by some form of well formatted number string, followed by a number indicating the sequence number of the directive, then followed by an Asterisk operational command in our case, the Macro command..

Asterisk and Code 39 for .NET AsteriskNOW include over 150 different applications; explanation of each and every application is beyond the scope of this book. Visit the Asterisk Wiki page at http://www.

voip-info. org/wiki/index.php page=Asterisk for more information about Asterisk and AsteriskNOW applications.

. The way the dial plan analyzes dialed numbers is explained next. Consider one of the dialing rules:. exten=_9XXX! Visual Studio .NET ANSI/AIM Code 39 ,1,Macro(trunkdial,${trunk_1}/${EXTEN:1}). The interest ing portion of this line is the _9XXX!. The following is an extract from an Asterisk documentation:. ; Extension Code 39 Extended for .NET names may be numbers, letters, or combinations ; thereof. If an extension name is prefixed by a _" ; character, it is interpreted as a pattern rather than a ; literal.

In patterns, some characters have special meanings: ; ; X - any digit from 0-9 ; Z - any digit from 1-9 ; N - any digit from 2-9 ; [1235-9] - any digit in the brackets (in this example, 1,2,3,5,6,7,8,9) ; . - wildcard, matches anything remaining (e.g.

_9011. matches [ 82 ]. 5 ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; anything starting with 9011 excluding 9011 itself) ! - wildcard, causes the matching process to complete as soon as it can unambiguously determine that no other matches are possible For example the extension _NXXXXXX would match normal 7 digit dialings, while _1NXXNXXXXXX would represent an area code plus phone number preceded by a one. Each step of an extension is ordered by priority, which must always start with 1 to be considered a valid extension. The priority "next" or "n" means the previous priority plus one, regardless of whether the previous priority was associated with the current extension or not.

The priority "same" or "s" means the same as the previously specified priority, again regardless of whether the previous entry was for the same extension. Priorities may be immediately followed by a plus sign and another integer to add that amount (most useful with s" or n"). Priorities may then also have an alias, or label, in ; parenthesis after their name which can be used in goto situations.

As this text Code 3 of 9 for .NET suggest, the underscore marking (_) indicates the start of a pattern matching rule. This is then followed by a form of expression indicating the pattern to match.

In the example, the pattern match is _9XXX!, so, interpreting this according to the documentation:.
Copyright © . All rights reserved.