3CX V20 Update 7 running on Debian
Got a Teams Direct Routing integration, it works, but issue we have is when users click-to-call their colleagues within Teams, when it reaches the 3CX side the caller id is the external number of the user.
Eg, Joe Bloggs, Ext 100, DDI +441234567890
calls
Jane Doe, ext 101, DDI +441234567899
This comes through on 3CX as
Contact: <sip:[email protected]:5062;transport=TLS>
To: <sip:[email protected]:5062;user=phone>;tag=7ebe5f51
From: "Joe Bloggs"<sip:+441234567890;ext=[email protected]:5061;user=phone>
which results in the call going out through the SIP trunk and then back in, to the callee (Jane Doe in this case), it appears as a call coming from the company's main line (outbound rules present all outbound calls as the main line number) and so they don't know who's calling them.
All users have their LineUri set in format
tel:+441234567899;ext=101
However their "Office Phone" field in AD is set just to the DDI (eg +441234567899) and I suspect this is where the click-to-call is pulling their number from.
If a user dials the person's internal extention from Teams rather than clicking their card, it comes through correctly to 3CX and is treated as an internal call, but the users are too used to just clicking their colleagues within Teams.
I tried using normalization rules to convert user's DDIs to their internal ext, eg
number dialed: ^.+1234567899$
translate to: 101
but this resulted in the call coming in to 3CX as "to: +44jane@.."
Where it's getting this "Jane" from I don't know as their "DisplayName" field is their full name and "Alias" and email are in format FLastName, eg JDoe, also not sure why +44 is getting tagged in front but end result is call obviously fails.
Firstly, is this normal expected behaviour? Or if not, any hints where I can check to fix?
Have been toying with changing the user's Office Phone field to "+441234567899 x101" as apparently this will result in both the DDI and ext being sent to 3CX and 3CX can then pick extension, but would then need to change their signatures as they use this field for sigs and then changing processes moving forward for new user creation ect so looking for advice before firing.
Got a Teams Direct Routing integration, it works, but issue we have is when users click-to-call their colleagues within Teams, when it reaches the 3CX side the caller id is the external number of the user.
Eg, Joe Bloggs, Ext 100, DDI +441234567890
calls
Jane Doe, ext 101, DDI +441234567899
This comes through on 3CX as
Contact: <sip:[email protected]:5062;transport=TLS>
To: <sip:[email protected]:5062;user=phone>;tag=7ebe5f51
From: "Joe Bloggs"<sip:+441234567890;ext=[email protected]:5061;user=phone>
which results in the call going out through the SIP trunk and then back in, to the callee (Jane Doe in this case), it appears as a call coming from the company's main line (outbound rules present all outbound calls as the main line number) and so they don't know who's calling them.
All users have their LineUri set in format
tel:+441234567899;ext=101
However their "Office Phone" field in AD is set just to the DDI (eg +441234567899) and I suspect this is where the click-to-call is pulling their number from.
If a user dials the person's internal extention from Teams rather than clicking their card, it comes through correctly to 3CX and is treated as an internal call, but the users are too used to just clicking their colleagues within Teams.
I tried using normalization rules to convert user's DDIs to their internal ext, eg
number dialed: ^.+1234567899$
translate to: 101
but this resulted in the call coming in to 3CX as "to: +44jane@.."
Where it's getting this "Jane" from I don't know as their "DisplayName" field is their full name and "Alias" and email are in format FLastName, eg JDoe, also not sure why +44 is getting tagged in front but end result is call obviously fails.
Firstly, is this normal expected behaviour? Or if not, any hints where I can check to fix?
Have been toying with changing the user's Office Phone field to "+441234567899 x101" as apparently this will result in both the DDI and ext being sent to 3CX and 3CX can then pick extension, but would then need to change their signatures as they use this field for sigs and then changing processes moving forward for new user creation ect so looking for advice before firing.
