Home > Articles > Certification > Cisco Certification

Cisco Unified Communications Manager and Unity Connection: Configuring Class of Service and Call Admission Control

  • Print
  • + Share This
This chapter examines the various concepts associated with CoS and CAC and describes how to configure the required components for each.
This chapter is from the book

Now that you have created a basic dial plan, it is time to build on that and create a more complete dial plan. Often you want to allow and disallow access to certain destinations. For example, you might want only a certain group of callers to dial international numbers. This is done by creating a telephony class of service (CoS). In addition, if there are calls traversing limited-bandwidth links, some type of Call Admission Control (CAC) should be deployed to help ensure voice quality. This chapter examines the various concepts associated with CoS and CAC and describes how to configure the required components for each.

Rights and Restrictions

After the dial plan is created and users can place calls to destinations outside the cluster, you might think that you are all set and can sit back and relax. Not quite. After the system is configured to enable calls to be placed outside of the system, you need to start working on how to prevent certain calls from being placed. This chapter touches on how you can use route patterns to block certain destinations, and now you need to move beyond that and discuss how certain destinations can be reachable by some devices, but not by others. To accomplish this, you need to configure Calling Search Spaces (CSS) and partitions. The following sections explain what these are and how they work.

Understanding Call Search Spaces and Partitions

Of all the concepts within a Communications Manager environment, it is believed that the CSS and partitions cause the most confusion. This is rather odd because they are not complex. Simply put, the partition assigned to the destination affects what devices can reach it, and the CSS determines which destinations can be reached. Locks and key rings are good analogies. Think of the partition as a lock and the CSS as the key ring. To place a call to a destination, you must have a key that matches the device's lock. The key ring contains all the keys and therefore determines which destinations you can reach.

Of course, there is more to it than just locks and keys, but by using this analogy, you begin to understand how they work. You take a closer look at this analogy. Figure 5-1 shows five phones. The first four phones have partitions (locks). It is important to point out that the partitions (locks) are not assigned to devices, but rather to patterns and directory numbers (DN). For this example, assume that each phone has only a single line and that the partition (lock) is assigned to that line. Below each phone is a CSS (key ring) that shows to which partitions (locks) the phone has access. CSS (key rings) can be assigned to the device or the line. In this example, assume that they are assigned to the device.

Figure 5-1

Figure 5-1 Calling Search Spaces and Partitions Analogy

The locks in this figure have different-shaped keyholes, which means that to open a lock, you must have a key ring that has the correct-shape key. Keeping in mind that the locks represent partitions and that the key rings represent CSS, answer the following questions:

  • What phones can phone A reach?
  • What phones can phone D reach?
  • What phone can reach all other phones?
  • What phones can reach phone E?
  • What phones can phone E reach?

The answers to these questions are as follows:

  • Q. What phones can phone A reach?

    A. To determine what phones phone A can reach, you need to look at its CSS (key ring). Phone A has a circular key and a square key on its key ring, which means that it can call itself and phone B. However, because phone E has no lock (partition) assigned to it, any phone can reach it, just as a door with no lock can be opened by anyone.

  • Q. What phones can phone D reach?

    A. Because phone D has only a square key, it can dial phone A and, of course, phone E because it has no lock (partition).

  • Q. What phone can reach all other phones?

    A. Because phone B has a key ring (CSS) that contains all the keys, it can reach all the devices.

  • Q. What phones can reach phone E?

    A. Because phone E has no lock (partition), all phones can reach it.

  • Q. What phones can phone E reach?

    A. Because phone E has no keys, it can only reach devices that have no locks. In this example, phone E can only dial itself.

Figure 5-1, along with these questions and answers, should help you begin to understand how partitions and CSS work. Of course, as with any simple concept, it has the potential to become more complicated as the number of CSS and partitions grows. This is where some people begin to become confused, because of an inaccurate base understanding of the concepts. Now look at some of the more interesting aspects of CSS and partitions.

The first misconception that should be dispelled is this: If two devices have the same partition, they can call each other. Having the same partition alone is not enough. Going back to the lock and key ring analogy, if two people have the same locks, keyed the same way on their houses, but they have no keys, can they access each other's houses? Of course they can't, and they cannot even access their own houses. This demonstrates that a device's partition (lock) has no effect on where the device can call. However, if two devices that have the same partition also have a CSS that enables them access to their partitions, they can dial each other.

