Difference between revisions of "SIP Header Manipulation"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(One intermediate revision by one other user not shown)
Line 10: Line 10:
= M4 =
= M4 =


* [[M4 Header Transformation Rules Groups]]
* [[M4 Source Transformation | CallerID]] and [[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
Line 23: Line 24:
* Can we add a Custom SIP header in Origination Point settings? I need each OP to send a unique Custom SIP header.
* Can we add a Custom SIP header in Origination Point settings? I need each OP to send a unique Custom SIP header.


No, this is not possible currently. However, there's a development request for this (internal link for Kolmisoft users): https://support.kolmisoft.com/cd_requests/view/384
No, this is not possible currently. However, there's a development request for this. An internal link for Kolmisoft users: https://support.kolmisoft.com/cd_requests/view/384

Latest revision as of 06:52, 12 March 2024

MOR



M4



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.

  • Can we add a Custom SIP header in Origination Point settings? I need each OP to send a unique Custom SIP header.

No, this is not possible currently. However, there's a development request for this. An internal link for Kolmisoft users: https://support.kolmisoft.com/cd_requests/view/384