Configure a gateway.

1. Click Add new entry next to Gateway.
2. In the Name box, enter the identifier for the BSG.
3. In the Comment box, enter the comment.
4. From the Service Interface list, select the name and logical unit number of the Multiservices PIC or DPC.

Configure an admission controller for a border signaling gateway (BSG).

1. Click Add new entry next to Gateway.
2. Click Admission Controller next to gateway.
3. In the Name box, enter the identifier for the BSG.
4. In the Comment box, enter the comment.
5. From the Service Interface list, select the name and logical unit number of the Multiservices PIC or DPC.
6. Click Admission Control next to gateway.
7. Click Add new entry next to Admission Control.
8. In the Name box, enter the name of the admission controller.
9. In the Comment box, enter the comment.

Configure admission control settings for dialogs.

1. Click Dialogs next to admission-control.
2. From the Maximum Concurrent list, select the maximum number of concurrent dialogs. 0 causes all calls to be rejected.

   Range: 0 through 100,000

3. From the Committed Attempts Rate list, select the maximum number of attempts per second to initiate a dialog.

   Range: 0 through 100

4. From the Committed Burst Rate list, select the maximum number of dialogs allowed to burst above the committed rate and still be accepted.

Configure admission control settings for out-of-dialog transactions.

1. Click Transactions next to admission-control.
2. From the Maximum Concurrent list, select the maximum number of concurrent transactions. 0 causes all calls to be rejected.

   Range: 0 through 50000

3. From the Committed Attempts Rate list, select the maximum number of attempts per second to initiate an out-of-dialog transaction.

   Range: 0 through 1500

4. From the Committed Burst Rate list, select the maximum number of transactions allowed to burst above the committed rate and still be accepted.

   Range: 0 through 3000

Configure the SPDF.

1. Click Add new entry next to Gateway.
2. Click Embedded Spdf next to gateway.
3. In the Comment box, enter the comment.

Configure service classes for the embedded SPDF.

1. Click Service Class next to Embedded Spdf.
2. From the Service Interface list, select the name and logical unit number of the Multiservices PIC or DPC.
3. Click Add new entry next to Service Class.
4. In the Name box, enter the identifier for the service class.
5. In the Comment box, enter the comment.

Specify the service class term properties.

1. Click Term next to service-class.
2. Click Add new entry next to Term.
3. In the Name box, enter the identifier for the term.
4. In the Comment box, enter the comment.
5. Click From next to term.
6. In the Comment box, enter the comment.
7. Click Media Type next to From.
8. Click Add new entry next to Media Type.
9. In the New media-type window, select the type of media that the service class matches.
   • any-media—Match all media types.
   • audio—Match audio traffic.
   • video—Match video traffic.
10. Click Then next to term.
11. In the Comment box, enter the comment.
12. Select the Reject check box to not accept the traffic and return a rejection message.
13. From the Committed Information Rate list, select the maximum bandwidth that can be allocated to a packet that is flowing under normal line conditions.

    Range: 0 through 2147483647

14. From the Committed Burst Size list, select the maximum number of bytes allowed for incoming packets to burst above the committed information rate.

    Range: 20 through 2147483647

15. From the Dscp list, select the values for DSCP marking that the BSG uses for traffic that matches the service class term.

    Default: be

Configure a service point.

1. Click Add new entry next to Gateway.
2. Click Service Point next to gateway.
3. Click Add new entry next to Service Point.
4. In the Name box, enter the name.
5. In the Comment box, enter the comment.
6. From the Service Point Type list, select the type of VoIP protocol for this service point.

   Values: sip

7. From the Service Interface list, select the name of the service interface.
8. From the Default Media Realm list, select the realm number used to match to a virtual interface

   Range: 0 through 1023

Configure service classes for the embedded SPDF.

1. Click Service Class next to Embedded Spdf.
2. From the Service Interface list, select the name and logical unit number of the Multiservices PIC or DPC.
3. Click Add new entry next to Service Class.
4. In the Name box, enter the identifier for the service class.
5. In the Comment box, enter the comment.

Assign new call usage policies or policy sets to the service point.