The next important point is the order of CSS. As demonstrated in the earlier example, CSS can enable access to more than one partition. Now, imagine that a device has a CSS that enables it to match two devices with the same number, but in different partitions. Figure 5-2 offers an example of this situation.

Figure 5-2

Figure 5-2 CSS Matches Multiple Destinations

In this example, phones A and D have the same extension of 1001. Phones B and C can reach both phones because their CSS enables access to both the square and triangle partition. So the question is, which phone rings when phone C dials 1001? Often people answer this question with, "It takes the closer match." Because 1001 matches 1001 exactly, both phones are the closest matches. Others assume that both phones ring because phone C has access to both partitions. What actually happens is that when a search for a match is conducted, multiple closest matches are found. Because there are multiple closest matches, the order in which objects appear in the CSS comes into play. When you create a CSS, you prioritize the order in which partitions should be searched. This order determines which partition is used if there are two closest matches. In the example, Figure 5-2 shows that the order of the keys for phone C is square followed by triangle, meaning that when phone C dials 1001, it would first match the 1001 that has the square partition, which is phone A.

To add a little more complexity to this, it is possible to have a CSS on both the device and the line. For example, the phone can have a CSS that grants access to the square partition, and a line on the phone can have a CSS that grants access to the triangle partition. In such a case, the line CSS takes priority. Figure 5-3 shows an example of this. This example moves away from the locks and keys analogy to focus more on the actual terms.

Figure 5-3

Figure 5-3 Line/Device CSS Example

In Figure 5-3, phone A has two lines, 1001 and 1010. 1001 has no CSS, and line 1010 has a CSS that grants access to devices in the executive partition. Phone A also has a CSS at the device level, which enables access to devices in the lobby and employee partitions. Because the 1001 line does not have a CSS of its own, it has access only to devices that can be reached using the device's CSS. Because line 1010 has a CSS of its own, it has access to devices that can be reached using its CSS and the device's CSS. This means that when dialing from line 1001, only devices in the lobby and employee partitions are accessible; but when dialing from line 1010, devices in the lobby, employee, and exec partitions are accessible.

Now, take a look at the other three phones. Phone B has the extension of 1004, and that line is in the employee partition. Phone C has the extension of 1003, and that line is in the lobby partition. Phone D has the extension of 1004, and that line is in the exec partition.

Using what you have learned, answer the following three questions:

  • What is the result if 1004 is dialed from line 1001?
  • What is the result if 1004 is dialed from line 1010?
  • Can line 1010 reach line 1003?

The answers to these questions are as follows:

  • Q. What is the result if 1004 is dialed from line 1001?

    A. Because line 1001 has no CSS of its own, it relies solely on the device's CSS. The device's CSS has access to the employee and lobby partitions, so line 1001 can reach only the 1004 on phone B because it is in the employee partition.

  • Q. What is the result if 1004 is dialed from line 1010?

    A. Because line 1010 has a CSS, it has access to all devices to which the line and device's CSS grants access. Because it can reach phones B and D and both of them match 1004, the line's CSS takes priority and phone D rings.

  • Q. Can line 1010 reach line 1003?

    A. Line 1010 can reach any device to which the line and/or the device's CSS grants access. Because the device's CSS has access to the lobby partition, which is the partition that 1003 is in, it can reach it.

At this point, you should have a good idea of how partitions and CSS work. We now take a look at a real-world, practical example of how CSS and partitions can be used.

The BGD Company has deployed a Communications Manager solution and has configured the route patterns that are shown in Table 5-1. As you can see, the route patterns enable callers to reach anywhere they need to dial with the exception of 1-900 numbers, which are blocked. The problem is that these patterns also enable some callers to make unauthorized calls that the company disapproves of. For example, if a person's job does not require the placement of international calls, the dial plan should not enable the employee's phone to place them.

Table 5-1. BGD's Route Patterns

Pattern

Notes

Matches

9.[2-9]XXXXXX

9.810[2-9]XXXXXX

PreDot Discard

PreDot Discard

Local 7- and 10-digit calls

9.810586XXXX

9.810587XXXX

PreDot Discard

PreDot Discard

10-digit calls that are not local

9.1[2-9]XX[2-9]XXXXXX

PreDot Discard

Long-distance calls

9.011!

9.011!#

PreDot Discard

PreDot Trailing-# Discard

International calls

9.1900[2-9]XXXXXX

Block Pattern

1-900 numbers

911

9.911

Urgent Priority

