Configuring Normalization Policies
Viewing a List of Normalization Policies
Adding a Normalization Policy
Working With URI Components for a Request URI
Working With URI Conversion Parameters for a Request URI
Working With URI Parameters for a Request URI
Working With SIP Headers
Working With URI Components for SIP Headers
Working With URI Conversion Parameters for SIP Headers
Working With URI Parameters for SIP Headers
Working With Header Parameters for SIP Headers

Configuring Normalization Policies

Viewing a List of Normalization Policies

Procedure

Step 1

Choose Configure > Normalization Policies.

The system displays the Normalization Policies page, containing the fields described in the section Normalization Policy Fields.

Step 2

To delete a normalization policy, do the following:

Check the check box next to the name of the normalization policy to delete.
Click Remove.
In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Step 3

To revert any changes you have made back to the state they were in at the time of the last commit, do the following:

Check the check box next to the name of the normalization policy that has the changes to revert back to.
Click Revert.
In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

About Normalization Policies

Normalization policies modify SIP messages to account for incompatibilities between networks.

Normalization Policy Fields

The table lists the fields on the Normalization Policies page.

Table 1. Normalization Policy Parameters
Parameter	Description
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
Name	Name of this normalization policy.

Request URI, URI Component Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the Request URI and URI Component tabs are displayed.

Table 2. Request URI, URI Component Fields
Parameter	Description
Category	There are five boxes on this page, one for each of the following: User—Specifies the normalization policy to apply to the user URI component. Phone—Specifies the normalization policy to apply to the phone URI component. Host—Specifies the normalization policy to apply to the host URI component. Host and Port—Specifies the normalization policy to apply to the host-port URI component. URI—Specifies the normalization policy to apply to the full URI. For each box, enter the match pattern and replace value.
Match Pattern	Specifies the regular expression string in the URI component that is matched. If you enter all, the full header is replaced.
Replace Value	Specifies the regular expression string in the URI component that replaces the matched string.

Request URI, URI Conversion Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the Request URI and URI Conversion tabs are displayed.

Table 3. Request URI, URI Conversion Fields
Parameter	Description
SIP URI to TEL URI Conversion
Conversion	Whether this conversion is enabled or disabled. The default is disabled.
TEL URI to SIP URI Conversion
Conversion	Whether this conversion is enabled or disabled. The default is disabled.
Host	Specifies the host of the URI.
Port	Specifies the port of the URI.

Request URI, URI Parameter Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the Request URI and URI Parameter tabs are displayed.

Table 4. Request URI, URI Parameter Fields
Parameter	Description
Add URI Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
Name	Specifies the URI parameter name to which the normalization rule applies.
Value	Specifies the value to be added to the URI parameter.
Remove URI Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
Name	Specifies the URI parameter name.
Update URI Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
Name	Specifies the header parameter name.
Match Pattern	Specifies the regular expression string in the URI parameter that is matched. If you enter all, the full header is replaced.
Replace Value	Specifies the regular expression string in the URI parameter that replaces the matched string.

SIP Headers Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the SIP Header tabs are displayed.

Table 5. SIP Header Parameter Fields
Parameter	Description
Add SIP Headers
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Instances	The SIP header instances to be added.
Remove SIP Headers
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
Total Number of Header Instances	Total number of SIP header instances to be removed.
Update SIP Headers
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the first occurrence. last—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the last occurrence. all—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied to all occurrences.
Match Pattern	Specifies the regular expression string in the header parameter that is matched. If you enter all, the full header is replaced.
Replace Value	Specifies the regular expression string in the header parameter that replaces the matched string.

SIP Header, URI Component Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the SIP Header and URI Component tabs are displayed.

