Caller ID and Direct Routing

%3CLINGO-SUB%20id%3D%22lingo-sub-222812%22%20slang%3D%22en-US%22%3ECaller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222812%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20setup%20Direct%20Routing%20with%20an%20AudioCodes%20virtual%20SBC.%26nbsp%3B%20The%20caller%20ID%20information%20is%20currently%20not%20passing%20to%20Microsoft%20Teams.%26nbsp%3B%20Is%20this%20a%20known%20issue%20or%20is%20there%20a%20configuration%20piece%20missing%3F%26nbsp%3B%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-222812%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDirect%20Routing%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390179%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390179%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F237681%22%20target%3D%22_blank%22%3E%40Daniel%20Jelinek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThat%20feature%20is%20definitely%20on%20the%20engeineering%20road%20map.%20Again%20no%20specific%20ETA%20to%20share.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390103%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390103%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20that's%20exactly%20what%20i%20like%20to%20do.%20When%20I%20search%20in%20Teams%20for%20contacts%20i%20find%20only%20my%20outlook%20contacts.%20i%20like%20to%20search%20in%20Azure%20AD%20for%20%22company%20contacts%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390091%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390091%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F237681%22%20target%3D%22_blank%22%3E%40Daniel%20Jelinek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20are%20welcome.%20I%20could%20never%20communicate%20a%20date%20until%20it%20appears%20on%20official%20roadmap%20because%20although%20engineering%20has%20specific%20targets%20unexpected%20roadblocks%20can%20occur%20to%20change%20those%20targets.%20I%20think%20its%20safe%20to%20say%20that%20soon%20indicates%20this%20year%20and%20earlier%20than%20later.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EBy%20global%20contacts%20available%20to%20Teams%20users%2C%20do%20you%20mean%20Azure%20AD%20contacts%2C%20as%20opposed%20to%20user's%20own%20mailbox%20contacts%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390038%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390038%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3BThanks%20for%20your%20really%20fast%20reply.%20But%20can%20you%20tell%20me%20if%20this%20is%20in%20a%20timeframe%20%22this%20year%22%20or%20even%20better%20Q2%2FQ3%202019%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20there%20any%20other%20options%20to%20make%20global%20contacts%20available%20to%20teams%20phone%20users%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390037%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390037%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20have%20any%20specific%20ETA%20to%20share%20at%20this%20time%20but%20engineering%20is%20very%20much%20aware%20of%20the%20importance%20of%20this%20feature%20and%20are%20working%20on%20it.%20Will%20be%20coming%20relatively%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390034%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390034%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eany%20news%20regarding%20RNL%20and%20even%20Number%20Lookup%20in%20Azure%20AD%20from%20Teams%3F%3C%2FP%3E%3CP%3EWaiting%20for%20this...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389416%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389416%22%20slang%3D%22en-US%22%3EHi%20Ben%2C%20I%20don't%20have%20any%20specific%20ETA%20to%20share%20at%20this%20time%20but%20engineering%20is%20very%20much%20aware%20of%20the%20importance%20of%20this%20feature%20and%20are%20working%20on%20it.%20Will%20be%20coming%20relatively%20soon.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-388699%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388699%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%26nbsp%3B%26nbsp%3BAny%20update%20on%20this%3F%26nbsp%3B%20Teams%20is%20not%20a%20viable%20phone%20solution%20until%20it%20is%20able%20to%20simple%20caller%20ID.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364791%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364791%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EAny%20news%2C%20regarding%20RNL%20against%20Azure%20AD%3F%20We've%20been%20waiting%20far%20too%20long%20for%20this%20basic%20functionality.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-359894%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359894%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F175497%22%20target%3D%22_blank%22%3E%40Andrew%20Schwalbe%3C%2FA%3Ethis%20is%20still%20an%20issue%20for%20us.%26nbsp%3B%20We%20want%20to%20move%20to%20Teams%2C%20but%20this%20issue%20is%20completely%20blocking%20us%20from%20moving%20users%20to%20Teams%20from%20our%2011%20year%20old%20PBX%20that%20has%20this%20functionality.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-358536%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-358536%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20heard%20anything%20about%20getting%20Caller%20ID%20working%20with%20Teams%20yet%3F%26nbsp%3B%20We've%20been%20using%20Skype%20for%20Business%20online%20with%20Microsoft%20PSTN%20for%20several%20years%20and%20are%20ready%20to%20migrate%20to%20teams%2C%20but%20as%20someone%20else%20has%20mentioned%2C%20Caller%20ID%20is%20a%20must%20have%20to%20gain%20user%20acceptance.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325567%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325567%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%20is%20there%20any%20updates%20that%20you%20can%20provide%20in%20regards%20to%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324866%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324866%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20with%20Teams%20Direct%20Routing%20but%20the%20caller%20name%20display%20is%20not%20shown%20when%20contact%20is%20existing.%3CBR%20%2F%3EWill%20the%20Caller%20Name%20Display%20feasible%20in%20the%20coming%20future%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%40%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20do%20you%20mean%20by%20Caller%20ID%3F%20Are%20you%20referring%20to%20the%20Calling%20Line%20Identity%20phone%20number%20or%20Display%20Name%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20Direct%20Routing%20does%20support%20sending%20the%20number%20of%20the%20user%20who%20placed%20the%20call%20unless%20that%20number%20was%20set%20to%20appear%20as%20anonymous%20or%20as%20another%20service%20number%20by%20tenant%20administrator.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20currently%20missing%20and%20work%20underway%20to%20resolve%20is%20Calling%20Name%20Display%20included%20in%20the%20From%20field.%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292130%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292130%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20news%20on%20RNL%20against%20Azure%20AD%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279403%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279403%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%20I%20don't%20have%20an%20ETA%20for%20either%20to%20share%20at%20this%20time.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279124%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279124%22%20slang%3D%22en-US%22%3EIs%20there%20a%20timeline%20on%20when%20we%20can%20expect%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278574%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278574%22%20slang%3D%22en-US%22%3E%3CP%3EGot%20it.%26nbsp%3BRNL%20against%20Azure%20AD%20is%20planned.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278563%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278563%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20I%20mean%20by%20Exchange%20is%20the%20Global%20Address%20List.%26nbsp%3B%20It%20currently%20will%20only%20resolve%20the%20name%20if%20I%20have%20added%20the%20user%20to%20my%20personal%20contacts%20in%20Outlook.%26nbsp%3B%20It%20will%20not%20resolve%20all%20people%20in%20the%20GAL.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278558%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278558%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20do%20you%20mean%20against%20Exchange%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECurrently%20RNL%20works%20against%20contacts%20stored%20by%20user%20in%20Teams%20A-Z%20contacts%20in%20Calls%20tab.%20These%20contacts%20will%20be%20synchronized%20from%20user's%20Exchange%20mailbox%20contacts%20store%20if%20the%20user%20mailbox%20is%20home%20online%20for%20now%20until%20support%20for%20contacts%20are%20available%20in%20on%20premise%20mailbox%3B%20see%20here%20for%20more%20about%20feature%20capabilities%20with%20Teams%20and%20Exchange%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fexchange-teams-interact%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EHow%20Exchange%20and%20Microsoft%20Teams%20interact%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20do%20have%20plans%20for%20support%20inbound%20CNAM%20from%20SBC%20to%20Teams.%20No%20ETA%20on%20this%3B%20under%20investigation.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278470%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278470%22%20slang%3D%22en-US%22%3E%3CP%3EOurs%20is%20working%20for%20looking%20up%20against%20a%20user%20who%20has%20contacts%20saved%20in%20their%20Outlook.%26nbsp%3B%20It%20does%20not%20however%20lookup%20against%20Exchange.%26nbsp%3B%20Will%20it%20be%20able%20to%20lookup%20against%20Exchange%20in%20the%20future%3F%26nbsp%3B%20When%20will%20caller%20ID%20passed%20by%20PSTN%20start%20working%20as%20well%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278467%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278467%22%20slang%3D%22en-US%22%3E%3CP%3EExcellent.%20Thanks%20for%20sharing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278002%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278002%22%20slang%3D%22en-US%22%3EI%20can%20see%20it!%20%3Athumbs_up%3A%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-277870%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-277870%22%20slang%3D%22en-US%22%3E%3CP%3EGetting%20closer.%20Currently%20testing%20reverse%20number%20lookup%20against%20recipients%20contacts.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-277824%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-277824%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20news%20on%20this%3F%20This%20is%20really%20the%20most%20annoying%20point%20in%20our%20POC%20with%20teams.%20You%20want%20to%20switch%20to%20a%20modern%20tool%20and%20parity%20with%20S4B%20is%20promised.%20And%20then%20I%20only%20see%20the%20phone%20number%20and%20have%20to%20find%20out%20who%20this%20number%20belongs%20to%2C%20with%20every%20missed%20call%20first.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-255023%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-255023%22%20slang%3D%22en-US%22%3EUnderstood%20Ben.%20I%20don't%20have%20any%20ETA%20for%20this%20yet%20but%20do%20know%20it's%20actively%20being%20worked%20on%20and%20the%20priority%20is%20understood.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251914%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251914%22%20slang%3D%22en-US%22%3E%3CP%3Eany%20link%20to%20feature%20about%20teams%20client%20to%20lookup%20mailbox%20contacts%20for%20incoming%20calls%20regarding%20the%20incoming%20phone%20numbers%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251770%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251770%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20update%20on%20progress%20of%20this%3F%26nbsp%3B%20Until%20Teams%20is%20capable%20of%20displaying%20caller%20name%20there%20is%20no%20way%20we%20would%20get%20any%20buy%20in%20from%20our%20general%20users.%26nbsp%3B%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227865%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227865%22%20slang%3D%22en-US%22%3EThese%20are%20mandatory%20functions%20to%20gain%20user%20acceptance.%20Please%20increase%20the%20priority%20level.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-226165%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226165%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20the%20great%20feedback.%20We%20do%20have%20plans%20to%20implement%20both%20items%2C%20passing%20name%20to%20Teams%20when%20available%20in%20the%20inbound%20invite%20From%20field%20as%20well%20as%20RNL%20against%20Exchange%20and%20Contacts.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20don't%20have%20an%20ETA%20for%20this%20changes%20but%20we%20do%20understand%20the%20importance%20of%20these%20features.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-225135%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-225135%22%20slang%3D%22en-US%22%3E%3CP%3EI%20meant%20if%20I%20call%20any%20other%20PSTN%20from%20my%20cell%20phone%20it%20shows%20my%20name%20and%20my%20number.%26nbsp%3B%20In%20Microsoft%20Teams%20with%20Direct%20Routing%20it%20is%20showing%20only%20the%20phone%20number%20and%20not%20passing%20the%20name%20information%20to%20the%20Teams%20client.%26nbsp%3B%20In%20working%20with%20AudioCodes%20they%20said%20that%20the%20SBC%20is%20passing%20that%20information%20to%20Microsoft.%26nbsp%3B%20I%20get%20bombarded%20my%20sales%20calls%20so%20I%20tend%20to%20screen%20my%20calls%20using%20the%20names%20that%20come%20in%20on%20calls%20to%20determine%20whether%20I%20want%20to%20answer%20the%20call%20or%20not.%26nbsp%3B%20Moving%20to%20Microsoft%20Teams%20I%20have%20now%20lost%20that%20ability.%26nbsp%3B%20It%20also%20doesn't%20seem%20to%20have%20the%20ability%20to%20look%20at%20Contacts%20or%20Exchange%20to%20look%20up%20any%20names%20either.%26nbsp%3B%20Once%20they%20have%20these%20little%20features%20ironed%20out%20it%20will%20be%20much%20more%20usable%20as%20an%20actual%20phone%20client%20than%20it%20is%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-224914%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-224914%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20do%20you%20mean%20by%20Caller%20ID%3F%20Are%20you%20referring%20to%20the%20Calling%20Line%20Identity%20phone%20number%20or%20Display%20Name%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECurrently%20Direct%20Routing%20does%20support%20sending%20the%20number%20of%20the%20user%20who%20placed%20the%20call%20unless%20that%20number%20was%20set%20to%20appear%20as%20anonymous%20or%20as%20another%20service%20number%20by%20tenant%20administrator.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20is%20currently%20missing%20and%20work%20underway%20to%20resolve%20is%20Calling%20Name%20Display%20included%20in%20the%20From%20field.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-222888%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222888%22%20slang%3D%22en-US%22%3EIt%20doesn't%20work%20even%20with%20Microsoft's%20PSTN%20call%20in.%20Client%20doesn't%20quiet%20support%20it%20yet.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552227%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552227%22%20slang%3D%22en-US%22%3EHi%20Carolyn%2C%20are%20there%20any%20updates%20that%20you%20can%20share%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-643921%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-643921%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20my%20case%2C%20the%20on-prem%20(direct%20routing)%20number%20is%20assigned%20to%20user%2C%20caller%20id%20is%20visible.%3C%2FP%3E%3CP%3EBut%20if%20it%20is%20assigned%20to%20call%20queue%2C%20then%20it%20says%20%22anonymous%22%2C%20after%20answer%2Ftakeover%20the%20call%2C%20it%20is%20again%20visible.%20Using%20Microsoft%20Teams%20-%20Windows%2010%20desktop%20app.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-668768%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-668768%22%20slang%3D%22en-US%22%3EAny%20update%20that%20you%20can%20provide%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-686815%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-686815%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F280793%22%20target%3D%22_blank%22%3E%40hkusulja%3C%2FA%3E%26nbsp%3BWe%20also%20see%20the%20same%20thing%20-%20using%20Ribbon%20SBC.%26nbsp%3B%20Caller%20ID%20is%20showing%20as%20anonymous%20when%20passed%20through%20to%20Call%20Queue%20with%20direct%20routing.%26nbsp%3B%20%26nbsp%3BCan%20you%20confirm%20which%20SBC%20you%20are%20using%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-688872%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-688872%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F358833%22%20target%3D%22_blank%22%3E%40GlennL%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F15379%22%20target%3D%22_blank%22%3E%40Ben%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20not%20seeing%20in%20this%20in%20testing.%20I%20have%20Direct%20Routing%20%23%20assigned%20to%20AA%2FCall%20Queues.%20For%20Call%20Queues%2C%20when%20Agent's%20pick%20up%20they%20see%20both%20the%20Call%20Queue%20name%20and%20the%20Caller's%20Number%2C%20or%20Name%20if%20the%20Agent%20has%20a%20contact%20record%20for%20the%20caller%20in%20their%20Teams%20client.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-688896%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-688896%22%20slang%3D%22en-US%22%3EThe%20original%20question%20had%20nothing%20to%20do%20with%20AA%20or%20call%20queues.%20We%20are%20still%20not%20seeing%20any%20caller%20identifications%20passed%20from%20any%20PSTN%20calls%20or%20exchange%20lookup%20for%20any%20calls%20on%20a%20direct%20call.%20Please%20let%20us%20know%20timeline%20on%20that%20and%20not%20random%20posts%20having%20nothing%20to%20do%20with%20the%20original%20post%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-717399%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-717399%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%2B1%20to%20this%20issue.%20We%20moved%20a%20few%20people%20from%20the%20legacy%20phone%20system%20to%20Teams.%20They%20like%20everything%20except%20that%20they%20don't%20know%20who%20is%20calling.%20It's%20a%20non-starter%20for%20rolling%20this%20out%20company%20wide.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737212%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737212%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228637%22%20target%3D%22_blank%22%3E%40Kade%20Cole%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20sharing.%20Indeed%2C%20as%20a%20best%20practice%20you%20should%20use%20globally%20unique%20numbers%20for%20Direct%20Routing%20in%20all%20URI's.%20Certainly%20for%20successfully%20matching%20for%20Call%20Blocking%2C%20or%20for%20successful%20Call%20Escalation%2C%20the%20From%20URI%20should%20be%20a%20globally%20unique%20number.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20only%20place%20I%20see%20it%20being%20preferable%20to%20use%20a%20non%20globally%20unique%20%23%20is%20outbound%20from%20Teams%20-%26gt%3B%20SBC%20where%20you%20want%20the%20SBC%20to%20pick%20up%20a%20short%20digit%20%23%20to%20route%20to%20an%20on%20premise%20device%20and%20not%20need%20to%20manipulate%20the%20%23%202%20times.%20From%20teams%20and%20then%20again%20from%20SBC%20to%20on%20premise%20device.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20inbound%20to%20Teams%2C%20all%20URI's%2C%20both%20To%2C%20From%2C%20Contact%20should%20be%20Globally%20unique%20%23's.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737761%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737761%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20SBC%20sends%20phone%20number%20in%26nbsp%3BE.164%20format%2C%20then%20it%20is%20ok%20inside%20Microsoft%20Teams..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737165%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737165%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F280793%22%20target%3D%22_blank%22%3E%40hkusulja%3C%2FA%3EI%20was%20able%20to%20somewhat%20solve%20this%20by%20making%20sure%20that%20calls%20from%20the%20SBC%20through%20direct%20routing%20are%20using%2010%20digit%20numbers%20in%20the%20SIP%20FROM%20field.%20I%20at%20least%20now%20get%20calls%20to%20the%20call%20queue%20showing%20the%20full%2010%20digit%20number%20and%20not%20%22anonymous%22.%20Hope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-755334%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-755334%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIts%20coming%20up%20on%20a%20year%20since%20you%20said%20this%3B%20%22%3CSPAN%3E%3CEM%3EWhat%20is%20currently%20missing%20and%20work%20underway%20to%20resolve%20is%20Calling%20Name%20Display%20included%20in%20the%20From%20field.%3C%2FEM%3E%20%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20there%20any%20update%20on%20when%20this%20will%20manifest%20results%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772157%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772157%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BThis%20is%20also%20an%20issue%20for%20my%20organization.%20I%20can%20see%20on%20my%20Audiocodes%20SBC%20that%20the%20caller%20name%20CNAM%20info%20is%20being%20passed%20to%20MS%20Teams%20in%20the%20invite.%20Teams%20doesn't%20do%20anything%20with%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772488%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772488%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F381635%22%20target%3D%22_blank%22%3E%40BrendanORegan%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F199017%22%20target%3D%22_blank%22%3E%40David%20Heighton%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20in%20testing%20phase%20now%20for%20CNAM%20delivery%20to%20Teams%20client%20and%20will%20be%20in%20test%20phase%20for%20reverse%20number%20lookup%20against%20Azure%20AD%2FExchange%20very%20shortly.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECarolyn%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-797550%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-797550%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20any%20further%20progress%20been%20made%20regarding%20CNAM%20delivery.%20This%20is%20the%20only%20thing%20my%20organization%20is%20waiting%20on%20for%20a%20mass%20rollout.%20The%20last%20update%20on%207%2F24%20indicated%20that%20it%20is%20in%20testing%20phase%2C%20how%20long%20should%20we%20expect%20that%20to%20be%20the%20case%3F%20Thanks!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-797570%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-797570%22%20slang%3D%22en-US%22%3ESame%20here.%20Once%20available%20I'll%20be%20ready%20to%20cutover%20our%20entire%20org%20from%20Skype%20for%20Business%20Online.%20People%20at%20my%20org%20are%20ready%20to%20adopt%20Teams%20and%20have%20started%20doing%20so%20already%20for%20everything%20except%20calling.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-806778%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-806778%22%20slang%3D%22en-US%22%3EAny%20update%20on%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-806788%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-806788%22%20slang%3D%22en-US%22%3EHow%20is%20the%20testing%20going%2C%20is%20there%20any%20update%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824442%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824442%22%20slang%3D%22en-US%22%3EOur%20company%20also%20is%20needing%20Name%20%26amp%3B%20AD%20lookup.%20Any%20status%20update%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826679%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826679%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20a%20status%20about%20this%20feature%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20starting%20our%20POC%20on%20Teams%20Telephony%20and%20this%20feature%20is%20something%20we%20are%20waiting%20for.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20a%20lot%20for%20the%20update%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBye%2C%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-828854%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-828854%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Carolyn%20(can't%20tag%20you%20for%20some%20reason)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20regards%20to%20the%20Display%20Name%20support%20for%20inbound%20calls%20with%20direct%20routing%20(ie%3A%20presenting%20the%20Display%20Name%20information%20as%20providedin%20the%20FROM%20Header%20of%20the%20SIP%20Invite).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20roadmap%20ID%20or%20a%20UserVoice%20thread%20we%20can%20follow%20for%20this%20feature%20request%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20number%20of%20customers%20who%20are%20hesitant%20to%20migrate%20from%20Skype%20for%20Business%20into%20Teams%20due%20to%20this%20missing%20feature.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-828879%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-828879%22%20slang%3D%22en-US%22%3EI%20believe%20this%20is%20the%20roadmap%20link%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D53937%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D53937%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-837804%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-837804%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20there%20any%20updates%20on%20the%20availability%3F%20We'd%20need%20this%20feature%20so%20much.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856567%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856567%22%20slang%3D%22en-US%22%3E%3CP%3Eaccording%20to%20the%20roadmap%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131905i753738A2400C60A1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22CallerID.jpg%22%20title%3D%22CallerID.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-863647%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-863647%22%20slang%3D%22en-US%22%3EHi%20Carolyn%2C%20is%20there%20any%20update%20you%20can%20provide%20on%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-867461%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867461%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20started%20seeing%20Telco%20provided%20lookup%20information%20in%20our%20tenant%20this%20morning.%26nbsp%3B%20We%20are%20not%20seeing%20the%20%3CSPAN%3EPSTN%20Callers%20Name%20based%20on%20Azure%20Active%20Directory%20data%20working%20as%20of%20yet%20though.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870354%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870354%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3BDid%20you%20have%20to%20make%20any%20changes%20to%20see%20the%20CNAM%20info%3F%20Our%20Ribbon%20SBCs%20are%20passing%20CNAM%20from%20Mitel%20to%20Microsoft%20just%20waiting%20for%20it%20to%20be%20seen.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870432%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870432%22%20slang%3D%22en-US%22%3EWe%20did%20not%20have%20to%20make%20any%20changes.%20However%20it%20does%20not%20keep%20the%20information%20for%20the%20call%20history%20area%20though.%20It%20only%20shows%20on%20the%20notification%20banner.%20It%20is%20still%20not%20doing%20Exchange%20lookup%20either%20so%20all%20of%20our%20%22internal%22%20calls%20show%20the%20CNAM%20information%20of%20our%20company%20name%20for%20all%20of%20those%20calls.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870548%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870548%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here.%20Only%20for%20%22internal%22%20calls%2C%20only%20in%20notification%20banner.%20Nothing%20in%20calls%20history.%20And%20not%20on%20mobile%2C%20desktop%20only.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-871922%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871922%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20second%20part%20for%20Azure%20AD%20lookup%20is%20due%20this%20month%20as%20well.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20class%3D%22align-cell%22%3E%0A%3CP%20class%3D%22c-paragraph-3%20x-weight-semibold%22%3EMicrosoft%20Teams%20-%20Reverse%20Number%20Lookup%26nbsp%3B%3CSPAN%3ESeptember%20CY2019%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3CP%20class%3D%22c-paragraph-3%20x-weight-semibold%22%3EDisplay%20PSTN%20Callers%20Name%20based%20on%20Azure%20Active%20Directory%20data%20and%2For%20Telco%20provided%20display%20name%3C%2FP%3E%0A%3CUL%20class%3D%22c-list%20f-bare%20f-lean%20data-list%22%3E%0A%3CLI%3EFeatured%20ID%3A%2053937%3C%2FLI%3E%0A%3CLI%3EAdded%20to%20Roadmap%3A%207%2F30%2F2019%3C%2FLI%3E%0A%3CLI%3ELast%20Modified%3A%209%2F3%2F2019%3C%2FLI%3E%0A%3CLI%3ETags%3A%20O365%2C%20Microsoft%20Teams%2C%20All%20environments%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-872169%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-872169%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F29245%22%20target%3D%22_blank%22%3E%40Guido%20Peter%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20your%20Teams%20Desktop%20Client%20version%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20got%20%3A%26nbsp%3B%3CSPAN%3E1.2.00.24753%20(64%20bits)%20and%20I%20can't%20see%20this%20information%20in%20the%20ribbon%20.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%2C%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-874317%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-874317%22%20slang%3D%22en-US%22%3EI%20am%20on%201.2.00.24753%20(64-bit).%20It%20was%20last%20updated%20on%209%2F20%2F19%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-875519%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-875519%22%20slang%3D%22en-US%22%3EI'm%20seeing%20the%20caller%20ID%20information%20being%20passed%20from%20both%20Telco%20database%20and%20Azure%20AD%20into%20MS%20Teams%20for%20inbound%20calls.%20As%20others%20have%20mentioned%2C%20the%20CID%20data%20is%20only%20being%20passed%20in%20the%20notification%20ribbon.%20It%20doesn't%20make%20it%20into%20the%20history%20area.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-879587%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-879587%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20checking%20out%20Teams%20with%20Direct%20routing%20(Audiocodes)%20through%20a%20partner.%3C%2FP%3E%3CP%3EWe%20notice%20that%20we%20have%20caller%20ID%20(also%20when%20receiving%20a%20call%20through%20AutoAttendant%20and%2For%20Call%20queueus)%20on%20the%20windows%2010%20client%20and%20would%20like%20to%20see%20the%20Azure%20AD%20lookup.%3C%2FP%3E%3CP%3EBut%20when%20we%20use%20the%20MS%20Teams%20App%20on%20iPhone%20or%20Android%20we%20don't%20get%20the%20caller%20ID.%3C%2FP%3E%3CP%3EThen%20it%20shown%20%22%3CEM%3ECall%20Queue%3C%2FEM%3E%22%20calling%20for%20%22%3CEM%3ECall%20Queue%3C%2FEM%3E%22%26nbsp%3B%20where%20Call%20queue%20is%20the%20configured%20resource%20account.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20better%20then%20the%20Skype%20for%20Business%20client%20which%20just%20shows%20the%20inbound%20number%20but%20not%20for%20with%20queue%20they%20are%20calling%20but%26nbsp%3B%3CEM%3ECallerID%26nbsp%3B%3C%2FEM%3Ecalling%20for%26nbsp%3B%3CEM%3ECall%20Queue%3C%2FEM%3E%20would%20be%20the%20way%20to%20go%20from%20my%20point%20of%20view.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-898601%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898601%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20information%20when%20this%20is%20rolled%20out%20to%20germany%20%2F%20Europe%3F%3C%2FP%3E%3CP%3EAnd%20in%20which%20format%20do%20we%20have%20to%20put%20the%20number%20in%20Azure%20AD%3F%20E.164%20or%20is%20there%20any%20kind%20of%20normalization%20done%2C%20when%20the%20format%20is%20different%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-927416%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-927416%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F237681%22%20target%3D%22_blank%22%3E%40Daniel%20Jelinek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENumber%20matching%20will%20be%20based%20on%20what%20is%20delivered%20against%20what%20is%20stored.%20So%20if%20in%20Azure%20AD%20the%20phone%20number%20is%20E.164%20and%20that%20is%20what%20is%20delivered%20there%20will%20be%20a%20match.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-933856%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-933856%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3Eok%2C%20it's%20working%20for%20the%20Toast%20popup%20now%2C%20but%20not%20in%20call%20history%20and%20activity%20feed.%20Is%20this%20planned%20to%20change%20also%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-939835%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-939835%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F237681%22%20target%3D%22_blank%22%3E%40Daniel%20Jelinek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExcellent.%20I'm%20not%20sure%20on%20status%20for%20the%20remaining%20work%20to%20show%20RNL%20display%20in%20activity%2Fcall%20history.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-942184%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-942184%22%20slang%3D%22en-US%22%3E%3CP%3ECome%20on%20Carolyn%2C%20these%20are%20just%20basic%20features%20that%20we%20still%20miss.%20For%20almost%20a%20year%2C%20Microsoft%20has%20been%20telling%20us%20about%20parity%20to%20SfB.%20Parity%3F%20Yes%2C%20we%20can%20make%20calls%20with%20teams%2C%20but%20without%20any%20comfort.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere's%20just%20one%20exception%2C%20internally%20from%20Teams%20to%20Teams.%20As%20soon%20as%20you%20have%20to%20call%20external%20contacts%2C%20it%20becomes%20difficult%20and%20uncomfortable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20almost%20a%20year%2C%20we%20can%20finally%20see%20which%20external%20contact%20is%20calling%20us.%20But%20only%20in%20the%20Toaster%20PopUp%20but%20still%20not%20in%20the%20calls%20history%20and%20also%20not%20in%20the%20activity%20list.%20I%20still%20don't%20see%20it%20on%20mobile%20devices%20and%20also%20not%20on%20IP%20phones%20like%20Audiocodes%20C450HD.%3C%2FP%3E%3CP%3ESo%20if%20I%20missed%20a%20call%2C%20I%20just%20see%20a%20number.%20I%20don't%20know%20which%20customer%20or%20partner%20called%20me.%20Should%20I%20call%20back%20and%20ask%2C%20hello%20which%20customer%20are%20you%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20if%20I'm%20looking%20for%20a%20contact%2C%20I%20still%20don't%20have%20the%20possibility%20to%20do%20this%20in%20teams.%20I%20always%20only%20see%20the%20personal%20contacts%20I%20have%20saved.%20How%20do%20you%20actually%20make%20calls%20at%20Microsoft%3F%20Do%20you%20only%20call%20each%20other%20internally%20or%20do%20you%20also%20communicate%20with%20the%20outside%20world%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20call%20an%20external%20contact%20on%20a%20Teams-certified%20device%20like%20the%20Audicodes%20C450HD%3F%20I%20search%20in%20any%20external%20directory%20and%20then%20type%20in%20the%20number.%20Come%20on%2C%20we%20are%20soon%20in%20the%20year%202020!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20simply%20can't%20be%20that%20everything%20only%20works%20with%20saved%20contacts.%20We%20have%2015'000%20contacts%20in%20our%20directory.%20But%20it%20has%20people%20here%20in%20the%20community%20who%20have%2080'000%20or%20more.%20And%20even%20if%20the%20user%20doesn't%20need%20them%20all%2C%20you%20don't%20want%20to%20save%20them%20all%2C%20just%20to%20have%20the%20RNL%20and%20the%20comfort%20to%20search%20somebody.%20But%20I%20want%20everyone%20to%20be%20able%20to%20search%20and%20then%20call.%20And%20that%20must%20be%20possible%20in%20teams%20and%20not%20in%20any%20other%20directory.%20And%20I%20am%20sure%20I%20am%20not%20the%20only%20one%2C%20who%20is%20missing%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20want%20to%20be%20unfriendly.%20But%20we%20are%20forced%20here%20to%20replace%20our%20PBX.%20The%20people%20we've%20had%20in%20the%20test%20group%20for%20over%20a%20year%20are%20slowly%20getting%20annoyed.%20I%20put%20them%20off%20from%20week%20to%20week%20with%20your%20statements.%20But%20slowly%20displeasure%20comes%20up%20and%20people%20are%20thinking%20about%20quitting.%3C%2FP%3E%3CP%3EWe%20got%20a%20lot%20of%20nice%20%22gimmick%22%20features%20like%20background%20blur%20etc..%20Regarding%20calls%2C%20we%20are%20still%20in%20the%20Stone%20Age%20or%20shortly%20after.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20report%20from%20the%20real%20world.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3CBR%20%2F%3EGuido%20Peter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-942202%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-942202%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F29245%22%20target%3D%22_blank%22%3E%40Guido%20Peter%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Peter%2C%20you're%20speaking%20out%20of%20my%20mind....%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-942194%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-942194%22%20slang%3D%22en-US%22%3E%3CP%3ECome%20on%20Carolyn%2C%20these%20are%20just%20basic%20features%20that%20we%20still%20miss.%20For%20almost%20a%20year%2C%20Microsoft%20has%20been%20telling%20us%20about%20parity%20to%20SfB.%20Parity%3F%20Yes%2C%20we%20can%20make%20calls%20with%20teams%2C%20but%20without%20any%20comfort.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20almost%20a%20year%2C%20we%20can%20finally%20see%20which%20external%20contact%20is%20calling%20us.%20But%20only%20in%20the%20Toaster%20PopUp%20but%20still%20not%20in%20the%20call%20list%20and%20also%20not%20in%20the%20activity%20list.%20I%20still%20don't%20see%20it%20on%20mobile%20devices%20and%20also%20not%20on%20IP%20phones%20like%20Audiocodes%20C450HD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20if%20I%20missed%20a%20call%2C%20I%20just%20see%20a%20number%20in%20history.%20I%20don't%20know%20which%20customer%20or%20partner%20called%20me.%20Should%20I%20call%20back%20and%20ask%2C%20hello%20which%20customer%20are%20you%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20if%20I'm%20looking%20for%20a%20contact%2C%20I%20still%20don't%20have%20the%20possibility%20to%20do%20this%20in%20Teams.%20I%20always%20only%20see%20the%20personal%20contacts%20I%20have%20saved.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20you%20actually%20call%20at%20Microsoft%3F%20Do%20you%20only%20call%20each%20other%20internally%20or%20do%20you%20also%20communicate%20with%20the%20outside%20world%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20call%20an%20external%20contact%20on%20a%20Teams-certified%20device%20like%20the%20Audiocodes%20C450HD%3F%20I%20search%20in%20any%20directory%20and%20then%20type%20in%20the%20number.%20Come%20on!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20simply%20can't%20be%20that%20everything%20only%20works%20with%20saved%20contacts.%20We%20have%2015'000%20contacts%20in%20our%20directory.%20But%20it%20has%20people%20here%20in%20the%20community%20who%20have%2080'000.%20And%20even%20if%20the%20user%20doesn't%20need%20them%20all%2C%20you%20don't%20want%20to%20save%20them%20all.%20But%20I%20want%20everyone%20to%20be%20able%20to%20search%20and%20then%20call.%20And%20that%20must%20be%20possible%20in%20teams%20and%20not%20in%20any%20directory.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20want%20to%20be%20unfriendly.%20But%20we%20are%20forced%20here%20to%20replace%20our%20PBX.%20The%20people%20we've%20had%20in%20the%20test%20group%20for%20over%20a%20year%20are%20slowly%20getting%20annoyed.%20I%20put%20them%20off%20from%20week%20to%20week%20with%20your%20statements.%20But%20slowly%20displeasure%20comes%20up%20and%20people%20are%20thinking%20about%20quitting.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20got%20a%20lot%20of%20nice%20gimmick%20features%20like%20Background%20blur%20etc..%20Regarding%20calls%2C%20we%20are%20still%20in%20the%20Stone%20Age%20or%20shortly%20after.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20report%20from%20the%20real%20world.%20we%20are%20soon%20in%20the%20year%202020%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere's%20just%20one%20exception%2C%20internally%20from%20Teams%20to%20Teams.%20As%20soon%20as%20you%20have%20to%20call%20external%20contacts%2C%20it%20becomes%20difficult%20and%20uncomfortable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3CP%3EGuido%20Peter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-942232%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-942232%22%20slang%3D%22en-US%22%3E%3CP%3ECome%20on%20Carolyn%2C%20these%20are%20just%20basic%20features%20that%20we%20still%20miss.%20For%20almost%20a%20year%2C%20Microsoft%20has%20been%20telling%20us%20about%20parity%20to%20SfB.%20Parity%3F%20Yes%2C%20we%20can%20make%20calls%20with%20teams%2C%20but%20without%20any%20comfort.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere's%20just%20one%20exception%2C%20internally%20from%20Teams%20to%20Teams.%20As%20soon%20as%20you%20have%20to%20call%20external%20contacts%2C%20it%20becomes%20difficult%20and%20uncomfortable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20almost%20a%20year%2C%20we%20can%20finally%20see%20which%20external%20contact%20is%20calling%20us.%20But%20only%20in%20the%20Toaster%20PopUp%20but%20still%20not%20in%20the%20call%20list%20and%20also%20not%20in%20the%20activity%20list.%20I%20still%20don't%20see%20it%20on%20mobile%20devices%20and%20also%20not%20on%20IP%20phones%20like%20Audiocodes%20C450HD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20if%20I%20missed%20a%20call%2C%20I%20just%20see%20a%20number%20in%20history.%20I%20don't%20know%20which%20customer%20or%20partner%20called%20me.%20Should%20I%20call%20back%20and%20ask%2C%20hello%20which%20customer%20are%20you%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20if%20I'm%20looking%20for%20a%20contact%2C%20I%20still%20don't%20have%20the%20possibility%20to%20do%20this%20in%20Teams.%20I%20always%20only%20see%20the%20personal%20contacts%20I%20have%20saved.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20you%20actually%20call%20Microsoft%3F%20Do%20you%20only%20call%20each%20other%20internally%20or%20do%20you%20also%20communicate%20with%20the%20outside%20world%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20call%20an%20external%20contact%20on%20a%20Teams-certified%20device%20like%20the%20Audiocodes%20C450HD%3F%20I%20search%20in%20any%20directory%20and%20then%20type%20in%20the%20number.%20Come%20on!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20simply%20can't%20be%20that%20everything%20only%20works%20with%20saved%20contacts.%20We%20have%2015'000%20contacts%20in%20our%20directory.%20But%20it%20has%20people%20here%20in%20the%20community%20who%20have%2080'000.%20And%20even%20if%20the%20user%20doesn't%20need%20them%20all%2C%20you%20don't%20want%20to%20save%20them%20all.%20But%20I%20want%20everyone%20to%20be%20able%20to%20search%20and%20then%20call.%20And%20that%20must%20be%20possible%20in%20Teams%20and%20not%20in%20any%20directory.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20want%20to%20be%20unfriendly.%20But%20we%20are%20forced%20here%20to%20replace%20our%20PBX.%20The%20people%20we've%20had%20in%20the%20test%20group%20for%20over%20a%20year%20are%20slowly%20getting%20annoyed.%20I%20put%20them%20off%20from%20week%20to%20week%20with%20your%20statements.%20But%20slowly%20displeasure%20comes%20up%20and%20people%20are%20thinking%20about%20quitting.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20got%20a%20lot%20of%20nice%20gimmick%20features%20like%20Background%20blur%20etc..%20Regarding%20calls%2C%20we%20are%20still%20in%20the%20Stone%20Age%20or%20shortly%20after.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20report%20from%20the%20real%20world.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3CP%3EGuido%20Peter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-942230%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-942230%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F237681%22%20target%3D%22_blank%22%3E%40Daniel%20Jelinek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20second%20time%20my%20post%20has%20been%20deleted!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-952131%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-952131%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20seen%20the%20Azure%20AD%20lookup%20working%20yet%3F%26nbsp%3B%20Ours%20is%20still%20showing%20our%20company%20name%20which%20is%20put%20out%20by%20our%20PBX%20system%20so%20it%20is%20not%20doing%20any%20Azure%20AD%20lookup%20yet.%26nbsp%3B%20We%20store%20our%20numbers%20in%20E.164%20format%20in%20AD%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-952139%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-952139%22%20slang%3D%22en-US%22%3EYes%2C%20I%20have%20seen%20it%20on%20desktop.%20But%20I%20think%20it%20depends%20on%20which%20ring%20you%20are.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-976161%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-976161%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F29245%22%20target%3D%22_blank%22%3E%40Guido%20Peter%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20my%20test%20results%2C%2011%2F3%2F2019.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELab%3C%2FP%3E%3CUL%3E%3CLI%3EO365%20Tenant%20-%20standard%20ring%20%2F%20not%20in%20an%20earlier%20ring.%3C%2FLI%3E%3CLI%3ECUCM%20user%20(Allen)%20with%20E.164%20number%20published%20in%20Active%20Directory%20and%20sync'd%20to%20O365%20via%20Azure%20AD%20Connect.%3C%2FLI%3E%3CLI%3ETeamsOnly%20user%20(Jerry)%20w%2F%20Phone%20System%20%2B%20Direct%20Routing%3C%2FLI%3E%3C%2FUL%3E%3CP%3ETests%3C%2FP%3E%3CP%3E1.%26nbsp%3B%20CUCM%20(Allen)%20dials%20Jerry's%2010%20digit%20number%20via%20direct%20routing.%26nbsp%3B%20%26nbsp%3BJerry%20answers%20on%20the%20following%20endpoints.%3C%2FP%3E%3COL%3E%3CLI%3ETeams%20Windows%20Client%20%3D%20Success%20-%20We%20see%20Allen's%20full%20name.%3C%2FLI%3E%3CLI%3ETeams%20Mobile%20%3D%20Success%20-%20We%20see%20Allen's%20full%20name.%3C%2FLI%3E%3CLI%3ETeams%20Mac%20Client%20%3D%20Success%20-%20We%20see%20Allen's%20full%20name.%3C%2FLI%3E%3CLI%3EYealink%20T58A%20Phone%20%3D%20Failure%20-%20No%20name%2C%20Number%20only.%3C%2FLI%3E%3CLI%3EAudioCodes%20C450HD%20Phone%20%3D%20Failure%20-%20No%20Name%2C%20Number%20only.%3C%2FLI%3E%3CLI%3EMicrosoft%20Teams%20Room%20(Skype%20for%20Business%20and%20Microsoft%20Teams%20%3CDEFAULT%3E)%20%3D%20Failure%2C%20No%20Name%2C%20Number%20only.%3C%2FDEFAULT%3E%3C%2FLI%3E%3CLI%3ESurface%20Hub%202S%20(Skype%20for%20Business%20%3CDEFAULT%3E%20and%20Microsoft%20Teams)%20%3D%20Success%2C%20We%20see%20Allen's%20full%20name.%3C%2FDEFAULT%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3ECall%20History%20on%20Windows%20client%20and%20Mobile%20only%20shows%20numbers%2C%20no%20names.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-977462%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-977462%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F125905%22%20target%3D%22_blank%22%3E%40Matt%20Edlhuber%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENice%20summary%20Matt%2C%20we%20do%20have%20basically%20same%20experience%20in%20our%20tenant.%3C%2FP%3E%3CP%3EI%20also%20tested%20the%20experience%20if%20really%20the%20number%20is%20not%20present%20in%20the%20Azure%20AD%20that%20it%20will%20leverage%20SIP%20header%20CLI%20and%20vice%20versa.%3C%2FP%3E%3CP%3EI%20am%20struggling%20as%20many%20other%20as%20I%20can%20see%20with%20Call%20History%20tab.%20and%20missing%20information.%20One%20would%20say%20it%20cannot%20be%20so%20hard%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-977485%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-977485%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F125905%22%20target%3D%22_blank%22%3E%40Matt%20Edlhuber%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20tested%20this%20on%20our%20side%20again.%3C%2FP%3E%3COL%3E%3CLI%3ETeams%20Windows%20Client%20%3D%20Success.%3C%2FLI%3E%3CLI%3ETeams%20Mobile%20%3D%20Failure%20-%20No%20name%2C%20Number%20only.%3C%2FLI%3E%3CLI%3EAudioCodes%20C450HD%20Phone%20%3D%20Failure%20-%20No%20Name%2C%20Number%20only.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20RNL%20works%20on%20a%20device%2C%20it%20also%20works%20with%20AAD%20contacts.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-977552%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-977552%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F125905%22%20target%3D%22_blank%22%3E%40Matt%20Edlhuber%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESomeone%20has%20turned%20a%20switch%20over!%20Now%20it%20suddenly%20works%20on%20Teams%20mobile.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-978819%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-978819%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F29245%22%20target%3D%22_blank%22%3E%40Guido%20Peter%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Call%20History%20piece%20seems%20to%20be%20a%20bug.%26nbsp%3B%20I%20was%20able%20to%20confirm%20it's%20an%20issue%20in%20early%20rings%20(1.5)%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELook%20at%20Paul%20Cannon's%20post%20on%20the%20Teams%20Blog%20this%20morning%22%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FWhat-s-New-for-Calling-in-Microsoft-Teams-Ignite-2019-Edition%2Fba-p%2F974935%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EWhat%E2%80%99s%20New%20for%20Calling%20in%20Microsoft%20Teams%3C%2FA%3E%22%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22Knowing%20who%20is%20calling%20and%20having%20your%20delegates%20properly%20screen%20and%20route%20these%20calls%20is%20key%20to%20a%20productive%20day.%20Recently%20we%20made%20available%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EReverse%20Number%20Lookup%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Bto%20display%20a%20caller%E2%80%99s%20name%20based%20on%20multiple%20sources.%20This%20includes%20caller%20ID%20in%20history%20and%20voicemail%20ensuring%20you%20always%20know%20who%20has%20called.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-992020%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-992020%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F125905%22%20target%3D%22_blank%22%3E%40Matt%20Edlhuber%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F29245%22%20target%3D%22_blank%22%3E%40Guido%20Peter%3C%2FA%3E%26nbsp%3BHave%20seen%20this%20blog%20also%2C%20hopefully%20the%20fix%20the%20call%20history%20and%20activity%20in%20the%20next%20release....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1070832%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1070832%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F125905%22%20target%3D%22_blank%22%3E%40Matt%20Edlhuber%3C%2FA%3E%26nbsp%3Band%20everyone%20else%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20updated%20the%20iOS%20Teams-Apps%20to%20Version%201.0.91%20(Build%3A%201.077.2019121004)%20and%20now%20some%20more%20information%20seems%20to%20be%20shown%20in%20the%20call%20history.%3C%2FP%3E%3CP%3ENow%20I%20can%20also%20see%20the%20names%20provided%20from%20the%20incoming%20call%20toast%20inside%20the%20call%20history.%20This%20has%20already%20been%20stored%20in%20the%20iOS%20phone%20app%20the%20days%20before.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20doesn't%20count%20for%20outbound%20calls%2C%20so%20i%20assume%20that%20reverse%20number%20lookup%20is%20not%20completely%20working%20against%20AAD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdditionaly%20here's%20a%20question%20from%20my%20side%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat's%20the%20Use%20of%20the%20%22-ForwardCallHistory%22%20Property%20for%20the%20SBC%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F162209i33DFB4BC40F434D2%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20hope%20anyone%20can%20describe%20this%20in%20detail.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1081463%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1081463%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F266576%22%20target%3D%22_blank%22%3E%40FloTob%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20confirm%20that%20we%20have%20also%20two%20weeks%20ago%20found%20out%20that%20Call%20History%20for%20iOS%20devices%20is%20translating%20numbers%20into%20names.%20Funny%20that%20application%20for%20Apple%20devices%20is%20fixed%20earlier%20than%20Windows%20app...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20regards%20of%20your%20question%20about%20ForwardCallHistory.%20This%20simply%20enables%20in%20SIP%20signalling%20both%20described%20parameters%20in%20SIP%20header.%20History-Info%20and%20Reffered-By.%20In%20easy%20way%20described%20if%20you%20have%20call%20that%20is%20transferred%20or%20forwarded%20and%20there%20is%20new%20SIP%20INVITE%20for%20this%20call%20which%20is%20sent%20to%20your%20SBC%20it%20will%20contain%20in%20Reffered-By%2FHistory-Info%20information%20about%20user%20who%20is%20transferring%2Fforwarding%20the%20call.%20We%20used%20this%20information%20for%20proper%20routing%20of%20the%20call%20through%20appropriate%20user's%20local%20PSTN%20line.%20It%20might%20be%20also%20used%20by%20some%20applications...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1496648%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1496648%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64287%22%20target%3D%22_blank%22%3E%40Ben%20Lockwood%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20the%20same%20setup%20and%20are%20seeing%20the%20same%20issue.%20Will%20wait%20for%20Microsoft%20to%20work%20with%20AudioCodes%20to%20iron%20out%20this%20feature%20and%20make%20it%20happen.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1657653%22%20slang%3D%22en-US%22%3ERe%3A%20Caller%20ID%20and%20Direct%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1657653%22%20slang%3D%22en-US%22%3E%3CP%3Eagreed!%20we%20just%20switched%20to%20Teams%20calling%20and%20half%20our%20staff%20is%20in%20the%20field.%20Calls%20from%20cellphone%20just%20show%20as%20wireless%20caller%20even%20though%20the%20cell%20number%20is%20in%20AD...%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