PreDot Discard and Urgent Priority

Emergency service calls

In this example, BGD has decided that it actually has four classes of users. The first class, the executives, can make any calls they want, other than 1-900 calls. The second class, the administrative assistants, are not allowed to make 1-900 calls or international calls. The third class, standard users, can only reach internal extensions, local numbers, and emergency services. The fourth class, lobby phones, for example, can only make calls internally and to emergency services. To accomplish this, partitions and CSS must be configured and assigned to patterns and devices.

When creating partitions, a common practice is to name them so that the name describes to what the partition is assigned. For example, a partition that is going to be assigned to a pattern that matches a local number can be called Local PT.

In this example, five types of calls are allowed: internal, local, long-distance, international, and emergency. The following is the list of partitions that are needed, and to which patterns they are assigned:

  • Internal_PT: Patterns that match internal numbers
  • Local_PT: Patterns that match local numbers
  • LD_PT: Patterns that match long-distance numbers
  • International_PT: Patterns that match international numbers
  • Emergency_PT: Patterns that match emergency service numbers

After the partitions are created, CSS are needed. Because BGD has defined four classes of users, four CSS are needed. Just as with partitions, it is recommended that CSS are named so that the name helps identify to which partitions the CSS have access. Table 5-2 shows the CSS and the partitions to which each has access and that are needed for BGD.

Table 5-2. CSS and Associated Partitions

CSS

Partitions

Internal_CSS

Internal_PT

Emergency_PT

Internal_Local_LD_CSS

Internal_PT

Local_PT

Emergency_PT

Internal_CSS

Internal_PT

Local_PT

LD_PT

Emergency_PT

Unlimited_CSS

Internal_PT

Local_PT

LD_PT

International_PT

Emergency_PT

Now that partitions and CSS are defined, take a look at what each is assigned to. First, examine the partitions. You need to understand that partitions are assigned to patterns of DNs, not devices. This means that if you want to prevent a device from making long-distance calls, you assign a partition to the patterns that match long-distance numbers, and make sure that the device's CSS does not have access to the partition. Table 5-3 shows the five partitions that have been created and the patterns to which each is assigned.

Table 5-3. Partitions and Patterns

Partitions

Patterns

Internal_PT

DNs of the phones

Local_PT

9.[2-9]XXXXXX

9.810[2-9]XXXXXX

LD_PT

9.810586XXXX

9.810587XXXX

9.1[2-9]XX[2-9]XXXXXX

International_PT

9.011!

9.011!#

Emergency_PT

911

9.911

You might notice that the 9.1900[2-9]XXXXXX pattern has not been assigned to a partition but will still work. Remember, if a pattern does not have a partition explicitly assigned, it falls into the null partition, and all devices have access to the null partition. Because the 9.1900[2-9]XXXXXX pattern is set up so that it blocks all calls that match it, you want all devices to have access to it so that no one can place these types of calls. However, it is recommended to apply partitions to all patterns to ensure that no calls can be placed by phones that do not have the proper CSS. With this is mind, the Internal_PT partition can be applied to the 9.1900[2-9]XXXXXX pattern because all devices can reach that partition.

Now look at how the CSS should be assigned. Remember that CSS can be assigned at both the device and line. For this example, they are assigned at the device level only. Table 5-4 shows the CSS and the types of device to which each is assigned.

Table 5-4. CSS and Assigned Devices

CSS

Devices

Unlimited_CSS

Executive phones

Internal_Local_LD_CSS

Administrative assistant phones

Internal_Local_CSS

Standard users

Internal_CSS

Lobby phones

Now that you understand which CSS and partitions are needed for BGD, and where each is applied, take a look at the big picture. Table 5-5 shows which CSS is assigned to each of the four different classes of phones. Under the CSS heading is a list of the partitions that can be accessed. Under the partitions is a list of patterns. Using this table, it is easy to see what destinations various phones can reach.

Table 5-5. CSS Assigned to Phones and the Patterns They Can Reach

Device

CSS>Partition>Patterns

Executive phones

Unlimited_CSS

Internal_PT

All Internal Phones

Local_PT

9.[2-9]XXXXXX

9.810[2-9]XXXXXX

LD_PT

9.810586XXXX

9.810587XXXX

9.1[2-9]XX[2-9]XXXXXX

International_PT

9.011!

9.011!#

Emergency_PT

911

9.911

Administrative assistant phones

Internal_Local_LD_CSS

