Cisco Unified Border Element (Enterprise) Protocol-Independent Features and Setup Configuration Guide, Cisco IOS XE Release 3S
SIP Profiles
Downloads: This chapterpdf (PDF - 1.48MB) The complete bookPDF (PDF - 7.56MB) | The complete bookePub (ePub - 2.15MB) | Feedback

SIP Profiles

SIP Profiles

Session Initiation Protocol (SIP) profiles change SIP incoming or outgoing messages so that interoperability between incompatible devices can be ensured.

SIP profiles can be configured with rules to add, remove, copy, or modify the SIP, Session Description Protocol (SDP), and peer headers that enter or leave CUBE.

Figure 1. Incoming and Outgoing messages where SIP Profiles can be applied



You can use the following tool to test your SIP profile on an incoming message. http:/​/​cantor.cisco.com/​sip-profiles.html

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 SIP Profile

SIP Profile

Protocol translation and repair is a key Cisco Unified Border Element (CUBE) function. CUBE can be deployed between two devices that support the same VoIP protocol (For example. SIP), but do not interwork because of differences in how the protocol is implemented or interpreted. CUBE can customize the SIP messaging on either side to what the devices in that segment of the network expects to see by normalizing the SIP messaging on the network border, or between two non-interoperable devices within the network.

Service providers may have policies for which SIP messaging fields should be present (or what constitutes valid values for the header fields) before a SIP call enters their network. Similarly, enterprises and small businesses may have policies for the information that can enter or exit their networks for policy or security reasons from a service provider SIP trunk.

Figure 2. SIP Profile



In order to customize SIP messaging in both directions, you can place and configure a CUBE with a SIP profile at the boundary of these networks.

In addition to network policy compliance, the CUBE SIP profiles can be used to resolve incompatibilities between SIP devices inside the enterprise network. These are the situations in which incompatibilities can arise:

  • A device rejects an unknown header (value or parameter) instead of ignoring it
  • A device sends incorrect data in a SIP message
  • A device does not implement (or implements incorrectly) protocol procedures
  • A device expects an optional header value or parameter, or an optional protocol procedure that can be implemented in multiple ways
  • A device sends a value or parameter that must be changed or suppressed before it leaves or enters the network
  • Variations in the SIP standards on how to achieve certain functions

The SIP profiles feature on CUBE provides a solution to these incompatibilities and customization issues.

SIP profiles can also be used to change a header name from the long form to the compact form. For example, From to f. This can be used as a way to reduce the length of a SIP message. By default, the device never sends the compact form of the SIP messages although it receives either the long or the short form.

Important Notes for SIP Profiles

Given below are a few important notes for SIP Profiles:

  • Copy Variables u01 to u99 are shared by inbound and outbound SIP Profiles.
  • Session Initiation Protocol (SIP) and Session Description Protocol (SDP) headers are supported. SDP can be either a standalone body or part of a Multipurpose Internet Mail Extensions (MIME) message.
  • The rules configured for an INVITE message are applied only to the first INVITE of a call. A special REINVITE keyword is used to manipulate subsequent INVITEs of a CALL.
  • Manipulation of SIP headers by outbound SIP profiles occurs as the last step before the message leaves the CUBE device; that is, after destination dial-peer matching has taken place. Changes to the SIP messages are not remembered or acted on by the CUBE application. The Content-length field is recalculated after the SIP Profiles rules are applied to the outgoing message.
  • The ANY keyword indicates that a rule must be applied to any message within the specified category.
  • SIP header modification can be cryptic. It is easier to remove a header and add it back (with the new value), rather than modifying it.
  • To include '?' (question-mark) character as part of match-pattern or replace-pattern, you need to press "Ctrl+v" keys and then type '?'. This is needed to treat ‘?’ as a input character itself instead of usual device help prompt.
  • For header values used to add, modify or copy a header:
    • If a whitespace occurs, the entire value must be included between double quotes. For example, “User-Agent: CISCO CUBE”
    • If double quotes occurs, a back slash must prefix the double quotes. For example, “User-Agent: \”CISCO\” CUBE”
    • Regular expressions are supported.

