Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 3

changes.mady.by.user Ribbon Communications

Saved on

Key

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

Add_workflow_for_techpubs
REV4REV2
AUTH2UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a0c85bb25531015bc4122a4f0003, userName='null'}
JIRAIDAUTHSYM-2772028938
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7f0006a8a00a0c85bb25531015bc4122a4f0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a0c85bb25531015bc4122a4f0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c857f0393d01581c58d24000058a00a0c8601a1bc701602339d1190006, userName='null'}
UserResourceIdentifier{userKey=8a00a0c856ed5c6701572cb23680000b, userName='null'}REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f08a00a0c8601a1bc701602339d1190006, userName='null'}UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca2f03d1, userName='null'}

Section


Column


Panel

In this section:

Table of Contents
maxLevel3



Column


Info
titleAbout this Page

This document describes how to resolve integration issues that can occur with the Microsoft Teams Direct Routing interface for connecting the Ribbon SBC Edge 1000/2000 to Microsoft Teams.


Tip
titleRelated Articles



...

  1. Enable "ForwardPAI" in CsOnlinePSTNGateway. Teams Direct Routing adds P-Asserted-Identy header and Privacy:id in INVITE for transfer.
  2. On Teams Direct Routing SIP Profile, leave the "Calling Info Source" as "RFC Standard" (by default).

  3. For ISDN: Add a transformation table entry to set the Calling Presentation "Allowed",  otherwise the called party sees the calling number as anonymous.

Pagebreak

Call drop after 15 sec of call

If Early Media is enabled, disable Early Media on the Teams Direct Routing SIP Signaling Group. This is a known Direct Routing issue until a fix is provided from Microsoft. 

...

...

0Figure
1SIP Signaling Group - Early Media

...

 Image Removed

Call forwarding is failing for Microsoft Teams Client

...

  1. On the laptop running the Teams Client:
    1. Access  http://www.myipaddress.com/what-is-my-ip-address/ and take note of the Teams Client Public IP.

    2. Start a Command terminal, type the following command, and take note of the Teams Client internal IPv4 Address and Subnet Mask.


      Code Block
      ipconfig


  2. Connect Office 365 Tenant via Powershell.

    1. Verify the Public IP address displayed earlier is listed when you type the following Office 365 Powershell command:

      Code Block
      Get-CsTenantTrustedIPAddress


    2. Verify the internal IPv4 Address and Subnet Mask displayed earlier is listed when you type the following Office 365 Powershell command:

      Code Block
      Get-CsTenantNetworkSite


Pagebreak

Unable To Get Local Issuer Certificate


Warning
titleWarning

Common Encryption Certificate Issues Arise from Missing Root Certificates


  • Did you onlyinstall the CA-signed SBC certificate, along with the intermediate certificate(s) sent by your issuing CA?
  • Did you get the following error message from the SBC?
    Image Added

If so, the likely reason is a missing CA Root Certificate. The SBC does not have any pre-installed CA root X.509 certificates, unlike typical browsers found on your PC. Ensure the entire certificate chain of trust is installed on the SBC, including the root certificate. Acquire the CA root certificate as follows:

  1. Contact your system administrator or certificate vendor to acquire the root, and any further missing intermediate certificate(s) to provision the entire certificate chain of trust within the SBC;

  2. Load the root certificate, along with the intermediate and SBC certificates, according to Importing Trusted Root CA Certificates.

    Info
    titleNote

    Root certificates are easily acquired from the certificate authorities. For example, the root certificate for the GoDaddy Class 2 Certification Authority may be found at https://ssl-ccp.godaddy.com/repository?origin=CALLISTO . For more information about root certificates, intermediate certificates, and the SBC server (“leaf”) certificates, refer to this tutorial.


For other certificate-related errors, refer to Common Troubleshooting Issues with Certificates in SBC Edge.