Anonymous Assert PAI for Unknown caller ID

I am trying to send call from gateway A with the hidden caller ID although the pai sends in the caller ID but the termination gateway does not receive the caller ID. on my end I checked the log it shows the pai with caller ID from sender but on the pai out it shows anonymous.

how do I send the pai in received to the termination gateway even though the sender sending with unknown number but pai information intact @dmitry.s


@dmitry.s @admins please can you assist with this

Read about paid send mode in documentation Gateways — Yeti documentation

I read through and also the gateway headers are set with the Pai also under translation it is set to trusted and forwarded yet. The termination gateway sees anonymous on the pai even though pai in comes in with the CLI


So you configured yeti to build pai header from source number and it doing exactly this

Yes it is doing exactly this even when configured to build pai header from source number..

Pai In sip:9000000@A.A.A.A;transport=udp;user=phone
Ppi In Empty
Privacy In id
Rpid In Empty
Rpid Privacy In Empty
Pai Out sip:anonymous@A.A.A.A;user=phone

So src number is anonymous and you configured yeti to use it to build pai header. So everything works according to documentation

Oh thank you it was fixed by changing that

Hi dmitry I tried using the relay pai/ppi it forwarded the right sip message but this time it displayed the unknown number at the destination phone… What I wanted was for the destination phone to see unknown caller or anonymous while the termination gateway sees the pai with the exact info

Yeti can’t control what displayed by destination phone. Yeti configuration only affects how yeti sends call to termination gateway, so if it sent something wrong - you have to provide examples what was sent and what you expecting there.

Ok. I sent the pai send to relay pai/ppi and the privacy to do nothing… the termination gateway can now see the pai info as received from the originator but at the phone it shows the caller ID even though the originator sent a private caller ID.
What is expected is for the termination gateway to receive this calls with the pai as received from the originator showing its number and also at the destination phone it shows unknown caller ID

Is your privacy header being sent correctly? Need to inspect the CDR Privacy Information tab and perhaps SIP headers and make sure it is being sent and in the right format.

If it is set correctly and the real phone number is still getting through to the destination phone, that means your termination gateway isn’t respecting the Privacy header and anonymizing the call like it should. You’ll need to take that up with whoever manages your termination gateway.

You have to ask termination side about these expectations.

In yeti you can control only what system sending to termination gateway. So if you think something wrong there - show trace and share your expectation what system should send. What displayed on end-user side is not yeti responsibility.