From 8e1c07308c10abd6aab7c8fb32efd6eed6875f7c Mon Sep 17 00:00:00 2001 From: Neels Hofmeyr Date: Mon, 20 Nov 2017 16:57:29 +0100 Subject: [PATCH] osmo-hnbgw: drop erratic log line on remote STP address The stp_host is just the *default* that may be overridden by the VTY configuration. Don't log it as the one that is going to be used. It's not trivial to print the actual IP address being used, there may be any number of ASP, theoretically. Hence leave logging up to osmo_sccp_simple_client_on_ss7_id(), after another hypothetical patch. Change-Id: Ia438143606913faccc8cdf4fd5f7d376f93e7891 --- src/hnbgw_cn.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/hnbgw_cn.c b/src/hnbgw_cn.c index 3b828b44..81ef6704 100644 --- a/src/hnbgw_cn.c +++ b/src/hnbgw_cn.c @@ -474,8 +474,6 @@ int hnbgw_cnlink_init(struct hnb_gw *gw, const char *stp_host, uint16_t stp_port local_pc = ss7->cfg.primary_pc; osmo_sccp_make_addr_pc_ssn(&gw->sccp.local_addr, local_pc, OSMO_SCCP_SSN_RANAP); - - LOGP(DRANAP, LOGL_NOTICE, "M3UA uplink to STP: %s %u\n", stp_host, stp_port); LOGP(DRANAP, LOGL_NOTICE, "Local SCCP addr: %s\n", osmo_sccp_addr_name(ss7, &gw->sccp.local_addr)); gw->sccp.client = osmo_sccp_simple_client_on_ss7_id(gw, ss7->cfg.id, "OsmoHNBGW",