[OpenSIPS-Users] HEP Address Hostname error

Bogdan-Andrei Iancu bogdan at opensips.org
Wed Apr 4 13:41:15 EDT 2018


OK, backported, thanks for the confirmation !

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 08:36 PM, Ben Newlin wrote:
>
> Bogdan,
>
> Yes, this patch does work. The full URI is now being processed. Thanks!
>
> Thanks,
>
> Ben Newlin
>
> *From: *Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Date: *Wednesday, April 4, 2018 at 12:08 PM
> *To: *Ben Newlin <Ben.Newlin at genesys.com>, OpenSIPS users mailling 
> list <users at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Users] HEP Address Hostname error
>
> Oh...you mentioned in the first email that you are looking to migrate 
> the "duplicate_uri" from 1.11 to something 2.3 specific. This is why I 
> pointed out the SIP based tracing.
>
> Now, checking the hep_id parser, I guess it does not expect the '-' 
> char in the URI part - could you check out this patch 
> https://github.com/OpenSIPS/opensips/commit/ba2840639777d797889e4a3a74c0b56f02ce9aba 
> please? if this fix the problem, I can do a backport.
>
> 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:50 PM, Ben Newlin wrote:
>
>     Bogdan,
>
>     Yes, that is what I have done, as I detailed originally. I am
>     configuring the hep_id in the proto_hep module like this:
>
>     modparam("proto_hep", "hep_id",
>     "[hid]homer-hep.test.com:5656;transport=udp;version=2")
>
>     But the module is not using the full URI I provided. I get the
>     following errors:
>
>     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 seems to be discarding everything in the URI after the dash.
>
>     Thanks,
>
>     Ben Newlin
>
>     *From: *Bogdan-Andrei Iancu <bogdan at opensips.org>
>     <mailto:bogdan at opensips.org>
>     *Date: *Wednesday, April 4, 2018 at 11:37 AM
>     *To: *Ben Newlin <Ben.Newlin at genesys.com>
>     <mailto:Ben.Newlin at genesys.com>, OpenSIPS users mailling list
>     <users at lists.opensips.org> <mailto:users at lists.opensips.org>
>     *Subject: *Re: [OpenSIPS-Users] HEP Address Hostname error
>
>     Hi Ben,
>
>     So, from siptrace module, 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 pack it 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
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180404/977f861f/attachment.html>


More information about the Users mailing list