Trouble with Teams Integration Feature in v18 (No incoming and outgoing calls)

[ileacon]

Hi @all,

I am having a problem with the new Teams integration feature in v18. I configured it as described in the docs but cannot I get incoming or outgoing calls to work.

In the Logs I can see the following if an incoming call is reaching the 3cx:

Call to T:Extn:101@[Dev:sip:[email protected]:5063;rinstance=bb4472144fe752d7,Dev:sip:+494XXXXXXXX;ext=[email protected]] from L:24.1[Line:10000<<0175XXXXXXX] failed, cause: Cause: 404 Not Found/INVITE from 52.114.76.76:5061

Could you please help me? Our 3CX is located in Azure Cloud.

 

[StefanW]

Hi,

Teams, or in this case actually Lync of MS, is stating that it cannot locate the number.
This can happen if you just did the install and configuration. It can take up to 24h until it takes effect.
Also restarting the teams client which has configured to be +494XXXXXXXX;ext=101

In case you changed the number (Office Phone) for the user in the meantime, you also need to wait until this updates.

 

[ileacon]

....thanks for the information.

Is the string +494XXXXXXXX;ext=101 correct? Teams only knows +494XXXXXXXX but not ext=101?

 

[ileacon]

I think I get it to work. I had to add my phone number in Teams as followed:

Set-CsUser -Identity sip:[email protected] -OnPremLineURI "tel:+49XXXXXXXXX;ext=101"

Is there a way that 3cx is using +494XXXXXXXX@ instead of +494XXXXXXXX;ext=101@

 

[StefanW]

when you look in the second script generated by 3CX the correct format is +49XXXXXXXXX;ext=101. In full

Set-CsUser -Identity [email protected] -OnPremLineURI "tel:+49XXXXXXXXX;ext=101" -EnterpriseVoiceEnabled $true -HostedVoiceMail $true

 

[ileacon]

you are right. After I generated the user script a second time now, these parts are included. The first time the script only looks like this

$users_ids = @()
New-CsBatchPolicyAssignmentOperation -PolicyType TenantDialPlan -PolicyName "3CX Dial Plan" -Identity $users_ids -OperationName "Batch assign dial plan"
New-CsBatchPolicyAssignmentOperation -PolicyType OnlineVoiceRoutingPolicy -PolicyName "3CX Voice Route Policy" -Identity $users_ids -OperationName "Batch assign voice routing"
New-CsBatchPolicyAssignmentOperation -PolicyType TeamsCallingPolicy -PolicyName "3CX Calling Policy" -Identity $users_ids -OperationName "Batch assign calling policy"

So if the user sync did not run completely, the script will not be generated completely either

 

[Evolute IT]

you are right. After I generated the user script a second time now, these parts are included. The first time the script only looks like this

$users_ids = @()
New-CsBatchPolicyAssignmentOperation -PolicyType TenantDialPlan -PolicyName "3CX Dial Plan" -Identity $users_ids -OperationName "Batch assign dial plan"
New-CsBatchPolicyAssignmentOperation -PolicyType OnlineVoiceRoutingPolicy -PolicyName "3CX Voice Route Policy" -Identity $users_ids -OperationName "Batch assign voice routing"
New-CsBatchPolicyAssignmentOperation -PolicyType TeamsCallingPolicy -PolicyName "3CX Calling Policy" -Identity $users_ids -OperationName "Batch assign calling policy"

So if the user sync did not run completely, the script will not be generated completely either

That script has no users, which means 2 possibilities:

1. The users are not configured with an E164-formatted number in Office Phone, which can also be the DID.

2. The users don't have the right licenses to use Direct Routing.

 

[StefanW]

$users_ids = @() is empty and should be filled with email addresses and phone numbers, I agree with @Frederick Marcoux.