Fixing bug in S1 Setup response.

7 years ago · a7b540c18e
parent bdc72c65c4
commit a7b540c18e
2 changed files with 4 additions and 2 deletions
--- a/srsepc/src/main.cc
+++ b/srsepc/src/main.cc
@ -204,6 +204,7 @@ parse_args(all_args_t *args, int argc, char* argv[]) {
  }
  args->mme_args.s1ap_args.mme_bind_addr = mme_bind_addr;
  args->mme_args.s1ap_args.mme_name = mme_name;
  args->spgw_args.gtpu_bind_addr = spgw_bind_addr;
  args->spgw_args.sgi_if_addr = sgi_if_addr;
  args->hss_args.db_file = hss_db_file;
--- a/srsepc/src/mme/s1ap_mngmt_proc.cc
+++ b/srsepc/src/mme/s1ap_mngmt_proc.cc
@ -102,6 +102,7 @@ s1ap_mngmt_proc::handle_s1_setup_request(LIBLTE_S1AP_MESSAGE_S1SETUPREQUEST_STRU
    {
      //eNB already registered
      //TODO replace enb_ctx
      m_s1ap_log->warning("eNB Already registered\n");
    }
    else
    {