Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Select VoIP from the Configuration Menu on the left-hand side.



  2. Configure the system’s VoIP settings.



    Caption
    0Table
    1Configuring VoIP Parameters
    3Configuring VoIP Parameters

    Parameter

    Example Configuration Value

    Enable LLDP:

    Enabled (default)

    LLDP-MED with tagged VLAN:

    Enabled (default)

    LLDP Broadcast Interval (sec):

    30 (default)

    TFTP Server IP address:

    Disabled

    Use ALG Alias IP Addresses:

    Disabled

    Public NAT WAN IP address:

    Public WAN IPv4 address when using a 1-to-1 NAT configuration

    Private NAT LAN IP address:

    Private LAN IPv4 address when using a 1-to-1 NAT configuration

    Do strict RTP source check:

    Disabled

    Enable Client List lockdown:

    Disabled

    Allow Shared Usernames:

    Disabled

    Strip G.729 from calls:

    Disabled

    UDP

     UDP System Port:

    5060,5070,5075 (default)

    UDP

    UDP System Source Port:

    5060 (default)

    UDP

    REGISTER restricted to port:

    0 (default)

    UDP

    Block UDP support on WAN:

    Disabled

    TCP

    TCP System Port:

    5060 (default)

    TCP

    TCP Connection Timeout (m):

    10 (default)

    TCP

    Block TCP support on WAN:

    Disabled

    TLS

    TLS System Port:

    5061

    TLS

    TLS Protocol:

    TLSv1.2

    TLS

    Use only selected version:

    Disabled

    TLS

    Ciphers String:

    TLSv1.2+HIGH:!eNULL:!aNULL

    TLS

    LAN:

    Certificate: Default

    Policy: No Check

    TLS

    WAN:

    Certificate: SBC_Cert

    Policy: No Check

    TLS

    Block TLS support on WAN:

    Disabled

    TLS

    Exclude sips headers for TLS Transport:

    Enabled

    TLS

    Set TLS source port:

    Disabled

    NAT Traversal

    Disabled

    Route all SIP signalling through B2BUA:

    Enabled

    Enable Microsoft Feature:

    Enabled

    Enable Comfort Noise Generation (CNG):

    Enabled

    Enable User-Agent header pass-through:

    Disabled

    B2BUA Redirect Support (302):

    Disabled

    Enable PANI Header Support:

    Disabled

    Enable B2BUA Session Timer Support:

    Enabled

    Session Refresh Interval (s):

    1800

    Enable SRTP support:

    Enabled

    Enable MKI support:

    Set as required to match the MKI setting selected in the MS Teams configuration

    SRTP Key Life Time (2^):

    32

    H.225/H.245 Port Range:

    14085-15084 (default)

    RTP Port Range:

    16386-18385 (default)

    RTP Packetization Time (ms):20
    Enable multi-ports:Disabled
    Multi-port Port Range:22000 – 22999 (default)
    Prioritize Microsoft Teams: Disabled (default)This should be enabled if MS Teams client, present/exists on the LAN side of EM and if EM needs to prioritize the Voice traffic from Teams client.
    Calculate RTT:Enabled (default)
    RTCP MUX support: Disabled (default)

    Disabled – Edgemarc will operate in Direct Routing mode


  3. Configure the SIP Server Settings for the SIP trunking service parameters.


    Caption
    0Table
    1Configuring SIP Server Settings Parameters
    3Configuring SIP Server Settings


    Parameter

    Example Configuration Value

    SIP Server Address

    siptrunk.example.com

    SIP Server Port

    5060  (Verify with your SIP trunking provider which SIP port to configure).

    Note

    If the FQDN resolves to a different port for the SIP Server Address the system will use the port returned in the DNS query response.


    SIP Server Transport

    UDP

    Enable SRTP

    Disabled

    Use Custom Domain:

    Disabled

    SIP Server Domain:

    Not set

    List of SIP Servers:

    None

    Enable Multi-homed Outbound Proxy Mode:

    Disabled

    Enable Transparent Proxy Mode:

    Disabled

    Limit Outbound to listed SIP Servers:

    Disabled

    Limit Inbound to listed SIP Servers:

    Disabled

    Include UPDATE In Allow:

    Enabled

    PRACK Support:

    Enabled

    GEOLOCATION Support:

    Enabled

    Call Audit Support:

    Disabled

    Stale client time (m):

    1440 (default)

    Force Hairpinning of RTP:

    Disabled

    SDP Codec Operation:

    Allow only given codecs

    SDP Section that will be modified:

    Audio

    Codecs (comma separated list):

    PCMU,PCMA,CN,telephone-event

    Reject when No Match Codec:

    Enabled

    Strip Matched Expressions:


    SIP Use New Port On Hold Resume:

    Disabled

    Priority Number 1:

    Priority Number 2:

    Priority Number 3:

    Priority Number 4:

    Not set




  4. Click Submit to apply changes.

