[OpenSIPS-Users] HEP Address Hostname error

[Bogdan-Andrei Iancu]

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 <Ben.Newlin at genesys.com>
>> *Date: *Friday, March 30, 2018 at 10:15 AM
>> *To: *OpenSIPS users mailling list <users at lists.opensips.org>
>> *Subject: *Re: HEP Address Hostname error
>>
>> Has anyone had a chance to look into this DNS issue?
>>
>> Thanks,
>>
>> Ben Newlin
>>
>> *From: *Ben Newlin <Ben.Newlin at genesys.com>
>> *Date: *Monday, March 26, 2018 at 4:02 PM
>> *To: *OpenSIPS users mailling list <users at lists.opensips.org>
>> *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")
>>
>> 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
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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