Solved Teams Direct Routing Fail to dialout or dial in

[Patrick_Frigon]

Hi,

We try to install teams Direct Routing from Hosted 3CX 18.0 Update 2 (Build 314)Version.

- My sync Microsoft 365 was done
- My certificate was succesful loaded
- the synced With Ms 365+Teams was done from my user
- My Ms Licences is M365 Buisness Voice without calling plan
- i see the call activity on ms teams management consol . The code for Final Sip code for outbound call from teams is 603 and for incoming call is 404

see the two print screen

Direct Routing​

 

[Yacman]

Are these values the same?
View attachment 28205

Also are these values the same?
View attachment 28206

If you all this matches, what you can try is:

1. Disable MS365 User Sync in 3CX
2. Delete Extension 002
3. Re-create Ext 002, in the email put the UPN of the MS365 user, and leave First/Last Name fields empty.
4. Re-enable User Sync
5. Wait a few minutes and re-check Ext 002, it should now have First/Last name and "Teams" appeared in the "Synced with" column (if it hasn't, restart all 3CX Services).
6. Try a call from Teams to 3CX again to number *777 (Echo Test Extension)

Hi Nick,

Cheers for taking the time to respond!

Yes the DID entries are identical between the logs and the user entry in 3CX

Within teams this is also identical however, I note that the extension ID starts with x for me as opposed to your screenshot which actually says ext. I imagine this is nothing but worth noting?

I will try the steps you mentioned and let you know how I get on!

 

[NickD_3CX]

Within teams this is also identical however, I note that the extension ID starts with x for me as opposed to your screenshot which actually says ext. I imagine this is nothing but worth noting?

Could you send a screenshot of this?

 

[Yacman]

Could you send a screenshot of this?

 

[NickD_3CX]

Can you run this command in Powershell?

Set-CsPhoneNumberAssignment -Identity [email protected] -PhoneNumber "+44203xxxxx;ext=002" -PhoneNumberType DirectRouting

Replace of course the Email and Phone number to the proper values, in the number don't leave any spaces, dashes, etc, then wait 5-10 minutes and check there again.
Does the number presentation change to what it looks like in my screenshot?

 

[Yacman]

Ran the command and the presentation doesn't change. Looks like its more a GUI thing as I relaunched the app after waiting and it briefly shows ext=002 but instantly changes to x002

Attached screenshot of users lineuri property in Powershell which at least shows the correct value

 

[NickD_3CX]

Ran the command and the presentation doesn't change. Looks like its more a GUI thing as I relaunched the app after waiting and it briefly shows ext=002 but instantly changes to x002

Attached screenshot of users lineuri property in Powershell which at least shows the correct value

Fair enough, I just haven't happened to notice this before.

In this case try the instructions and let us know how that goes.

 

[Yacman]

Fair enough, I just haven't happened to notice this before.

In this case try the instructions and let us know how that goes.

Just done everything you listed - Only extra thing I needed to do was re-add the DID but once done I still got the Declined in Teams



3CX Activity also shows the same as prior with the caller being unknown

 

[NickD_3CX]

Just done everything you listed - Only extra thing I needed to do was re-add the DID but once done I still got the Declined in Teams

View attachment 28315

3CX Activity also shows the same as prior with the caller being unknown

OK, one last thing to check please. In Settings --> Microsoft 365, in the "User Sync" tab, check the option "Sync Microsoft 365 user "Office phone" to extension "Outbound Caller ID"", then press OK.

Then go to the "Users" node, edit Ext 002 and check the "Outbound Caller ID" field in the "General" tab.

Does it show the "+44...." number that also exists in the INVITE message you see in the logs?

 

[Yacman]

Okay so the number in outbound id appears as the below

+44203xxxxxxxext002 which I find odd

So yes, the number itself is identical to the number that appears in the logs however not in this format

 

[Yacman]

I had the telephone field in AD which we have configured to sync to Office365 populated as the LineURI value for some reason. Can't remember why I did this but I've just removed this, and am currently resyncing the user.

Once done, I'm going to run the phone assignment again just to see if it made any difference to the situation

 

[NickD_3CX]

Okay so the number in outbound id appears as the below

+44203xxxxxxxext002 which I find odd

So yes, the number itself is identical to the number that appears in the logs however not in this format

This could be the problem then, as this is also used to identify the user.
It should look something like this:
https://www.3cx.com/docs/microsoft-teams-integration-faqs/#h.4dm9u5zhjuda

 

[Yacman]

Yeah could be the problem, I've changed everything but it might be taking a while to propagate through so I'll give it 30min and try again

Thanks for your help so far! It's appreciated

 

[Yacman]

Right! Looks like it's working now but also not sure what exactly did it!

While I was waiting for this to work, I went into the Teams GUI and pressed Edit on my number and noted that the DDI set there wasn't prepended with + so I added that, and waited about 5 seconds and made the calls again and bam, worked.

Granted, config wise, nothing changed by adding the +. I do think however with the combination of the Office property being set incorrectly from the beginning and changing this in the GUI prompted some form of refresh on Teams for this to suddenly work.

Tested all calls and all looks fine but I have encountered one weird thing which is when I call my mobile and hang up from my mobile rather than Teams, the call remains active in Teams but 3CX acknowledged the call as ended. Almost as though the "BYE" isn't reaching teams but I can see it being sent in verbose logs

 

[NickD_3CX]

Right! Looks like it's working now but also not sure what exactly did it!

While I was waiting for this to work, I went into the Teams GUI and pressed Edit on my number and noted that the DDI set there wasn't prepended with + so I added that, and waited about 5 seconds and made the calls again and bam, worked.

Granted, config wise, nothing changed by adding the +. I do think however with the combination of the Office property being set incorrectly from the beginning and changing this in the GUI prompted some form of refresh on Teams for this to suddenly work.

Tested all calls and all looks fine but I have encountered one weird thing which is when I call my mobile and hang up from my mobile rather than Teams, the call remains active in Teams but 3CX acknowledged the call as ended. Almost as though the "BYE" isn't reaching teams but I can see it being sent in verbose logs

Glad to hear it is figured out!

I think it must have been the "Office Number" property that did the trick and just happened around the same time you tried the other settings to.

Anyhow, as this problem is resolved I shall mark this one as 'Solved'.

About the other you mentioned, I seem to recall hearing of something like this before.
Try logging out of ALL other devices/PCs you may have your Teams account logged into, then log in only from your PC, then try again.
Does it hang up OK then?

If not, if you want open another thread to discuss this.