Cisco Unified Border Element Configuration Guide Through Cisco IOS XE 17.5

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

• Read Me First
• New and Changed Information
• Supported Platforms
• CUBE Fundamentals and Basic Setup
  • Overview of Cisco Unified Border Element
  • Virtual CUBE
  • Dial-Peer Matching
  • DTMF Relay
  • Introduction to Codecs
  • Call Admission Control
  • Basic SIP Configuration
  • SIP Binding
  • Media Path
  • SIP Profiles
  • SIP Out-of-Dialog OPTIONS Ping Group
  • Configure TCL IVR Applications
  • VoIP for IPv6
  • Monitoring of Phantom Packets
  • Configurable SIP Parameters via DHCP
  • Matching Inbound Dial Peers by URI
  • URI-Based Dialing Enhancements
  • Multiple Pattern Support on a Voice Dial Peer
  • Outbound Dial-Peer Group as an Inbound Dial-Peer Destination
  • Inbound Leg Headers for Outbound Dial-Peer Matching
  • Server Groups in Outbound Dial Peers
  • Domain-Based Routing Support on the Cisco UBE
  • ENUM Enhancement per Kaplan Draft RFC
  • Support for Multi-VRF
  • Configuring Multi-Tenants on SIP Trunks
  • Codec Support and Restrictions
  • Codec Preference Lists
  • Transcoding
  • Transrating
  • Call Progress Analysis Over IP-to-IP Media Session
  • Voice Packetization
  • Fax Detection for SIP Call and Transfer
  • Video Suppression
  • Configuring RTCP Report Generation
  • Network-Based Recording
  • SIPREC (SIP Recording)
  • Video Recording - Additional Configurations
  • Third-Party GUID Capture for Correlation Between Calls and SIP-based Recording
  • Cisco Unified Communications Gateway Services--Extended Media Forking
  • CUBE Media Proxy
  • Passing Headers Unsupported by CUBE
  • Copying SIP Headers
  • Manipulate SIP Status-Line Header of SIP Responses
  • Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
  • Delayed-Offer to Early-Offer
  • H.323-to-SIP Interworking on CUBE
  • H.323-to-H.323 Interworking on CUBE
  • SIP RFC 2782 Compliance with DNS SRV Queries
  • SRTP-SRTP Interworking
  • SRTP-RTP Interworking
  • SRTP-SRTP Pass-Through
  • High Availability on Cisco 4000 Series ISR and Cisco Catalyst 8000 Series Edge Platforms
  • High Availability on Cisco ASR 1000 Series Aggregation Services Routers
  • High Availability on Cisco CSR 1000V or C8000V Cloud Services Routers
  • High Availability on Cisco Integrated Services Routers (ISR-G2)
  • DSP High Availability Support
  • Stateful Switchover Between Redundancy Paired Intra- or Inter-box Devices
  • CVP Survivability TCL support with High Availability
  • ICE-Lite Support on CUBE
  • Mid-call Signaling Consumption
  • Early Dialog UPDATE Block
  • Consumption of Forked 18x Responses with SDP During Early Dialog
  • Support for Pass-Through of Unsupported Content Types in SIP INFO Messages
  • Support for PAID PPID Privacy PCPID and PAURI Headers on the Cisco Unified Border Element
  • Dynamic Refer Handling
  • Cause Code Mapping
  • Hosted and Cloud Services Delivery with CUBE
  • CUBE SIP Registration Proxy
  • Survivability for Hosted and Cloud Services
  • SUBSCRIBE-NOTIFY Passthrough
  • Cisco Unified Communications Manager Line-Side Support
  • SIP TLS Support on CUBE
  • CUBE Call Quality Statistics Enhancement
  • Voice Quality Monitoring
  • CUBE Smart Licensing
  • VoIP Trace for CUBE
  • Support for Session Identifier
  • Common Criteria (CC) and The Federal Information Processing Standards (FIPS) Compliance
  • Additional References
  • Glossary
  Find Matches in This Book Log in to Save Content Available Languages Download Options

  Book Title

  Cisco Unified Border Element Configuration Guide Through Cisco IOS XE 17.5

  Transcoding

  • PDF - Complete Book (18.55 MB)PDF - This Chapter (1.19 MB) View with Adobe Reader on a variety of devices

  Results

  Updated: August 15, 2022

  Chapter: Transcoding

  Chapter Contents
  • Transcoding
  • Configure LTI-Based Transcoding
  • Configuration Examples for LTI Based Transcoding
  • Configuring SCCP-based Transcoding (ISR-G2 devices only)
  • TLS for SCCP Connection for DSP Services
  • Configuring Secure Transcoding
    • Configuring the Certificate Authority
    • Configuring a Trustpoint for the Secure Universal Transcoder
    • Configuring DSPFARM Services
    • Associating SCCP to the Secure DSPFARM Profile
    • Registering the Secure Universal Transcoder to the CUBE

    Transcoding

    Transcoding is a process of converting one voice codec to another. For example, transcoding between iLBC and G.711 or iLBC and G.729.

    In every transcoding operation, media flows through CUBE .

    LTI based Transcoding

    • Internal API is used to access Digital Signaling Processor (DSP) resources for transcoding.
    • Transcoding resources (DSPFARM) and CUBE must be on the same platform.
    • Only DSPFARM profile configuration is required. Skinny Client Control Protocol (SCCP) configuration is not required.
    • No TCP socket is opened and no registration is used.
    • DSPFARM profile is associated to a new application type CUBE.

    Device(config)# dspfarm profile 1 transcode Device(config-dspfarm-profile)# associate application CUBE

    • Cisco Aggregated Services Routers 1000 Series (ASR 1K)
    • Cisco-Integrated Services Generation 2 Routers (Cisco ISR G2)
    • Cisco 4000 Series-Integrated Services Routers (ISR G3)
    • Cisco 8200 Catalyst Edge Series
    • Cisco 8300 Catalyst Edge Series

    SCCP based Transcoding

    • Skinny Client Control Protocol (SCCP) protocol is used for controlling Digital Signaling Processor (DSP) resources used for transcoding.
    • Transcoding resources (DSPFARM) and CUBE can be on different platforms.
    • SCCP client (For example, sccp ccm configuration and SCCP server (telephony service) configuration is required apart from DSPFARM profile configuration.
    • DSPFARM registers with Cisco Unified Border Element over TCP Socket, using SCCP.
    • DSPFARM profile is associated to SCCP using the following commands:

    Device(config)# dspfarm profile 1 transcode Device(config-dspfarm-profile)# associate application SCCP

    Integrated Services Routers Generation 1 series and Integrated Services Routers Generation 2 Series devices support SCCP-based Transcoding only.

    Configure LTI-Based Transcoding

    SUMMARY STEPS

    1. enable
    2. configure terminal
    3. voice-card voice-interface-slot-number
    4. dsp services dspfarm
    5. exit
    6. dspfarm profile profile-identifier transcode
    7. codec codec
    8. maximum sessions sessions
    9. associate application CUBE
    10. no shutdown

    DETAILED STEPS

    Example:

    Device> enable 

    Enables privileged EXEC mode.

    • Enter your password if prompted.

    Example:

    Device> configure terminal 

    Enters global configuration mode.

    Example:

    Device(config)# voice-card 0/2 

    Configures a voice card and enters voice-card configuration mode.

    dsp services dspfarm

    Enable voice-only DSP services on the Voice Card.

    Exits the voice-card configuration mode.

    dspfarm profile profile-identifier transcode

    Example:

    Device(config)# dspfarm profile 2 transcode

    • profile-identifier - Number that uniquely identifies a profile. Range: 1–65535.
    • transcode - Enables profile for transcoding.

    Example:

    Device(config-dspfarm-profile)# codec opus

    Add a list of codecs that you wish to transcode.

    maximum sessions sessions

    associate application CUBE

    Example:

    Device(config)# associate application CUBE

    Configuration Examples for LTI Based Transcoding

    LTI-based Transcoding

     ! Enabling dspfarm services under voice-card Device(config)# voice-card 0/2 Device(config-voicecard)# dsp services dspfarm Device(config-voicecard)# exit ! Configuring dspfarm profile Device(config)# dspfarm profile 2 transcode Device(config-dspfarm-profile)# codec g711ulaw Device(config-dspfarm-profile)# codec g711alaw Device(config-dspfarm-profile)# codec g729r8 Device(config-dspfarm-profile)# maximum sessions 10 Device(config-dspfarm-profile)# associate application CUBE Device(config-dspfarm-profile)# no shutdown ! Starting Service Engine Device(config)# interface ServiceEngine0/1/0 Device(config-if)# no shutdown Device(config-if)# exit 

    Example: Secure LTI-based Transcoding

     !Client trustpoints use HTTP to receive certificate from CA. Device(config)#ip http server 

     !Generate an RSA Keypair. !(This step generates Private and Public keys. In this example, CUBE is just a label. It can be anything.) crypto key generate rsa general-keys label CUBE modulus 1024 The name for the keys will be: CUBE % The key modulus size is 1024 bits % Generating 1024 bit RSA keys, keys will be non-exportable. [OK] (elapsed time was 0 seconds) 

     !Configure IOS CA Server. In this example, CA Server is named cube-ca. crypto pki server cube-ca database level complete no database archive grant auto lifetime certificate 1800 Secure-CUBE(cs-server)#no shut %Some server settings cannot be changed after CA certificate generation. % Please enter a passphrase to protect the private key % or type Return to exit Password: Re-enter password: % Generating 1024 bit RSA keys, keys will be non-exportable. [OK] (elapsed time was 0 seconds) % Certificate Server enabled. 

     !Create PKI trustpoints for cube for TLS communication. crypto pki trustpoint CUBE-TLS enrollment url http://X.X.X.X:80 serial-number none fqdn none ip-address none subject-name CN=Secure-CUBE revocation-check none rsakeypair CUBE 

     !Authenticate the trustpoint with CA server and accept certificate of CA crypto pki authenticate CUBE-TLS Certificate has the following attributes: Fingerprint MD5: BCEBB5A1 1AC882F7 24BE476D 06537711 Fingerprint SHA1: CE2FEEA5 42515B33 3EF6A8F6 7E31D6DF 8E32BEB6 % Do you accept this certificate? [yes/no]: yes Trustpoint CA certificate accepted. 

     !Enroll the trustpoint with CA server. !In this step the CUBE receives a signed certificate from CA. Secure-CUBE(config)#crypto pki enroll CUBE-TLS % % Start certificate enrollment .. % Create a challenge password. You will need to verbally provide this password to the CA Administrator in order to revoke your certificate. For security reasons your password will not be saved in the configuration. Please make a note of it. Password: Re-enter password: % The subject name in the certificate will include: CN=Secure-CUBE % The fully-qualified domain name will not be included in the certificate Request certificate from CA? [yes/no]: yes % Certificate request sent to Certificate Authority % The 'show crypto pki certificate verbose CUBE-TLS' commandwill show the fingerprint. 

     !Configure TCP TLS as transport protocol voice service voip sip session transport tcp tls 

     !Assign trustpoint for sip-ua, this trustpoint is used for all SIP signaling between CUBE and CUCM. sip-ua crypto signaling remote-addr 255.255.255.255 trustpoint CUBE-TLS crypto signaling remote-addr 255.255.255.255 trustpoint CUBE-TLS !or or default trustpoint can be configured for all SIP signaling from CUBE. sip-ua crypto signaling default trustpoint CUBE-TLS 

     !Enable SRTP. Voice service voip srtp fallback

     !Configure secure transcoder is required. dspfarm profile 1 transcode universal security codec g711ulaw codec g711alaw codec g729ar8 codec g729abr8 maximum sessions 10 associate application CUBE 

    Configuring SCCP-based Transcoding (ISR-G2 devices only)

    SUMMARY STEPS

    1. enable
    2. configure terminal
    3. voice-card voice-interface-slot-number
    4. dspfarm
    5. dsp service dspfarm
    6. exit
    7. telephony-service
    8. sdspfarm units units
    9. sdspfarm transcode sessions units
    10. sdspfarm tag value Device-Name
    11. max-ephones max-phones-to-be-supported
    12. max-dn max-directorynumbers-to-be-supported
    13. ip source-address CUBE-internal-ipv4-address [ port port-number ]
    14. exit
    15. sccp local interface-type number
    16. sccp ccm CUBE-internal-ipv4-address identifier identifier-number version version-number
    17. sccp
    18. sccp ccm group group-id
    19. associate ccm CCM-identifier priority priority
    20. associate profile profile-identifier register Device-Name
    21. exit
    22. dspfarm profile profile-id transcode
    23. codec codec
    24. maximum sessions sessions
    25. associate application sccp
    26. exit

    DETAILED STEPS

    Example:

    Device> enable