Home

Incoming calls anonymous - Ressource account assigned to call group

%3CLINGO-SUB%20id%3D%22lingo-sub-1034858%22%20slang%3D%22en-US%22%3EIncoming%20calls%20anonymous%20-%20Ressource%20account%20assigned%20to%20call%20group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1034858%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20are%20currently%20in%20the%20process%20of%20migrating%20Skype%20users%20on-premise%20to%20Teams%20including%20a%20Direct%20Routing%20Scenario.%20Part%20of%20our%20setup%20are%20call%20groups%20containing%20operators%20that%20can%20take%20the%20call%20and%20the%20resource%20account%20assigned%20to%20that%20call%20group%20has%20a%20number%20assigned.%26nbsp%3B%20We%20have%20followed%20the%20article%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmanage-resource-accounts%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EManage%20Ressource%20Accounts%3C%2FA%3E%26nbsp%3Band%20everything%20works%20as%20expected%20except%20that%20the%20incoming%20call%20always%20has%20the%20Caller%20ID%20%22anonymous%22%20(see%20screenshot%20below).%20As%20soon%20as%20an%20operator%20takes%20the%20call%20the%20correct%20number%20will%20be%20displayed.%3C%2FP%3E%3CP%3EFirst%20I%20thought%20that%20this%20as%20to%20do%20with%20the%20Caller%20ID%20Policy%20blocking%20the%20incoming%20Caller%20ID%20but%20we%20have%20only%20one%20org-wide%20(Global)%20policy%20in%20place%20and%20that%20is%20set%20to%20not%20block%20the%20ID.%20I%20also%20created%20a%20user%20Caller%20ID%20policy%20and%20assigned%20that%20to%20the%20resource%20account%20without%20any%20change.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20an%20idea%20how%20to%20get%20the%20correct%20Caller%20ID%20displayed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%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%2F159053iC0AD170C629CBFBB%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1034858%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1057749%22%20slang%3D%22en-US%22%3ERe%3A%20Incoming%20calls%20anonymous%20-%20Ressource%20account%20assigned%20to%20call%20group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1057749%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20issue%20has%20been%20resolved%20together%20with%20Microsoft%20Premier%20Support.%3CBR%20%2F%3EThe%20root%20cause%20was%20the%20source%20Caller%20ID%20not%20being%20in%20E.164%20format.%20Our%20PSTN%20%22Sipgate%22%20does%20not%20send%20Caller%20ID's%20in%20this%20format%2C%20the%20country%20code%20e.g.%20%2B49%20was%20always%20missing.%20Therefore%20we%20needed%20to%20configure%20our%20SBC%20to%20manipulate%20the%20number%20from%20e.g.%20%22030123456%22%20to%20%22%2B4930123456%22.%3CBR%20%2F%3E%3CBR%20%2F%3EStrange%20is%20that%20this%20was%20never%20an%20issue%20when%20directly%20calling%20a%20Teams%20user%2C%20only%20when%20a%20resource%20account%20was%20called%20and%20in%20turn%20a%20call%20group.%3C%2FP%3E%3C%2FLINGO-BODY%3E
meisterheister
New Contributor

Hello community,

 

we are currently in the process of migrating Skype users on-premise to Teams including a Direct Routing Scenario. Part of our setup are call groups containing operators that can take the call and the resource account assigned to that call group has a number assigned.  We have followed the article Manage Ressource Accounts and everything works as expected except that the incoming call always has the Caller ID "anonymous" (see screenshot below). As soon as an operator takes the call the correct number will be displayed.

First I thought that this as to do with the Caller ID Policy blocking the incoming Caller ID but we have only one org-wide (Global) policy in place and that is set to not block the ID. I also created a user Caller ID policy and assigned that to the resource account without any change.

 

Has anyone an idea how to get the correct Caller ID displayed?

 

clipboard_image_1.png

 

1 Reply

The issue has been resolved together with Microsoft Premier Support.
The root cause was the source Caller ID not being in E.164 format. Our PSTN "Sipgate" does not send Caller ID's in this format, the country code e.g. +49 was always missing. Therefore we needed to configure our SBC to manipulate the number from e.g. "030123456" to "+4930123456".

Strange is that this was never an issue when directly calling a Teams user, only when a resource account was called and in turn a call group.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Dev channel update to 80.0.355.1 is live
josh_bodner in Discussions on
67 Replies