Table 6. SIP Header, URI Component Fields
Parameter	Description
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given URI component, apply this normalization step only to the first occurrence. last—Specifies that if there are multiple occurrences of a given URI component, apply this normalization step only to the last occurrence. all—Specifies that if there are multiple occurrences of a given URI component, apply this normalization step to all occurrences.
URI Component Type	Can be one of the following: URI—Specifies the lookup policy to apply to the full URI. User (default)—Specifies the lookup policy to apply to the user URI component. Phone—Specifies the lookup policy to apply to the phone URI component. Host—Specifies the lookup policy to apply to the host URI component. Host-Port—Specifies the lookup policy to apply to the host-port URI component.
Match Pattern	Specifies the regular expression string in the URI component that is matched. If you enter all, the full header is replaced.
Replace Value	Specifies the regular expression string in the URI component that replaces the matched string.

SIP Header, URI Conversion Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the SIP Header and URI Conversion tabs are displayed.

Table 7. SIP Header, URI Conversion Fields
Parameter	Description
TEL URI to SIP URI Conversions
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given TEL URI, apply this normalization step only to the first occurrence. last—Specifies that if there are multiple occurrences of a given TEL URI, apply this normalization step only to the last occurrence. all—Specifies that if there are multiple occurrences of a given TEL URI, apply this normalization step to all occurrences.
Host	Specifies the host of the URI.
Port	Specifies the port of the URI.
SIP URI to TEL URI Conversions
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a specific SIP URI, apply this normalization step only to the first occurrence. last—Specifies that if there are multiple occurrences of a specific SIP URI, apply this normalization step only to the last occurrence. all—Specifies that if there are multiple occurrences of a specific SIP URI, apply this normalization step to all occurrences.

SIP Header, URI Parameter Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the SIP Header and URI Parameter tabs are displayed.

Table 8. SIP Header, URI Parameter Fields
Parameter	Description
Add URI Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step only to the first occurrence. last—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step only to the last occurrence. all—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step to all occurrences.
Parameter Name	Specifies the URI parameter name to which the normalization rule applies.
Value	Specifies the value to be added.
Remove URI Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step only to the first occurrence. last—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step only to the last occurrence. all—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step to all occurrences.
Parameter Name	Specifies the URI parameter name.
Update URI Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step only to the first occurrence. last—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step only to the last occurrence. all—Specifies that if there are multiple occurrences of a given URI parameter, apply this normalization step to all occurrences.
Parameter Name	Specifies the header parameter name.
Match Pattern	Specifies the regular expression string in the URI parameter that is matched. If you enter all, the full header is replaced.
Replace Value	Specifies the regular expression string in the URI parameter that replaces the matched string.

SIP Header, Header Parameter Fields

The table lists the fields on the Normalization Policy ‘<name of normalization policy>’ page when the SIP Header and Header Parameter tabs are displayed.

Table 9. SIP Header, Header Parameter Fields
Parameter	Description
Add Header Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the first occurrence. last—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the last occurrence. all—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied to all occurrences.
Parameter Name	Name of this add URI parameter.
Value	Value of the add URI parameter.
Remove Header Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the first occurrence. last—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the last occurrence. all—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied to all occurrences.
Parameter Name	Name of this remove URI parameter.
Update Header Parameters
State	Can be one of the following: New—New record. Will be added to the active configuration when it is committed. Modified—Modified record. Will become the active configuration when it is committed. Deleted—Deleted record. Will be removed from the active configuration when it is committed. Active—Active record and active configuration.
SIP Header Name	Specifies the SIP message header for which the normalization step is applicable. Examples include: From, To, Record-Route, Diversion, Request-URI, and P-Asserted-Identity.
SIP Header Index	Can be one of the following: first—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the first occurrence. last—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied only to the last occurrence. all—Specifies that if there are multiple occurrences of a given header parameter, this normalization step is applied to all occurrences.
Parameter Name	Name of this update URI parameter.
Match Pattern	Specifies the regular expression string in the URI component that is matched. If you enter all, the full header is replaced.
Replace Value	Specifies the regular expression string in the URI component that replaces the matched string.