Inbound SIP Profile:

  • If the incoming message contains multiple instances of same header, the header values are stored as a comma separated list, and this needs to be considered while modifying it.
  • Modification by an inbound SIP profile takes place before regular SIP call processing happens so that behavior of CUBE would be as if it received the message directly without modification. If inbound dial peer matching fails as required information could not be extracted from headers (like Request-URI, Via, From or To) due to issues in them, global dial peers are applied. An example is a request with invalid SIP-Req-URI.
  • After modification by inbound SIP Profiles, the parameters in SIP message might change, which might change the inbound dial-peer matched when actual dial-peer lookup is done.
  • In the register pass-through feature, there is only one dial-peer for register and response. So both register from phone and response from registrar would go through the same inbound sip profile under the dial-peer if any.

How to Configure SIP Profiles

To configure SIP Profiles, you must first configure the SIP Profile globally, and apply it at either to all dial peers (globally) or to a single dial peer (dial-peer level). Once a SIP profile is configured, it can be applied as an inbound or outbound profile.

Configuring a SIP Profile to Manipulate SIP Request Headers

SUMMARY STEPS

    1.    enable

    2.    configure terminal

    3.    voice class sip-profiles profile-id

    4.    Add, remove, modify, or copy SIP headers or responses:

    • request message {sip-header | sdp-header} header-to-add add header-value-to-add
    • request message {sip-header | sdp-header} header-to-remove remove
    • request message {sip-header | sdp-header} header-to-modify modify header-value-to-match header-value-to-replace

    5.    end


