Blocked Caller ID or Privacy

Incoming call to Yeti-Switch has privacy on (meaning Block caller id), but Yeti seems to terminate the call with caller ID, What should PAI setting or config in this case?

Hey Team, Any update or suggestion on this one?

I have also found out the SDP gets filtered from SEMS to CARRIER as it is not passing thru Privacy information to carrier, which is causing the Caller ID to pass instead of being blocked

Here is the SIP trace:

LoadBalancer to SEMS

2020/07/29 12:38:21.363129 Loadbalancer.IP:port -> SEMS.IP:port
INVITE sip:6111111111@Loadbalancer.IP SIP/2.0
Record-Route: <sip:Loadbalancer.IP;lr;ftag=e3a5N6UgNBmZe>
Via: SIP/2.0/UDP Loadbalancer.IP;branch=z9hG4bK0a7c.cc87242949b3d3071245bebd81dddbc4.0
Via: SIP/2.0/UDP RemoteUAS.IP:Port;received=RemoteUAS.IP;rport=Port;branch=z9hG4bKv8ZHgmyHKv4KB
Max-Forwards: 65
From: <sip:611111112@RemoteUAS.IP>;tag=e3a5N6UgNBmZe
To: <sip:6111111111@Loadbalancer.IP>
Call-ID: 68a89485-4be7-1239-8db1-6ef96320167f
CSeq: 23441358 INVITE
Contact: <sip:gw+SBC-Outbound@RemoteUAS.IP:Port;transport=udp;gw=SBC-Outbound>
User-Agent: SBC
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Privacy: id
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 244
X-path-uuid: 912497c4-d144-11ea-9934-15a1390d60d6
X-FS-Support: update_display,send_info
P-Asserted-Identity: <sip:6111111112@RemoteUAS.IP>
X-ORIG-IP: RemoteUAS.IP
X-ORIG-PORT: RemoteUAS:Port
X-ORIG-PROTO: 1

SEMS to Carrier

2020/07/29 12:38:21.505529 SEMS.IP:port -> Carrier.IP
INVITE sip:6111111111@Carrier.IP SIP/2.0
Via: SIP/2.0/UDP SEMS.IP:port;branch=z9hG4bKp0u89aZU;rport
From: <sip:6111111112@SEMS.IP>;tag=12-1D3FDBAE-5F20E11D0007A6B9-04CAF700
To: <sip:6111111111@Carrier.IP>
CSeq: 10 INVITE
Call-ID: 12-258D3320-5F20E11D0007A6BE-04CAF700
Max-Forwards: 70
User-Agent: yeti-switch 1.9.8
Content-Type: application/sdp
Contact: <sip:SEMS.IP:port;transport=udp>
Content-Length: 508

v=0
o=yeti-switch 1595967163 1595967164 IN IP4 SEMS.IP
s=yeti-switch
c=IN IP4 SEMS.IP
t=0 0
m=audio 16383 RTP/AVP 0 96 97 98 18 101 99 8 100 2 3 102
c=IN IP4 SEMS.IP
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-16/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:98 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=rtpmap:99 G726-40/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:100 G726-24/8000
a=rtpmap:2 G721/8000
a=rtpmap:3 GSM/8000
a=rtpmap:102 L16/8000
a=ptime:20
a=sendrecv

https://yeti-switch.org/docs/en/headers-filtering.html

I have also found out the SDP gets filtered from SEMS to CARRIER

What do you mean under “SDP gets filtered”?

Filtering in a sense that SDP are somewhat manipulated on the last leg between the SEMS and Carrier

as you can see the Invite from the LoadBalancer to SEMS had a particular field called:
Privacy: id
But from SEMS to carrier, that field has been removed/cleared

but nevertheless,I have found an work around solution to this issue and will be planning to implement that given that now I understand Yeti Switch better from before :slight_smile: Thank you for your help @dmitry.s

Filtering in a sense that SDP are somewhat manipulated on the last leg between the SEMS and Carrier

SIP headers is not SDP.

have you read https://yeti-switch.org/docs/en/headers-filtering.html ?

Yes, I have read it, it is great but how do i use it?

I need to pass-thru privacy parameter from origination to termination
Is that how we configure it,refer to image below or could you please let me know how to use it