Downloads |
Table Of Contents
Domain-Based Routing Feature Module
Related Features and Technology
Supported Standards, MIBs, and RFCs
Configuring Domain-Based Call Processing
Nested Result Processing Example
Call Redirection for Non-E.164 Headers
Using the IP_SOURCE_SCREEN Result Type
Adding the IP_SOURCE_SCREEN Result Type
Modifying the IP_SOURCE_SCREEN Result Type
Deleting the IP_SOURCE_SCREEN Result Type
Using the IP_SET_SOURCE_DMN Result Type
Adding the IP_SET_SOURCE_DMN Result Type
Modifying the IP_SET_SOURCE_DMN Result Type
Deleting the IP_SET_SOURCE_DMN Result Type
Using the IP_DEST_TRANS Result Type
Adding the IP_DEST_TRANS Result Type
Modifying the IP_DEST_TRANS Result Type
Deleting the IP_DEST_TRANS Result Type
Using the IP_ROUTE_SEL Result Type
Adding the IP_ROUTE_SEL Result Type
Modifying the IP_ROUTE_SEL Result Type
Deleting the IP_ROUTE_SEL Result Type
Using the DRP_EXIT Result Type
Adding the DRP_EXIT Result Type
Modifying the DRP_EXIT Result Type
Deleting the DRP_EXIT Result Type
NUMAN-ADD:DESTTRANS (Release 9.8(1))
NUMAN-ADD:DMNMODSTRING (Release 9.8(1))
NUMAN-ADD:DRPTABLE (Release 9.8(1))
NUMAN-ADD:ROUTESEL (Release 9.8(1))
NUMAN-ADD:SOURCEBLACK (Release 9.8(1))
NUMAN-RTRV:DESTTRANS (Release 9.8(1))
NUMAN-RTRV:DMNMODSTRING (Release 9.8(1))
NUMAN-RTRV:DRPTABLE (Release 9.8(1))
NUMAN-RTRV:ROUTESEL (Release 9.8(1))
NUMAN-RTRV:SOURCEBLACK (Release 9.8(1))
Software Changes for This Feature
Original Source Header (Tag: 4249)
Original Source URI (Tag: 4250)
Final Destination URI (Tag: 4251)
Non-E.164 Destination Route Select Failure (Tag: 4252)
Domain Screening Failure URI (Tag: 4253)
SIP Final Source URI (Tag: 4255)
Domain Strings (DMNMODSTRING) Table
Domain Routing Policy (DRPTABLE) Table
Source Blacklist Screening (SOURCEBLACK) Table
Route Selection (ROUTESEL) Table
Destination Username/Domain Translation (DESTTRANS) Table
SIP Attributes (SIPRTTRNKGRP) Table
Updating the TimesTen Database
Translation Verification Tool (callver)
Mini-parse Trace Analysis Tool
Obtaining Documentation and Submitting a Service Request
Domain-Based Routing Feature Module
Feature History
This document describes the Domain-Based Routing (DBR) feature in the following sections.
•
Configuring Domain-Based Call Processing
•
•
Feature Description
DBR enhances the PGW 2200 Softswitch analysis and routing functions to allow the PGW 2200 Softswitch to route calls based on user and domain names. These changes allow the PGW 2200 Softswitch to simultaneously route calls using E.164 numbers, domain names, user names, or a combination of E.164 and non-E.164 data.
DBR also introduces domain-based call screening functions and translation tables to map E.164 numbers to domain and user names.
Benefits
This feature provides the following benefits:
•
•
–
–
–
•
•
Prerequisites
The PGW 2200 Softswitch must be running PGW 2200 Softswitch Software Release 9.8(1). Prerequisites for this release can be found in the Release Notes for the PGW 2200 Softswitch Software Release 9.8(1) at
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/pgw/9/release/note/rn981.html
Restrictions or Limitations
•
•
•
•
•
Related Features and Technology
The following features are related to DBR:
•
•
•
•
•
•
Related Documents
This document contains information that is strictly related to this feature. The documents that contain additional information related to the PGW 2200 Softswitch are at
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
Supported Standards, MIBs, and RFCs
This section identifies the new or modified standards, MIBs, and RFCs that are supported by this feature.
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature. For more information on the MIBs used in the PGW 2200 Softswitch software, see the PGW 2200 Softswitch MIBs at
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/prod_technical_reference_list.html
RFCs
No new or modified RFCs are supported by this feature.
Configuring Domain-Based Call Processing
DBR introduces a domain routing policy (DRP) table, which allows you to configure the PGW 2200 Softswitch to analyze calls based on user and domain names. The DRP table establishes a separate preanalysis structure for calls that use domain names rather than E.164 numbers.
The following sections describe how to use the DRP table:
Understanding the DRP Table
The PGW 2200 Softswitch uses the DRP table to analyze calls as follows:
•
•
•
Note
Figure 1 shows the new preanalysis design.
Figure 1 New Preanalysis Design
For a summary of the current preanalysis design, see the PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
Using the DRP Table
The DRP table is a sequential list of result sets that the PGW 2200 Softswitch executes when analyzing domain-based calls. The DRP can contain up to six steps, each of which contain the name of a result set. The DRP table allows you to define the PGW 2200 Softswitch's domain-based call processing according to your needs.
Table 1 shows a sample DRP table.
Table 1 Sample Domain Routing Policy Table
1
ResultSet1
2
ResultSet2
3
ResultSet3
4
ResultSet4
5
ResultSet5
6
ResultSet6
For existing result set types, the PGW 2200 Softswitch processes the result sets sequentially. Analysis ends when the PGW 2200 Softswitch has processed all the steps in the table or it reaches a DRP_EXIT result type.
However, DBR also introduces several new result types that can contain references to other result sets. For more information about the new result types, see the "New TimesTen Tables" section.
New TimesTen Tables
The DBR feature adds the following new tables to the TimesTen database:
•
•
•
The PGW 2200 Softswitch uses TimesTen for these functions in order to accommodate the potentially large volume of entries. For more information about the new TimesTen tables, see the "Dial Plan Components" section.
New Dial Plan Tables
This feature also introduces two new dial plan tables:
•
•
New Result Types
The PGW 2200 Softswitch feature introduces six new result types that allow you to configure the PGW 2200 Softswitch to process domain-based calls. The new result types are
•
•
•
•
•
Note
Nested Result Sets
This feature allows you to create a nested group of result sets that allows for more complex handling of domain-based calls. The IP_SOURCE_SCREEN, IP_DEST_TRANS, and IP_ROUTE_SEL result types have two data words, foundSetName (dw3) and notFoundSetName (dw4), that direct the PGW 2200 Softswitch to execute another result set. Applying a nested result set diverts the PGW 2200 Softswitch from normal processing of the DRP table until all nested results have been processed.
When the PGW 2200 Softswitch executes a nested result, it performs a database lookup and records the outcome (found or not found). If the result value is found in the database and dw3 is set, the PGW 2200 Softswitch executes the result set in dw3. If the result value is not found in the database and dw4 is set, the PGW 2200 Softswitch executes the result set in dw4; otherwise it moves to the next result in the result set.
To create a nested result set, use the foundSetName and notFoundSetName data words to specify result sets that the PGW 2200 Softswitch executes. You can nest results up to three levels.
Note
Nested Result Processing Example
The following example shows a complex implementation of nested result sets and explains how the PGW 2200 Softswitch processes the configuration.
In this example, the following assumptions are made:
•
•
Figure 2 shows the PGW 2200 Softswitch processing of a set of results.
Figure 2
Sample Preanalysis Using Nested Results
The PGW 2200 Softswitch processes the result set configuration as follows:
1.
–
–
–
2.
3.
4.
5.
6.
Call Processing
The following sections describe how the PGW 2200 Softswitch processes a SIP Invite in order to determine a source and list of destinations.
Source Selection
The following sections describe how the PGW 2200 Softswitch determines a source URI.
Single Source URI
DBR does not impact how the PGW 2200 Softswitch determines the source URI for SIP Invites with a single source URI. If the header contains a P-asserted or Remote Party ID (RPID) header, the PGW 2200 Softswitch uses this header to determine the source URI; otherwise, the PGW 2200 Softswitch uses the From header to determine the source URI.
Multiple Source URIs
The PGW 2200 Softswitch evaluates SIP Invites with multiple source URIs as follows:
•
•
If the Invite contains multiple P-Asserted or RPID headers, the PGW 2200 Softswitch uses the following rules:
•
•
•
Destination Selection
The PGW 2200 Softswitch determines the destination URI by building a prioritized list of destination URIs on the SipIngressRoutingControl trunk group property settings.
SipIngressRoutingControl defines the preferred SIP header used for ingress routing decisions as determined from the initial Invite message. It has the following values:
•
•
•
For more information about SipIngressRoutingControl, see the PGW 2200 Softswitch Release 9.8 Provisioning Guide.
Analysis
The PGW 2200 Softswitch continues DRP analysis until it has evaluated all the destinations in the SIP Invite header. If the PGW 2200 Softswitch does not find a route, it restarts analysis on the next destination in the header. The PGW 2200 Softswitch exits the DRP stage as soon as it finds a route. The PGW 2200 Softswitch incorporates the SIPAttributes property value of a trunk when determining a route.
The PGW 2200 Softswitch records source and destination information for incoming and outgoing calls in the Call Data Records (CDRs). For more information about CDRs, see the "Billing Interface" section.
Call Redirection Handling
Prior to the introduction of this feature, the PGW 2200 Softswitch supported call redirection using recursion, local treatment, and backward transit. The following sections describe how the PGW 2200 Softswitch handles call redirection using the DBR feature.
•
Call Redirection for Non-E.164 Headers
Table 2 summarizes how the PGW 2200 Softswitch handles call redirection for calls with non-E.164 URIs.
SIP 302 Rejection
This feature adds the ability for the PGW 2200 Softswitch to reject a SIP 302 (Moved Temporarily/redirection) request unconditionally or when the Contact header does not contain an E.164 number. You can apply this capability to
•
•
To use this capability, use data words 1 and 2 for the FACILITY result type. For more information about the updates to the FACILITY result type, see the "FACILITY" section.
Figure 3 shows the call flow for 302 rejection.
Figure 3 SIP 302 Redirection Rejection
SIP Refer Rejection
DBR introduces the ability to reject a SIP Refer request unconditionally or when the Refer-To header does not contain an E.164 number. You can apply this capability to
•
•
To use this capability, use data words 1 and 2 for the FACILITY result type. For more information about the updates to the FACILITY result type, see the "FACILITY" section.
Figure 4 shows the call flow for a Refer rejection.
Figure 4 SIP Refer Rejection
Updated CDR Viewer
DBR updates the CDR viewer utility for use with domain-based calls. The new interface incorporates the source and destination URI. Figure 5 shows the new interface.
Figure 5 CDR Viewer
For more information about the CDR viewer, see the PGW 2200 Softswitch Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Dial Plan Procedures
The following sections describe how to use the new result types that allow you to control how the PGW 2200 Softswitch dial plan processes domain-based calls:
•
•
•
•
•
For more information on the tasks related to creating a dial plan, see the PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
Using the IP_SOURCE_SCREEN Result Type
The IP_SOURCE_SCREEN result type allows you to screen non-E.164 calls based on a source URI.This capability allows you to restrict calling permissions for a user or group of users on your network, which can be useful for purposes such as billing or security.
This result is supported for blacklist screening only. The following sections describe how to use the IP_SOURCE_SCREEN result type.
Adding the IP_SOURCE_SCREEN Result Type
Use the following steps to add the IP_SOURCE_SCREEN result type:
Step 1
mml> numan-add:dialplan:custgrpid="dpl1"Step 2
mml> numan-add:resultset:custgrpid="dpl1",name="set1"Step 3
mml> numan-add:service:custgrpid="dpl1", name="group1"Step 4
mml> numan-add:resulttable:custgrpid= "dp11", name="result1", resulttype= "IP_SOURCE_SCREEN", dw1="1", dw2="group1", dw3="foundResultSet", dw4="notFoundResultSet", setname="set1"
Note
Where:
•
•
•
•
–
–
–
•
•
•
•
•
Modifying the IP_SOURCE_SCREEN Result Type
To modify the IP_SOURCE_SCREEN result type, complete the following steps:
Step 1
mml> numan-ed:resulttable: custgrpid="dp11",name="result1", resulttype="IP_SOURCE_SCREEN", dw1="1", dw2="group1", dw3="foundResultSet", dw4="notFoundResultSet", setname="set1"Where:
•
•
•
•
–
–
–
•
•
•
•
Step 2
mml> numan-rtrv:resulttable:custgrpid="dp11", setname="set1", name="result1"Step 3
Deleting the IP_SOURCE_SCREEN Result Type
To delete an IP_SOURCE_SCREEN entry in the result table, complete the following steps:
Step 1
mml> numan-dlt:resulttable:custgrpid= "dp11", name= "result1", resulttype="IP_SOURCE_SCREEN", dw1="1", dw2="group1", dw3="foundResultSet", dw4="notFoundResultSet", setname="set1"This command deletes the IP_SOURCE_SCREEN result type from the result table.
Step 2
mml> numan-rtrv:resulttable:custgrpid="dp11", name="result1", setname="set1"Step 3
Using the IP_SET_SOURCE_DMN Result Type
The IP_SET_SOURCE_DMN result type allows you to set the source domain name for domain-based calls. You can use this capability to hide the origin of a call from nontrusted users or disguise the origin of a call for business purposes. This result is supported for preanalysis and A and B number analysis only.
The following sections describe how to use the IP_SET_SOURCE_DMN result type.
Adding the IP_SET_SOURCE_DMN Result Type
Use the following steps to add the IP_SET_SOURCE_DMN result type:
Step 1
mml> numan-add:dialplan:custgrpid="dpl2",overdec="yes"Step 2
mml> numan-add:resultset:custgrpid="dpl2",name="set3"Step 3
numan-add:dmnmodstring: custgrpid="dpl2",name="domainname1", dmnstring="dmnstring1"Step 4
numan-add:resulttable:custgrpid="dp12", name="result1", resulttype="IP_SET_SOURCE_DMN", dw1="domainname1", dw2="0", dw3="0", setname="set3"Where:
•
•
•
•
•
Note
•
Note
•
Step 5
Modifying the IP_SET_SOURCE_DMN Result Type
To modify the IP_SET_SOURCE_DMN result type, complete the following steps:
Step 1
mml> numan-ed:resulttable:custgrpid="dpl2", name="result1", resulttype="IP_SET_SOURCE_DMN", dw1="domainname1", dw2="0", dw3="0", setname="set3"Where:
•
•
•
•
•
•
•
Step 2
mml> numan-rtrv:resulttable:custgrpid="dpl2",name="result1", setname="set3"If the command succeeds, the output shows the modified result type.
Step 3
Deleting the IP_SET_SOURCE_DMN Result Type
To delete an IP_SET_SOURCE_DMN result type from the result table, complete the following steps:
Step 1
mml> numan-dlt:resulttable:custgrpid="dpl2",name="result1",resulttype="IP_SET_SOURCE_DMN", dw1="domainname1", dw2="0", dw3="0", setname="set3"This command deletes the IP_SET_SOURCE_DMN result type from the result table.
Step 2
mml> numan-rtrv:resulttable:custgrpid="dpl2", name="result1", setname="set3"If the command succeeds, the output does not show the deleted result type.
Step 3
Using the IP_DEST_TRANS Result Type
The following sections describe how to use the IP_DEST_TRANS result type.
The IP_DES_TRANS result type can translate between two E.164 or non-E.164 destinations, such as the following:
•
•
•
Adding the IP_DEST_TRANS Result Type
Perform the following steps to add the IP_DEST_TRANS result type:
Step 1
mml> numan-add:dialplan:custgrpid="dpl2",overdec="yes"Step 2
mml> numan-add:resultset:custgrpid="dpl2",name="dmnrtgset1"Step 3
mml> numan-add:service:custgrpid="dpl2",name="set3"Step 4
mml> numan-add:resulttable: custgrpid="dpl2", name="result1", resulttype="IP_DEST_TRANS",dw1="1", dw2="set3", dw3="foundSet", dw4="notFoundSet", setname="dmnrtgset1"Where:
•
•
•
•
•
•
•
Note
•
Step 5
Modifying the IP_DEST_TRANS Result Type
To modify the IP_DEST_TRANS result type, complete the following steps:
Step 1
mml> numan-ed:resulttable: custgrpid="dpl2", name="result1", resulttype="IP_DEST_TRANS",dw1="1", dw2="set3", dw3="foundSet", dw4="notFoundSet", setname="dmnrtgset1"Where:
•
•
•
•
•
•
•
Note
•
This command modifies the IP_DES_TRANS result type in the result table.
Step 2
mml> numan-rtrv:resulttable: custgrpid="dpl2",name="result1", setname="dmnrtgset1"If the command succeeds, the output shows the modified result type.
Step 3
Deleting the IP_DEST_TRANS Result Type
To delete an IP_DEST_TRANS result type from the result table, complete the following steps:
Step 1
mml> numan-dlt:resulttable: custgrpid="dpl2", name="result1", resulttype="IP_DEST_TRANS",dw1="1", dw2="set3", dw3="foundSet", dw4="notFoundSet", setname="dmnrtgset1"This command deletes the IP_DES_TRANS result type from the result table.
Step 2
mml> numan-rtrv:resulttable: custgrpid="dpl2", name="result1", setname="dmnrtgset1"If the command succeeds, the output does not show the deleted result type.
Repeat Steps 1 and 2, as necessary, to remove IP_DES_TRANS result types from the result table.
Using the IP_ROUTE_SEL Result Type
The IP_ROUTE_SEL result type allows the PGW 2200 Softswitch to route domain-based calls according to their destination user or domain name, source user or domain name, or a combination of the two. This result replicates the routing options for E.164 calls, while providing more flexibility about the information used to route the call.
The following sections describe how to use the IP_ROUTE_SEL result type.
Adding the IP_ROUTE_SEL Result Type
Use the following steps to add the IP_ROUTE_SEL result type:
Step 1
mml> numan-add:dialplan:custgrpid="dpl2", overdec="yes"Step 2
mml> numan-add:resultset:cusgrpid="dpl2", name="dmnrtgset1"Step 3
mml> numan-add:service:custgrpid="dpl2", name="set3"Step 4
mml> numan-add:resulttable: custgrpid="dpl2", name="result1", resulttype="IP_ROUTE_SEL", dw1="1", dw2="set3", dw3="foundSet", dw4="notFoundSet", setname="dmnrtgset1"Where:
•
•
•
•
–
–
–
–
–
–
–
–
•
•
•
•
Step 5
Modifying the IP_ROUTE_SEL Result Type
To modify the IP_ROUTE_SEL result type, complete the following steps:
Step 1
mml> numan-ed:resulttable: custgrpid="dpl2", name="result1", resulttype="IP_ROUTE_SEL", dw1="1", dw2="set3", dw3="foundSet", dw4="notFoundSet", setname="dmnrtgset1"Where:
•
•
•
•
–
–
–
–
–
–
–
–
•
•
•
•
Step 2
mml> numan-rtrv:resulttable: custgrpid="dpl2", name="result1", setname="dmnrtgset1"Step 3
Deleting the IP_ROUTE_SEL Result Type
The IP_ROUTE_SEL result type allows the PGW 2200 Softswitch to select a route based on a destination user or domain name, source user or domain name, or a combination of the two. To delete an IP_ROUTE_SEL result type from the result table, complete the following steps:
Step 1
mml> numan-dlt:resulttable:custgrpid="dpl2", setname="dmnrtgset1", name="result1"This command deletes the IP_ROUTE_SEL result type from the result table.
Step 2
mml> numan-rtrv:resulttable: custgrpid="dpl2", setname="dmnrtgset1", name="result1"Step 3
Using the DRP_EXIT Result Type
The DRP_EXIT result type directs the PGW 2200 Softswitch to exit from an individual step of the DRP table or to exit DRP analysis completely. The following sections describe how to use the DRP_EXIT result type.
Note
Adding the DRP_EXIT Result Type
Use the following steps to add the DRP_EXIT result type:
Step 1
mml> numan-add:dialplan:custgrpid="dpl2",overdec="yes"Step 2
mml> numan-add:resultset:cusgrpid="dpl2", name="dmnrtgset1"Step 3
mml> numan-add:resulttable: custgrpid="dp12", name="result1", resulttype="DRP_EXIT", dw1="1", setname="dmnrtgset1"Where:
•
•
•
•
–
–
•
Step 4
Modifying the DRP_EXIT Result Type
To modify the DRP_EXIT result type, complete the following steps:
Step 1
mml> numan-ed:resulttable: custgrpid="dp12", name="result1", resulttype="DRP_EXIT", dw1="1", setname="dmnrtgset1"Where:
•
•
•
•
–
–
•
This command modifies the DRP_EXIT result type in the result table.
Step 2
mml> numan-rtrv:resulttable:custgrpid="dp12", setname="dmnrtgset1", name="result1"If the command succeeds, the output shows the modified result type.
Step 3
Deleting the DRP_EXIT Result Type
To delete an DRP_EXIT result type from the result table, complete the following steps:
Step 1
mml> numan-dlt:resulttable: custgrpid="dp12", setname="dmnrtgset1", name="result1"This command deletes the DRP_EXIT result type from the result table.
Step 2
mml> numan-rtrv:resulttable:custgrpid="dp12", name="result1", resulttype="DRP_EXIT"If the command succeeds, the output does not show the deleted result type.
Step 3
MML Command Reference
This section documents new, modified, or deleted Man-Machine Language (MML) commands. All other MML commands are documented in the PGW 2200 Softswitch Software Release 9 MML Command Reference.
New MML Commands
This section contains the MML commands that are new for this feature.
NUMAN-ADD:DESTTRANS (Release 9.8(1))
Purpose:
This MML command adds an entry to the destination username/domain translation table. For more information about the destination username/domain translation table, see the "Destination Username/Domain Translation (DESTTRANS) Table" section.
Syntax:
mml> numan-add:desttrans: custgrpid="custgrpid", destdmnstring="destdmnstring", svcname="svcname", displayname="displayname", username="username", domainname="domainname", uriparameters= "uriparameters"Input Description:
•
•
•
•
Note
•
•
•
Note
Output Description:
•
•
Examples:
The MML command shown in the following example adds one entry in the destination username/domain translation table:
mml> numan-add:desttrans: custgrpid="dp11", destdmnstring="bob@cisco.com", svcname="destgroup1", displayname="BobOffice", username="bjones", domainname="example.com", uriparameters=";USER=phone"MGC-01 - Media Gateway Controller 2008-08-01 16:40:09.168 EDTM COMPLD"Desttrans";Comments:
Performance impact category: A
NUMAN-ADD:DMNMODSTRING (Release 9.8(1))
Purpose:
This MML command adds an entry to the domain strings table. For more information about the DRP, see the "Domain Strings (DMNMODSTRING) Table" section.
Syntax:
Input Description:
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example adds one entry in the domain strings table:
mml> numan-add:dmnmodstring:custgrpid="T002", name="dmn1", dmnstring="example.com"MGC-01 - Media Gateway Controller 2008-08-04 10:22:29.141 EDTM COMPLD"dmnmodstring";Comments:
Performance impact category: A
NUMAN-ADD:DRPTABLE (Release 9.8(1))
Purpose:
This MML command adds an entry to the domain routing policy (DRP) table. For more information about the DRP, see the "Domain Routing Policy (DRPTABLE) Table" section.
Syntax:
Input Description:
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example adds one entry in the DRP table:
mml> numan-add:drptable: custgrpid="T002", drpstepnum="1", setname="dmnrtgset1"MGC-01 - Media Gateway Controller 2008-08-01 16:40:09.168 EDTM COMPLD"Drptable";Comments:
Performance impact category: A
NUMAN-ADD:ROUTESEL (Release 9.8(1))
Purpose:
This MML command adds an entry to the route selection table. For more information about the route selection table, see the "Route Selection (ROUTESEL) Table" section.
Syntax:
Input Description:
•
•
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example adds one entry in the route selection table:
mml> numan-add:routesel:custgrpid="dpl1","destdmnstring="cisco.com", srcdmnstring="example.com", svcname="svcname", rtlistname="rtlistcisco1"MGC-01 - Media Gateway Controller 2008-08-04 10:30:27.394 EDTM COMPLD"routesel";Comments:
Performance impact category: A
NUMAN-ADD:SOURCEBLACK (Release 9.8(1))
Purpose:
This MML command adds an entry to the source domain blacklist table. For more information about the source blacklist table, see the "Source Blacklist Screening (SOURCEBLACK) Table" section.
Syntax:
Input Description:
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example adds one entry in the source blacklist table:
mml> numan-add:sourceblack:custgrpid="dp11", svcname="destgroup1", srcdmnstring="cisco.com"MGC-01 - Media Gateway Controller 2008-08-04 10:35:41.680 EDTM COMPLD"sourceblack";Comments:
Performance impact category: A
NUMAN-RTRV:DESTTRANS (Release 9.8(1))
Purpose:
This MML command retrieves entries in the destination username/domain translation table. For more information about the destination username/domain translation table, see the "Destination Username/Domain Translation (DESTTRANS) Table" section.
Syntax:
mml> numan-rtrv:desttrans: custgrpid="custgrpid", svcname="svcname", destdmnstring="destdmnstring"mml> numan-rtrv:desttrans:custgrpid="custgrpid", "all"Input Description:
•
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example retrieves one entry in the destination username/domain translation table:
mml> numan-rtrv: desttrans: custgrpid="dp11", svcname="destgroup1", destdmnstring="cisco.com"MGC-01 - Media Gateway Controller 2008-08-01 16:43:09.101 EDTM RTRV"session=sessionname:desttrans"/*CustGrpId ServiceName DestUserDomain NewDisplay NewUser NewDomain NewUriParameters-------------------------------------------------------------------------dp11 destgroup1 bob@cisco.com BobOffice bjones example.com ;USER=phone*/;Comments:
Performance impact category: A
NUMAN-RTRV:DMNMODSTRING (Release 9.8(1))
Purpose:
This MML command retrieves an entry from the domain strings table. For more information about the domain strings table, see the "Domain Strings (DMNMODSTRING) Table" section.
Syntax:
mml> numan-rtrv:dmnmodstring:custgrpid="T002", allInput Description:
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example retrieves one entry from the domain strings table:
mml> numan-rtrv:dmnmodstring:custgrpid="dp11", name="dmn1"MGC-01 - Media Gateway Controller 2008-08-04 10:23:44.807 EDTM RTRV"session=sessionname:dmnmodstring"/*dmnName dmnString------- ---------example.com cisco.com*/;Comments:
Performance impact category: A
NUMAN-RTRV:DRPTABLE (Release 9.8(1))
Purpose:
This MML command retrieves entries in the route selection table. For more information about the route selection table, see the "Route Selection (ROUTESEL) Table" section.
Syntax:
Input Description:
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example retrieves one entry from the DRP table:
mml> numan-rtrv:drptable:custgrpid="T002", drpstepnum="1"MGC-01 - Media Gateway Controller 2008-08-01 16:54:51.010 EDTM RTRV"session=sessionname:drptable"/*stepIndex resultSetName--------- -------------1 dmnRtgExitSet*/;Comments:
Performance impact category: A
NUMAN-RTRV:ROUTESEL (Release 9.8(1))
Purpose:
This MML command retrieves entries from the route selection table. For more information about the route selection table, see the "Route Selection (ROUTESEL) Table" section.
Syntax:
Input Description:
•
•
•
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example retrieves one entry in the route selection table:
mml> numan-rtrv:routesel:custgrpid="dpl1","destdmnstring="cisco.com", srcdmnstring="example.com",svcname="svcname", rtlistname="rtlistcisco1"MGC-01 - Media Gateway Controller 2008-08-04 10:33:15.042 EDTM RTRV"session=sessionname:routesel"/*CustGrpId ServiceName DestUserDomain SrcUserDomain Route List Name--------- --------------------------------------------------------------dp11 destgroup1 cisco.com fred@example.com rtlist60*/;Comments:
Performance impact category: A
NUMAN-RTRV:SOURCEBLACK (Release 9.8(1))
Purpose:
This MML command retrieves entries from the source domain blacklist table. For more information about the source blacklist table, see the "Source Blacklist Screening (SOURCEBLACK) Table" section.
Syntax:
Input Description:
•
•
•
•
Output Description:
•
•
Examples:
The MML command shown in the following example retrieves one entry from the source blacklist table:
mml> numan-rtrv:sourceblack:custgrpid="dp11", svcname="destgroup1", srcdmnstring="cisco.com"MGC-01 - Media Gateway Controller 2008-08-04 10:37:11.471 EDTM RTRV"session=sessionname:sourceblack"/*CustGrpId ServiceName SourceUserDomain-------------------------------------------------------------------------dp11 destgroup1 cisco.com*/;Comments:
Performance impact category: A
Software Changes for This Feature
The following sections contain software changes related to this feature:
Billing Interface
This section identifies the Call Detail Record (CDR) data added for this feature. For billing interface information for the rest of the PGW 2200 Softswitch software, refer to the PGW 2200 Softswitch Release 9 Billing Interface Guide.
Original Source Header (Tag: 4249)
Original Source URI (Tag: 4250)
Final Destination URI (Tag: 4251)
Non-E.164 Destination Route Select Failure (Tag: 4252)
Domain Screening Failure URI (Tag: 4253)
SIP Final Source URI (Tag: 4255)
Dial Plan Components
The following sections discuss the dial plan components that are added, modified, or deleted for this feature. This feature introduces the following new components:
•
•
•
•
•
•
For information on the rest of the dial plan components in the PGW 2200 Softswitch software, see the PGW 2200 Softswitch Software Release 9.8 Dial Plan Guide.
Domain Strings (DMNMODSTRING) Table
The domain strings table allows you to define domains for use with the IP_SET_SOURCE_DMN result type. Table 9 summarizes the structure of the domain strings table structure.
Domain Routing Policy (DRPTABLE) Table
The Domain Routing Policy (DRP) table allows you to define the result sets that the PGW 2200 Softswitch executes at a given step in the DRP table. For more information about the DRP table, see the "Using the DRP Table" section. Table 10 summarizes the DRP table structure.
Source Blacklist Screening (SOURCEBLACK) Table
The Source Blacklist Screening (SOURCEBLACK) table allows you to screen calls based on their source domain name. Table 11 summarizes the Source Blacklist Screening table.
Route Selection (ROUTESEL) Table
The Route Selection Table allows the PGW 2200 Softswitch to route calls based on the source and destination domain names. Table 12 summarizes the Route Selection table structure.
Destination Username/Domain Translation (DESTTRANS) Table
The Destination username/Domain Translation table translates the non-E.164 destinations to E.164 destinations (domains to phone numbers). Table 13summarizes the Destination username/Domain Translation table structure.
SIP Attributes (SIPRTTRNKGRP) Table
DBR modifies the SIP Attributes table to add a the DomainBasedRtgSupport field. This field allows you to specify whether a trunk group supports non-E.164 based routing.
Result Type Definitions
The DBR feature introduces several changes to the result types for the PGW 2200 Softswitch. The changes are summarized in the following sections:
For information on other result type definitions for the PGW 2200 Softswitch software, see the PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
New Result Types
The DBR feature adds five new result types. Table 15 summarizes the new result types.
The following section contains definitions of each result type listed in Table 15.
IP_SOURCE_SCREEN
Table 16 summarizes the IP_SOURCE_SCREEN result type.
IP_SOURCE_SCREEN has the following data words:
•
–
–
–
•
•
•
Note
IP_DEST_TRANS
Table 17 summarizes the IP_DEST_TRANS result type.
IP_DEST_TRANS has the following data words:
•
•
•
•
IP_SET_SOURCE_DMN
Table 18 summarizes the IP_SET_SOURCE_DMN result type.
IP_SET_SOURCE_DMN has the following data words:
•
•
–
–
•
–
–
IP_ROUTE_SEL
Table 0-1 summarizes the IP_ROUTE_SEL result type.
IP_ROUTE_SEL has the following data words:
•
–
–
–
–
–
–
–
–
•
•
•
DRP_EXIT
Table 0-1 summarizes the DRP_EXIT result type.
Table 19 DRP_EXIT Result Type
DRP_EXIT
(<drpExitType>)
DRP_EXIT (1)
I
Intermediate
Preanalysis
DRP_EXIT has one data word, drpExitType (dw1). This data word specifies the type of DRP exit. Valid values are
–
–
Results Added to Preanalysis
DBR adds six existing A and B analysis result types to preanalysis. Table 20 summarizes the existing result types that are now available in preanalysis.
For information about these result types, see the PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
Modified Result Types
The DBR feature modifies the result types listed in Table 21.
The following paragraphs contain definitions of the result type listed in Table 21.
NEW_DIALPLAN
The DBR feature modifies the NEW_DIALPLAN result type to allow the PGW 2200 Softswitch to restart at the A Number stage of analysis. To use this setting, set data word 2 to a value of 3.
Table 22 summarizes the updated NEW_DIALPLAN result type.
NEW_DIALPLAN has the following data words:
•
•
–
–
–
–
FACILITY
The DBR feature modifies the FACILITY result type to introduce new values for data words 1 and 2. You can use these values to conditionally reject calls based on source or destination domain name.
The DBR feature also adds the FACILITY result type to preanalysis.
Table 23 summarizes the FACILITY result type.
The DBR feature introduces the following new data word values:
•
•
Thus, the updated Facility result type has the following data words:
•
–
–
–
–
–
–
•
–
The DBR feature defines two new values for data word 2 for use when data word 1 (Type) is set to 4 (Terminating Redirection treatment action). Table 24 summarizes these values.
The DBR feature defines two new values for data word 2 for use when data word 1 (Type) is set to 6 (Terminating Call Transfer Treatment action). Table 25 summarizes these values.
RETRY_ACTION
The DBR feature modifies the RETRY_ACTION result type, allowing you to configure the stage of analysis in which the PGW 2200 Softswitch restarts when retrying a call. This capability provides consistent redirection handling for E.164 and non-E.164 calls. To configure this option, use data word 2.
Table 26 summarizes the RETRY_ACTION result type.
RETRY_ACTION has the following data words:
•
–
–
–
•
–
–
Cause and Location Codes
This section describes the cause and location codes that are updated for this feature. For table setup examples for cause and location codes, see the PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
This feature introduces the IC_BLACKLIST_SRC_MATCHED cause code. IC_BLACKLIST_SRC_MATCHED uses internal value 222 and is mapped to the corresponding SIP cause code, 403 Forbidden.
Dial Plan Examples
This section provides the following examples of dial plan provisioning for this feature. Additional examples of dial plan provisioning for the PGW 2200 Softswitch software can be found in the PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
In these examples, the assumption is that you have already created route lists with the following names:
•
•
•
IP_DEST_TRANS Example
In this example, the IP_DEST_TRANS result type is used to translate the destination URI and displayname from Bob <sip:bob@dbrpgw.cisco.com:5060> to JoeAtlanta <sip:Joe@abc.cisco.com:5079> ;user=phone. The PGW 2200 Softswitch routes the call based on the new destination URI using the routelist rtlistcisco2.
prov-stp::; Start a new MML session prov-sta::srcver="active", dstver="TRANS",confirm prov-ed:siprttrnkgrp:name="2002", domainbasedrtgsupport=1, url="abc.cisco.com" numan-add:dialplan:custgrpid="T002", overdec="YES" numan-add:service:custgrpid="T002", name="group1" ; Defines destination translation from Bob to JoeAtlantanuman-add:desttrans:custgrpid="T002", svcname="group1", destdmnstring="bob@dbrpgw.cisco.com", displayname="JoeAtlanta", username="Joe", domainname="abc.cisco.com:5079", uriparameters=";user=phone" ; Adds JoeAtlanta to the Route Selection table to enable routing based on the destination ; domain name.numan-add:routesel:custgrpid="T002", svcname="group1", destdmnstring="Joe@abc.cisco.com", rtlistname="rtlistcisco2"; Result sets numan-add:resultset:custgrpid="T002", name="drpstep1" numan-add:resultset:custgrpid="T002", name="dmnRtgExitSet" numan-add:resultset:custgrpid="T002", name="routeCall"; Result table entries numan-add:resulttable:custgrpid="T002", name="resultexitdrp", resulttype="DRP_EXIT", dw1="2", setname="dmnRtgExitSet" numan-add:resulttable:custgrpid="T002", name="resultrsel1", resulttype="IP_ROUTE_SEL", dw1="1", dw2="group1", dw3="dmnRtgExitSet", setname="routeCall" ; Adds a result set that translates based on the user and host. The PGW 2200 Softswitch; routes the call if the set is found.numan-add:resulttable:custgrpid="T002", setname="drpstep1", name="trans", resulttype="IP_DEST_TRANS", dw1="1", dw2="group1", dw3="routeCall" numan-add:drptable:custgrpid="T002", drpstepnum="1", setname="drpstep1" Prov-dply::IP_SET_SOURCE_DMN Example
In this example, the IP_SET_SOURCE_DMN result type is used to overwrite the source domain of incoming traffic with the source domain abc.cisco.com. The PGW 2200 Softswitch routes calls based on the new source domain using routelist rtlistcisco2.
prov-stp::; Start a new MML sessionprov-sta::srcver="active", dstver="SETDOMAIN", confirm; Enable Domain-Based Routing using trunk group 2002prov-ed:siprttrnkgrp:name="2002", domainbasedrtgsupport=1, url="abc.cisco.com"numan-add:service:custgrpid="T002", name="group1"numan-add:dialplan:custgrpid="T002", overdec="YES"; Add abc.cisco.com to the route selection tablenuman-add:routesel:custgrpid="T002", svcname="group1", srcdmnstring="abc.cisco.com", rtlistname="rtlistcisco2"; Add abc.cisco.com to the Domain Strings tablenuman-add:dmnmodstring:custgrpid="T002", name="domainname1", dmnstring="abc.cisco.com" ; Add result sets numan-add:resultset:custgrpid="T002" name="rsetdrpstep1" numan-add:resultset:custgrpid="T002", name="dmnRtgExitSet"; Result table entries numan-add:resulttable:custgrpid="T002", name="resultexitdrp", resulttype="DRP_EXIT", dw1="2", setname="dmnRtgExitSet"; Adds a result set that overwrites the source domain on the outgoing side. The; PGW 2200 Softswitch applies this change to the current source header only. numan-add:resulttable:custgrpid="T002", name="resultchangesrc1", resulttype="IP_SET_SOURCE_DMN", dw1="domainname1", setname="rsetdrpstep1", dw2="0", dw3="1" numan-add:resulttable:custgrpid="T002", name="resultrsel1", resulttype="IP_ROUTE_SEL", dw1="4", dw2="group1", dw3="dmnRtgExitSet", setname="rsetdrpstep1" numan-add:drptable:custgrpid="T002", drpstepnum="2", setname="rsetdrpstep1" Prov-dply::IP_ROUTE_SEL Example
In this example, the IP_ROUTE_SEL result type is used to route calls based on the destination hostname joe@cisco.com or the destination domain cisco.com.
prov-stp::; Start a new MML sessionprov-sta::srcver="active", dstver="mod_ver01", confirmnuman-add:dialplan:custgrpid="T002", overdec="YES"numan-add:resultset:custgrpid="T002", name="dmnrtgset1"numan-add:resultset:custgrpid="T002", name="dmnRtgExitSet"numan-add:resultset:custgrpid="T002", name="finalDefaultRtgSet"numan-add:resultset:custgrpid="T002", name="dmnrtgDefaultSet"numan-add:service:custgrpid="T002", name="group1"; Adds a route selection table entry to route based on destination domain joe@cisco.comnuman-add:routesel:custgrpid="T002", destdmnstring="joe@cisco.com", svcname="group1", rtlistname="rtlistcisco1"; Adds a route selection table entry to route based on destination domain cisco.comnuman-add:routesel:custgrpid="T002", destdmnstring="cisco.com", svcname="group1", rtlistname="rtlistcisco2"numan-add:resulttable:custgrpid="T002", name="resultexitdrp", resulttype="DRP_EXIT", dw1="2", setname="dmnRtgExitSet"numan-add:resulttable:custgrpid="T002", name="resultfinalrte", resulttype="ROUTE", dw1="rtlistdefaultswbd", setname="finalDefaultRtgSet"; Adds a result that selects a route based on the destination hostnamenuman-add:resulttable:custgrpid="T002", name="resultrsel2", resulttype="IP_ROUTE_SEL", dw1="2", dw2="group1", dw3="dmnRtgExitSet", dw4="finalDefaultRtgSet", setname="dmnrtgDefaultSet"; Adds a result that selects a route based on destination user and hostnamenuman-add:resulttable:custgrpid="T002", name="resultrsel1", resulttype="IP_ROUTE_SEL", dw1="1", dw2="group1", dw3="dmnRtgExitSet", dw4="dmnrtgDefaultSet", setname="dmnrtgset1"numan-add:drptable:custgrpid="T002", drpstepnum="1", setname="dmnrtgset1"Prov-dply::IP_SOURCE_SCREEN Example
In this example, calls are screened based on the source domain example.com. Non-screened calls are routed based on the destination URI dbrpgw.cisco.com.
prov-stp::; Start a new MML session prov-sta::srcver="active", dstver="source_screen", confirm; Enable non-164 routing on the siprttrnkgrp prov-ed:siprttrnkgrp:name="2002", DomainBasedRtgSupport="1", url="dbrpgw.cisco.com"; Add result set entries numan-add:resultset:custgrpid="T002", name="screenURI" numan-add:service:custgrpid="T002", name="group1"; Add a route selection entry to route based on the destination bob@dbrpgw.cisco.com numan-add:routesel:custgrpid="T002", svcname="group1", destdmnstring="bob@dbrpgw.cisco.com", rtlistname="rtlist002"; Screen calls based on the source domain example.com. numan-add:sourceblack:custgrpid="T002", svcname="group1", srcdmnstring="example.com"; Add resulttable entries numan-add:resulttable:custgrpid="T002", setname="screenURI", name="UserHost", resulttype="IP_SOURCE_SCREEN", dw1="1", dw2="group1", dw3="0" numan-add:resulttable:custgrpid="T002", setname="screenURI", name="routecall", resulttype="IP_ROUTE_SEL", dw1="1", dw2="group1" ; Add an entry to the DRP table numan-add:drptable:custgrpid="T002", drpstepnum="1", setname="screenURI"Prov-dply::Example with All Result Types
In this example, two domain routing policy (DRP) table steps and all of the result types introduced in the DBR feature are defined.
A PGW 2200 Softswitch with this configuration would process calls as follows:
•
•
prov-stp:: ; Start a new MML session prov-sta::srcver="active", dstver="nested", confirm ; Add a new entry in the service table numan-add:service:custgrpid="T002", name="group1" ; Enable DBR on trunk group 2002 prov-ed:siprttrnkgrp:name="2002", domainbasedrtgsupport=1, url="bob@atlanta.cisco.com" ; Add entries in TimesTen tables numan-add:routesel:custgrpid="T002", svcname="group1", destdmnstring="bob@atlanta.cisco.com", rtlistname="rtlist002" numan-add:sourceblack:custgrpid="T002", svcname="group1", srcdmnstring="example.com" numan-add:desttrans:custgrpid="T002", svcname="group1", destdmnstring="dbrpgw.cisco.com", domainname="atlanta.cisco.com:5079" ; Add result set entries numan-add:resultset:custgrpid="T002", name="drpstep1" numan-add:resultset:custgrpid="T002", name="drpstep2" numan-add:resultset:custgrpid="T002", name="setSource" numan-add:resultset:custgrpid="T002", name="exitdrp" numan-add:resultset:custgrpid="T002", name="trans" numan-add:resultset:custgrpid="T002", name="routeCall" ; Add example.com to domain strings table numan-add:dmnmodstring:custgrpid="T002", name="domainname1", dmnstring="abc.cisco.com" ; Add result table entries for DRP step 1 numan-add:resulttable:custgrpid="T002", name="resultexitdrp", resulttype="DRP_EXIT", dw1="2", setname="exitdrp" numan-add:resulttable:custgrpid="T002", name="changesource", resulttype="IP_SET_SOURCE_DMN", dw1="domainname1", setname="setSource", dw2="0", dw3="1" numan-add:resulttable:custgrpid="T002", setname="drpstep1", name="screen", resulttype="IP_SOURCE_SCREEN", dw1="2", dw2="group1", dw3="setSource" ; Add result table entries for DRP step 2 numan-add:resulttable:custgrpid="T002", name="resultrsel1", resulttype="IP_ROUTE_SEL", dw1="1", dw2="group1", dw3="exitdrp", setname="routeCall" numan-add:resulttable:custgrpid="T002", setname="drpstep2", name="trans", resulttype="IP_DEST_TRANS", dw1="2",dw2="group1", dw3="routeCall", dw4="exitdrp" ; Add DRP table entries numan-add:drptable:custgrpid="T002", drpstepnum="1", setname="drpstep1" numan-add:drptable:custgrpid="T002", drpstepnum="2", setname="drpstep2"Prov-dply::Worksheets
You can use the following worksheets to implement the DBR feature.
Provisioning Worksheets
This section contains a worksheet for the provisioning components required for this feature. For worksheets covering the rest of the provisioning components in the PGW 2200 Softswitch software, refer to the PGW 2200 Softswitch Release 9.8 Provisioning Guide.
Table 27 Provisioning Worksheet
9001
2
PGW 2200 Softswitch analyzes B-number
Dial Plan Worksheets
This section contains worksheets for the dial plan components required for this feature. For worksheets covering the rest of the dial plan components in the PGW 2200 Softswitch software, refer to the PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
Table 28 IP_SOURCE_SCREEN Worksheet Example
9001
IP_SOURCE_SCREEN
Table 29 IP_SET_SOURCE_DOMAIN Worksheet Example
9001
IP_SET_SOURCE_DOMAIN
Table 30 IP_DEST_TRANS Worksheet Example
9001
IP_DEST_TRANS
Table 31 IP_ROUTE_SEL Worksheet Example
9001
IP_ROUTE_SEL
Updating the TimesTen Database
There are three ways to update a table in the TimesTen database.
•
•
•
Using the db-bulkcp Tool
The db-bulkcp tool allows you to quickly add a large number of records to the TimesTen database.
The benefits of using db-bulkcp are
•
•
Db-bulkcp can detect duplicate rows.
To load data into the TimesTen database, follow these steps:
Note
Step 1
##ttBulkCp## CISCO.PORTEDNUMBERS, 4 columns# columns:# 1. CALLEDNUM CHAR(20)# 2. ROUTINGNUM CHAR(20)# 3. MINLENGTH TINYINT# 4. MAXLENGTH TINYINT# end#"123456789","444",0,0"1234567890","555",5,12"1234567891","5566",3,9......
Note
Step 2
# db-bulkcp import tablename filename
Note
Using MML Import/Export
You can import data in MML using the prov-add command. This method uses the following file format:
Note
To import data with MML, use the following command:
mml> prov-add:files:name="TKGFile",file="<dir_name>/export_trkgrp.dat",action="import"For more information about importing with MML, see the PGW 2200 Softswitch Release 9.8 Provisioning Guide.
Translation Verification Tool (callver)
The DBR feature modifies the Translation Verification Tool (callver) so that it supports domain-based calls. The following new fields are now available for domain-based (non-E.164) calls:
•
•
•
•
Figure 6 shows the modified Translation Verification Tool.
Figure 6
Translation Verification Tool
Mini-parse Trace Analysis Tool
This feature updates the mini-parse trace analysis tool introduced in CSCsk32769. The tool has been modified to capture the following information:
•
•
•
•
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Glossary
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.
