In this section:
Use the Call Notification commands to configure call notification criteria as part of the SBC's call notification feature. For deployments requiring notifications when calls are set up by the SBC, you can configure the SBC to send SIP NOTIFY messages to a specified Application Server when a call's calling party or called party matches criteria you specify. Refer to Sending Unsolicited Call Notifications to Application Servers for more information on the call notification feature.
Use the callNotificationCriteria
object to specify individual sets of criteria (called party, calling party, trunk group for the other call leg) that the SBC's Embedded Routing Engine (ERE) compares against calls. This object also identifies the servers, using a cnsGroupCluster
, to notify in the event of a match.
% set global servers callNotificationCriteria <criteria ID> calledPartyId calledPartyType <AoR | number> callingPartyId callingPartyType <AoR | number> cnsGroupClusterId <cns group cluster ID> otherLegTG role <egress | ingress | none> userPartType <none | useCalledNumber | useCallingNumber | useConfigured> userPartValue
Use the callNotificationCriteriaGroup
object to group up to 32 callNotificationCriteria
objects that you can then assign to a SIP trunk group. For calls on that trunk group, the ERE compares the calling number/called number and other-leg trunk group against the criteria in the group. The callNotificationCriteriaGroup
specifies the sequence in which the criteria is evaluated. Once a call matches one of the callNotificationCriteria
objects, the matching process skips the remaining criteria in the group and the SBC initiates its notification process.
% set global servers callNotificationCriteriaGroup <group ID> callNotificationCriteriaGroupData <sequence: 0 - 31> callNotificationCriteriaId <call notification criteria ID> description
For command examples, refer to Configuring the SBC to Send Unsolicited Call Notifications to Application Servers.