[VoiceOps] RPID vs. PAI

[Victor Chukalovskiy]

Best to use PAI across the board and convince your RPID loving carrier 
to change it to PAI. RPID is a failed outdated standard indeed as Alex 
just indicated (similar to 0.0.0.0 SDP hold method :) )

But if you have to, you can not map it one-to-one. RPID has all caller 
ID related info in one line including privacy indicator. While 
P-Asserted-Identity: only carries caller id name / number, and privacy 
is expected in a separate Privacy: header (with somewhat different set 
of values).

So if you were to do it, you need to do some parsing of what you get in 
RPID and re-populate the info into two separate headers (PAI and 
Privacy) and do some mapping of the values along the way. This may or 
may not be implemented well in your equipment.


On 2021-12-20 7:45 p.m., Zilk, David wrote:
>
> I am working with a provider that wants to see PAI and not RPID, 
> however we receive calls from a different provider that sends us RPID. 
> Can I simply copy the RPID header into PAI so that all the necessary 
> screen= and privacy= parameters are preserved when forwarding the call 
> from the second provider to the first?
>
> Is there a better way of going about this?
>
> Thanks for your help.
>
> David
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20211220/661acf53/attachment-0001.htm>