Incoming call rejected, caller is unknown

[fneufang]

Hello everyone here,

we currently have the problem, that our Direct Routing with Teams does not work fully.

Inbound calls can be answered as normal, but outbound calls are rejected by the 3CX.

In the activity log of the 3CX the following messages pop up:

22.03.2024 10:05:05 - [CM502001]: Source info: From: "Neufang, Fabian"<sip:+49[officenumber]@sip.pstnhub.microsoft.com:5061;user=phone>;tag=8d7d469ef05141c6bd829b7715f5dfcc; To: <sip:+49[callednumber]@teams.neufang.com:5062;user=phone>

22.03.2024 10:05:05 - [CM503013]: Call(C:1923): Incoming call rejected, caller is unknown; msg=Invite-IN Recv Req INVITE from 52.114.76.76:18637 tid=0ac0ad0d Call-ID=681ede837d6b5175a955f843bb231c75:INVITE sip:+49[callednumber]@teams.neufang.com:5062;user=phone;transport=tls SIP/2.0Via: SIP/2.0/TLS 52.114.76.76:5061;branch=z9hG4bK0ac0ad0dMax-Forwards: 70Record-Route: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr>Contact: <sip:api-du-c-euno.pstnhub.microsoft.com:443;x-i=6d8919f5-f4bc-4195-b1b5-7191dcb6f6b3;x-c=681ede837d6b5175a955f843bb231c75/d/8/bb82fe7ada89410fa4610a8a072f9b3d>To: <sip:+49[callednumber]@teams.neufang.com:5062;user=phone>From: "Neufang, Fabian"<sip:+49[officenumber]@sip.pstnhub.microsoft.com:5061;user=phone>;tag=8d7d469ef05141c6bd829b7715f5dfccCall-ID: 681ede837d6b5175a955f843bb231c75CSeq: 1 INVITESession-Expires: 3600Min-SE: 300Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, NOTIFYContent-Type: application/sdpSupported: histinfo, timerUser-Agent: Microsoft.PSTNHub.SIPProxy v.2024.2.6.5 i.EUNO.12Privacy: idP-Asserted-Identity: <tel:+49[officenumber];ext=22>P-Asserted-Identity: <sip:[email protected]>Content-Length: 1103v=0o=- 499125 0 IN IP4 127.0.0.1s=sessionc=IN IP4 52.113.60.174b=CT:10000000t=0 0m=audio 49446 RTP/SAVP 104 9 103 111 18 0 8 97 101 13 118c=IN IP4 52.113.60.174a=rtcp:49447a=ice-ufrag:44Aya=ice-pwd:lia=rtcp-muxa=candidate:1 1 UDP 2130706431 52.113.60.174 49446 typ srflx raddr 10.0.26.164 rport 49446a=candidate:1 2 UDP 2130705918 52.113.60.174 49447 typ srflx raddr 10.0.26.164 rport 49447a=candidate:2 1 tcp-act 2121006078 52.113.60.174 49152 typ srflx raddr 10.0.26.164 rport 49152a=candidate:2 2 tcp-act 2121006078 52.113.60.174 49152 typ srflx raddr 10.0.26.164 rport 49152a=label:main-audioa=mid:1a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:4XTd9oUNg8wpeyb5clA4lRq/2+17OVFlrejYj0us|2^31a=sendrecva=rtpmap:104 SILK/16000a=rtpmap:9 G722/8000a=rtpmap:103 SILK/8000a=rtpmap:111 SIREN/16000a=fmtp:111 bitrate=16000a=rtpmap:18 G729/8000a=fmtp:18 annexb=noa=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:97 RED/8000a=rtpmap:101 telephone-event/8000a=fmtp:101 0-16a=rtpmap:13 CN/8000a=rtpmap:118 CN/16000a=ptime:20

22.03.2024 10:05:05 - Leg L:1923.1[Unknown:] is terminated: Cause: BYE from PBX

The config is as recommended by 3CX, the teams policies were configured with the powershell script and the SBC does not show any errors in the admin center.

It would be awesome if anyone could help us.

Thank you very much,
Fabian

 

[OlegR_3CX]

Hi Fabian, thank you for the feedback provided.

We know about this issue with Teams and our team is on it. In short, Teams made some changes affecting the integration.
If you can, please open a ticket with support so that we can keep track of your systems to update you ASAP.

 

[fneufang]

Hey Oleg,

thank you very much for your answer.

Is there an estimated time till the patch is released?

Thanks

 

[fneufang]

I just received user feedback that calling from teams does work again and was able to reproduce it working.

Thank you very much for your help, Oleg.

Have a nice weekend!

Fabian

 

[OlegR_3CX]

Great! Thank you for the feedback, Fabian.
Seems that the Teams sort things out from their end.
Have a nice weekend too

 

[UrielFoster]

Are you sure your Teams account has all the necessary permissions to make outgoing calls through 3CX? This may require configuration in the 3CX system itself or in the Teams admin panel.
Check if the network is configured correctly and does not block outgoing calls through the ports used by 3CX.

 

[OlegR_3CX]

@UrielFoster There was an issue for Teams, that affected many users. At the time of the message above it was resolved from the Team end infrastructure.