[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-06-24

You can use the View voice routing test case information dialog box to run informal tests before creating an actual test case. When you are satisfied with the outcome of a test, you have the option of saving it as a formal test case.

To run an informal voice routing test

  1. Open Communications Server Control Panel.

  2. In the left navigation bar, click Voice Routing.

  3. Click the Test Voice Routing tab.

  4. Click View voice routing test case information.

  5. In the Dialed number field, type in the phone number you want to use for this test. This number will be normalized and displayed in the Normalized number field of the Results pane.

  6. In the Dial plan list, select the dial plan to use for testing the dialed number. Default is the Global dial plan.

    When you run the test, the first normalization rule in this dial plan that matches the dialed number will be displayed in the Normalization rule field of the Results pane.

  7. In the Policy list, select the voice policy to use for testing the dialed number. Default is the Global voice policy.

    When you run the test, the first matching PSTN usage record in this voice policy will be displayed in the First PSTN usage field of the Results pane. Also, the first matching voice route that is associated with this PSTN usage record will be displayed in the First route field.

  8. (Optional) Select the Populate from user check box if you want to test the dialed number against the voice policy assigned to a particular user.

    1. Click Browse to display the Select Enterprise Voice Users dialog box.

    2. Click Find to display the list of users who are enabled for Enterprise Voice.

    3. Double-click the user name whose assigned voice policy you want to use for this test. The Policy field is now populated with the voice policy assigned to the selected user.

    When you run the test, the first matching PSTN usage record in this voice policy will be displayed in the First PSTN usage field of the Results pane. Also, the first matching voice route that is associated with this PSTN usage record will be displayed in the First route field.

  9. Click Run to run the test case. The results are shown in the right panel of the dialog box.

  10. (Optional) Click Save as if you want to save this test configuration as a formal test case.

    1. In the Name field of the Save Voice Routing Test Case Information dialog box, type a unique name for the test case.

      The name must be unique among all voice routing test cases in your Enterprise Voice deployment. It can be up to 32 characters in length and may contain any alphanumeric characters plus the backslash (\), period (.) or underscore (_).

    2. Note that the remaining fields on the Save Voice Routing Test Case Information dialog box are read-only, and are prepopulated from the informal test configuration and results. Verify that this is the configuration you want to save for the test case.

      Note:
      Values from the test results are used to prepopulate fields on the Save Voice Routing Test Case Information dialog box as follows:
      • Expected translation is prepopulated with the value in the Normalized number field.

      • Expected route is prepopulated with the value in the First route field.

      • Expected PSTN usage record is prepopulated with the value in the First PSTN usage field.

      If matches for any of these values were not found during the test run, the corresponding field is empty on the Save Voice Routing Test Case Information dialog box.
    3. Click Ok to save the test case, or click Cancel to return to return to the View voice routing test case information dialog box to further develop the test before saving it.

Any time you create a voice routing test case, you must run the Commit All command to publish the configuration change. For more information, see Publish Pending Changes to the Voice Routing Configuration.

See Also