DETAILED STEPS
     Command or ActionPurpose
    Step 1 enable
     

    Enables privileged EXEC mode.

    • Enter your password if prompted.
     
    Step 2 configure terminal
     

    Enters global configuration mode.

     
    Step 3 voice class sip-profiles profile-id


    Example:
    Device(config)# voice class sip-profiles 10
     

    Creates a SIP Profiles and enters voice class configuration mode.

     
    Step 4Add, remove, modify, or copy SIP headers or responses:
    • request message {sip-header | sdp-header} header-to-add add header-value-to-add
    • request message {sip-header | sdp-header} header-to-remove remove
    • request message {sip-header | sdp-header} header-to-modify modify header-value-to-match header-value-to-replace
     
    According to your choice, this step does one of the following:
    • Adds a SIP or SDP header to a SIP request.
    • Removes a SIP or SDP header to a SIP request.
    • Modifies a SIP or SDP header to a SIP request.
    • The ANY keyword indicates that a rule must be applied to any message within the specified category.
    • For header-value-to-add used to add a header, header-value-to-match or header-value-to-replace used to modify a header:
      • If a whitespace occurs, the entire value must be included between double quotes. For example, “User-Agent: CISCO CUBE”
      • If double quotes occurs, a back slash must prefix the double quotes. For example, “User-Agent: \”CISCO\” CUBE”
      • Regular expressions are supported.

    Refer to Example: Adding a SIP, SDP, or Peer Header, Example: Modifying a SIP, SDP, or Peer Header, and Example: Remove a SIP, SDP, or Peer Header for more details.

     
    Step 5 end
     

    Exits to privileged EXEC mode

     
    What to Do Next

    Now apply the SIP Profile as an inbound or outbound SIP profile.

    Configuring a SIP Profile to Manipulate SIP Response Headers

    SUMMARY STEPS

      1.    enable

      2.    configure terminal

      3.    voice class sip-profiles profile-id

      4.    Add, remove, modify, or copy SIP response headers:

      • response message [method method-type] {sip-header | sdp-header} header-to-add add header-value-to-add
      • response message [method method-type] {sip-header | sdp-header} header-to-remove remove
      • response message [method method-type] {sip-header | sdp-header} header-to-modify modify header-value-to-match header-value-to-replace

      5.    end


    DETAILED STEPS
       Command or ActionPurpose
      Step 1 enable
       

      Enables privileged EXEC mode.

      • Enter your password if prompted.
       
      Step 2 configure terminal
       

      Enters global configuration mode.

       
      Step 3 voice class sip-profiles profile-id


      Example:
      Device(config)# voice class sip-profiles 10
       

      Creates a SIP Profiles and enters voice class configuration mode.

       
      Step 4Add, remove, modify, or copy SIP response headers:
      • response message [method method-type] {sip-header | sdp-header} header-to-add add header-value-to-add
      • response message [method method-type] {sip-header | sdp-header} header-to-remove remove
      • response message [method method-type] {sip-header | sdp-header} header-to-modify modify header-value-to-match header-value-to-replace
       
      According to your choice, this step does one of the following:
      • Adds a SIP or SDP header to a SIP response.
      • Removes a SIP or SDP header to a SIP response.
      • Modifies a SIP or SDP header to a SIP response.
      • The ANY keyword indicates that a rule must be applied to any message within the specified category.
      • You can modify a SIP response status line, using the SIP-StatusLine SIP header of the response.
      • The method keyword is used to associate a response to its corresponding request before application of the SIP profile manipulations. For example, a SIP profile configured without the method keyword for a 200 response code is applied to the 200 response code for all requests such as INVITE, UPDATE, BYE, PRACK. But the method keword allows you to selectively apply the profiles based on the request to which the response is sent.
      • For header-value-to-add used to add a header, header-value-to-match or header-value-to-replace used to modify a header:
        • If a whitespace occurs, the entire value must be included between double quotes. For example, “User-Agent: CISCO CUBE”
        • If double quotes occurs, a back slash must prefix the double quotes. For example, “User-Agent: \”CISCO\” CUBE”
        • Regular expressions are supported.

      Refer to Example: Adding a SIP, SDP, or Peer Header, Example: Modifying a SIP, SDP, or Peer Header, and Example: Remove a SIP, SDP, or Peer Header for more details.

       
      Step 5 end
       

      Exits to privileged EXEC mode

       
      What to Do Next

      Now apply the SIP Profile as an inbound or outbound SIP profile.

      Configuring a SIP Profile as an Outbound Profile

      SUMMARY STEPS

        1.    enable

        2.    configure terminal

        3.    Apply the SIP profile to a dial peer:

        • voice-class sip profiles profile-id in the dial-peer configuration mode.
        • sip-profiles profile-id in the global VoIP configuration mode

        4.    end


      DETAILED STEPS
         Command or ActionPurpose
        Step 1 enable
         

        Enables privileged EXEC mode.

        • Enter your password if prompted.
         
        Step 2 configure terminal
         

        Enters global configuration mode.

         
        Step 3Apply the SIP profile to a dial peer:
        • voice-class sip profiles profile-id in the dial-peer configuration mode.
        • sip-profiles profile-id in the global VoIP configuration mode


        Example:In dial-peer configuration mode
        !Applying SIP profiles to one dial peer only
        Device (config) dial-peer voice 10 voip
        Device (config-dial-peer) voice-class sip profiles 30 
        Device (config-dial-peer) end
        


        Example:In global VoIP SIP mode
        ! Applying SIP profiles globally
        Device(config)# voice service voip
        Device (config-voi-serv) sip
        Device (config-voi-sip) sip-profiles 20
        Device (config-voi-sip) end 
        
         
         
        Step 4 end
         

        Exits to privileged EXEC mode .

         

        Configuring a SIP Profile as an Inbound Profile

        You can configure a SIP profile as an inbound profile applied globally or to a single inbound dial peer. Inbound SIP profiles feature must be enabled before applying it to dial peers.

        SUMMARY STEPS

          1.    enable

          2.    configure terminal

          3.    voice service voip

          4.    sip

          5.    sip-profiles inbound

          6.    Apply the SIP profile to a dial peer:

          • voice-class sip profiles profile-id inbound in the dial-peer configuration mode.
          • sip-profiles profile-id inbound in the global VoIP configuration mode

          7.    end


        DETAILED STEPS
           Command or ActionPurpose
          Step 1 enable
           

          Enables privileged EXEC mode.

          • Enter your password if prompted.
           
          Step 2 configure terminal
           

          Enters global configuration mode.

           
          Step 3 voice service voip


          Example:
          Device(config)# voice service voip
           

          Enters global VoIP configuration mode.

           
          Step 4 sip


          Example:
          Device(config-voi-serv)# sip
           

          Enters global VoIP SIP configuration mode.

           
          Step 5 sip-profiles inbound


          Example:
          Device(config-voi-sip)# sip-profiles inbound
           

          Enables inbound SIP profiles feature.

           
          Step 6Apply the SIP profile to a dial peer:
          • voice-class sip profiles profile-id inbound in the dial-peer configuration mode.
          • sip-profiles profile-id inbound in the global VoIP configuration mode


          Example:In dial-peer configuration mode
          !Applying SIP profiles to one dial peer only
          Device (config)# dial-peer voice 10 voip
          Device (config-dial-peer)# voice-class sip profiles 30 inbound 
          Device (config-dial-peer)# end
          


          Example:In global VoIP SIP mode
          ! Applying SIP profiles globally
          Device(config)# voice service voip
          Device (config-voi-serv)# sip
          Device (config-voi-sip)# sip-profiles 20 inbound
          Device (config-voi-sip)# end 
          
           
           
          Step 7 end
           

          Exits to privileged EXEC mode

           

          Verifying SIP Profiles

          SUMMARY STEPS

            1.    show dial-peer voice id | include profile


          DETAILED STEPS
          show dial-peer voice id | include profile


          Example:
          Device# show dial-peer voice 10 | include profile
          
                  Translation profile (Incoming):
                  Translation profile (Outgoing):
                  translation-profile = `'
                  voice class sip profiles = 11
                  voice class sip profiles inbound = 10
          
          

          Displays information related to SIP profiles configured on the specified dial peer.


          Troubleshooting SIP Profiles

          SUMMARY STEPS

            1.    debug ccsip all


          DETAILED STEPS
          debug ccsip all
          This command displays the applied SIP profiles.

          Example: Applied SIP profile is highlighted in the example below.
          Device# debug ccsip all
          …
          Oct 12 06:51:53.619: //-1/735085DC8F3D/SIP/Info/sipSPIGetShrlPeer: 
                               Try match incoming dialpeer for Calling number:  
                               : sippOct 12 06:51:53.619:  
                               //-1/735085DC8F3D/SIP/Info/sipSPIGetCallConfig:  
                               Peer tag 2 matched for incoming call 
          Oct 12 06:51:53.619: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIGetCallConfig:  
                               voice class SIP profiles tag is set : 1
          Oct 12 06:51:53.619: //-1/735085DC8F3D/SIP/Info/sipSPIGetCallConfig:  
                               Not using Voice Class Codec
          Oct 12 06:51:53.619: //-1/735085DC8F3D/SIP/Info/sipSPIGetCallConfig:  
                               xcoder high-density disabled
          Oct 12 06:51:53.619: //-1/735085DC8F3D/SIP/Info/sipSPIGetCallConfig:  
                               Flow Mode set to FLOW_THROUGH
          
          This command also displays the modifications performed by the SIP profile configuration, by preceding the modification information with the word sip_profiles, as highlighted in the example below.

          Example:
          Device# debug ccsip all
          …
          Oct 12 06:51:53.647: //-1/xxxxxxxxxxxx/SIP/Info/ 
                               sip_profiles_application_change_sdp_line:  
                               New SDP header is added : b=AS: 1600
          Oct 12 06:51:53.647: //-1/xxxxxxxxxxxx/SIP/Info/ 
                               sip_profiles_update_content_length:  
                               Content length header before modification :   
                               Content-Length: 290
          Oct 12 06:51:53.647: //-1/xxxxxxxxxxxx/SIP/Info/ 
                               sip_profiles_update_content_length:  
                               Content length header after modification :   
                               Content-Length: 279

          Examples: Adding, Modifying, Removing SIP Profiles

          Example: Adding a SIP, SDP, or Peer Header

          Example: Adding "b=AS:4000" SDP header to the video-media Header of the INVITE SDP Request Messages

          Device(config)# voice class sip-profiles 10
          Device(config-class)# request INVITE sdp-header Video-Bandwidth-Info add "b=AS:4000"
          Device(config-class)# end
          

          Example: Adding the Retry-After Header to the SIP 480 Response Messages

          Device(config)# voice class sip-profiles 20
          Device(config-class)# response 480 sip-header Retry-After add “Retry-After: 60”
          Device(config-class)# end
          

          Example: Adding "User-Agent: SIP-GW-UA" to the User-Agent Field of the 200 Response SIP Messages

          Device(config)# voice class sip-profiles 40
          Device(config-class)# response 200 sip-header User-Agent add "User-Agent: SIP-GW-UA"
          Device(config-class)# end
          

          Applying the SIP Profiles

          
          ! Applying SIP profiles globally
          Device(config)# voice service voip
          Device (config-voi-serv) sip-profiles 20
          Device (config-voi-serv) end
          
          ! Applying SIP profiles to one dial peer only
          Device (config) dial-peer voice 10 voip
          Device (config-dial-peer) voice-class sip profiles 30 
          Device (config-dial-peer) voice-class sip profiles 40 
          Device (config-dial-peer) voice-class sip profiles 10 
          Device (config-dial-peer) end
          

          Example: Modifying a SIP, SDP, or Peer Header

          Example: Modifying SIP-Req-URI of the Header of the INVITE and RE-INVITE SIP Request Messages to include "user=phone"

          Device(config)# voice class sip-profiles 30
          Device(config-class)# request INVITE sip-header SIP-Req-URI modify "; SIP/2.0" ";user=phone SIP/2.0"
          Device(config-class)# request RE-INVITE sip-header SIP-Req-URI modify "; SIP/2.0" ";user=phone SIP/2.0"
          Device(config-class)# end
          

          Modify the From Field of a SIP INVITE Request Messages to “gateway@gw-ip-address” Format

          For example, modify 2222000020@10.13.24.7 to gateway@10.13.24.7

          Device(config)# voice class sip-profiles 20
          Device(config-class)# request INVITE sip-header From modify "(<.*:)(.*@)" "\1gateway@"

          Replace "CiscoSystems-SIP-GW-UserAgent" with "-" in the Originator Header of the SDP in INVITE Request Messages

          Device(config)# voice class sip-profiles 10
          Device(config-class)# request INVITE sdp-header Session-Owner modify "CiscoSystems-SIP-GW-UserAgent“ "-"

          Convert "sip uri" to "tel uri" in Req-URI, From and To Headers of SIP INVITE Request Messages

          For example, modify sip:2222000020@9.13.24.6:5060” to “tel:2222000020

          Device(config)# voice class sip-profiles 40
          Device(config-class)# request INVITE sip-header SIP-Req-URI modify "sip:(.*)@[^ ]+" "tel:\1"
          Device(config-class)# request INVITE sip-header From modify "<sip:(.*)@.*>" "<tel:\1>"
          Device(config-class)# request INVITE sip-header To modify "<sip:(.*)@.*>" "<tel:\1>"

          Example: Change the Audio Attribute Ptime:20 to Ptime:30

          Inbound ptime:

          a=ptime:20
          

          Outbound ptime:

          a=ptime:30
          
          Device(config)# voice class sip-profiles 103
          Device(config-class)# request ANY sdp-header Audio-Attribute modify "a=ptime:20" "a=ptime:30"
            

          Example: Modify Audio direction "Audio-Attribute"

          Some service providers or customer equipment reply to delay offer invites and or re-invites that contain a=inactive with a=inactive, a=recvonly, or a=sendonly. This can create an issue when trying to transfer or retrieve a call from hold. The result is normally one-way audio after hold or resume or transfer or moh is not heard. To resolve this issue changing the audio attribute to Sendrecv prevents the provider from replaying back with a=inactive, a=recvonly, or a=sendonly.

          Case 1:

          Inbound Audio-Attribute
          
          a=inactive
          
          Outbound Audio-Attribute
          
          a=sendrecv
          

          Case 2:

          Inbound Audio-Attribute
          
          a=recvonly
          
          Outbound Audio-Attribute
          
          a=sendrecv
          

          Case 3

          Inbound Audio-Attribute
          
          a=sendonly
          
          Outbound Audio-Attribute
          
          a=sendrecv
          
          Device(config)# voice class sip-profiles 104
          Device(config-class)# request any sdp-header Audio-Attribute modify "a=inactive" "a=sendrecv"
          Device(config-class)# request any sdp-header Audio-Attribute modify "a=recvonly" "a=sendrecv"
          Device(config-class)# request any sdp-header Audio-Attribute modify "a=sendonly" "a=sendrecv"
          
          Device(config-class)# response any sdp-header Audio-Attribute modify "a=inactive" "a=sendrecv"
          Device(config-class)# response any sdp-header Audio-Attribute modify "a=recvonly" "a=sendrecv"
          Device(config-class)# response any sdp-header Audio-Attribute modify "a=sendonly" "a=sendrecv"
            

          Applying the SIP Profiles to Dial Peers

          ! Applying SIP Profiles globally
          Device(config)# voice service voip
          Device (config-voi-serv) sip-profiles 20
          Device (config-voi-serv) sip-profiles 10
          Device (config-voi-serv) sip-profiles 40
          Device (config-voi-serv) sip-profiles 103
          Device (config-voi-serv) sip-profiles 104
          Device (config-voi-serv) exit
          
          ! Applying SIP Profiles to one dial peer only
          Device (config) dial-peer voice 90 voip
          Device (config-dial-peer) voice-class sip profiles 30

          Example: Remove a SIP, SDP, or Peer Header

          Remove Cisco-Guid SIP header from all Requests and Responses

          Device(config)# voice class sip-profiles 20
          Device(config-class)# request ANY sip-header Cisco-Guid remove
          Device(config-class)# response ANY sip-header Cisco-Guid remove
          Device(config-class)# end

          Remove Server Header from 100 and 180 SIP Response Messages

          Device(config)# voice class sip-profiles 20
          Device(config-class)# response 100 sip-header Server remove
          Device(config-class)# response 180 sip-header Server remove
          Device(config-class)# end

          Example: Modifying Diversion Headers

          Example: Modify Diversion Headers from Three-Digit Extensions to Ten Digits.

          Most service providers require a ten digit diversion header. Prior to Call manager 8.6, Call manager would only send the extension in the diversion header. A SIP profile can be used to make the diversion header ten digits.

          Call manager version 8.6 and above has the field “Redirecting Party Transformation CSS” which lets you expand the diversion header on the call manager.

          The SIP profile will look for a diversion header containing "<sip:5..." , where ... stands for the three-digit extension and then concatenates 9789365 with these three digits.

          Original Diversion Header:

          Diversion:<sip:5100@161.44.77.193>;privacy=off;reason=unconditional;counter=1;screen=no

          Modified Diversion Header:

          Diversion: <sip:9789365100@10.86.176.19>;privacy=off;reason=unconditional;counter=1;screen=no
          
          Device(config)# voice class sip-profiles 101
          Device(config-class)# request Invite sip-header Diversion modify "<sip:5(...)@" "<sip:9789365\1@"
          Device(config-class)# end
          

          Example: Create a Diversion header depending on the area code in the From field

          Most service providers require a redirected call to have a diversion header that contains a full 10 digit number that is associated with a SIP trunk group. Sometimes, a SIP trunk may cover several different area codes, states, and geographic locations. In this scenario, the service provider may require a specific number to be placed in the diversion header depending on the calling party number.

          In the below example, if the From field has an area code of 978 "<sip:978", the SIP profile leaves the From field as is and adds a diversion header.

          Device(config)# voice class sip-profiles 102
          Device(config-class)# request INVITE sip-header From modify "From:(.*)<sip:978(.*)@(.*)" "From:\1<sip:978\2@\3\x0ADiversion: <sip:9789365000@10.86.176.19:5060;privacy=off;reason=unconditional;counter=1;screen=no"
            

          The below diversion header is added. There was no diversion header before this was added:

          Diversion: <sip:9789365000@10.86.176.19:5060;transport=udp>"

          Example: Sample SIP Profile Application on SIP Invite Message

          The SIP profile configured is below:

          voice class sip-profiles 1
            request INVITE sdp-header Audio-Bandwidth-Info add "b=AS:1600“
            request ANY sip-header Cisco-Guid remove
            request INVITE sdp-header Session-Owner modify "CiscoSystems-SIP-GW-UserAgent" "-“
          

          The SIP INVITE message before the SIP profile has been applied is show below:

          INVITE sip:2222000020@9.13.40.250:5060 SIP/2.0
          Via: SIP/2.0/UDP 9.13.40.249:5060;branch=z9hG4bK1A203F
          From: "sipp " <sip:1111000010@9.13.40.249>;tag=F11AE0-1D8D
          To: <sip:2222000020@9.13.40.250>
          Date: Mon, 29 Oct 2007 19:02:04 GMT
          Call-ID: 4561B116-858811DC-804DEF2E-4CF2D71B@9.13.40.249
          Cisco-Guid: 1163870326-2240287196-2152197934-1290983195
          Content-Length: 290
          
          v=0
          o=CiscoSystemsSIP-GW-UserAgent 6906 8069 IN IP4 9.13.40.249
          s=SIP Call
          c=IN IP4 9.13.40.249
          t=0 0
          m=audio 17070 RTP/AVP 0
          c=IN IP4 9.13.40.249
          a=rtpmap:0 PCMU/8000
          a=ptime:20
          
          The SIP INVITE message after the SIP profile has been applied is shown below:
          • The Cisco-Guid has been removed.
          • CiscoSystemsSIP-GW-UserAgent has been replaced with -.
          • The Audio-Bandwidth SDP header has been added with the value b=AS:1600.
          INVITE sip:2222000020@9.13.40.250:5060 SIP/2.0
          Via: SIP/2.0/UDP 9.13.40.249:5060;branch=z9hG4bK1A203F
          From: "sipp " <sip:1111000010@9.13.40.249>;tag=F11AE0-1D8D
          To: <sip:2222000020@9.13.40.250>
          Date: Mon, 29 Oct 2007 19:02:04 GMT
          Call-ID: 4561B116-858811DC-804DEF2E-4CF2D71B@9.13.40.249
          Content-Length: 279
          
          v=0
          o=- 6906 8069 IN IP4 9.13.40.249
          s=SIP Call
          c=IN IP4 9.13.40.249
          t=0 0
          m=audio 17070 RTP/AVP 0
          c=IN IP4 9.13.40.249
          a=rtpmap:0 PCMU/8000
          a=ptime:20
          b=AS:1600
          

          Feature Information for Configuring SIP Profiles

          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 Configuring SIP Profiles

          Feature Name

          Releases

          Feature Information

          SIP Profiles (for inbound messages)

          15.4(2)T

          Cisco IOS XE Release 3.12S

          This feature extends support to inbound messages.

          This feature modifies the following commands:

          The inbound keyword was added to the sip-profiles and voice-class sip profiles commands.

          Support for Rotary calls and Media Forking

          15.3(1)T

          With CSCty41575, this feature was enhanced to support forked and rotary calls.

          Configuring SIP Profile (Add, Delete or Modify)

          12.4(15)XZ

          12.4(20)T

          Cisco IOS XE Release 2.5

          This feature allows users to change (add, delete, or modify) the standard SIP messages that are sent or received for better interworking with different SIP entities.

          This feature introduces the following commands: voice class sip-profiles, response, request.