Hi, I think I have resolved the issue.
I reverted my config slightly to having multiple trace_id entries: loadmodule "proto_hep.so" modparam("proto_hep", "hep_id", "[homer_1]<HEP Server IP #1>:9060;transport=udp;version=3;") modparam("proto_hep", "hep_id", "[homer_2]<HEP Server IP #2>:9060;transport=udp;version=3;") loadmodule "siptrace.so" modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_id", "[traceid]uri=hep:homer_1") modparam("siptrace", "trace_id", "[traceid]uri=hep:homer_2") And the sip_trace() call used is: sip_trace("traceid","T","sip"); # stateful mode - in/out transaction With this configuration, the HEP traffic is sent to both destinations! 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. 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. On Mon, 20 Jul 2020 at 09:52, solarmon <solar...@one-n.co.uk> wrote: > Hi, > > So I RTFM'd on the siptrace module ( > https://opensips.org/html/docs/modules/2.4.x/siptrace) and realised that > I had to use the key pair format to define multiple destinations. > > So now my config is: > > > loadmodule "proto_hep.so" > modparam("proto_hep", "hep_id", "[homer_1]<HEP Server IP > #1>:9060;transport=udp;version=3;") > modparam("proto_hep", "hep_id", "[homer_2]<HEP Server IP > #2>:9060;transport=udp;version=3;") > > loadmodule "siptrace.so" > modparam("siptrace", "trace_on", 1) > modparam("siptrace", "trace_id", "[traceid]uri=hep:homer_1;uri=homer_2") > > And the sip_trace() call used is: > > sip_trace("traceid","T","sip"); # stateful mode - in/out > transaction > > > 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. > > So I know that HEP traffic can get each to the destinations - in terms of > routing and access control. > > Why is siptrace not sending to both HEP destinations at the same time? > > On Fri, 17 Jul 2020 at 16:49, solarmon <solar...@one-n.co.uk> wrote: > >> Hi, >> >> 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. >> >> 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. >> >> The config I used for proto_hep was: >> >> loadmodule "proto_hep.so" >> modparam("proto_hep", "hep_id", "[homer]<HEP Server IP >> #1>:9060;transport=tcp;version=3;") >> modparam("proto_hep", "hep_id", "[homer2]<HEP Server IP >> #2>:9060;transport=tcp;version=3;") >> >> The config I used for siptrace was: >> >> loadmodule "siptrace.so" >> modparam("siptrace", "trace_on", 1) >> modparam("siptrace", "trace_id", "[traceid]uri=hep:homer") >> modparam("siptrace", "trace_id", "[traceid2]uri=hep:homer2") >> >> And the sip_trace() call used were: >> >> sip_trace("traceid","T","sip"); # stateful mode - in/out >> transaction >> sip_trace("traceid2","T","sip"); # stateful mode - in/out >> transaction >> >> It is possible/probable that I have a misundertanding of how these >> variables/tokens in the brackets work. >> >> 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 >> >> >> Thank you. >> >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users