Routing based on OPTIONS pings

Use the following SMM to configure the SBC Core to interoperate with Net Number CRE and respond to OPTIONS pings locally at the SBC:

  1. Create SMM Profile:

    set profiles signaling sipAdaptorProfile test state enabled
    set profiles signaling sipAdaptorProfile test advancedSMM disabled
    set profiles signaling sipAdaptorProfile test profileType messageManipulation
    set profiles signaling sipAdaptorProfile test rule 1 applyMatchHeader one
    set profiles signaling sipAdaptorProfile test rule 1 criterion 1 type message
    set profiles signaling sipAdaptorProfile test rule 1 criterion 1 message
    set profiles signaling sipAdaptorProfile test rule 1 criterion 1 message messageTypes request
    set profiles signaling sipAdaptorProfile test rule 1 criterion 1 message methodTypes options
    set profiles signaling sipAdaptorProfile test rule 1 criterion 2 type header
    set profiles signaling sipAdaptorProfile test rule 1 criterion 2 header
    set profiles signaling sipAdaptorProfile test rule 1 criterion 2 header name Request-Line
    set profiles signaling sipAdaptorProfile test rule 1 criterion 2 header condition exist
    set profiles signaling sipAdaptorProfile test rule 1 criterion 2 header hdrInstance all
    set profiles signaling sipAdaptorProfile test rule 1 criterion 3 type token
    set profiles signaling sipAdaptorProfile test rule 1 criterion 3 token
    set profiles signaling sipAdaptorProfile test rule 1 criterion 3 token condition regex-match
    set profiles signaling sipAdaptorProfile test rule 1 criterion 3 token tokenType uriusername
    set profiles signaling sipAdaptorProfile test rule 1 criterion 3 token regexp
    set profiles signaling sipAdaptorProfile test rule 1 criterion 3 token regexp string test.*
    set profiles signaling sipAdaptorProfile test rule 1 action 1 type token
    set profiles signaling sipAdaptorProfile test rule 1 action 1 operation delete
    set profiles signaling sipAdaptorProfile test rule 1 action 1 to
    set profiles signaling sipAdaptorProfile test rule 1 action 1 to type token
    set profiles signaling sipAdaptorProfile test rule 1 action 1 to tokenValue uriusername
  2. Attach the following SMM to the ingress TG as inputAdaptorProfile.

    set addressContext default zone ZONE1 sipTrunkGroup TG1 signaling messageManipulation inputAdapterProfile test

Routing based on Trunk Context

 

Use the following SMM to configure the SBC Core to interoperate with Net Number CRE to populate the trunk context parameter at the SBC.

The SBC always stores and sends the SIP domain information that is used to populate the trunk-context parameter of the Request URI parameter in the INVITE in upper case letters. For example;

INVITE sip:+7317616310006;tgrp=761M52;trunk-context=S.10.711A.M52.STC@10.102.17.22:5060;transport=UDP;user=phone;sat-hops=0 SIP/2.0

The CRE is configured to expect upper case letters for routing based on trunk context.

The figure below describes the routing based on trunk context.

Routing Based on Trunk Context

 

 

  • No labels