rmalization techniques: In example (a), the user=phone tag is added to the SIP INVITE to comply with the needs of an application or SIP trunk provider on the outgoing side of the CUBE. In example (b), the sip: Uniform Resource Identifier (URI) is changed to a tel: URI in the SIP INVITE to interoperate with an application requiring a tel: URI. Incoming Outgoing INVITE sip:5551000@sip.com:5060 SIP/2.0 INVITE ip:5551000@sip.com:5060 user=phone Incoming Outgoing INVITE sip:2222000020@9.13.24.6:5060 INVITE tel:2222000020 SIP/2.0 SIP/2.0 Figure 8-2 SIP Normalization Examples 146 SIP Trunking Example 8-1 illustrates the regular expression commands configured to affect the SIP Normalization examples shown in Figure 8-2. Example 8-1 SIP Normalization Commands voice class sip-profiles 100 request INVITE sip-header SIP-Req-URI modify "; SIP/2.0" ';user=phone SIP/2.0" request REINVITE sip-header SIP-Req-URI modify "; SIP/2.0" ";user=phone SIP/2.0" voice class sip-profiles 100 request INVITE sip-header SIP-Req-URI modify"sip:(.*)@[^]+""tel:\1" request INVITE sip-header From modify"<sip:(.*)@.*>""<tel:\1>" request INVITE sip-header To modify "<sip:(.*)@.*>""<tel:\1>" Example 8-2 shows a number of additional examples that add an element to a SIP message. In example (a), a b=AS:4000 SDP header for the video-media line is added to INVITE messages. In example (b), a Retry-After SIP header is added to 480 Temporarily Not Available response message. In example (c), a user=phone field is added to SIP URI of INVITE and REINVITE messages. In example (d), a User-Agent SIP header is added to 200 response messages. Example 8-2 SIP Normalization Add Examples voice class sip-profiles 100 request INVITE sdp-header ideo-Bandwidth- - Info add "b=AS:4000" voice class sip-profiles 100 response 480 sip-header Retry-After add "Retry-After: 60" voice class sip-profiles 100 request INVITE sip-header SIP-Req-URI modify "; SIP/2.0" ";user=phone SIP/2.0" request REINVITE sip-header SIP-Req-URI modify "; SIP/2.0" ";user=phone SIP/2.0" voice class sip-pr