<p>If you want to use crypto hashing from libcrypto, the best way to do it is to add what you need to crypto module and then have an option via modparam in rtpengine module to bind to crypto module and use that function. Otherwise, it should be using the internal hashing function (can be changed from what is doing now with another hash function from those available in the core).</p>
<p>Not exactly the same, but a similar solution was made for having better "random" call-id for requests generated by Kamailio. That is done also via "crypto" module, but setting some core callback, instead of exporting an intermodule API. See this parameter:</p>
<ul>
<li><a href="https://www.kamailio.org/docs/modules/stable/modules/crypto.html#crypto.p.register_callid" rel="nofollow">https://www.kamailio.org/docs/modules/stable/modules/crypto.html#crypto.p.register_callid</a></li>
</ul>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1911#issuecomment-477270986">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZQtW_jCBzZ0bhamIQEOeGm8_Zz8Lks5va6vJgaJpZM4cOQFl">mute the thread</a>.<img src="https://github.com/notifications/beacon/AF36ZdEJpWHUhdV58l4S_NzXTjbhyP4vks5va6vJgaJpZM4cOQFl.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@miconda in #1911: If you want to use crypto hashing from libcrypto, the best way to do it is to add what you need to crypto module and then have an option via modparam in rtpengine module to bind to crypto module and use that function. Otherwise, it should be using the internal hashing function (can be changed from what is doing now with another hash function from those available in the core).\r\n\r\nNot exactly the same, but a similar solution was made for having better \"random\" call-id for requests generated by Kamailio. That is done also via \"crypto\" module, but setting some core callback, instead of exporting an intermodule API. See this parameter:\r\n\r\n  * https://www.kamailio.org/docs/modules/stable/modules/crypto.html#crypto.p.register_callid\r\n\r\n"}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1911#issuecomment-477270986"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/issues/1911#issuecomment-477270986",
"url": "https://github.com/kamailio/kamailio/issues/1911#issuecomment-477270986",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>