SOLVED

Internal Skype users cant call teams users following migration

%3CLINGO-SUB%20id%3D%22lingo-sub-1586230%22%20slang%3D%22en-US%22%3EInternal%20Skype%20users%20cant%20call%20teams%20users%20following%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1586230%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All.%26nbsp%3B%20I%20have%20a%20strange%20issue.%26nbsp%3B%20I%20have%20just%20migrated%20a%20pilot%20group%20from%20Skype%20on-prem%20to%20Direct%20routing%20in%20teams.%26nbsp%3B%20The%20tenant%20is%20configured%20in%20hybrid%20mode%20and%20the%20global%20upgrade%20settings%20are%20set%20to%26nbsp%3B%20'meetings%20first'.%20I%20last%20night%20moved%20the%20pilot%20users%20that%20were%20homed%20on%20SfB%20and%20set%20them%20to%20'Teams%20Only'%20with%20direct%20routing%20configured%20for%20calls.%26nbsp%3B%20They%20are%20now%20having%20issues%20communicating%20with%20internal%20users.%20PSTN%20functionality%20is%20fine%20and%20calls%20can%20be%20made%20in%20and%20out%20but%20when%20an%20internal%20skype%20user%20calls%20they%20are%20unable%20to%20answer%20and%20are%20given%20the%20message%20that%20the%20call%20is%20from%20a%20skype%20user%20and%20skype%20is%20needed%20to%20answer%20the%20call...%26nbsp%3B%20%26nbsp%3BIs%20this%20a%20replication%20timing%20issue%20in%20that%20the%20changes%20were%20only%20made%20at%20around%206pm%20last%20night%20and%20that%20some%20functionality%20is%20yet%20to%20be%20available%20as%20it%20is%20still%20within%20the%2024%20hour%20waiting%20period%20that%20is%20required%20when%20making%20changes...%26nbsp%3B%20%26nbsp%3Bi%20have%20not%20had%20this%20issue%20before%2C%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1586230%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1587710%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20Skype%20users%20cant%20call%20teams%20users%20following%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1587710%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%2F455378%22%20target%3D%22_blank%22%3E%40BenRooke%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%20point%20where%20you%20mention%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%3Ewhen%20an%20internal%20skype%20user%20calls%20they%20are%20unable%20to%20answer%20and%20are%20given%20the%20message%20that%20the%20call%20is%20from%20a%20skype%20user%20and%20skype%20is%20needed%20to%20answer%20the%20call%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20the%20calling%20user%20Teams%20only%20as%20if%20not%20and%20SfB%20then%20I%20would%20not%20expect%20them%20to%20be%20able%20to%20call%20someone%20that%20is%20Teams%20only%20and%20the%20recipient%20would%20be%20expected%20to%20be%20in%20SfB%20to.%20Ignore%20me%20if%20the%20caller%20is%20Teams%20Only%20too.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHenry%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1587876%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20Skype%20users%20cant%20call%20teams%20users%20following%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1587876%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F455378%22%20target%3D%22_blank%22%3E%40BenRooke%3C%2FA%3E%26nbsp%3Bsounds%20very%20much%20like%20a%20replication%20delay%2C%20it%20can%20take%20over%20a%20day%20sometimes%2C%20seems%20to%20depend%20on%20what%20else%20is%20happening%20in%20the%20service.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi All.  I have a strange issue.  I have just migrated a pilot group from Skype on-prem to Direct routing in teams.  The tenant is configured in hybrid mode and the global upgrade settings are set to  'meetings first'. I last night moved the pilot users that were homed on SfB and set them to 'Teams Only' with direct routing configured for calls.  They are now having issues communicating with internal users. PSTN functionality is fine and calls can be made in and out but when an internal skype user calls they are unable to answer and are given the message that the call is from a skype user and skype is needed to answer the call...   Is this a replication timing issue in that the changes were only made at around 6pm last night and that some functionality is yet to be available as it is still within the 24 hour waiting period that is required when making changes...   i have not had this issue before,  

2 Replies
Highlighted

Hi @BenRooke ,

 

On the point where you mention:

 

"when an internal skype user calls they are unable to answer and are given the message that the call is from a skype user and skype is needed to answer the call"

 

Is the calling user Teams only as if not and SfB then I would not expect them to be able to call someone that is Teams only and the recipient would be expected to be in SfB to. Ignore me if the caller is Teams Only too.

 

Thanks

 

Henry

Highlighted
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

@BenRooke sounds very much like a replication delay, it can take over a day sometimes, seems to depend on what else is happening in the service.