Contents

Cisco UBE as a Flow Metadata Producer

The Cisco Unified Border Element (Cisco UBE) as a Flow Metadata Producer feature supports rich media (UC and Collaboration Video) deployment, bandwidth management, and optimization over an enterprise WAN link. It also provides network support for various adaptive video endpoints as well as older non-adaptive endpoints to ensure a high quality experience.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Information About Cisco UBE as a Flow Metadata Producer

Cisco UBE Video Optimization at the Network Boundary

When the Cisco Unified Border Element (Cisco UBE) as a flow metadata producer feature is configured, then the media stream is terminated and regenerated on Cisco UBE in flow-through mode, and Cisco UBE also regenerates flow metadata for the media stream. This flow metadata is used by other applications to monitor and control the call quality. The following diagram shows how video optimization at the network boundary works.

Figure 1. Cisco UBE Video Optimization at the Network Boundary



Cisco UBE Flow Metadata Producer

Within the Cisco Medianet architecture the Cisco Unified Border Element (Cisco UBE) acts as an Real-time Transport Protocol (RTP) translator or mixer when media (RTP streams) flows through the Cisco UBE. Cisco UBE terminates and then regenerates the RTP stream (that is, it changes the IP address and port numbers) and Cisco UBE also terminates and regenerates flow metadata from upstream.

The Cisco UBE as a Flow Metadata Producer feature works with other functionality to allow intelligent marking so that RTP packets of a video call flowing through Cisco UBE can be properly marked. In situations where congestion occurs, on this device or a downstream device, selective dropping is possible to reduce the impact on video quality.

Configuring Cisco UBE as a Flow Metadata Producer

Configuring Cisco UBE as a Flow Metadata Producer at Global Level

SUMMARY STEPS

    1.    metadata flow

    2.    voice service voip

    3.    mode border-element

    4.    allow-connections sip to sip

    5.    allow-connections h323 to h323

    6.    media metadata generate local stream-direction tx-rx

    7.    exit


DETAILED STEPS
     Command or ActionPurpose
    Step 1 metadata flow


    Example:
    Device(config)# metadata flow
     

    Enables Cisco Unified Border Element (Cisco UBE) as a flow metadata producer for all interfaces.

     
    Step 2 voice service voip


    Example:
    Device(config)# voice service voip
     

    Enters voice-service configuration mode and specifies VoIP as the voice-encapsulation type.

     
    Step 3 mode border-element


    Example:
    Device(conf-voi-serv)# mode border-element
     

    Enables the set of commands used in border-element configuration on the Cisco 2900 and Cisco 3900 series platforms.

     
    Step 4 allow-connections sip to sip


    Example:
    Device(conf-voi-serv)# allow-connections sip to sip
     

    Allows connections between Session Interface Protocol (SIP) endpoints.

     
    Step 5 allow-connections h323 to h323


    Example:
    Device(conf-voi-serv)# allow-connections h323 to h323
     

    Allows connections between H.323 endpoints.

     
    Step 6 media metadata generate local stream-direction tx-rx


    Example:
    Device(conf-voi-serv)# media metadata generate local stream-direction tx-rx
     

    Configures Cisco UBE to generate flow metadata for incoming and outgoing call-legs.

     
    Step 7 exit


    Example:
    Device(conf-voi-serv)# exit
     

    Exits voice-service configuration mode.

     

    Configuration Examples for Cisco UBE as a Flow Metadata Producer

    Example: Cisco UBE as a Flow Metadata Producer at Global Level

    The following example shows the configuration required to set up Cisco UBE as a flow metadata producer at global level.

    Device(config)# metadata flow
