<div><span style>Hello,</span></div><div><span style><br></span></div><div><span style>I've been asked to move this feature request to this mailing list instead of using issue tracker. So, here I go...</span></div><span style><div>
<span style><br></span></div>Normally I tend to set systemname to the server's hostname, which makes asterisk generate uniqueids like hostname-XXXXXXX. Something which helps tracing calls, specially on multi-node setups. </span><span style>However, we've found that this is a problem as it provokes duplicated linkedid entries on our CDRs, which is caused by the fact that the internal linkedid field used by asterisk is 32 chars, while uniqueid is 150. (See: </span><a href="http://www.asterisk.org/doxygen/trunk/cdr_8h-source.html#l00124" target="_blank" style>http://www.asterisk.org/doxygen/trunk/cdr_8h-source.html#l00124</a><span style>) </span><div>
<span style><br></span></div><div><span style>This 32 chars limit on linkedid make forces asterisk to truncate them when systemname is long enough (~20 chars).. Is there any reason not to extend linkedid length to at least 150 chars like uniqueid?</span>
</div><div><span style><br></span></div><div><span style>As said I created a feat. request (</span><a href="https://issues.asterisk.org/jira/browse/ASTERISK-19766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192083#comment-192083" target="_blank" style>https://issues.asterisk.org/jira/browse/ASTERISK-19766</a>), but looks like this is a better place to discuss this matter.. Opinions? ;)</div>
<div><br></div><div>Regards</div><div>Pablo</div>