We have setup Direct Routing with an AudioCodes virtual SBC.  The caller ID information is currently not passing to Microsoft Teams.  Is this a known issue or is there a configuration piece missing?  Thanks!

83 Replies
Highlighted
It doesn't work even with Microsoft's PSTN call in. Client doesn't quiet support it yet.
Highlighted

Hi @Ben Lockwood

 

What do you mean by Caller ID? Are you referring to the Calling Line Identity phone number or Display Name? 

 

Currently Direct Routing does support sending the number of the user who placed the call unless that number was set to appear as anonymous or as another service number by tenant administrator. 

 

What is currently missing and work underway to resolve is Calling Name Display included in the From field. 

Highlighted

I meant if I call any other PSTN from my cell phone it shows my name and my number.  In Microsoft Teams with Direct Routing it is showing only the phone number and not passing the name information to the Teams client.  In working with AudioCodes they said that the SBC is passing that information to Microsoft.  I get bombarded my sales calls so I tend to screen my calls using the names that come in on calls to determine whether I want to answer the call or not.  Moving to Microsoft Teams I have now lost that ability.  It also doesn't seem to have the ability to look at Contacts or Exchange to look up any names either.  Once they have these little features ironed out it will be much more usable as an actual phone client than it is now.

Highlighted

@Ben Lockwood

