<div dir="ltr"><div dir="ltr"><br></div><div dir="ltr">Hi,<div><br></div><div>I think I have resolved the issue.</div><div><br></div><div>I reverted my config slightly to having multiple
trace_id entries:</div><div><br></div><div><br></div><div><div>loadmodule "proto_hep.so"<br></div><div>modparam("proto_hep", "hep_id", "[homer_1]<HEP Server IP #1>:9060;transport=udp;version=3;")<br>modparam("proto_hep", "hep_id", "[homer_2]<HEP Server IP #2>:9060;transport=udp;version=3;")<br></div><div><br></div><div>loadmodule "siptrace.so"<br>modparam("siptrace", "trace_on", 1)<br>modparam("siptrace", "trace_id", "[traceid]uri=hep:homer_1")<br></div><div>modparam("siptrace", "trace_id", "[traceid]uri=hep:homer_2") <br></div><div><br></div><div>And the sip_trace() call used is:</div><div><br></div><div>sip_trace("traceid","T","sip"); # stateful mode - in/out transaction</div></div><div><br></div><div><br></div><div>With this configuration, the HEP traffic is sent to both destinations!</div><div><br></div><div>I think the difference compared to my OP was that I was using TCP for the first hep_id Homer server - even though the OP showed I had it for both, my actual config only had TCP for the first entry.</div><div><br></div><div>A previous mailing list email (and subsequent github ticket) from me about getting Homer 7 to work resulted in showing that it was only worked with UDP, and not with TCP.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 20 Jul 2020 at 09:52, solarmon <<a href="mailto:solarmon@one-n.co.uk">solarmon@one-n.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<br><div><br></div><div>So I RTFM'd on the siptrace module (<a href="https://opensips.org/html/docs/modules/2.4.x/siptrace" target="_blank">https://opensips.org/html/docs/modules/2.4.x/siptrace</a>) and realised that I had to use the key pair format to define multiple destinations.</div><div><br></div><div>So now my config is:</div><div><br></div><div><br></div><div><div>loadmodule "proto_hep.so"<br></div><div>modparam("proto_hep", "hep_id", "[homer_1]<HEP Server IP #1>:9060;transport=udp;version=3;")<br>modparam("proto_hep", "hep_id", "[homer_2]<HEP Server IP #2>:9060;transport=udp;version=3;")<br></div><div><br></div><div>loadmodule "siptrace.so"<br>modparam("siptrace", "trace_on", 1)<br>modparam("siptrace", "trace_id", "[traceid]uri=hep:homer_1;uri=homer_2")<br></div><div><br></div><div>And the sip_trace() call used is:</div><div><br></div><div>sip_trace("traceid","T","sip"); # stateful mode - in/out transaction<br></div></div><div><br></div><div><br></div><div>However, it seems that the HEP traffic is only ever sent to the second/last uri defined. I can swap the uri's and the HEP traffic will only ever go to the second/last uri defined.</div><div><br></div><div>So I know that HEP traffic can get each to the destinations - in terms of routing and access control.</div><div><br></div><div>Why is siptrace not sending to both HEP destinations at the same time?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 17 Jul 2020 at 16:49, solarmon <<a href="mailto:solarmon@one-n.co.uk" target="_blank">solarmon@one-n.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<br><div><br></div><div>I was able to get siptrace sent to a single HEP server. Now I would like to be able to send to a secondary server as an additional destination.</div><div><br></div><div>I thought I could just create additional hep_id and trace_id entries and run sip_trace() twice, but this didn't work and only the second HEP server received traffic.</div><div><br></div><div>The config I used for proto_hep was:</div><div><br></div><div>loadmodule "proto_hep.so"<br>modparam("proto_hep", "hep_id", "[homer]<HEP Server IP #1>:9060;transport=tcp;version=3;")<br>
modparam("proto_hep", "hep_id", "[homer2]<HEP Server IP #2>:9060;transport=tcp;version=3;")
<br></div><div><br></div><div>The config I used for
siptrace
was: <br></div><div> <br></div><div>loadmodule "siptrace.so"<br>modparam("siptrace", "trace_on", 1)<br>modparam("siptrace", "trace_id", "[traceid]uri=hep:homer")<br>modparam("siptrace", "trace_id", "[traceid2]uri=hep:homer2")<br></div><div><br></div><div>And the sip_trace() call used were:</div><div><br></div><div>sip_trace("traceid","T","sip"); # stateful mode - in/out transaction<br>sip_trace("traceid2","T","sip"); # stateful mode - in/out transaction<br></div><div><br></div><div>It is possible/probable that I have a misundertanding of how these variables/tokens in the brackets work.</div><div><br></div><div>Please can somebody provide, or point me to, an example of how this multiple HEP server destinations could be achieved, assuming it can be done</div><div><br></div><div><br></div><div>Thank you. </div></div>
</blockquote></div>
</blockquote></div></div>