1. Click Service Policies next to service-point.
2. In the Comment box, enter the comment.
3. Click New Call Usage Policies next to Service Policies.
4. Click Add new entry next to New Call Usage Policies.
5. In the New new-call-usage-policies window, enter the names of new call usage policies or policy sets.

   Syntax: If you specify more than one policy or policy set, you must enclose all policy names in brackets.

6. Click New Transaction Policies next to Service Policies.
7. Click Add new entry next to New Transaction Policies.
8. In the New new-transaction-policies window, enter the names of new call usage policies or policy sets.

   Syntax: If you specify more than one policy or policy set, you must enclose all policy names in brackets.

9. Click Transport Details next to service-point.
10. In the Comment box, enter the comment.
11. From the Port Number list, select the port number.
12. In the Ip Address box, enter the IP address.
13. Select the corresponding transport protocol.

Configure a message manipulation rule.

1. Click Add new entry next to Gateway.
2. Click Sip next to gateway.
3. In the Comment box, enter the comment.
4. Click Message Manipulation Rules next to Sip.
5. In the Comment box, enter the comment.

Configure a manipulation rule.

1. Click Manipulation Rule next to Message Manipulation Rules.
2. Click Add new entry next to Manipulation Rule.
3. In the Name box, enter the name of the manipulation rule.
4. In the Comment box, enter the comment.
5. Click Actions next to manipulation-rule.
6. In the Comment box, enter the comment.
7. Click Request Uri next to Actions.
8. In the Comment box, enter the comment.
9. Click Field Value next to Request Uri.
10. In the Comment box, enter the comment.
11. Click Modify Regular Expression next to Field Value.
12. Click Add new entry next to Modify Regular Expression.
13. In the Name box, enter the regular expression that you want to modify.
14. In the Comment box, enter the comment.
15. In the With box, enter the regular expression that you want to modify followed by the value with which you want to replace the regular expression.

Configure Session Initiation Protocol (SIP) header.

1. Click Sip Header next to manipulation-rule.
2. Click Add new entry next to Sip Header.
3. In the Name box, enter the name of the header field in SIP headers for which you want to define field values.
4. In the Comment box, enter the comment.
5. Click Field Value next to sip-header.
6. In the Comment box, enter the comment.
7. Select the Remove All check box to remove all instances of the header field.
8. Click Add next to Field Value.
9. Select from the following field values:
   • Add—Adds an instance of the header field with the field value that you define. If the header field already exists, the software creates a new instance of the header field and inserts it before any existing instance of the header field. Having more than one field value is not allowed for some header fields.
   • Add Missing—Adds a new header field with the field value that you define if the header field is missing from the SIP header.
   • Add Overwrite—Adds a new header field with the field value that you define if the header field is missing from the SIP header. If the header field already exists, its field value is overwritten with the new field value. The software overwrites the field value in all instances of the header field.
   • Modify Regular Expression—Changes the value of a regular expression.
   • Reject Regular Expression—Rejects SIP messages and terminates the usage that the message is part of if the header field contains the regular expression.
   • Remove Regular Expression—Removes all of the header fields that have field values that match this regular expression.
10. Enter the Name and Comment.

Configure a new call usage policy.

1. Click Add new entry next to Gateway.
2. Click Sip next to gateway.
3. In the Comment box, enter the comment.
4. Click New Call Usage Policy next to Sip.
5. Click Add new entry next to New Call Usage Policy.
6. In the Name box, enter the identifier for the new call usage policy.
7. In the Comment box, enter the comment.

Define the new call usage policy term properties.

1. Click Term next to new-call-usage-policy.
2. Click Add new entry next to Term.
3. In the Name box, enter the identifier for the term.
4. In the Comment box, enter the comment.

Configure match conditions for a new call usage policy.

1. Click From next to term.
2. In the Comment box, enter the comment.
3. Click Add new entry next to Term.
4. In the Name box, enter the identifier for the term.
5. Click Contact next to From.
6. Click Add new entry next to Contact.
7. In the Comment box, enter the comment.
8. Click Regular Expression next to contact.
9. Click Add new entry next to Regular Expression.
10. In the New regular-expression window, enter the regular expression used to match the contents of the contact field.

    Syntax: To specify more than one regular expression, enclose the regular expressions in brackets.

