Busy signal on outbound call to PSTN

%3CLINGO-SUB%20id%3D%22lingo-sub-2464672%22%20slang%3D%22en-US%22%3EBusy%20signal%20on%20outbound%20call%20to%20PSTN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2464672%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20user%20configured%20to%20the%20point%20where%20they%20now%20have%20a%20dialpad%20in%20their%20Teams%20client.%20We%20have%20an%20auto-attendant%20created%20and%20when%20we%20dial%20into%20that%20number%2C%20we%20can%20transfer%20the%20call%20to%20the%20user's%20Teams%20client%20successfully.%3C%2FP%3E%3CP%3EHowever%2C%20when%20we%20try%20to%20make%20a%20call%20out%20to%20the%20PSTN%20we%20just%20get%20a%20%22Unavailable%20The%20person%20you're%20trying%20to%20reach%20isn't%20available.%20Try%20again%20later.%22%3C%2FP%3E%3CP%3EThe%20user%20has%20a%20calling%20plan%20assigned.%20We%20can't%20see%20anything%20that%20could%20be%20the%20issue%20since%20everything%20seems%20to%20be%20in%20order.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20some%20parameters%20from%20the%20user%3A%3C%2FP%3E%3CP%3EPhone%20number%20type%3A%20Online%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnPremEnterpriseVoiceEnabled%3A%20False%3CBR%20%2F%3EHostedVoiceMail%3A%20True%3CBR%20%2F%3EEnterpriseVoiceEnabled%3A%20True%3CBR%20%2F%3ETeamsVoiceRoute%3A%20False%3CBR%20%2F%3EOnPremLineURIManuallySet%3A%20True%3CBR%20%2F%3EVoicePolicy%3A%20BusinessVoice%3CBR%20%2F%3ETeamsUpgradeEffectiveMode%3A%20TeamsOnly%3CBR%20%2F%3EDialPlan%3A%20US%3CBR%20%2F%3ELocationPolicy%3A%20US%3CBR%20%2F%3EHostedVoicemailPolicy%3A%20BusinessVoice%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2464672%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEnterprise%20Voice%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVoice%20%26amp%3B%20Calling%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2475905%22%20slang%3D%22en-US%22%3ERe%3A%20Busy%20signal%20on%20outbound%20call%20to%20PSTN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2475905%22%20slang%3D%22en-US%22%3EIf%20user%20has%20a%20calling%20plan%20and%20it%20is%20configured%20appropriately%2C%20outbound%20PSTN%20should%20work%20-%20recommend%20to%20create%20support%20incident%20with%20microsoft%20for%20this.%3C%2FLINGO-BODY%3E
Regular Visitor

We have a user configured to the point where they now have a dialpad in their Teams client. We have an auto-attendant created and when we dial into that number, we can transfer the call to the user's Teams client successfully.

However, when we try to make a call out to the PSTN we just get a "Unavailable The person you're trying to reach isn't available. Try again later."

The user has a Microsoft calling plan assigned and we are not using direct routing. We can't see anything that could be the issue since everything seems to be in order.

 

Here are some parameters from the user:

Phone number type: Online

 

OnPremEnterpriseVoiceEnabled: False
HostedVoiceMail: True
EnterpriseVoiceEnabled: True
TeamsVoiceRoute: False
OnPremLineURIManuallySet: True
VoicePolicy: BusinessVoice
TeamsUpgradeEffectiveMode: TeamsOnly
DialPlan: US
LocationPolicy: US
HostedVoicemailPolicy: BusinessVoice

 

 

2 Replies
If user has a calling plan and it is configured appropriately, outbound PSTN should work - recommend to create support incident with microsoft for this.
Does the user have a phone number assigned? If not, can one be assigned? Or create a caller id policy and use the service number of the auto attendant and assign that caller id policy to the user.

There are "new" laws relating to caller ID and caller identification that could cause some issues if there is no caller ID in place.