[h323plus] Previous bug report...
jan at willamowius.de
Wed Nov 13 04:58:42 EST 2013
what I fixed was a different issue where H323Plus endpoints wouldn't
try to re-register. Francisco issue is which endpoint id is used.
I can reproduce the issue Francisco reports with GnuGk when I set
AcceptEndpointIdentifier=0. With that setting H323Plus endpoints will
keep sending their old endpoint identifier, even if the gatekeeper
assigned them a new identifier after a full RRQ.
I believe the change in gkclient.cxx should be reverted so the
endpointIdentifier provided by the gatekeeper in RCF should
unconditionally be used, not only if the id was empty before.
If there still is an issue with alternate gatekeepers, it should
probably be solved differently.
Jan Willamowius, Founder of the GNU Gatekeeper Project
EMail : jan at willamowius.de
Simon Horne wrote:
> I think the bug was fixed here by Jan. Did you test this?
> It will retry until registration can be re-established.
> The changes you mentioned below were to fix an issue when using alternate
> -----Original Message-----
> From: h323plus-bounces at lists.packetizer.com
> [mailto:h323plus-bounces at lists.packetizer.com] On Behalf Of Francisco Olarte
> Sent: 12 November 2013 22:40
> To: h323plus
> Subject: [h323plus] Previous bug report...
> Hello everyone.
> In my previous mail I blamed my problems on commit
> while it seems is due to a combination of that and the previous one:
> It seem the endpointdidentifier assignement was removed in the 1.23 rev (
> although the comment talks about gatekeeper identifier ) and reinstated
> conditionalized in 1.24 ( which comment i do not fully understand, seems
> like a partial revert of the previous one ).
> Francisco Olarte
More information about the h323plus