Direct Routing keeps sending Anonymous

Problem While i was configuring an Audiocdes SBC with Direct Routing setup and started testing, we faced the issue that every call outgoing is presenting Anonymous as caller ID. When looking up the SDP invite i saw the parameter Privacy showing up. Solution After some digging, i found that the Privacy ID is added automatically when you enable the option -forwardPAI $true (P-Asserted-Identity) within the Set-CsOnlinePSTNGateway cmdlet. Because i don’t want to remove the PAI, i created the following manipulation rule in the Audiocodes SBC to remove the Privacy ID. Continue reading

Using Reverse Number Lookup in Microsoft Teams

What is Reverse Number Lookup (RNL) When you receive calls in your Teams client Reverse Number Lookup (RNL) will show the displayname instead of the actual phone number. With RNL the system converts the number that is calling you to a name configured in your outlook contact or even Azure Active Directory. The following order will be used to check and the last one will always override: SIP Invite From Header Azure Active Directory Outlook contacts Teams contacts Requirements Exchange The callee, in your tenant, needs to have a Exchange Online mailbox. Continue reading

Setup Direct Routing with Microsoft teams

Direct Routing lets you connect a supported, customer-provided Session Border Controller (SBC) to the Microsoft Phone System. With this capability you can configure on-premises PSTN (bring your own sip trunk, BYOT) connectivity with your Microsoft Teams client. There are a couple of certified SBC vendors you can use to setup Direct Routing. Audiocodes Ribbon AnyNode Thinktel What do you need? In order to setup Direct routing you will need to have some prerequisites: Continue reading

No RingBack when using Microsoft Teams Direct Routing

Recently we have decomissioned our Microsoft Cloud Connector Edition and migrated most of our telephony users to Microsoft Teams with Direct Routing. One big issue we faced was that when a external caller called us by PSTN, they only heard one RingBack tone followed by deadly silence till someone picked up or landed in Azure VoiceMail. Thanks to my friend Goos Stuut, working at our local distri for Audiocodes we found out what was happening and we solved this issue. Continue reading