Configuring VoIP with a Configuration Editor

To configure VoIP on a device, perform the following tasks marked (Required). Perform other tasks if needed on your network.

Configuring the VoIP Interface (Required)

You must assign a local IP address to the vp-pim/0/0 interface on the Services Router and also a destination IP address to the TGM550 so that they can communicate with each other.

To configure the VoIP interface on the device:

  1. Navigate to the top of the interfaces configuration hierarchy.
  2. Perform the configuration tasks described in Table 39.
  3. If you are finished configuring the router, commit the configuration.
  4. Continue with Configuring the Media Gateway Controller List (Required).

Table 39: Configuring the VoIP Interface

Task

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

From the [edit] hierarchy level, enter

edit interfaces vp-3/0/0

Select the VoIP interface—for example, vp-3/0/0.

 

Create the logical unit 0.

Note: You cannot configure more than one logical unit on the VoIP interface. The logical unit number must be 0.

Enter

edit unit 0

Configure the source IPv4 address—for example, 10.10.10.1/32—for the VoIP interface.

The following rules apply:

  • You cannot specify more than one IPv4 address.
  • Do not assign the following IPv4 addresses:
    • A broadcast address (255.255.255.255)
    • A class E address (240.0.0.0 to 255.255.255.254)
    • A loopback address (127.0.0.0 to 127.255.255.255)
    • A multicast address (224.0.0.0 to 239.255.255.255)
    • An address with 0 as the first byte or an address with 0 or 255 as the last byte
  • The VoIP interface needs a point-to-point connection to the TGM550. To configure the point-to-point connection, specify /32 as the subnet mask in the IPv4 address.

Enter

set family inet address 10.10.10.1/32 destination 10.10.10.2

Configure the destination IP address—for example 10.10.10.2—for the TGM550. The TGM550 uses this IP address to identify itself when communicating with other devices, particularly the Media Gateway Controller (MGC).

Caution: Applying a new or modified IP address resets the TGM550. For existing configurations, ensure that the TGM550 configuration is saved (see Saving the TGM550 Configuration) and that the TGM550 module is carrying no voice traffic.

You cannot specify more than one IP address. For more information, see TGM550 IP Addressing Guidelines.

Configuring the Media Gateway Controller List (Required)

To provide telephony services, the TGM550 must be registered with at least one Media Gateway Controller (MGC). You can configure the IP addresses of up to four MGCs that the TGM550 can connect to in the event of a link failure. For more information, see Media Gateway Controller.

In addition to configuring the MGC list from J-Web and the Junos OS CLI, you can log in to the TGM550 and configure the list. For more information, see the Administration for the Avaya IG550 Integrated Gateway at http://support.avaya.com.

This section contains the following topics:

Configuring an MGC List and Adding Addresses

In the following example, a TGM550 installed in slot 2 of a Services Router has the IP address 10.10.10.2. The TGM550 needs to have registered a primary MGC at address 172.16.0.0, and second and third MGC at addresses 10.10.10.30 and 10.10.10.10.40.

To configure the MGC list with the Junos OS CLI:

  1. Enter operational mode on the Junos OS CLI.
  2. Configure the IP addresses of the Media Gateway Controllers, by entering the set tgm fpc slot media-gateway-controller command with the IP addresses of the primary, second, and third MGC:

    user@host> set tgm fpc 2 media-gateway-controller [172.16.0.0 10.10.10.30 10.10.10.40]

    Note: Running the set tgm fpc slot media-gateway-controller command updates the startup configuration on the TGM550. You do not need to run the copy running-config start-config command to save the configuration on the module.

  3. Log in to the TGM550 with SSH, and verify that each MGC can be reached over the network.

    user@host> ssh 10.10.10.2
    password> root

    TGM550-00<root># ping 172.16.0.0
    ...

    TGM550-00<root># ping 10.10.10.30
    ...

    TGM550-00<root># ping 10.10.10.40
    ...
  4. Do one of the following:

Clearing an MGC List

In the following example, a TGM550 is installed in slot 2 of the router.

To remove all the IP addresses from the MGC list:

  1. Enter operational mode on the CLI.
  2. Enter the clear tgm fpc slot media-gateway-controller command:

    user@host> clear tgm fpc 2 media-gateway-controller

    The clear command removes all the MGC IP addresses. You cannot clear the IP address of a single MGC with this command.

  3. Add one or more new MGC IP addresses. (See Configuring an MGC List and Adding Addresses.)

