ShirazOnline
نمایش نتایج: از شماره 1 تا 1 , از مجموع 1

موضوع: Personalize Your Own PBX Using FreePBX Features

  1. #1
    Super Moderator patris_70 آواتار ها
    تاریخ عضویت
    Jan 1970
    نوشته ها
    6,863
    تشکرها / پسندها

    پیش فرض Personalize Your Own PBX Using FreePBX Features

    کد:
    http://www.packtpub.com/article/personalize-your-pbx-using-freepbx-features?utm_source=sr_freepbx_abr2_0909&utm_medium=content&utm_campaign=sanjay

    In this article by Alex Robar, we will introduce some of the FreePBX features that allows us to personalize our PBX, which essentially means to make our PBX on our own. We will discuss how to configure FreePBX to check additional sources for caller ID information if none is provided, using the HTTP source type method or MySQL source type method. We will also learn how to configure PIN sets to password protect various FreePBX features.
    Let's get started.
    CallerID Lookup Sources

    Caller ID lookup sources supplement the caller ID name information that is sent by most telephone companies. A caller ID lookup source contains a list of phone numbers matched with names. When FreePBX receives a call, it can query a lookup source with the number of the caller. If the caller is on the lookup source's list, a name is returned that will be sent along with the call wherever the call gets routed to. The name will be visible on a phone's caller ID display (if the phone supports caller ID), and is also visible in the FreePBX call detail records.
    In order to set up a caller ID lookup source, click on the CallerID Lookup Sources link under the Inbound Call Control section of the navigation menu on the left side of the FreePBX interface as shown in the following screenshot:
    The Add Source screen has three common configuration options:

    • Source Description
    • Source type
    • Cache results

    Source Description is used to identify this lookup source when it is being selected as a caller ID lookup source during the configuration of an inbound route.
    Source type is used to select the method that this source will use to obtain caller ID name information. FreePBX allows a lookup source to use one of the following methods:
    ENUM: FreePBX will use whichever ENUM servers are configured in /etc/asterisk/enum.conf to return caller ID name information. By default, this file contains the e164.arpa and e164.org zones for lookups. All ENUM servers in the enum.conf file will be queried.

    • HTTP: FreePBX will query a web service for caller ID name information using the HTTP protocol. A lookup source that uses HTTP to query for information can use services such as Google Phonebook or online versions of the white/yellow pages to return caller ID names. When HTTP is selected as the source type, six additional options will appear for configuration. These options are discussed in the HTTP source type section.
    • MySQL: FreePBX will connect to a MySQL database to query for caller ID name information. Usually, this will be a database belonging to a Customer Relationship Management (CRM) software package in which all customer information is stored. When MySQL is selected as the Source type, five additional options will appear for configuration. These options are discussed later in the MySQL source type section.
    • SugarCRM: As of FreePBX version 2.5.1, this option is not yet implemented. In the future, this Source type option will allow FreePBX to connect to the database used by the SugarCRM software package to query for caller ID name information.

    If the Cache results checkbox is selected, then when a lookup source returns results they will be cached in the local AstDB database for quicker retrieval the next time the same number is looked up. Note that values cached in the AstDB will persist past a restart of Asterisk and a reboot of the PBX. Once a caller ID name has been cached, FreePBX will always return that name even if the name in the lookup source changes. Caching must be disabled for a new caller ID name to be returned from the lookup source.
    Once all configuration options have been filled out, click on the Submit Changes button followed by the orange-colored Apply Configuration Changes bar to make the new lookup source available to inbound routes. Now that we have an available lookup source, we can configure an inbound route to use this source to set caller ID information. Click on the Inbound Routes link under the Inbound Call Control section of the navigation menu on the left side of the FreePBX interface as shown in the following screenshot:
    Click the name of the inbound route that will use the new lookup source in the menu on the right side of the page (in this example, DID 5551234567) as shown in the following screenshot:
    Scroll down the page to the CID Lookup Source section. Select the name of the new lookup source from the Source drop-down menu:
    Click on the Submit button at the bottom of the page, followed by the orange-colored Apply Configuration Changes bar at the top of the page. Calls that are routing using this inbound route will now query our new lookup source for caller ID name information.

    HTTP source type

    When HTTP is selected as the Source type for a caller ID lookup source, six additional configuration options become visible:

    1. Host
    2. Port
    3. Username
    4. Password
    5. Path
    6. Query

    The Host field is used to specify the hostname or IP address of the web server that hosts the caller ID lookup service. This might be in the format of server.company.com or 255.255.255.255. Only the server hostname or IP address should be entered in this field. Do not include any prefixes or the remainder of the service path here (for example, exclude text such as "http://" and "/lookup.php"). If the service host provided an example address along the lines of [فقط اعضا می توانند لینک ها را مشاهده کنند برای ثبت نام اینجا را کلیک کنید][number], then server.company.com would be the value that is entered into the Host field.
    The Port field is used if the web service is hosted on a custom port. If this field is left blank, then the default value of 80 will be used (most HTTP servers are running on port 80). If the example address supplied by the provider starts with HTTPS instead of HTTP, then enter 443 into the Port field. If the example address has a number after the hostname (for example, [فقط اعضا می توانند لینک ها را مشاهده کنند برای ثبت نام اینجا را کلیک کنید]), then enter that number into the Port field.
    The Username and Password fields should only be filled in if the service provider supplied a set of credentials to use. If credentials are listed in the sample address supplied by the provider (for example, [فقط اعضا می توانند لینک ها را مشاهده کنند برای ثبت نام اینجا را کلیک کنید][number]&username=exampleuser&password=examplepassword), then do not enter the credentials in these fields. Credentials that are embedded in the web service address will be entered as part of the Query field.
    The Path field is used to specify the path on the web server to the caller ID lookup script. This means everything after the hostname through to the question mark in the service address. For example, if the provider has supplied a service address of [فقط اعضا می توانند لینک ها را مشاهده کنند برای ثبت نام اینجا را کلیک کنید][number], then /callerid/lookup.php is the value that should be entered into the Path field. Be sure to include the slash (/) at the beginning of the path.
    The Query field is the query string that is sent to the web service. The query string is everything that comes after the question mark in the service address. For example, if the provider has supplied a service address of [فقط اعضا می توانند لینک ها را مشاهده کنند برای ثبت نام اینجا را کلیک کنید][number]&type=callerid, then q=[number]&type=callerid is the value that should be entered into the Query field. The query string must contain a placeholder for the telephone number that is being looked up. FreePBX will replace the special token [NUMBER] with the telephone number to look up. If the example address supplied by the provider uses a different token (such as #NUMBER#, or {TelNumber}), be sure to replace this token with [NUMBER], so that FreePBX will know how to query the provider properly.
    A very good example of a free, public HTTP lookup source is the "CallerID Superfecta" script from Nerd Vittles. The script uses an HTTP lookup source to query several public phone books, including:

    • Google Phonebook
    • AnyWho
    • Whitepages

    More information on the CallerID Superfecta script can be found at: [فقط اعضا می توانند لینک ها را مشاهده کنند برای ثبت نام اینجا را کلیک کنید]
    MySQL source type

    When MySQL is selected as the Source type for a caller ID lookup source, five additional configuration options become visible:

    • Host
    • Database
    • Query
    • Username
    • Password

    The Host field is used to specify the hostname or IP address of the server that hosts the MySQL database. This might be in the format of server.company.com, or 255.255.255.255. If a database has been set up on the PBX itself to store caller ID information, then localhost should be the value of the Host field.
    Housing a database with caller ID data on the same server that runs Asterisk can cause performance issues. On a server that routes a high volume of calls, the added load of performing a MySQL query against a local database will impact disk performance and reduce available processor resources. If MySQL will be used to store caller ID data, then it is best to host that caller ID database on a separate server from the PBX.
    Database is the name of the database on the MySQL server.
    Query is the SQL query string that will be used to retrieve names from the database. The query string must contain a placeholder for the telephone number that is being looked up. FreePBX will replace the special token [NUMBER] with the number to lookup. If the MySQL lookup was supposed to pull the value of a field called cidname from a table called cidinfo, then the query string might look like this:
    codeXXXX
    The Username and Password fields are used to provide credentials that have access to the caller ID database. The user should be a MySQL user that has the ability to read the database. The user will not require permissions to insert new data or alter existing data in the database.

    PIN Sets

    A Personal Identification Number (PIN) is a numeric password that FreePBX can use to authenticate users when they attempt to dial specific features on the PBX such as outbound routes or DISA. Without entering a valid PIN, these features are inaccessible. A PIN set provides the ability for a group of PINs to be used to authenticate the use of a feature instead of just a single PIN. With a PIN set, each individual user can be given a unique PIN, and it is possible to revoke one user's access to a PBX feature without changing anyone else's PIN.
    In addition to authenticating users, PIN sets can also be helpful in tracking which users used which features. When a PIN set is used as an authentication mechanism, FreePBX can log which unique PIN was used to access a feature in the accountcode column of the call detail records. Even if a user places a call from someone else's extension, they will need to enter their own account code. When generating a report of which users used certain features, the detail records will provide an accurate report based on which PINs were used. This feature is often used by companies which implement restrictions on long-distance calling. It is possible to track which users make heavy use of the long-distance outbound routes by checking the PINs used to dial out.
    As of FreePBX version 2.5.1, only outbound routes make use of the PIN sets feature. Future versions will expand the use of PIN sets to cover any PIN protected feature such as DISA and conferences.
    In order to set up a PIN set, click on the PIN Sets link under the Internal Options & Configuration section of the navigation menu on the left side of the FreePBX interface as shown in the following screenshot:
    PIN sets have only three configuration options:

    • PIN Set Description
    • Record In CDR?
    • PIN List

    PIN Set Description is used to identify this PIN set when it is being selected during the configuration of an outbound route.
    If the Record In CDR? checkbox is selected, then anytime a user authenticates themselves using this PIN set, the PIN they used will be stored in the accountcode field of the call detail records alongside the details of the call they made. This is a reliable method of tracking the usage of outbound routes, because even if a user calls from an extension other than their own, they still must enter their own PIN to place a call through a protected route. If this option is not enabled then the call is logged normally without any details in the accountcode field.
    The PIN List is a list of one or more PIN codes. Each PIN should be on its own line. PINs can be as long as desired. However, as users are supposed to remember their PINs, it is typical to make PINs only four or five digits long.
    A completed PIN set might look like the following:
    In order to put our new PIN set to use we must assign it to an outbound route. Click on the Outbound Routes link under the Basic section of the navigation menu on the left side of the FreePBX interface as shown in the following screenshot:
    Click on the name of outbound route that the new PIN set will be associated with (in this example, LongDistance):
    From the PIN Set drop-down menu, select the name of the new PIN set:
    Click on the Submit Changes button at the bottom of the page followed by clicking on the orange-colored Apply Configuration Changes bar at the top of the page. All calls that pass through the selected outbound route will now be authenticated through one of the PINs in our new PIN set.
    Summary

    This article introduced us to some of the FreePBX features that allowed us to make our PBX on our own. We discussed how to configure FreePBX to check additional sources for caller ID information if none is provided, using the HTTP source type method or MySQL source type method. We also learned how to configure PIN sets to password protect various FreePBX features
    داخل انجمن سوال کنید تا دیگران هم اگر مشکل شما را دارند یا برایشان در آینده پیش بیاید استفاده کنند. پیغام خصوصی برای جواب دادن به سوال نیست.

  2. # ADS
    Circuit advertisement
    تاریخ عضویت
    Always
    نوشته ها
    Many
    مودم LTE بیرونی
     

اطلاعات موضوع

کاربرانی که در حال مشاهده این موضوع هستند

در حال حاضر 1 کاربر در حال مشاهده این موضوع است. (0 کاربران و 1 مهمان ها)

علاقه مندی ها (Bookmarks)

علاقه مندی ها (Bookmarks)

مجوز های ارسال و ویرایش

  • شما نمیتوانید موضوع جدیدی ارسال کنید
  • شما امکان ارسال پاسخ را ندارید
  • شما نمیتوانید فایل پیوست کنید.
  • شما نمیتوانید پست های خود را ویرایش کنید
  •