/mcpSIP profiles are robust Regular Expression (regex) Match statements which allow an administrator to change any aspect of a SIP message which includes SDP and SIP headers. These can be enabled globally, per dial- peer or per tenant. SIP Profiles are available for inbound modifications starting with with Cisco IOS 15.4(2)T and Cisco IOS XE 3.12S . Since SIP profiles are so robust, this document only covers a few specific examples. SIP profiles also add the ability for custom SIP headers to be modified or added in Cisco IOS 15.5(2)T and Cisco IOS-XE 3.13S. Key Points about inbound versus outbound SIP Profiles Inbound SIP Profiles change the message BEFORE the CUBE processes the message for call routing. • Outbound SIP Profiles change the message AFTER the CUBE has processed the call routing and before the message is sent to the next hop. • Other notes about sip-profile Configuration: SIP Profiles cannot manipulate m=image SDP attributes. The enhancement for this was filed under Cisco bug ID CSCsr20474
Additionally, SIP profiles cannot remove or add values to SDP. Only you can modify these values. However, it is possible to modify an SDP value into a null value by specifying the entire value then setting the output to a set of empty quotes without a space. • There are no checks performed to see if the current command being entered already exists or a version of that command already exists when entering commands within voice class sip-profile. If an administrator pastes a line 7 times into a sip-profile, it displays 7 times in the running configuration. It is advised to remove the command being modified and then enter the new command when editing sip- profiles to avoid multiple commands being present. • Full Documentation: Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards SIP Profile Testing Tool on CSA: SPT Tool
