Hi Walter, I don't think GnuGk 'steals' your destination IP. ;-) When GnuGk receives the ARQ, it prints it out as it got it before starting any rewrites. I remember old Polycom endpoints having a bug where the didn't transmit the destination IP when they were registered to a gatekeeper, but that should long be fixed. Can you please post the full ARQ and your RoutingPolicy config ? Did you check if your endpoint moved the IP to the destCallSignalAddress field in the ARQ ? Regards, Jan -- Jan Willamowius, Founder of the GNU Gatekeeper Project EMail : jan@xxxxxxxxxxxxxx Website: http://www.gnugk.org Support: http://www.willamowius.com/gnugk-support.html Relaxed Communications GmbH Frahmredder 91 22393 Hamburg Geschäftsführer: Jan Willamowius HRB 125261 (Amtsgericht Hamburg) USt-IdNr: DE286003584 archlinux@xxxxxxxxxxx wrote: > Dears, > > We have an issue with full URI connection strings which we cannot sort out. > I checked this forum for similar entries but the posts I found did not really apply to our version/setup or were very old posts from years ago. If this was already dealt with I appreciate that you point me to the right place in this forum. > > The setup is gnugk 4.1 on Centos 7 self compiled. The binary is working nicely and we can set up and receive calls using E.164 numbers. URI connection strings do also work with our internal endpoints and with endpoints registered on a neighbored external gatekeeper. > > However, when we dial a full URI string like H323_alias@IP_address to any other system, non-internal, non-neighbored, this just fails with the message "system not registered with the gatekeeper". > In the gk log we can see > ... > admissionRequest { > ... > [0]=dialedDigits "H323_alias (without @IP address)" > > and below > .... > RAS ARQ received from our_IP > H460 Loaded Std 9 > DNS Query failed: error=-1 > ARJ...calledPartyNotRegistered > > It looks like gk is removing the IP address from a full URI string as in the admission request in the log appears only the H_323 alias and not the full URI string. > Is this the expected behavior? Or does it point to a wrong configuration on our side? > I thought the expected behavior was to be able to place calls with full URI strings without problems with gk registration. > When we remove the gk registration from the endpoint, the URI string does work as expected and calls are established. > > Any help is highly appreciated. > > Best regards, > Walter ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
