SOLVED

Outbound calls from teams, Caller-ID not working, shows as "Restricted"

Contributor

We're running an audiocodes SBC with direct routing set up.  Currently anyone in our Teams PSTN test group shows up as "restricted" to the party they're calling.

 

Our Global policy looks fine: 

 

PS C:\Scripts> Get-CsCallingLineIdentity


Identity : Global
Description :
EnableUserOverride : False
ServiceNumber :
CallingIDSubstitute : LineUri
BlockIncomingPstnCallerID : False

 Only odd thing I see in the SIP invite from Teams is "Privacy: id" is being sent.

 

09:15:26.985 ---- Incoming SIP Message from 52.114.148.0:3392 to SIPInterface #1 (Teams) TLS TO(#123) SocketID(469568) ---- [Time:01-11@08:15:26.124]

 

INVITE sip:+15032016242@bvtsbc.biamp.com:5068;transport=tls SIP/2.0

FROM: Ron Prague<sip:+15037189158@sip.pstnhub.microsoft.com:5061;user=phone>;tag=00763c3ad16d4c77a728e9c8d69669f8

TO: <sip:+15032016242@bvtsbc.biamp.com:5068>

CSEQ: 1 INVITE

CALL-ID: 2769353d73b7409d92e8d1834e7ec216

MAX-FORWARDS: 70

VIA: SIP/2.0/TLS 52.114.148.0:5061;branch=z9hG4bK485bde5

RECORD-ROUTE: <sip:sip-du-a-us.pstnhub.microsoft.com:5061;transport=tls;lr>

CONTACT: <sip:api-du-c-usea.pstnhub.microsoft.com:8000;transport=tls;x-i=3f74ad0b-85e0-43e1-8c01-9932b7b3ad25;x-c=/v1/ngc/call/2769353d73b7409d92e8d1834e7ec216/d/8/0c0d5fe1e3e749f892cd7095ec2e09b6>

CONTENT-LENGTH: 1116

USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2018.10.22.2 i.USWE2.4

CONTENT-TYPE: application/sdp

ALLOW: INVITE

ALLOW: ACK

ALLOW: OPTIONS

ALLOW: CANCEL

ALLOW: BYE

ALLOW: NOTIFY

P-ASSERTED-IDENTITY: <tel:+15037189158>,<sip:ron.prague@biamp.com>

PRIVACY: id

 

I can't find any way to make sure that's not being sent.  I don't think it should be.

 

I'm sure I can do an inbound manipulation in the SBC, but I'd rather not.

 

 

3 Replies
best response confirmed by Ron Prague (Contributor)
Solution

If you configured the csOnlinePSTNGateway (Direct Routing) with -ForwardPAI $true, Microsoft will include the Privacy Header. There should be some info in the AudioCodes documentation on how to remove the privacy restriction or you can change the gateway to have -ForwardPAI $false.

Thank you Michael, looks like I did set -ForwardPAI as $true, going to change that now and retest!

Section 2.19 (page 37 of version 7.2) of the official Audiocodes documentation for Direct Routing has the steps needed to override PAI.  You could choose to leave PAI in place on the trunk and then just strip it off at the SBC, for the particular IP Profile assigned to your internal IP Group.

www.000webhost.com