Asterisk : Remote-Party-Id

Asterisk : Remote-Party-Id

If you have set “sendrpid=yes” in the settings for the destination peer in sip.conf then Asterisk will always add an RPI header. Here is a typical example:

Remote-Party-ID: “Satya” <sip:1000@192.168.1.10>;privacy=off;screen=no

The name “Satya” and the number, 1000, get copied from the From header of the inbound call leg. The IP address 192.168.1.10 is the IP of the Asterisk server, but can be over-ridden using the “fromdomain” parameter in the definition of the destination peer in sip.conf.

If you set “trustrpid=yes” in the definition of the source peer in sip.conf, then Asterisk will copy the number from the RPI header (instead of the From header) of the request it received on the inbound call leg.

Sendrpid

Defines whether a Remote-Party-ID SIP header should be sent. Defaults to no.

This field is often used by wholesale VoIP providers to provide calling party identity regardless of the privacy settings (the From SIP header).

trustrpid

This defines whether or not Remote-Party-ID is trusted.

P-Asserted-Identity
Asterisk does nothing when it receives a P-Asserted-Identity header. It ignores it totally no matter what settings you use for “trustrpid” or “sendrpid”. It does not copy it from an inbound call leg to an outbound call leg for a bridged SIP-to-SIP call.