Difference between revisions of "M4 PAI And RPID Header Generation"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(2 intermediate revisions by 2 users not shown)
Line 16: Line 16:
  <sip:3701234567@myhost.sip> - simple static generation.
  <sip:3701234567@myhost.sip> - simple static generation.
  <sip:anonymous@anonymous.invalid> - simple static generation.
  <sip:anonymous@anonymous.invalid> - simple static generation.
  <sip:$fU@myhost.sip> - using Kamailio variable $fU to generate header with value from SIP FROM header
  <sip:$fU@myhost.sip> - using Kamailio variable $fU to generate a header with the original value from SIP FROM header


=See also=
=See also=


* [[M2_Origination_Points | M2 Origination Points]]
* [[M4 RPID/PAI]] Forwarding/Host changing
* [[M2_Termination_Points| M2 Termination Points]]
* [[M4 Origination Points]]
* [[M4 Transformations | M4 Transformations]]
* [[M4 Termination Points]]
* [[M4 Transformations]]

Latest revision as of 09:24, 7 February 2023

M4 can generate P-Asserted-Identity (PAI) and Remote-Party-ID (RPID) headers

Usage

Go to Users -> Connection Points, click EDIT on Connection Point. PAI/RPID Transformations are located under Termination Point Signaling Settings.

Rpid pai to tp generation.png

Generation can happen under Generate if missing and Overwrite tabs.

Generation format

Generation string should be either:

Examples

<sip:3701234567@myhost.sip> - simple static generation.
<sip:anonymous@anonymous.invalid> - simple static generation.
<sip:$fU@myhost.sip> - using Kamailio variable $fU to generate a header with the original value from SIP FROM header

See also