Solved Teams Direct routing - Dial Plan Outbound calls - 404 Not Found

[neil_HRC]

Have configured Teams direct routing on our PBX, UK based. Only immediate issue is number formatting on outbound calls via the Teams client. On my desk phone and 3CX app i can successfully dial a UK based mobile number using format 07974 xxx xxx. Same number via Teams client produces a "404 Not Found" as it seems to strip the leading "0". Now think its concerning the Teams dial plan but hoping for some assistance. A lot of our clients no doubt will use this number format in the UK so will need to accommodate.

Thanks in advance,

Neil

 

[Evolute IT]

Have configured Teams direct routing on our PBX, UK based. Only immediate issue is number formatting on outbound calls via the Teams client. On my desk phone and 3CX app i can successfully dial a UK based mobile number using format 07974 xxx xxx. Same number via Teams client produces a "404 Not Found" as it seems to strip the leading "0". Now think its concerning the Teams dial plan but hoping for some assistance. A lot of our clients no doubt will use this number format in the UK so will need to accommodate.

Thanks in advance,

Neil

Teams should be converting the number to E164 automatically. Do you have a rule that can take a + format number?

Also, check the Call Log to see what was dialed from Teams to make sure.

 

[neil_HRC]

Hey, thanks for teh reply.

Have checked log, as below:

08/03/2022 11:08:52 - Call to T:Line:10000>>7974xxxxxx@[Dev:sip:[email protected]:5060] from L:12.1[Extn:111] failed, cause: Cause: 404 Not Found/INVITE from xx.xx.xx.xx:5060

So looks like its stripping the leading "0".

So in summary testing:

+4407974xxxxxx works on Teams
+447974xxxxxx does not work on Teams
07974xxxxxx does not work on Teams


+4407974xxxxxx does not work on desk phone/3CX App
+447974xxxxxx does work on desk phone/3CX App
07974xxxxxx does work on desk phone/3CX App

 

[NickD_3CX]

Hi!

In the Management Console under Settings --> e164 Processing, do you have this enabled?
If yes, disable it, then try again.

If it still doesn't work, could you take a screenshot of your Outbound Rules and post it here?

 

[neil_HRC]

Hi NickD, thanks for the reply. We are in the process of swapping our instance. Will replicate the issue and report back when up and running.

Neil

 

[neil_HRC]

Hey Nick, ok finally have this setup again. As suggested I disabled "Settings --> e164 Processing" and this seems to have fixed it!

Thanks

 

[NickD_3CX]

Hey Nick, ok finally have this setup again. As suggested I disabled "Settings --> e164 Processing" and this seems to have fixed it!

Thanks

I'm very glad to hear that!

I'll go ahead and mark this one as 'Solved'.