Hi Ben,
So, from siptracemodule, you have multiple options in terms of what to
do with the traced data:
* you can duplicate it via SIP
* you can dump it into DB
* you can packit over HEP for Homer
This is controlled via trace_id parameter in siptrace module.
Now, next step: if you decided for HEP, you need the proto_hep module
where you have to define the Homer servers where the HEP data is to be
sent - see the "hep_id" parameter.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 04/04/2018 06:24 PM, Ben Newlin wrote:
Bogdan,
That is very good to know. I thought the siptrace module was using HEP.
But still, if I want to switch to HEP in the future, which I do, I
need to be able to properly use a domain name in the proto_hep config.
Any idea why that is not working as I described originally?
Thanks,
Ben Newlin
*From: *Bogdan-Andrei Iancu <[email protected]>
*Date: *Wednesday, April 4, 2018 at 10:56 AM
*To: *OpenSIPS users mailling list <[email protected]>, Ben
Newlin <[email protected]>
*Subject: *Re: [OpenSIPS-Users] HEP Address Hostname error
OK, it was a quick one :D...
The "duplicate_uri" from 1.11 was duplicating the traffic via SIP, not
via HEP, so if you want to translate this setting, it has nothing to
do with the proto_hep module, but still with the siptrace module like:
/*sip trace id*/
modparam("siptrace", "trace_id",
"[tid]uri=sip:homer-hep.test.com:5656")
and use "tid" as tracing ID in the sip_trace function.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 04/04/2018 05:50 PM, Bogdan-Andrei Iancu wrote:
Hi Ben,
Let me look quickly into this ;)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 04/04/2018 05:49 PM, Ben Newlin wrote:
Bumping this again. I can open a bug on Github if that is
preferred.
Thanks,
Ben Newlin
*From: *Ben Newlin <[email protected]>
<mailto:[email protected]>
*Date: *Friday, March 30, 2018 at 10:15 AM
*To: *OpenSIPS users mailling list <[email protected]>
<mailto:[email protected]>
*Subject: *Re: HEP Address Hostname error
Has anyone had a chance to look into this DNS issue?
Thanks,
Ben Newlin
*From: *Ben Newlin <[email protected]>
<mailto:[email protected]>
*Date: *Monday, March 26, 2018 at 4:02 PM
*To: *OpenSIPS users mailling list <[email protected]>
<mailto:[email protected]>
*Subject: *HEP Address Hostname error
Hi,
While upgrading from 1.11 to 2.3, we have run into an issue
with the parsing of the hep_id parameter in the proto_hep module.
In 1.11, we used the duplicate_uri setting in the siptrace
module like so:
modparam("siptrace", "duplicate_uri",
"sip:homer-hep.test.com:5656"<sip:homer-hep.test.com:5656>)
In 2.3, we converted this into the appropriate module config
for proto_hep:
modparam("proto_hep", "hep_id",
"[hid]homer-hep.test.com:5656;transport=udp;version=2")
However, this results in OpenSIPS complaining about receiving
the wrong address:
Mar 26 19:59:58 [332] CRITICAL:core:mk_proxy: could not
resolve hostname: "homer"
Mar 26 19:59:58 [332] ERROR:proto_hep:send_hep_message: bad
hep host name!
Mar 26 19:59:58 [332]
ERROR:siptrace:send_trace_proto_duplicate: failed to forward
message to destination!
Mar 26 19:59:58 [332] ERROR:siptrace:save_siptrace: Failed to
duplicate with hep to <homer:5656>
It appears the proto_hep module parameter parsing doesn’t
allow for dashes/hyphens in the address portion, so it ends up
with only a small part of the actual hostname of our Homer server.
Thanks,
Ben Newlin
_______________________________________________
Users mailing list
[email protected]<mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]<mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