Adding a Normalization Policy

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click Add. The system displays the Normalization Policies page.
Step 3	Enter a name for this normalization policy. Click Add. The system displays the Normalization Policies page, with the new normalization policy listed.
Step 4	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With URI Components for a Request URI

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to work with. The system displays the Normalization Policy ‘<name of normalization policy>’ page and the URI Component tab is highlighted.
Step 3	To add or edit a URI component, do the following: Check the check box of the component to which you want to add or edit values. Enter or change values. See Request URI, URI Component Fields. Click Update.
Step 4	To delete a URI component, do the following: Uncheck the check box of the component to delete. Click Update.
Step 5	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With URI Conversion Parameters for a Request URI

Follow this procedure to configure a normalization policy step that converts a destination TEL URI to a SIP URI with the given host-port value.

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to work with. The system displays the Normalization Policy ‘<name of normalization policy>’ page.
Step 3	Click the URI Conversion tab.
Step 4	Enter or update values. See Request URI, URI Conversion Fields.
Step 5	Click Update.
Step 6	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With URI Parameters for a Request URI

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to work with. The system displays the Normalization Policy ‘<name of normalization policy>’ page.
Step 3	Click the URI Parameter tab.
Step 4	To add a URI parameter to the Request URI, do the following: Under the Add URI Parameters heading, click New. Enter the name of the parameter and a value. Click Add.
Step 5	To remove a parameter from the URI, do the following: Under the Remove URI Parameters heading, click New. Enter the name of the parameter to remove. Click Add.
Step 6	To update a parameter in the URI, do the following: Under the Update URI Parameters heading, click New. Enter the name of the parameter to update and the pattern to match. Optionally, you can enter a value to replace the pattern. Click Add.
Step 7	To remove any parameters that you added in Step 4 to Step 6Step 6, check the check box next to the parameter and click Remove.
Step 8	To revert to the previous setting for any parameters that you added in Step 4 to Step 6, check the check box next to the parameter and click Revert.
Step 9	To edit the add or update parameters that you added in Step 4 or Step 6, click the name of the parameter and make changes.
Step 10	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With SIP Headers

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to which you want to add a SIP header. The system displays the Normalization Policy ‘<name of normalization policy>’ page.
Step 3	Click the SIP Header tab. The system displays the Normalization Policy ‘<name of normalization policy>’ page with the SIP Header tabs displayed.
Step 4	To add a SIP header, do the following: Under the Add SIP Headers heading, click New. Enter the name of the parameter. Click Add. Enter a SIP header index and value. Click Add. Click Cancel to go back to the Normalization Policy: <name of normalization policy> page with the SIP Header tabs displayed.
Step 5	To remove a SIP header, do the following: Under the Remove SIP Headers heading, click New. Enter the name of the SIP header to remove. Enter the number of header instances to be removed from the top and the number to be removed from the bottom. Click Add.
Step 6	To update a SIP header, do the following: Under the Update SIP Headers heading, click New. Enter the name of the SIP header to update and the pattern to match. You can optionally enter a SIP header index and a value to replace the pattern with. Click Add.
Step 7	To remove any SIP headers that you added in Step 4 to Step 6, check the check box next to the parameter and click Remove.
Step 8	To revert to the previous setting for any SIP headers that you added in Step 4 to Step 6, check the check box next to the SIP header and click Revert.
Step 9	To edit the add or update parameters that you added in Step 4 or Step 6, click the name of the SIP header and make changes.
Step 10	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With URI Components for SIP Headers

