In this section:

Bandwidth can be reserved for a time interval for calls from or to an endpoint or between two endpoints. An endpoint is identified by its H.323 ID and E.164 aliases. The amount of bandwidth to reserve is taken from the endpoint ARQ message at the beginning of the call and is not specified here in a reservation.

If a call is scheduled but there is not enough bandwidth for it, first unscheduled calls and then scheduled calls past their stop time are terminated. The call is rejected if there is still not enough bandwidth (scheduled calls within their reserved times are never terminated). A reservation does not specify or imply the number of calls for which bandwidth is reserved.

Reservation Tips

Specifying both aliases is useful for point-to-point calls where the aliases of both parties are known. For presentations, it may be useful to just reserve bandwidth for the presenter by specifying his or her endpoint's alias and leaving the other alias field blank. Leaving both alias fields blank matches all calls. If both time fields are blank, the reservation is forever—no time constraint is applied. Reservations are not recurring, for example, every week at 14:00; however, you can edit a reservation and update the time.

The schedule entry shown in the following screen capture reserves bandwidth for any number of calls to or from an endpoint whose ARQ contains an H.323 ID or E.164 alias beginning with 5612.

Bandwidth Scheduling Example



The 5612 alias could have been specified in the Alias 2 field, instead. Because an alias expression is used as a prefix, this matches any alias that begins with 5612. In most cases, this subtlety does not matter; there is little to no risk of there being another endpoint on the network with the alias of 561230, for example.

However, if you want to be extra careful, you could follow 5612 with a special character like the dollar sign, for example “5612$.” The special character indicates the end of the expression. Conversely, if you didn’t want your alias expression to be treated as a prefix, you could include the asterisk character at the beginning, for example, “*@example.net.” This indicates any number of any kind of character.

The Reservations table lists reservations in chronological order according to start time. All “forever” reservations are listed first. There are no duplicate entries. An ARQ may match multiple reservations, so the first reservation is used. The only impact is that the call's reservation ends based on the stop time for that reservation. The call is not terminated just because its reservation has expired; however, if there is a new scheduled call, it might be terminated to make room for the new call.

Configure H.323 Bandwidth Scheduling

This section outlines how to configure the H.323 Bandwidth Scheduling.

To Configure H.323 Bandwidth Scheduling

  1. Choose VoIP > H.323.

  2. Click Scheduling in the H.323 Settings navigation panel at the top of the page to open the H.323 Scheduling page.

  3. Configure settings using the information in the following table as a guide. When you have finished configuring settings, click Commit to make your changes take effect.

    H.323 Scheduling Parameters

    ItemDescription

    Reservations

    Lists reservations in chronological order according to start time. All “forever” reservations are listed first. There are no duplicate entries.

    Start time

    		Describes the date and time in Coordinated Universal Time (UTC), no time-zone offset is applied. Fields use the format, mm/dd/yyyy hh:mm. Leading zeros are allowed, the year must be four digits, the time uses a 24-hour clock.

    Stop time

    Alias 1

    (Optional) Identifies the two endpoints in a call.

    An alias field contains a regular expression for matching at least one H.323 ID or E.164 alias in the list of source or destination aliases in an ARQ. An alias expression is always treated as a prefix; matching begins at the beginning of an alias. ARQ source and destination aliases are searched using Alias 1 and Alias 2, respectively, or Alias 2 and Alias 1, respectively. It is not necessary to specify the direction of the call—who is the called party and who is the calling party. A blank alias field is a wildcard; it matches all aliases.

    Alias 2

    Add a Reservation

    ActionAdds or edits a reservation.
    Start

    Specifies the start date and time in the format mm/dd/yyyy hh:mm. Leading zeros are allowed, the year must be four digits, the time uses a 24-hour clock.

    Stop

    Specifies the stop date and time in the format mm/dd/yyyy hh:mm. Leading zeros are allowed, the year must be four digits, the time uses a 24-hour clock.

    Alias 1

    (Optional) Specifies the two endpoints in a call.

    An alias field contains a regular expression for matching at least one H.323 ID or E.164 alias in the list of source or destination aliases in an ARQ. An alias expression is always treated as a prefix; matching begins at the beginning of an alias.

    Alias 2

  4. Manage the bandwidth schedule in the Reservations table:

    1. Select checkboxes for the entries that you want to delete. Click All to choose all the entries or None to clear your selections.

    2. Click Delete.

    3. Click OK to confirm.

  5. Proceed to Adding a Reservation.

Adding a Reservation

This section outlines how to add a reservation.

To add a Reservation

  1. Choose Add a New Reservation from the Action drop-down list.
  2. Enter the start and stop times in the Start Time and Stop Time fields. Enter values in mm/dd/yyyy hh:mm format. Leading zeros are allowed, the year must be four digits, the time uses a 24-hour clock.

  3. (Optional) Enter an alias value in the Alias 1 and Alias 2 fields to identify the two endpoints in a call.
    Regular expressions are listed in the Regular Expressions table. Regular expression examples are listed in the Regular Expression Examples table. Refer to Regular Expressions and Expression Examples.

  4. Click Commit to save your settings.

  • No labels