Stefan Sayer writes:
> in your case, trans_layer::set_next_hop is called, which means the
> next hop is definitely not set. Can you please apply this small debug
> info output and run again? I would definitely like to know how
> next_hop_ip is reset in your case, as there's no place in the code
> that touches it.
stefan,
perhaps NextHop patch was not included in my source. i applied it to my
git 1.4 source, but then my build script does:
git archive origin/1.4 | (cd $ROOT/$DIR-src/openxg-sems && tar xf -
--exclude-vcs)
and i get to console:
Already on '1.4'
Your branch is ahead of 'origin/1.4' by 1 commit.
so looks like git archive does not use the cherry pick that i have
done, because when i do grep this in my git dir, i get:
$ egrep NextHop *.cpp
AmConfig.cpp:string AmConfig::NextHopIP = "";
AmConfig.cpp:unsigned int AmConfig::NextHopPort = 0;
AmConfig.cpp:bool AmConfig::NextHopForReplies = false;
AmConfig.cpp: NextHopIP = cfg.getParameter("next_hop_ip");
AmConfig.cpp: NextHopPort = cfg.getParameterInt("next_hop_port", 0);
AmConfig.cpp: NextHopForReplies = (cfg.getParameter("next_hop_for_replies")
== "yes");
AmSipDialog.cpp: next_hop_port(AmConfig::NextHopPort),
AmSipDialog.cpp: next_hop_ip(AmConfig::NextHopIP),
AmSipDialog.cpp: next_hop_for_replies(AmConfig::NextHopForReplies),
but when i do the same in the dir where git archive placed the source, i
get nothing.
i don't know enough about git in order to proceed with this.
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
