Has anyone had a chance to look into this DNS issue? Thanks, Ben Newlin
From: Ben Newlin <[email protected]> Date: Monday, March 26, 2018 at 4:02 PM To: OpenSIPS users mailling list <[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") 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] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
