Unable to get inbound call from cisco phone ring within teams application

Question

Unable to get inbound call from cisco phone ring within teams application

khznm 21 1

i have teams integration with cisco sbc4431 done , but inbound call to team app is not working..

i have SNR ( simultenous ring) setup in cisco cucm, any call to 2947111 should ring on both cisco phone and teams client user on which +2947111 is associated , cisco phone rings, but not teams client. traces in sbc shows calls routing it to sip.pstnhub.micosoft.com

Sent:
INVITE sip:+2947111@Sip .pstnhub.microsoft.com:5061;user=phone SIP/2.0
Via: SIP/2.0/TLS 10.179.5.72:5061;branch=z9hG4bK23A622E3
From: "2233000" <sip:******@csbc.xyx..com>;tag=29504485-1D70
To: <sip:+2947111@Sip .pstnhub.microsoft.com>

and also the error msg

Received:
SIP/2.0 488 Not Acceptable Here
FROM: "2233000"<sip:******@csbc.xyx.com>;tag=29504485-1D70
TO: <sip:+2947111@Sip .pstnhub.microsoft.com>;tag=01d8e452e14f410695eb7f808996b79f
CSEQ: 101 INVITE
CALL-ID: ******@csbc.xyx.com
VIA: SIP/2.0/TLS 10.179.5.72:5061;branch=z9hG4bK23A622E3
REASON: Q.850;cause=79;text="c4f42fed-cb82-4527-9cc5-ba61e792dfb2;InternalDiagCode: RtcpAddressDoesNotEqualRtpAddress, InternalErrorPhrase: RTCP IP address must be the same as the RTP address"
RECORD-ROUTE: <sip:sip-du-a-eu.pstnhub.microsoft.com:5061;transport=tls;lr>
CONTACT: <sip:api-du-c-euwe.pstnhub.microsoft.com:443;x-i=c4f42fed-cb82-4527-9c

Expert have any solution to this issue.

Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-11-19T02:29:39.257+00:00
@khznm 21 ,

If you’re an administrator, you can use the following diagnostic tool to validate that a user is correctly configured for Direct Routing:

Open Run Tests: Direct Routing, which will populate the diagnostic in the Microsoft 365 admin center.

In the Run diagnostic pane, enter the email of the user you want to test in the Username or Email field, and then select Run Tests as below:

The tests will return the best next steps to address any tenant, user, or policy configurations to validate that the user is properly configured for Direct Routing in Microsoft Teams.

For more details, please refer to Direct Routing Diagnostic Tool section in this article.

Moreover, you can go to Health Dashboard for Direct Routing to check if there is any information between your SBC and the Direct Routing interface. Then, we could identify issues, including reason for dropped calls. For more information, please focus on Overall health part in this link.
Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-11-24T08:37:09.93+00:00

@khznm 21 ,

Do you have a chance to check with Direct Routing Diagnostic Tool?

Please feel free to drop us ant notes.

Wish all the best!

1 answer

Your answer

Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-11-19T02:29:39.257+00:00

@khznm 21 ,

If you’re an administrator, you can use the following diagnostic tool to validate that a user is correctly configured for Direct Routing:

Open Run Tests: Direct Routing, which will populate the diagnostic in the Microsoft 365 admin center.

In the Run diagnostic pane, enter the email of the user you want to test in the Username or Email field, and then select Run Tests as below:

The tests will return the best next steps to address any tenant, user, or policy configurations to validate that the user is properly configured for Direct Routing in Microsoft Teams.

For more details, please refer to Direct Routing Diagnostic Tool section in this article.

Moreover, you can go to Health Dashboard for Direct Routing to check if there is any information between your SBC and the Direct Routing interface. Then, we could identify issues, including reason for dropped calls. For more information, please focus on Overall health part in this link.
Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-11-24T08:37:09.93+00:00

@khznm 21 ,

Do you have a chance to check with Direct Routing Diagnostic Tool?

Please feel free to drop us ant notes.

Wish all the best!

Answer 1

Bai, Andy 241

Hi,

As the log mentioned,

REASON: Q.850;cause=79;text="c4f42fed-cb82-4527-9cc5-ba61e792dfb2;InternalDiagCode: RtcpAddressDoesNotEqualRtpAddress, InternalErrorPhrase: RTCP IP address must be the same as the RTP address"

If you use NAT to translate your SBC'private address to public, you need to make sure RTP and SRTP has the same address. You need to change the sdp-header Audio-Attribute for request and response in outbound dial-peer to ms teams.

   !This one changes the IP Address for the RTCP connection

rule 100 request ANY sdp-header Audio-Attribute modify "SBC_private_address" "SBC_Public_IP"
!This one changes the IP Address for the RTCP connection
rule 110 response ANY sdp-header Audio-Attribute modify "SBC_private_address" "SBC_Public_IP

Thanks.

Bai, Andy 241 Reputation points

2021-11-24T07:53:13.857+00:00

@khznm 21
how is it going on about this issue? Have you fixed it?
Bai, Andy 241 Reputation points

2021-11-30T02:05:19.493+00:00

@ khznm21-7771

This is your issue, have you fixed it?

Share via

Unable to get inbound call from cisco phone ring within teams application

1 answer

Your answer