11. Click Method next to From.
12. Click Add new entry next to Method.
13. From the Name list, select method-invite to match the policy to SIP INVITE methods.
14. In the Comment box, enter the comment.
15. Click Request Uri next to From.
16. Click Add new entry next to Request Uri.
17. In the Comment box, enter the comment.
18. Click Regular Expression next to request-uri.
19. In the New regular-expression window, enter the regular expression used to match the contents of the request URI field.

    Syntax: To specify more than one regular expression, enclose the regular expressions in brackets.

20. Click Source Address next to From.
21. Click Add new entry next to Source Address.
22. In the New source-address window, enter the IP addresses that you want to match.

    Syntax: To specify more than one IP address, enclose the IP addresses in brackets.

Define the actions performed on incoming requests that match the new call usage policy.

1. Click Then next to From.
2. In the Comment box, enter the comment.
3. Select one of the following check boxes:
   • accept—To accept the traffic and send it to its destination.
   • reject—To reject the traffic and return a rejection message. Rejected traffic can be logged or sampled.
   • trace—To trace messages accepted by this policy.
4. Click Media Policy next to Then.
5. In the Comment box, enter the comment.
6. Select the No Anchoring check box to disable or enable media anchoring for the policy.
7. In the Service Class box, enter the name of the service class to be applied to traffic that matches the new call usage policy.
8. Click Data Inactivity Detection next to Media Policy.
9. In the Comment box, enter the comment.
10. From the Inactivity Duration list, select the time interval that determines inactivity.

    Range: 30 through 3600

Configure a new call usage policy set.

1. Click Add new entry next to Gateway.
2. Click Sip next to gateway.
3. In the Comment box, enter the comment.
4. Click New Call Usage Policy Set next to Sip.
5. Click Add new entry next to New Call Usage Policy Set.
6. In the Name box, enter the identifier for the new call usage policy set.
7. In the Comment box, enter the comment.

Define the new call usage policies.

1. Click Policy Name next to new-call-usage-policy-set.
2. Click Add new entry next to Policy Name.
3. In the New policy-name window, enter the names of one or more new call usage policies that you want to add to the set.

   Syntax: To specify a list of policies, enclose the policy names in brackets.

Configure new transaction policy.

1. Click Add new entry next to Gateway.
2. Click Sip next to gateway.
3. In the Comment box, enter the comment.
4. Click New Transaction Policy next to Sip.
5. Click Add new entry next to New Call Transaction Policy.
6. In the Name box, enter the identifier for the new transaction policy.
7. In the Comment box, enter the comment.

Define the new transaction policy term properties.

1. Click Term next to new-transaction-policy.
2. Click Add new entry next to Term.
3. In the Name box, enter the identifier for the term.
4. In the Comment box, enter the comment.

Configure match conditions for a new transaction policy.

1. Click From next to term.
2. In the Comment box, enter the comment.
3. Click Add new entry next to Term.
4. In the Name box, enter the identifier for the term.
5. Click Contact next to From.
6. Click Add new entry next to Contact.
7. In the Comment box, enter the comment.
8. Click Regular Expression next to contact.
9. Click Add new entry next to Regular Expression.
10. In the New regular-expression window, enter the regular expression used to match the contents of the contact field.

    Syntax: To specify more than one regular expression, enclose the regular expressions in brackets.

11. Click Method next to From.
12. Click Add new entry next to Method.
13. From the Name list, select the type of SIP method.
14. In the Comment box, enter the comment.
15. Click Request Uri next to From.
16. Click Add new entry next to Request Uri.
17. In the Comment box, enter the comment.
18. Click Regular Expression next to request-uri.
19. In the New regular-expression window, enter the regular expression used to match the contents of the request URI field.

    Syntax: To specify more than one regular expression, enclose the regular expressions in brackets.

20. Click Source Address next to From.
21. Click Add new entry next to Source Address.
22. In the New source-address window, enter the IP addresses that you want to match.

    Syntax: To specify more than one IP address, enclose the IP addresses in brackets.

Define the actions performed on incoming requests that match this policy.

