Solved Teams Trunk and 3 Digit Extensions transfers with legacy PBX

[hwsknudsen]

I'm not sure if this is a bug, or just a quirk of how I have teams setup, but thought it would be worthwhile posting,

So say for example you have a 3cx PBX with 3 digit extensions, you a migrating from another PBX that also has 3 digit extensions

on the 3cx PBX you can dial a 3 digit extension, if it exists on the 3cx PBX it routes directly to the extension,

if on the 3cx pbx you call a 3 digit extension and it doesn't exist it will go out a trunk to the legacy PBX and reach the extension

so everything seems to work,


Now turn on teams (be happy making and receiving calls) exactly the same flow as outside teams on the 3cx PBX even calling extensions works


--- this is where it breaks - call transferring on teams
receive a call from a Public number e.g. +1.111.111.1111 -> on prem non 3cx PBX ext 123 route to 3cx PBX 123---> teams user for ext 123-- works great
now transfer the call to ext 345

anyone have any ideas, ??

Thanks,

08/10/2021 9:31:12 PM - [CM503014]: Call(C:135): No known route from Line:10000<<+11111111111to target: <sip:[email protected]:5061/tls>

08/10/2021 9:31:12 PM - Call(C:135): from Line:10000<<+11111111111to to 345doesn't match any known extension number.

08/10/2021 9:31:12 PM - [Flow] Target endpoint for 172 can not be built!

08/10/2021 9:31:12 PM - [CM503010]: Call(C:135): Making route(s) from Line:10000<<+11111111111to to <sip:[email protected]:5061/tls>

08/10/2021 9:31:12 PM - [CM505003]: Provider:[OnPrem-5190-User] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]]

08/10/2021 9:31:12 PM - [Flow] Refer: RefTo=<sip:[email protected]:5061>; was call from=<sip:+11111111111to ;ext=[email protected]:0> to=<sip:+11111111111to @teamssbc.domain.com:5062>

 

[StefanW]

Sorry but this is a flow which is not going to work. Once all users are on 3cx it will be okey.

 

[hwsknudsen]

Understand - (i should probably get rid of the legacy PBX)

FYI lets encrypt certs work with teams (you might want to add them for testing with auto renew) would make it really easy

 

[Evolute IT]

Understand - (i should probably get rid of the legacy PBX)

FYI lets encrypt certs work with teams (you might want to add them for testing with auto renew) would make it really easy

The problem is the way the Let's Encrypt process is designed would require the PBX to use 80/443 for the SBC FQDN, instead of the PBX FQDN, which would cause issues with the validation process and render the UI unusable through those ports every time it renews. It would also be very prone to random failures.