Configuring an Inbound Dial Peer to Match on a URI

To configure an inbound dial peer to match an URI on a remote IP Address on SIP Trunks, perform the following task.

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.

Prerequisites for Configuring an Inbound Dial Peer to Match on a URI

  • Enable SIP header passing. For information, see the Cisco IOS SIP Configuration Guide, Release 15.1
  • Write a Tcl IVR 2.0 script or VoiceXML document that accepts a SIP or TEL URI. For information, see the Tcl IVR API Version 2.0 Programmer's Guide or Cisco VoiceXML Programmer's Guide.

Cisco Unified Border Element

Cisco IOS Release 15.1(2)T or a later release must be installed and running on your Cisco Unified Border Element.

Cisco Unified Border Element (Enterprise)

Cisco IOS XE Release 3.6S or a later release must be installed and running on your Cisco Unified Border Element (Enterprise).

Configuring an Inbound Dial-Peer to Match the URI on SIP Calls

This task describes how to configure an inbound dial-peer to match the URI in a SIP call.

SUMMARY STEPS

    1.    enable

    2.    configureterminal

    3.    voice class uritag

    4.    host hostname-pattern or host {host {ipv4: ipv4-address | ipv6:ipv6-address |dns:dns-address |hostname-pattern }

    5.    exit

    6.    dial-peer voice tagvoip

    7.    sessionprotocol sipv2

    8.    incoming uri { from | request | to | via tag

    9.    end


DETAILED STEPS
      Command or Action Purpose
    Step 1 enable


    Example: 
    Device> enable
     

    Enables privileged EXEC mode.

    • Enter your password if prompted.
     
    Step 2 configureterminal


    Example: 
    Device> configure terminal
     

    Enters global configuration mode.

     
    Step 3 voice class uritag


    Example: 
    Device(config)# voice class uri ab200 sip
     

    Creates a voice class for matching dial peers to a SIP and enters voice URI class configuration mode.

     
    Step 4 host hostname-pattern or host {host {ipv4: ipv4-address | ipv6:ipv6-address |dns:dns-address |hostname-pattern }

    Example: 
    Device(config-voice-uri-class)# host server1 
or 
Device(config-voice-uri-class)# host ipv4:10.0.0.0
     

    (Optional) Specifies a regular expression pattern for matching the hostname field in the SIP URI.

    • This command can have a single instance only.
    • You can specify up to ten instances of this command.
    Note   

    You can use either the host hostname or host {host {ipv4: ipv4-address | ipv6:ipv6-address |dns:dns-address |hostname-pattern } command.

     
    Step 5 exit


    Example: 
    Device(config-voice-uri-class)# exit
     

    Enters global configuration mode.

     
    Step 6 dial-peer voice tagvoip


    Example: 
    Device(config)# dial-peer voice 6000 voip
     

    Enters dial peer voice configuration mode.

     
    Step 7 sessionprotocol sipv2


    Example: 
    Device(config-dial-peer)# session protocol sipv2
     

    Configures SIP as the session protocol type.

     
    Step 8 incoming uri { from | request | to | via tag


    Example: 
    Device(config-dial-peer)# incoming uri via ab200
     

    Specifies the voice class used to match a VoIP dial peer to the URI of an incoming call.

     
    Step 9 end


    Example: 
    Device(config-dial-peer)# end
     

    Exits dial peer voice configuration mode and enters privileged EXEC mode.

     

    Feature Information for Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks

    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.

    Feature Name

    Releases

    Feature Information

    Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks

    15.1(2)T

    The Support Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks feature supports the expansion of inbound dial-peer matching logic to include matching based on the source IP address of inbound signaling on a SIP trunk. This feature enables enforcement of specific call-treatment, security, and routing policies on each SIP trunk.

    In Cisco IOS Release 15.1(2)T this feature was implemented on the Cisco Unified Border Element.

    The following commands were introduced or modified: dial-peer voice, voice-class uri.

    SIP and TEL URL support

    Cisco IOS XE Release 3.6S

    Cisco IOS XE Release 3.8S

    The Support Inbound Dial-peer Match Based on Remote IP Address on SIP Trunks feature supports the expansion of inbound dial-peer matching logic to include matching based on the source IP address of inbound signaling on a SIP trunk. This feature enables enforcement of specific call-treatment, security, and routing policies on each SIP trunk.

    In Cisco IOS Release 15.1(2)T this feature was implemented on the Cisco Unified Border Element (Enterprise).

    The following commands were introduced or modified: dial-peer voice, voice-class uri.