Configuring the B2BUA and Header Manipulation rules

This step discusses how to configure a B2BUA trunking device to the WAN side of the system for MS-Teams support. Header manipulation rules will be used to modify the headers required for interoperability to/from MS-Teams and to/from the SIP trunking provider.

  1. Choose VoIP > SIP > B2BUA from the Configuration Menu on the left-hand side.



  2. Add a B2BUA Trunking Device for the MS Teams cloud servers and click Update. Then, scroll to the bottom and click Submit.


    Caption
    0Table
    1Configuring the First B2BUA Trunk
    3Configuring the B2BUA Trunk


    Parameter

    Example Configuration Value

    Name:

    Teams1

    Arbitrary name (alpha/numeric characters only)

    Model:

    Microsoft Teams

    Address(IP/FQDN):

    sip.pstnhub.microsoft.com

    Use DNS SRV:

    Not set for MS-Teams

    Port:

    5061

    Transport:

    TLS

    SRTP:

    Mandatory

    Source FQDN:

    sbc1.rbbn.com

    (This name must be identical to the name configured as the SIP provider PSTN gateway)

    Ignore alias source:

    Disabled for most deployments

    Username:/Password:

    Not used for MS-Teams

    Authenticate Registration:

    Disabled

    SIP ICE-Support:

    None – Use None for Direct Routing deployments

    Lite – use Lite for Media-Bypass deployments.




    Caption
    0Table
    1Configuring the Second B2BUA Trunk
    3Configuring the Second B2BUA Trunk


    ParameterExample Configuration Value

    Name:

    Teams2

    Arbitrary name (alpha/numeric characters only)

    Model:

    Microsoft Teams

    Address(IP/FQDN):

    sip2.pstnhub.microsoft.com

    Use DNS SRV:

    Not set for MS-Teams

    Port:

    5061

    Transport:

    TLS

    SRTP:

    Mandatory

    Source FQDN:

    sbc1.rbbn.com

    (This name must be identical to the name configured as the SIP provider PSTN gateway)

    Ignore alias source:

    Disabled

    Username:/Password:

    Not used for MS-Teams

    Authenticate Registration:

    Disabled

    SIP ICE-Support:

    None – Use None for Direct Routing deployments

    Lite – use Lite for Media-Bypass deployments.




    Caption
    0Table
    1Configuring the Third B2BUA Trunk
    3Configuring the Third B2BUA Trunk


    ParameterExample Configuration Value

    Name:

    Teams3

    Arbitrary name (alpha/numeric characters only)

    Model:

    Microsoft Teams

    Address(IP/FQDN):

    sip3.pstnhub.microsoft.com

    Use DNS SRV:

    Not set for MS-Teams

    Port:

    5061

    Transport:

    TLS

    SRTP:

    Mandatory

    Source FQDN:

    sbc1.rbbn.com

    (This name must be identical to the name configured as the SIP provider PSTN gateway)

    Ignore alias source:

    Disabled

    Username:/Password:

    Not used for MS-Teams

     Authenticate Registration:

    Disabled

     SIP ICE-Support:

    None – Use None for Direct Routing deployments

    Lite – use Lite for Media-Bypass deployments.



  3. Create a routing group for the MS Teams servers with the Trunking Group Availability function.





    Caption
    0Table
    1Configuring the Routing Group
    3Configuring the Routing Group


    ParameterExample Configuration Value

    Group Name

    TeamsGroup

    N/A

    State

    Display Only

    Keep Alive

    Enabled

    Load Balance

    Optional

    Invite Failover

    Enabled

    Trust Enabled

    Enabled

    Trusted List

    52.112.0.0/14;52.120.0.0/14

    (note support for sip-all.pstnhub.microsoft.com has been discontinued by Microsoft.
    This FQDN should be removed if previously configured)

    Members for Group:

    TeamsGroup

    Keep Alive Interval:

    60 (default)

    Error Response:

    Not Set

    From User:

    Not Set

    To User:

    Not Set

    Backoff on No Response

    Enabled

    Regular with max. Interval:

    Enabled

    0sec (default)

    Random with max. Interval:

    N/A

    N/A

    Failover upon Invite Responses:

    503

    Fallback with auto keep alive

    Not Selected

    Fallback Interval:

    Enabled

    60(s) (default)

    *1 - When configuring Teams, the subnet masks 52.112.0.0/14 and 52.120.0.0/14 are automatically added to the trusted list. As of VOS version 16.3.1, entering sip-all.pstnhub.microsoft.com is no longer required. Existing references to the FQDN should be removed. For more information about Microsoft's deprecation of sip-all.pstnhub.microsoft.com, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments


  4. Choose VoIP > SIP > B2BUA from the Configuration Menu on the left-hand side. Header manipulation rules are used to modify the headers required for interoperability to-and-from MS Teams and to-and-from the SIP trunking provider.



  5. Scroll down to Actions and add the actions mentioned in the following steps, and associated HMR rules.
  6. The first Actions is “ToTeams”. This rule has an associated “Match” rule for calls going to Teams.
    1. Configure the parameters in the actions pane.
    2. Configure each Header Value one at a time and click Add before creating the next rule.

    3. Click Update and then click Submit to save the action.


      Info
      titleNote

      In the example given in the following table, the dialing code +1 is used in reference to the USA. Change it to the dialing code of the country of your choice. 


      Caption
      0Table
      1Configuring the ToTeams Action
      3Configuring the ToTeams Action


      Parameter

      Example Configuration Value

      Name:

      ToTeams

      Arbitrary name (alpha/numeric characters only)

      Send To:

      TeamsGroup

      Prioritize:

      Not used for MS-Teams

      Refer to Re-INVITE:

      Enabled

      Serial Hunting:

      Not used for MS-Teams

      E.164 Conversion rule:

      None

      Conversion mode:

      Add (default)

      Request-URI

      'sip:+1' + $to.uri.user + '@' +

      $env.target_domain + ':' + $env.target_port + ';user=phone'

      From

      '<sip:+1' + $from.uri.user + '@' +

      $env.target_src_domain + ':' +

      $env.target_port + ' ;user=phone>'

      To

      $to.dispname + '<sip:+1' + $to.uri.user + '@'

      + $env.target_domain + ':' + $env.target_port

      + ';user=phone>'

      Contact

      '<sip:+1' + $from.uri.user + '@' +

      $env.target_src_domain + ':' +

      $env.out_intf_port + ';transport=TLS>' +

      $contact.parameter



    1. Configure the parameters in the actions pane.
    2. Configure each Header Value one at a time and click Add before creating the next rule.

    3. Click Update and then click Submit to save the action.



      Caption
      0Table
      1Configuring the FromTeams2ServerAnonymous Action
      3Configuring the FromTeams2ServerAnonymous Action


      ParameterExample Configuration Value
      Name

      FromTeams2ServerAnonymous

      Arbitrary name (alphanumeric characters only)
      Send ToTrunking DeviceNone
      PrioritizeNot used for MS Teams
      Refer to Re-INVITEEnabled
      Serial HuntingNot used for MS Teams
      E.164 Conversion ruleNone
      Conversion modeAdd (default)


      HeaderExample Value

      Request-URI

      'sip:' + substr($request.uri.user, 2, 0) + '@' + $env.available_domain + ':' +

      $env.available_port

      From

      $from.dispname + ' <sip:' +

      $from.uri.user + '@' + $env.out_intf_host

      + ':' + $env.out_intf_port + '>'

      To

      $to.dispname + ' <sip:' + substr($to.uri.user, 2, 0) + '@' +

      $env.available_domain + ':' +

      $env.available_port + '>'

      Contact

      $from.dispname + ' <sip:' +

      $from.uri.user + '@' + $env.out_intf_host

      + ':' + $env.out_intf_port + '>' +

      $contact.parameter

      P-Asserted-Identity

      $pai?'<sip:' + substr($pai, 7, 10) + '@' +

      $env.out_intf_host + ':' +

      $env.out_intf_port + '>'

      Other

      Privacy

      'id'



      The second action is FromTeams2ServerAnonymous. This rule has an associated “Match” rule for calls with “Anonymous” in the SIP URI. For example, when a Teams caller is blocking their number, the SIP From URI will have the following format:
      From: "Anonymous"sip:anonymous@anonymous.invalid:5060.
      This rule allows anonymous calls inbound from Teams to the SIP trunking provider.

      To add a new action click anywhere in the New Entry bar.



  7. The third action will be “FromTeams2Server”, this rule will have an associated “Match” rule for calls outbound from Teams to the SIP Trunking provider for destination call routing. This example uses a “P-Asserted-Identity” header string which is common to many SIP trunking providers, please verify with your trunking provider “if” they require these SIP headers or other header requirements to interoperate with their SIP service.

    To add a new Action click anywhere in the “New Entry bar.



             


    1. Configure the parameters in the actions pane.

    2. Configure each Header Value one at a time and click Add before creating the next rule.

    3. Click Update and then click Submit to save the action.



      Caption
      0Table
      1Configuring the FromTeams2Server Action
      3Configuring the FromTeams2Server Action


      ParameterExample Configuration Value
      Name

      FromTeams2Server

      Arbitrary name (alphanumeric characters only)
      Send ToTrunking DeviceNone
      PrioritizeNot used for MS Teams
      Refer to Re-INVITEEnabled
      Serial HuntingNot used for MS Teams
      E.164 Conversion ruleNone
      Conversion modeAdd (default)


      HeaderExample Value

      Request-URI

      'sip:' + substr($request.uri.user, 2, 0) + '@'

      + $env.available_domain + ':' +

      $env.available_port

      From

      $from.dispname + ' <sip:' + substr($from.uri.user, 2, 0) + '@' +

      $env.out_intf_host + ':' + $env.out_intf_port

      + '>'

      To

      $to.dispname + ' <sip:' + substr($to.uri.user, 2, 0) + '@' +

      $env.available_domain + ':' +

      $env.available_port + '>'

      Contact

      $from.dispname + ' <sip:' + substr($from.uri.user, 2, 0) + '@' +

      $env.out_intf_host + ':' + $env.out_intf_port

      + '>' + $contact.parameter

      P-Asserted-Identity

      $pai?'<sip:' + substr($pai, 7, 10) + '@' +

      $env.out_intf_host + ':' + $env.out_intf_port

      + '>'

      History-info

      $history-info?' <sip:' + replace($history- info.uri.user, '+1', '' ) + '@' +

      $env.out_intf_host + ':' + $env.out_intf_port

      + '>;reason=unknown;counter=1' + ‘,’+$history-info#1?' <sip:' + replace($history- info#1.uri.user, '+1', '' ) + '@' +

      $env.out_intf_host + ':' + $env.out_intf_port

      + '>;reason=unknown;counter=1'



  8.  The next action will be “Teams2Analog”, this rule will have an associated “Match” rule for calls inbound from Teams to an analog line in the EdgeMarc. 

            To add a new Action click anywhere in the “New Entry bar.

           

             
             a. Configure the parameters in the actions pane.
             b. Configure each Header Value one at a time and click Add before creating the next rule.
             c. Click Update then click Submit to save the Action.

    
                        
 
              


  • Caption
    0Table
    1 Configuring the Teams2AnalogAnonymous Action
    2center


    Parameter

    Example Configuration Value

    Name:

    Teams2AnalogAnonymous

    Arbitrary name (alpha/numeric characters only)

    Send To:

    Trunking Device:

    EW_UA

    Prioritize:

    Not used for MS-Teams

    Refer to Re-INVITE:

    Enabled

    Serial Hunting:

    Not used for Skype for Business

    E.164 Conversion rule:

    None

    Conversion mode:

    Add (default)

    Header

    Example Value

    Request-URI

    'sip:' + substr($request.uri.user, 2, 0) + '@' + $env.target_host + ':' + $env.target_port

    From

    $from.uri.user +' <sip:' + substr($from.uri.user, 2, 0) + '@' + $env.out_intf_host + ':' + $env.out_intf_port + '>'

    To

    $to.dispname + ' <sip:' + substr($to.uri.user, 2, 0) + '@' + $env.target_host + ':' + $env.target_port + '>'

    Contact

    $from.dispname + ' <sip:' + substr($from.uri.user, 2, 0) + '@' +

    $env.out_intf_host + ':' + $env.out_intf_port

    + '>' + $contact.parameter



...