1. Click Then next to From.
2. In the Comment box, enter the comment.
3. Select the following check boxes:
   • accept—To accept the traffic and send it to its destination
   • reject—To reject the traffic and return a rejection message. Rejected traffic can be logged or sampled.
   • trace—To trace messages accepted by this policy
4. In the Admission Control box, enter the controller name.
5. Click Message Manipulation next to Then.
6. In the Comment box, enter the comment.
7. Click Forward Manipulation next to Message Manipulation.
8. Click Add new entry next to Forward Manipulation.
9. In the Name box, enter the name of the forward message manipulation rules that you want to add to your new transaction policy.
10. In the Comment box, enter the comment.
11. Click Reverse Manipulation next to Message Manipulation.
12. Click Add new entry next to Reverse Manipulation.
13. In the Name box, enter the name of the reverse message manipulation rules that you want to add to your new transaction policy.
14. In the Comment box, enter the comment.

Configure the next-hop destination and egress service point for a new transaction policy.

1. Click Route next to Then.
2. In the Comment box, enter the comment.
3. In the Egress Service Point box, enter the name of the service point that you want to use as the egress service point.
4. Click Next Hop next to Route.
5. In the Comment box, enter the comment.
6. Click Address next to Next Hop.
7. Select the SIP entity towards which SIP requests are sent.
   • address—To configure the destination IPv4 address of the next hop to contact
     1. In the Comment box, enter the comment.
     2. In the Ipv4 Address box, enter the destination IPv4 address of the next hop to contact.
     3. From the Port list, select the destination port of the next hop to contact. Default: 5060
     4. Click Transport protocol next to Address.
     5. In the Comment box, enter the comment.
     6. Select the transport protocol for routing to the next hop.
   • request-uri—To route all requests and responses on the dialog according to SIP.

Configure a new transaction policy set.

1. Click Add new entry next to Gateway.
2. Click Sip next to gateway.
3. In the Comment box, enter the comment.
4. Click New Transaction Policy Set next to Sip.
5. Click Add new entry next to New Transaction Policy Set.
6. In the Name box, enter the identifier for the new transaction policy set.
7. In the Comment box, enter the comment.

Define the new transaction policies.

1. Click Policy Name next to new-transaction-policy-set.
2. Click Add new entry next to Policy Name.
3. In the New policy-name window, enter the names of one or more new transaction policies that you want to add to the set.

   Syntax: To specify a list of policies, enclose the policy names in brackets.

Configure timers used to issue SIP timeouts.

1. Click Add new entry next to Gateway.
2. Click Sip next to gateway.
3. In the Comment box, enter the comment.
4. Click Timers next to Sip.
5. In the Comment box, enter the comment.
6. From the Inactive Call list, select the maximum time for signaling inactivity.

   Range: 300 through 86400

7. From the Timer C list, select the duration of the timeout period.

   Range: 180 through 300

Configure border signaling gateway (BSG) tracing operations.

1. Click Add new entry next to Gateway.
2. Click Traceoptions next to gateway.
3. Click Flag next to Traceoptions.
4. In the Comment box, enter the comment.
5. From the Minimum list, select the severity of the event being traced.
   • debug—Logging of all code flow of control.
   • trace—Logging of program trace for START, and EXIT macros.
   • info—Summary logs for normal operations. e.g. the policy decisions made for a call.
   • warning—Failure-recovery or failure of an external entity.
   • error—Failure with short-term effect, such as failed processing of a single call.
6. From the Session Trace list, select the minimum trace level for all session-trace messages.

Configure trace level options for the datastore component of the BSG.

1. Click Add new entry next to Gateway.
2. Click Traceoptions next to gateway.
3. Click Flag next to Traceoptions.
4. Click Datastore next to Flag.
5. In the Comment box, enter the comment.
6. From the Minimum list, select the minimum trace level for all datastore messages.
7. From the Data list, select the trace level for the data subcomponent.
8. From the Handle list, select the trace level for the access API for the database.
9. From the Db list, select the trace level for the wrapper layer around the database.

Configure trace options for the BSG component that provides an infrastructure that enables incremental functionality implementation.

