Teams calling error

Copper Contributor

We are an E5 customer w/ domestic calling plans. We submitted our port order a few weeks ago and it was scheduled for Monday 7/6/2020. The port order was successful but when we call out or in we get the error "You’re not set up to use this calling feature. Please contact your admin." I am the admin. I have spent the last 24 hours on and off the phone with Microsoft support some of which I could understand others I couldn't understand the first word they were saying. We have been without phones this entire time. Searching that error yields only 1 answer which is to remove the phone number and reassign it to the user no one has replied to the posts past the microsoft responses and none provided an answer that solved our issue. We have followed the instructions for this multiple times and are still receiving the same error. This is affecting our entire company not just a single user. We cannot go another day without phones. I have tried from multiple locations (3 sites + home) multiple OS's (Win 10 Win 7 legacy machine and Mac) Multiple Cellphones on multiple providers (android and ios; ATT Sprint and Verizon) 

 

This is the most recent of those posts https://answers.microsoft.com/en-us/msoffice/forum/all/calling-plan-not-set-up-correctly-in-teams/e4...

I have been redirected here per this thread https://answers.microsoft.com/en-us/msteams/forum/msteams_tfb-msteams_meeting-msteams_suboth/teams-c...

 

The call report for one of my test calls is below I have redacted some identifying information Hopefully this will help someone smarter than me figure out where the issue is. 

 

 

Report time

Jul 7, 2020, 8:51 AM CDT

source

noam.announcement.services.skypeforbusiness.com

reason

You’re not set up to use this calling feature. Please contact your admin.

Report time

Jul 7, 2020, 8:51 AM CDT

Cnd_Skype_InitiatingUser_Endpoint_EndpointValue

5973c5fc-ffff-ffff-5ff8-466d3b1c458b

Cnd_ClientHeader

True

Cnd_Skype_ResultDetail

Trouter client failed to deliver Http message.

Cnd_Skype_ResultCode

404

Report time

Jul 7, 2020, 8:51 AM CDT

CallAnsweredModalities

Audio[0] = Bidirectional

CallDurationInSeconds

2.01381

CallEndSubCode

0

CallOfferredModalities

Audio[0] = Bidirectional

SelfParticipantRole

caller

Skype_ResultCode

0

Skype_ResultDetail

CallEndReasonLocalUserInitiated

IsVBSSFromChatLeg

False

ProcessedFinalAnswer

****

Connected

****

IsChatEscalatedToAudio

False

Report time

Jul 7, 2020, 8:51 AM CDT

Connectivity_AckReinviteRcvMs

2347

Connectivity_AllocFinMs

535

Connectivity_AllocationTicks

12

Connectivity_AllocatorUsed

DefaultAllocator

Connectivity_AvgTickCpuUs

359

Connectivity_AvgTickMs

51

Connectivity_BaseAddress

*.*.*.*:50008

Connectivity_BlobGenTime

3803118660826

Connectivity_BlobVer

1

Connectivity_ConnChksStartTimeMs

2365

Connectivity_ContactSrvMs

0

Connectivity_FCsntRqRcvMs

4138

Connectivity_FCsntRqSntMs

3986

Connectivity_FinalAnsRcvMs

2347

Connectivity_FirstHopRTTInMs

78

Connectivity_FirstPathMs

2576

Connectivity_ICEWarn

0x400020

Connectivity_ICEWarnEx

0x609000

Connectivity_IceConnCheckStatus

4

Connectivity_IceInitTS

3803118656464

Connectivity_IceOptimizationMode

3

Connectivity_IceRole

0

Connectivity_LCsntRqRcvMs

4138

Connectivity_LCsntRqSntMs

3986

Connectivity_LocalAddrType

0

Connectivity_LocalAddress

*.*.*.0:50008

Connectivity_LocalInterface

0x4

Connectivity_LocalMR

*.*.*.*:52472

Connectivity_LocalSite

*.*.*.*:50008

Connectivity_LocalVNextVer

7

Connectivity_MediaDllVersion

2020.12.1.7

Connectivity_MediaPathLocal

HostUDP

Connectivity_MediaPathPipe

UDP

Connectivity_MediaPathRemote

StunUDP

Connectivity_MrBgnE

38031186564558080

Connectivity_MrDnsCacheReadAttempt

0

Connectivity_MrDnsE

worldaz.tr.teams.microsoft.com

Connectivity_MrEndE

38031186564558728

Connectivity_MrErrE

0

Connectivity_MrResE

1

Connectivity_PeerEndpointType

4

Connectivity_PortRange

50000:50019

Connectivity_PrelimConnChkFinMs

2347

Connectivity_Protocol

0

Connectivity_RTime_Call

4345833

Connectivity_ReconnectEnabled

0

Connectivity_ReinviteSntMs

3782

Connectivity_RemoteAddrType

1

Connectivity_RemoteAddress

*.*.*.*:1579

Connectivity_RemoteMR

*.*.*.*:53034

Connectivity_RemoteSite

*.*.*.*:1579

Connectivity_RemoteVNextVer

3

Connectivity_RoamingEnabled

0

Connectivity_RtpRtcpMux

0

Connectivity_TotalBytesReceived

27151

Connectivity_TotalBytesSent

36717

Connectivity_TotalPacketsReceived

121

Connectivity_TotalPacketsSent

129

Connectivity_TransportBytesReceived

4107

Connectivity_TransportBytesSent

5904

Connectivity_TransportMode

2

Connectivity_TransportPktsReceived

25

Connectivity_TransportPktsSent

30

Connectivity_UseCndChksStartTimeMs

3782

IsRetargeted

0

MediaAllocationFailures

0

MediaAllocations

1

Media_BlobVer

1

Media_ErrTime

0

Media_InterfacesConnCheck

0x0

Media_InterfacesStall

0x0

Media_MediaTimeout

0

Media_NetworkErr

no error

Media_RTCPTime

3803118660438

Media_RTPTime

3803118660825

Media_RecvErrTime

0

Media_RtcpByeRcvd

0

Media_RtcpByeSent

0

Media_RtpSeq

0

Media_SendErrTime

3803118658879

Media_SeqDelta

0

Media_TransptRecvErr

0x0

Media_TransptSendErr

0x-1073463292

Ring

general

channel_index

0

media_leg_id

596920119D054347AB554CE086DF7246

media_type

audio

1 Reply
Older post, but this is for the people searching for some type of solution.

We too had some crazy issues. It was an issue with assigning the E5 License assignment. If you recently changed it to E5 from say the E3 and, say "Business Voice". This assignment of E5 is broken and will cause issues.
Our fix was to move people away from E5 back to E3. Give it time to propagate, say 20 minutes, then switch to E5 WITH Domestic Calling Plan all at the same time.