Configuring Dynamic Call Admission Control on WAN Interfaces (Optional)

To configure dynamic call admission control (CAC), you define the bearer bandwidth limit (BBL) and activation priority on each WAN interface responsible for providing call bandwidth.

In this example, a Gigabit Ethernet, T1, and ISDN BRI interface are configured with the BBL and activation priority values shown in Table 40.

Table 40: Dynamic CAC Configuration Example

Interface Providing Call Bandwidth

Bearer Bandwidth Limit (BBL) Value

Activation Priority Value

Gigabit Ethernet

3000 Kbps

200

T1

1000 Kbps

150

ISDN BRI

128 Kbps

100

The Gigabit Ethernet interface is used as the primary link for providing call bandwidth because it has the highest activation priority value. When the Gigabit Ethernet interface is active, the TGM550 reports its BBL value of 3000 Kbps to the MGC. If the Gigabit Ethernet interface fails, the TGM550 automatically switches over to the T1 interface because it has the next highest activation priority. The TGM550 now reports the BBL value of the T1 interface to the MGC. If the T1 interface also fails, the TGM550 switches over to the ISDN BRI interface and reports the BBL value of the ISDN BRI interface to the MGC. Configuring dynamic CAC on multiple WAN interfaces allows the MGC to automatically control the call bandwidth when interfaces responsible for providing call bandwidth are unavailable.

For more information about dynamic CAC, see Dynamic Call Admission Control Overview.

To configure dynamic CAC on Services Router WAN interfaces:

  1. Navigate to the top of the interfaces configuration hierarchy.
  2. Perform the configuration tasks described in Table 41.
  3. If you are finished configuring the router, commit the configuration.
  4. Configure Call Admission Control: Bandwidth Limitation (CAC-BL) on Avaya Communication Manager. For more information, see the Administrator Guide for Avaya Communication Manager at http://support.avaya.com.
  5. Verify that dynamic CAC is configured correctly, see Verifying the VoIP Configuration.

Table 41: Configuring Dynamic CAC

Task

CLI Configuration Editor

Select the Gigabit Ethernet interface—for example, ge-0/0/3.

From the [edit] hierarchy level, enter

edit interfaces ge-0/0/3

Configure dynamic CAC on logical unit 0 of the Gigabit Ethernet interface with the activation priority and BBL values given in Table 40.

  1. Enter

    edit unit 0

  2. Enter

    set dynamic-call-admission-control activation-priority 200 bearer-bandwidth-limit 3000

Select the T1 interface—for example, t1-6/0/0.

From the [edit] hierarchy level, enter

edit interfaces t1-6/0/0

Configure dynamic CAC on logical unit 0 of the T1 interface with the activation priority and BBL values given in Table 40.

  1. Enter

    edit unit 0

  2. Enter

    set dynamic-call-admission-control activation-priority 150 bearer-bandwidth-limit 1000

Select the ISDN BRI interface—for example, br-1/0/3.

From the [edit] hierarchy level, enter

edit interfaces br-1/0/3

Configure dynamic CAC on logical unit 0 of the ISDN BRI interface with the activation priority and BBL values given in Table 40.

  1. Enter

    edit unit 0

  2. Enter

    set dynamic-call-admission-control activation-priority 100 bearer-bandwidth-limit 128

Modifying the IP Address of the TGM550

Caution: The TGM550 is reset when you commit the configuration after modifying the IP address. Before modifying the TGM550 IP address, take the following precautions:

  • Log into the TGM550 and enter copy running-config startup-config to save the TGM550 configuration. (For login instructions, see Accessing and Administering the TGM550 CLI.)
  • Ensure that the TGM550 is not currently handling voice traffic.

To modify the IP address of the TGM550:

  1. Navigate to the top of the interfaces configuration hierarchy.
  2. Perform the configuration tasks described in Table 42.
  3. If you are finished configuring the router, commit the configuration.

Table 42: Modifying the IP Address of the TGM550

Task

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

From the [edit] hierarchy level, enter

edit interfaces vp-3/0/0 unit 0

Select the logical VoIP interface—for example, vp-3/0/0.0.

 

Modify the destination IP address for the TGM550 to a different address—for example, 10.10.10.80.

For guidelines, see TGM550 IP Addressing Guidelines.

Note: You cannot specify more than one IP address.

Enter

set family inet address 10.10.10.1/32 destination 10.10.10.80

Copyright© 1999-2010 Juniper Networks, Inc. All rights reserved.