SigMa rule examples required for Microsoft Teams

Last Updated : Jul 24, 2020 |
Prolog information
Metadata
Keywords:
This section shows examples of SigMa rules that must be added when using Microsoft Teams. For more information about SigMa rules, see Administering Avaya Session Border Controller.

Remove History Info

Use the following script to remove History Info that Microsoft Teams does not understand, plus other Avaya Aura® specific headers not used by Microsoft Teams. The Avaya Aura® specific headers are shown in bold type. You must install this script.
within session "ALL"
{
    act on message where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
    {
   
       remove(%HEADERS["History-Info"][3]);
       remove(%HEADERS["History-Info"][2]);            
       remove(%HEADERS["History-Info"][1]);
       remove(%HEADERS["Remote-Party-ID"][1]); //Remove the header
       remove(%HEADERS["Remote-Address"][1]); //Remove the header
       remove(%HEADERS["P-AV-Message-Id"][1]); //Remove the header
       remove(%HEADERS["x-nt-e164-clid"][1]); //Remove the header
       remove(%HEADERS["P-Charging-Vector"][1]); //Remove the header
       remove(%HEADERS["Av-Global-Session-ID"][1]); //Remove the header
       remove(%HEADERS["P-Location"][1]); //Remove the header
       remove(%HEADERS["Alert-Info"][1]); //Remove the header
       remove(%HEADERS["User-to-User"][1]); //Remove the header
       remove(%HEADERS["Max-Breadth"][1]); //Remove the header

       
     
    }
        
}

Failover

Use the following script to insert the exact version of the Avaya SBC software release into the header. This is required for Microsoft Teams failover. When creating this script, use the actual release number; this is only an example of the release number.
within session "all" 

{
act on request where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"

  {
    %HEADERS["X-MS-SBC"][1] = "AVAYA SBCE-8.1.1.19158";
   }
}

Number manipulations

This is an example of a script that you can used to manipulate any required numbering plan changes. The following is only an example. You must change the script to match your numbering plan.
For instance, this example shows how the number 719 is manipulated to add the string +1 so that when a user simply dials the area code 719, the actual digit dialed is +1719.
within session "all" 

{
act on message where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"

  {
   
        %HEADERS["From"][1].URI.USER.regex_replace("^214","+1214");
        %HEADERS["To"][1].URI.USER.regex_replace("^719","+1719");
        %HEADERS["Request_Line"][1].URI.USER.regex_replace("719","+1719");

    }
}