Internal_PT

All Internal Phones

Local_PT

9.[2-9]XXXXXX

9.810[2-9]XXXXXX

LD_PT

9.810586XXXX

9.810587XXXX

9.1[2-9]XX[2-9]XXXXXX

Emergency_PT

911

9.911

Standard user phones

Internal_Local_CSS

Internal_PT

All Internal Phones

Local_PT

9.[2-9]XXXXXX

9.810[2-9]XXXXXX

Emergency_PT

911

9.911

Lobby phones

Internal_CSS

Internal_PT

All Internal Phones

Emergency_PT

911

9.911

Up to this point, only the assigning of CSS to phones and lines has been discussed. CSS are assigned to devices, which include gateways. A CSS is assigned to a gateway so that inbound calls can reach internal destinations. In the example of BGD, all the internal phones are placed in the Internal_PT partition. If the gateways do not have access to this partition, no incoming calls are allowed. So you can see that not only must phones have CSS, but gateways require them as well. In the case of BGD, the Internal_CSS can be assigned to the gateways, which would grant outside calls access to all internal phones.

In the BGD example, all internal phones were in the Internal_PT partition, meaning that because all devices had a CSS that granted access to the Internal_PT partition, all phones could be reached. In some cases, this is undesirable. Sometimes there are certain numbers that should be reached only by certain devices. An example often used is that of an executive's phone. Often it is desired that only the executive's assistant be able to reach the executive. To accomplish this, the executive's phone is placed in a separate partition, to which only the assistant's phone has access.

Now that you have a good idea of what CSS and partitions are, move on to discussing how they are created and configured.

Creating Calling Search Spaces and Partitions

Creating CSS and partitions is much easier than understanding and properly applying them. Before you move on to the process of creating them, you should make sure that you have taken the time to determine the different classes of users your environment has, and what destinations each user will be allowed to call. After you have done this, create a list of the partitions that are required. Next, create a CSS that defines what partitions are accessible. After you have created this, you can begin to create the partitions and CSS. Because CSS are created by choosing partitions to which they will have access, the partitions must be created first. The following steps show how to create partitions:

  • Step 1. From within CCMAdmin, select Call Routing > Class of Control > Partition.
  • Step 2. Click the Add New link.
  • Step 3. A screen displays that offers an area in which you can enter the name of the partition followed by a description. You must place a comma (,) between the name and description. If you do not enter a description, the name of the partition will be used as the description. You can create up to 75 partitions at a time on this screen by placing each on a new line. Figure 5-4 shows an example of adding five partitions at one time.
    Figure 5-4

    Figure 5-4 Creating Partition Configurations

  • Step 4. After you enter all the desired partitions, click Save.

As you can see, the creation of partitions is a simple task. Now that partitions are added, you can start to create CSS by working through the following steps:

  • Step 1. From within CCMAdmin, select Call Routing > Class of Control > Calling Search Space.
  • Step 2. Click the Add New link.
  • Step 3. A screen similar to that shown in Figure 5-5 displays.
    Figure 5-5

    Figure 5-5 Creating CSS

  • Step 4. Enter a name in the Calling Search Space Name field. Remember that the name should help identify the purpose of this CSS.
  • Step 5. Enter a description in the Description field.
  • Step 6. A list of partitions displays in the Available Partitions box. If you have a large number of partitions, you can limit the partitions that display in this list by entering the appropriate search criteria in the Find Partitions Where fields and clicking Find.
  • Step 7. Highlight the first partition to which you want the CSS to have access, and click the Down Arrow below this box. This causes that partition to display in the Selected Partitions box.
  • Step 8. Repeat Step 7 for each partition to which you want the CSS to have access. These should be added in the order you want to have them searched.
  • Step 9. After all the partitions have been added, you can change the order in which they display. Remember, the order in which they display determines which partition is used if multiple partitions within the same CSS contain exact matches for a dialed number. To change the order, highlight the partition you want to move, and click the Up or Down Arrow to the right of the box. Figure 5-6 shows what the screen looks like when adding the Internal_Local_CSS, which was used in the previous example.
    Figure 5-6

    Figure 5-6 Example CSS

  • Step 10. After all desired partitions are listed in the correct order in the Selected Partitions box, click Save.

You need to repeat these steps to add all the CSS that your environment requires. After all the partitions and CSS are added, it is time to apply them. Adding partitions and CSS have absolutely no effect on call processing until they are applied to patterns and devices.