1. Click Add new entry next to Gateway.
2. Click Traceoptions next to gateway.
3. Click Flag next to Traceoptions.
4. Click Framework next to Flag.
5. In the Comment box, enter the comment.
6. From the Minimum list, select the minimum trace level for all framework messages.
7. From the Executor list, select the trace level for the framework subcomponent that executes configured actions for an event, handles any error states, delays processing, and so on.
8. From the Action list, select the trace level for the framework subcomponent that creates, initiates, and manipulates event actions.
9. From the Event list, select the trace level for the framework subcomponent that creates, modifies, and terminates event members.
10. From the Freezer list, select the trace level for the framework subcomponent that delays the execution of an event until certain conditions are met.
11. From the Memory Pool list, select the trace level for the framework subcomponent that creates, deletes, and manipulates memory pools and pool managers, and controls the check-in to and check-out from memory pools of memory objects.

Configure trace options for the Signaling Border Controller (SBC) utilities component of the BSG.

1. Click Add new entry next to Gateway.
2. Click Traceoptions next to gateway.
3. Click Flag next to Traceoptions.
4. Click Sbc Utils next to Flag.
5. In the Comment box, enter the comment.
6. From the Minimum list, select the minimum trace level for all sbc-util messages.
7. From the Configuration list, select the trace level for the configuration component of SBC utilities.
8. From the Ipc list, select the trace level for the IPC component of SBC utilities.
9. From the Device Monitor list, select the trace level for the device monitor component of SBC utilities.
10. From the Memory Management list, select the trace level for the memory management component of SBC utilities.
11. From the Message list, select the trace level for the message component of SBC utilities.
12. From the Common list, select the trace level for the common component of SBC utilities.
13. From the User Interface list, select the trace level for the user interface component of SBC utilities.
14. From the Memory Pool list, select the trace level for the message component of SBC utilities.
15. From the Memory Pool list, select the trace level for the memory pool component of SBC utilities.

Configure trace options for the signaling component of the BSG.

1. Click Add new entry next to Gateway.
2. Click Traceoptions next to gateway.
3. Click Flag next to Traceoptions.
4. Click Signaling next to Flag.
5. In the Comment box, enter the comment.
6. From the Minimum list, select the minimum trace level for all signaling messages.
7. From the Sip Stack Wrapper list, select the trace options for the glue layer that receives events from the SIP stack and forwards them to the application and, conversely, receives events from the application and forwards them to the SIP stack.
8. From the b2b Wrapper list, select the trace options for entry and exit to the BSG signaling application.
9. From the Ua list, select the trace options for the signaling subcomponent that handles RECEIVE messages.
10. From the B2b list, select the trace options for the signaling component that implements the b2b logic (translating between dialogs, associating dialogs, creating new downstream dialogs, and so on).
11. From the Topology Hiding list, select the trace options for the signaling component that hides the network topology of a network by CONTACT replacement and removal or modification of certain headers.
12. From the Policy list, select the trace options for the signaling component that applies policies for call admission, routing decisions, security settings, and so on.

Set trace options for the SIP stack component of the BSG.

1. Click Add new entry next to Gateway.
2. Click Traceoptions next to gateway.
3. Click Flag next to Traceoptions.
4. Click Sip Stack next to Flag.
5. In the Comment box, enter the comment.
6. Select the Event Tracing check box to activate or deactivate the stack's event tracing.
7. Select the Event Tracing check box to activate or deactivate the stack's event tracing.
8. Select the Ips Tracing check box to activate or deactivate the stack’s IPS tracing.
9. Select the Per Tracing check box to activate or deactivate the stack’s performance tracing.
10. Select the Dev Logging check box to configure development tracing for the stack.
11. Select the Verbose Logging check box to configure verbose tracing for the stack.
12. From the Pd Log Level list, select which types of PD logs are to be printed to the log file. Select one of the following:
    • problem—Problem log messages are sent to the log file.
    • exception—Exception and problem log messages are sent to the log file.
    • audit—All log messages are sent to the log file.
13. From the Pd Log Detail list, select the amount of detail to be sent to the log file. Select one of the following:
    • full—All available information is sent to the log file.
    • summary—The type of logging, the identifier and the first line of the log message are sent to the log file.