Device(config)# voice service voip
Device(conf-voi-serv)# mode border-element
Device(conf-voi-serv)# allow-connections sip to sip
Device(conf-voi-serv)# allow-connections h323 to h323
Device(conf-voi-serv)# media metadata generate local stream-direction tx-rx
Device(conf-voi-serv)# exit

    Additional References for Cisco UBE as a Flow Metadata Producer

    Related Documents

    Related Topic

    Document Title

    Cisco IOS commands

    Cisco IOS Master Command List, All Releases

    Voice commands

    MIBs

    MIB MIBs Link
     

    To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

    http:/​/​www.cisco.com/​go/​mibs

    Technical Assistance

    Description Link

    The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

    To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

    Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

    http:/​/​www.cisco.com/​support

    Feature Information for Cisco UBE as a Flow Metadata Producer

    The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

    Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

    Table 1 Feature Information for Cisco UBE as a Flow Metadata Producer

    Feature Name

    Releases

    Feature Information

    Cisco UBE as a Flow Metadata Producer

    15.3(3)M

    The Cisco Unified Border Element (Cisco UBE) as a Flow Metadata Producer feature supports rich media (UC and Collaboration Video) deployment, bandwidth management, and optimization over an enterprise WAN link. It also provides network support for various adaptive video endpoints as well as older non-adaptive endpoints to ensure a high quality experience.

    The following commands were introduced or modified: media metadata.
    Cisco UBE as a Flow Metadata Producer

    Cisco UBE as a Flow Metadata Producer

    The Cisco Unified Border Element (Cisco UBE) as a Flow Metadata Producer feature supports rich media (UC and Collaboration Video) deployment, bandwidth management, and optimization over an enterprise WAN link. It also provides network support for various adaptive video endpoints as well as older non-adaptive endpoints to ensure a high quality experience.

    Finding Feature Information

    Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

    Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

    Information About Cisco UBE as a Flow Metadata Producer

    Cisco UBE Video Optimization at the Network Boundary

    When the Cisco Unified Border Element (Cisco UBE) as a flow metadata producer feature is configured, then the media stream is terminated and regenerated on Cisco UBE in flow-through mode, and Cisco UBE also regenerates flow metadata for the media stream. This flow metadata is used by other applications to monitor and control the call quality. The following diagram shows how video optimization at the network boundary works.

    Figure 1. Cisco UBE Video Optimization at the Network Boundary



    Cisco UBE Flow Metadata Producer

    Within the Cisco Medianet architecture the Cisco Unified Border Element (Cisco UBE) acts as an Real-time Transport Protocol (RTP) translator or mixer when media (RTP streams) flows through the Cisco UBE. Cisco UBE terminates and then regenerates the RTP stream (that is, it changes the IP address and port numbers) and Cisco UBE also terminates and regenerates flow metadata from upstream.

    The Cisco UBE as a Flow Metadata Producer feature works with other functionality to allow intelligent marking so that RTP packets of a video call flowing through Cisco UBE can be properly marked. In situations where congestion occurs, on this device or a downstream device, selective dropping is possible to reduce the impact on video quality.

    Configuring Cisco UBE as a Flow Metadata Producer

    Configuring Cisco UBE as a Flow Metadata Producer at Global Level

    SUMMARY STEPS

      1.    metadata flow

      2.    voice service voip

      3.    mode border-element

      4.    allow-connections sip to sip

      5.    allow-connections h323 to h323

      6.    media metadata generate local stream-direction tx-rx

      7.    exit


    DETAILED STEPS
       Command or ActionPurpose
      Step 1 metadata flow


      Example:
      Device(config)# metadata flow
       

      Enables Cisco Unified Border Element (Cisco UBE) as a flow metadata producer for all interfaces.

       
      Step 2 voice service voip


      Example:
      Device(config)# voice service voip
       

      Enters voice-service configuration mode and specifies VoIP as the voice-encapsulation type.

       
      Step 3 mode border-element


      Example:
      Device(conf-voi-serv)# mode border-element
       

      Enables the set of commands used in border-element configuration on the Cisco 2900 and Cisco 3900 series platforms.

       
      Step 4 allow-connections sip to sip


      Example:
      Device(conf-voi-serv)# allow-connections sip to sip
       

      Allows connections between Session Interface Protocol (SIP) endpoints.

       
      Step 5 allow-connections h323 to h323


      Example:
      Device(conf-voi-serv)# allow-connections h323 to h323
       

      Allows connections between H.323 endpoints.

       
      Step 6 media metadata generate local stream-direction tx-rx


      Example:
      Device(conf-voi-serv)# media metadata generate local stream-direction tx-rx
       

      Configures Cisco UBE to generate flow metadata for incoming and outgoing call-legs.

       
      Step 7 exit


      Example:
      Device(conf-voi-serv)# exit
       

      Exits voice-service configuration mode.

       

      Configuration Examples for Cisco UBE as a Flow Metadata Producer

      Example: Cisco UBE as a Flow Metadata Producer at Global Level

      The following example shows the configuration required to set up Cisco UBE as a flow metadata producer at global level.

      Device(config)# metadata flow
Device(config)# voice service voip
Device(conf-voi-serv)# mode border-element
Device(conf-voi-serv)# allow-connections sip to sip
Device(conf-voi-serv)# allow-connections h323 to h323
Device(conf-voi-serv)# media metadata generate local stream-direction tx-rx
Device(conf-voi-serv)# exit

      Additional References for Cisco UBE as a Flow Metadata Producer

      Related Documents

      Related Topic

      Document Title

      Cisco IOS commands

      Cisco IOS Master Command List, All Releases

      Voice commands

      MIBs

      MIB MIBs Link
       

      To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

      http:/​/​www.cisco.com/​go/​mibs

      Technical Assistance

      Description Link

      The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

      To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

      Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

      http:/​/​www.cisco.com/​support

      Feature Information for Cisco UBE as a Flow Metadata Producer

      The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

      Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

      Table 1 Feature Information for Cisco UBE as a Flow Metadata Producer

      Feature Name

      Releases

      Feature Information

      Cisco UBE as a Flow Metadata Producer

      15.3(3)M

      The Cisco Unified Border Element (Cisco UBE) as a Flow Metadata Producer feature supports rich media (UC and Collaboration Video) deployment, bandwidth management, and optimization over an enterprise WAN link. It also provides network support for various adaptive video endpoints as well as older non-adaptive endpoints to ensure a high quality experience.

      The following commands were introduced or modified: media metadata.