Follow this procedure to configure a normalization policy step that updates a URI component field within a header of the source message.

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to work with. The system displays the Normalization Policy ‘<name of normalization policy>’ page.
Step 3	Click the SIP Header tab.
Step 4	Click the URI Component tab.
Step 5	To add a URI component to a SIP header, do the following: Click New. Enter values. See SIP Header, URI Component Fields. Click Add.
Step 6	To edit a URI component for a SIP header, do the following: Click the underlined name of the SIP header. Update the match pattern or replace values. See SIP Header, URI Component Fields. Click Update.
Step 7	To remove a URI component for a SIP header, check the check box next to the URI component and click Remove.
Step 8	To revert to the previous setting for a URI component for a SIP header, check the check box next to the URI component and click Revert.
Step 9	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With URI Conversion Parameters for SIP Headers

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to work with. The system displays the Normalization Policy ‘<name of normalization policy>’ page.
Step 3	Click the SIP Header tab.
Step 4	Click the URI Conversion tab.
Step 5	To add a new conversion parameter, do the following: Click New under either the TEL URI to SIP URI Conversions header or the SIP URI to TEL URI Conversions header. Enter values. See SIP Header, URI Conversion Fieldsthe section SIP Header, URI Conversion Fields. Click Add.
Step 6	To edit a TEL URI to SIP URI conversion parameter, do the following: Click the underlined name of the SIP header. Update values. See SIP Header, URI Conversion Fields. Click Update.
Step 7	To remove a URI conversion parameter, check the check box next to the URI conversion parameter and click Remove.
Step 8	To revert to the previous setting for a URI conversion parameter, check the check box next to the URI conversion parameter and click Revert.
Step 9	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With URI Parameters for SIP Headers

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to work with. The system displays the Normalization Policy ‘<name of normalization policy>’ page.
Step 3	Click the SIP Header tab.
Step 4	Click the URI Parameter tab.
Step 5	To add a URI parameter to the SIP header do the following: Under the Add URI Parameters heading, click New. Enter values. See SIP Header, URI Parameter Fieldsthe section SIP Header, URI Parameter Fields. Click Add.
Step 6	To remove a URI parameter from the SIP header, do the following: Under the Remove URI Parameters heading, click New. Enter values. See SIP Header, URI Parameter Fields. Click Add.
Step 7	To update a URI parameter in the SIP header, do the following: Under the Update URI Parameters heading, click New. Enter values. See SIP Header, URI Parameter Fields. Click Add.
Step 8	To remove any parameters that you added in Step 5 to Step 7, check the check box next to the parameter and click Remove.
Step 9	To revert to the previous setting for any parameters that you added in Step 5 to Step 7, check the check box next to the parameter and click Revert.
Step 10	To edit the add or update parameters that you added in Step 5 or Step 7, click the name of the parameter and make changes.
Step 11	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

Working With Header Parameters for SIP Headers

Procedure

Step 1	Choose Configure > Normalization Policies. The system displays the Normalization Policies page.
Step 2	Click the underlined name of the normalization policy to work with. The system displays the Normalization Policy ‘<name of normalization policy>’ page.
Step 3	Click the SIP Header tab.
Step 4	Click the Header Parameter tab.
Step 5	To add a header parameter to the SIP header do the following: Under the Add Header Parameters heading, click New. Enter values. See SIP Header, Header Parameter Fields. Click Add.
Step 6	To remove a header parameter from the SIP header, do the following: Under the Remove Header Parameters heading, click New. Enter values. See SIP Header, Header Parameter Fields. Click Add.
Step 7	To update a header parameter in the SIP header, do the following: Under the Update Header Parameters heading, click New. Enter values. See SIP Header, Header Parameter Fields. Click Add.
Step 8	To remove any parameters that you added in Step 5 to Step 7, check the check box next to the parameter and click Remove.
Step 9	To revert to the previous setting for any parameters that you added in Step 5 to Step 7, check the check box next to the parameter and click Revert.
Step 10	To edit the add or update parameters that you added in Step 5 or Step 7, click the name of the parameter and make changes.
Step 11	In the Cisco Unified SIP Proxy header, click Commit Candidate Configuration to commit this change.

GUI Administration Guide for Cisco Unified SIP Proxy Release 10.1

Bias-Free Language

Book Title

GUI Administration Guide for Cisco Unified SIP Proxy Release 10.1

Chapter Title