Asterisk SIP trustrpid

trustrpid

This defines whether or not Remote-Party-ID is trusted. It’s defined in http://tools.ietf.org/id/draft-ietf-sip-privacy-04.txt

Usage

The following summarises information taken from Part 2 of this May 2010 blog post, based on testing v1.6:
https://kb.smartvox.co.uk/asterisk/how-it-works/caller-id-in-sip-and-asterisk-part-1/
https://kb.smartvox.co.uk/asterisk/how-it-works/caller-id-in-sip-and-asterisk-part-2/

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.

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: “Johns Linksys” <sip:[email protected]>;privacy=off;screen=no

The name “Johns Linksys” and the number, 1001, get copied from the From header of the inbound call leg. The IP address 192.168.1.15 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.

Privacy

Asterisk respects the privacy setting in the RPI header it receives (if there is an RPI header in the request) irrespective of any setting for “trustrpid”. You can change Privacy field by using SetCallerPres() function.

See also

• Asterisk sip sendrpid