Teams Direct Routing Issue - Outbound Calls

[infinity5]

Hi All,

Just enabled Teams Direct Routing, running my 3CX PBX on Azure - in the UK

Dialling into 3CX sends the call to Teams no issues - apart from Teams marking the call as "Likely Spam" something to do with the SIP header from 3CX possibly!?

Initially I was unable to dial out from Teams but as I am running on Azure port 5062 was not open, I have now opened it. Issue is now when I dial a number starting with 0, 3CX responds with "Called number does not exist" and in the 3CX logs the preceding 0 has stripped. I can dial local numbers without the dial code and the call works. I think this might be to do with my Outbound Rules in 3CX (not sure).

Any pointers?

Thanks
David

 

[infinity5]

As an update, if I dial the number in Teams as +440116xxxxxxx the call is successfull, but who wants to have to dial the +44??

 

[StefanW]

I feel like you have e164 processing enabled in 3CX, disable it and let me know how it goes.

FROM and TO Number Format​

The sip FROM is taken from the extension setting in 3CX when placing a call to the PSTN network. The TO number is formatted in e164 when the outbound call inbounds from Teams to 3CX. You may need to adjust your outbound rules to cater for numbers starting with a + or in case your SIP provider does not support dialling in e164 format, trim the number to a format known to your provider.

It is advisable to disable the e164 number processing in 3CX to have transparent management of the TO number in the outbound rules when combined with Microsoft Teams.