Difference between revisions of "SIP Header Manipulation"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 10: | Line 10: | ||
= M4 = | = M4 = | ||
* [[M4 Source Transformation | CallerID]] [[M4 Destination Transformation | Destination]] transformations | * [[M4 Source Transformation | CallerID]] and [[M4 Destination Transformation | Destination]] transformations | ||
* [[M4 Disconnect Codes]] allows changing the Reason Header and SIP Disconnect Codes | * [[M4 Disconnect Codes]] allows changing the Reason Header and SIP Disconnect Codes | ||
* [[M4_Kamailio_Transformations| Transformation]] \ [[M4 PAI And RPID Header Generation | Generation]] of P-Asserted-Identity (PAI) and Remote-Party-ID (RPID) headers | * [[M4_Kamailio_Transformations| Transformation]] \ [[M4 PAI And RPID Header Generation | Generation]] of P-Asserted-Identity (PAI) and Remote-Party-ID (RPID) headers |
Revision as of 09:55, 7 February 2023
This page will be updated soon.
MOR
- Number Manipulation allows changing CallerID and Destination numbers
- Hangup Cause Code changing
- Sending/Passing-through Custom headers
M4
- CallerID and Destination transformations
- M4 Disconnect Codes allows changing the Reason Header and SIP Disconnect Codes
- Transformation \ Generation of P-Asserted-Identity (PAI) and Remote-Party-ID (RPID) headers
- Sending/Passing-through Custom headers
FAQ
- Can we convert or rewrite each SIP header sequentially new (inbound) before calls are processed in routing and can we adjust all SIP headers also outbound depending on carrier accordingly?
No, this is not possible. Only outlined above transformations are possible. Not with ALL the headers.