Thanks for the great feedback. We do have plans to implement both items, passing name to Teams when available in the inbound invite From field as well as RNL against Exchange and Contacts. 

 

I don't have an ETA for this changes but we do understand the importance of these features. 

Highlighted
These are mandatory functions to gain user acceptance. Please increase the priority level.
Highlighted

Hi @Carolyn Blanding (MS TEAMS) 

 

Is there any update on progress of this?  Until Teams is capable of displaying caller name there is no way we would get any buy in from our general users.  Thanks!

Highlighted

any link to feature about teams client to lookup mailbox contacts for incoming calls regarding the incoming phone numbers?

Highlighted
Understood Ben. I don't have any ETA for this yet but do know it's actively being worked on and the priority is understood.
Highlighted

Any news on this? This is really the most annoying point in our POC with teams. You want to switch to a modern tool and parity with S4B is promised. And then I only see the phone number and have to find out who this number belongs to, with every missed call first.

Highlighted

Getting closer. Currently testing reverse number lookup against recipients contacts. 

Highlighted
I can see it! :thumbs_up:
Highlighted

Excellent. Thanks for sharing.

Highlighted

Ours is working for looking up against a user who has contacts saved in their Outlook.  It does not however lookup against Exchange.  Will it be able to lookup against Exchange in the future?  When will caller ID passed by PSTN start working as well?

Highlighted

What do you mean against Exchange? 

 

Currently RNL works against contacts stored by user in Teams A-Z contacts in Calls tab. These contacts will be synchronized from user's Exchange mailbox contacts store if the user mailbox is home online for now until support for contacts are available in on premise mailbox; see here for more about feature capabilities with Teams and Exchange How Exchange and Microsoft Teams interact

 

We do have plans for support inbound CNAM from SBC to Teams. No ETA on this; under investigation. 

Highlighted

What I mean by Exchange is the Global Address List.  It currently will only resolve the name if I have added the user to my personal contacts in Outlook.  It will not resolve all people in the GAL.

Highlighted

Got it. RNL against Azure AD is planned. 

Highlighted
Is there a timeline on when we can expect this?
Highlighted

Sorry I don't have an ETA for either to share at this time. 

Highlighted

Any news on RNL against Azure AD?