Applying Calling Search Spaces and Partitions

You are now ready to start applying the partitions and CSS to devices and patterns. After a partition is added to a pattern, only devices that have the correct CSS can reach that pattern. For this reason, you might want to assign CSS to the devices before assigning partitions. Assigning partitions before assigning CSS is similar to putting a lock on a door and not giving anyone a key. Until the keys are handed out, no one can get in.

CSS are applied to devices and lines. When applied to both, the line's CSS has priority but does not nullify the devices. This means a line that has its own CSS has access to partitions that both the line's CSS and the device's CSS allow.

Now take a look at how a CSS is assigned to a phone, a line on the phone, and a gateway.

Assigning a CSS to a Phone

The steps that follow show how to assign a CSS to a phone:

  • Step 1. From within CCMAdmin, Select Device > Phone.
  • Step 2. Enter search criteria in the search field to limit the results and click Find.
  • Step 3. Select the phone to which you want to assign a CSS from the list that is generated.
  • Step 4. The Phone Configuration screen displays. To assign a CSS to the phone, select a CSS from the Calling Search Space drop-down list, as shown in Figure 5-7.
    Figure 5-7

    Figure 5-7 Assigning a CSS to a Phone

  • Step 5. Click Save.
  • Step 6. A window displays to inform you that you must click the Apply Config button for the change to take affect. Click OK.
  • Step 7. Click Apply Config.
  • Step 8. A window displays to warn you that when you apply the configuration, the device might go through a restart. Click OK.

Assigning a CSS to a Line

The steps that follow show how to assign a CSS to a line on a phone:

  • Step 1. From within CCMAdmin, select Device > Phone.
  • Step 2. Enter search criteria in the search field to limit the results and click Find.
  • Step 3. Select the phone that contains the desired line from the list of phones that is generated.
  • Step 4. Click the desired line on the left side of the screen.
  • Step 5. On the Directory Number Configuration page, select the desired CSS from the Calling Search Space drop-down list, as shown in Figure 5-8.
    Figure 5-8

    Figure 5-8 Assigning a CSS to a Line

  • Step 6. Click Save.

Assigning a CSS to a Gateway or Trunk

The steps that follow show how to assign a CSS to a gateway or a trunk. Because the steps are so similar for both components, they have been combined.

  • Step 1. From within CCMAdmin, select Device > Gateway or Device > Trunk.
  • Step 2. Enter search criteria in the search field to limit the results, and click Find.
  • Step 3. From the list that is generated, select the gateway/trunk to which you want to assign a CSS.
  • Step 4. Select the CSS from the Calling Search Space drop-down list.
  • Step 5. Click Save.
  • Step 6. A window displays informing you that you must click Apply Config for the change to take affect. Click OK.
  • Step 7. Click Apply Config.
  • Step 8. A window displays warning you that when you apply the configuration, the device might go through a restart. Click OK.

Now that you have assigned CSS, you can assign partitions. Partitions are assigned to patterns of directory numbers. Examples of how to assign them to CSS and partitions follow.

Assigning a Partition to a Line (Directory Number)

The following steps show how to assign a partition to a line:

  • Step 1. From within CCMAdmin, select Device > Phone.
  • Step 2. Enter search criteria in the search field to limit the results and click Find.
  • Select the phone that contains the desired line from the list of phones that is generated.
  • Step 3. Click the desired line on the left side of the screen.
  • Step 4. On the Directory Number Configuration page, select the desired partition from the Route Partition drop-down list, as shown in Figure 5-9.
    Figure 5-9

    Figure 5-9 Assigning a Partition to a Line

  • Step 5. Click Save.

Assigning a Partition to a Pattern

  • Step 1. From within CCMAdmin, select Call Routing > Route/Hunt > Route Pattern.
  • Step 2. To limit the results, enter search criteria in the search field and click Find.
  • Step 3. Select the route pattern from the list that displays.
  • Step 4. Select the partition from the Route Partition drop-down list, as shown in Figure 5-10.
    Figure 5-10

    Figure 5-10 Assigning a Partition to a Route Pattern

  • Step 5. Click Save.

After the partitions are applied, you can begin testing the system to ensure that allowed calls can be placed, and those that are not allowed cannot be placed.

Adding CSS and partitions after the system is in place can require a lot of work. Remember that you can use the the Bulk Admin Tool (BAT) to quickly apply or change a CSS or partition on a large number of objects.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020