Re: Using GNUGK for LRQ responses only

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Maulik,

older versions of GnuGk will return 0 as call signal port if they are
in routed mode and don't have a call signal port. 1721 is GnuGk's
default signal port. If you think you changed it, check with "netstat
-tln" what your GnuGk is listening to and check the spelling of the
config switch.

Debian is rather conservative with the version updates, so you'll never
get the latest version, but there never was a 2.3.6 release.

Regards,
Jan

Maulik Shah wrote:
> I prefer catch all - will give that a shot.
> 
> I did try adding this as a permanent EP but in the LCF GnuGk sends back the
> Call Signal Port as 0 or 1721, even though I added it as 1720
> 
> 2012/03/30 09:58:55.647 1             RasTbl.cxx(282)   New
> EP|x.x.x.54:1720|e.bjn.vc:h323_ID|gateway|8358_endp
> 2012/03/30 09:58:55.647 2             RasTbl.cxx(1944)  Add permanent
> endpoint x.x.x.54:1720
> 
> Routing:
> 2012/03/30 09:59:55.098 3               gkauth.h(933)   GKAUTH  default LRQ
> check ok
> 2012/03/30 09:59:55.098 5              Routing.h(177)   ROUTING Checking
> policy Internal for the request LRQ 28936
> 2012/03/30 09:59:55.098 2             RasTbl.cxx(1336)  RASTBL  Gateway
> 8358_endp matched as a default gateway
> 2012/03/30 09:59:55.098 4             RasTbl.cxx(1724)  RASTBL  Prefix
> match for gateways:
> 199.48.152.54:1720
> 2012/03/30 09:59:55.098 5              Routing.h(183)   ROUTING Policy
> Internal applied to the request LRQ 28936
> 2012/03/30 09:59:55.098 2             RasSrv.cxx(408)
> LCF|10.35.59.170|8358_endp|123@xxxxxxxx:h323_ID|10.35.59.170;
> 2012/03/30 09:59:55.098 3             RasSrv.cxx(250)   RAS     Send to
> 10.35.59.170:1719
> locationConfirm {
>     requestSeqNum = 28936
>     callSignalAddress = ipAddress {
>       ip =  4 octets {
>         xx xx xx 36                                        .0.6
>       }
>       port = 1721
>     }
>     rasAddress = ipAddress {
>       ip =  4 octets {
>         xx xx xx 36                                        .0.6
>       }
>       port = 1719
>     }
>   }
> 
> BTW the apt-get install uses GNUGK 2.3.0, not 2.3.6
> 
> Any thoughts on this?
> 
> Thanks
> Maulik
> 
> On Fri, Mar 30, 2012 at 8:28 AM, Jan Willamowius <jan@xxxxxxxxxxxxxx> wrote:
> 
> > Hi,
> >
> > no, I meant when you use the 'catchall' policy, GnuGk will send a LCF
> > for all LRQs, even if there is no endpoint that exactly matches the
> > request. If thats what you want, use 'catchall'.
> > If you only want to send LCFs for requests that match your endpoints,
> > use the 'internal' policy.
> >
> > Regards,
> > Jan
> >
> > Maulik wrote:
> > > Hi Jan
> > >   Thx for the response - just to clarify you meant to send an LCF for s
> > non registered endpt, not avoid an LCF - correct?
> > >
> > > Thx
> > > Maulik
> > >
> > > Sent from my iPhone
> > >
> > > On Mar 30, 2012, at 12:42 AM, Jan Willamowius <jan@xxxxxxxxxxxxxx>
> > wrote:
> > >
> > > > Hi Maulik,
> > > >
> > > > as you said, the latest release of GnuGk is 3.0.1. Version 3.1 is still
> > > > in development and you can't get a packaged version, yet. You can get
> > > > the source code from the CVS and compile it yourself, but please
> > > > remember its not a release version, yet.
> > > >
> > > > The 'catchall' policy is available since GnuGk 2.3.1, but to avoid
> > > > sending an LCF for a non existing endpoint, you might want to use the
> > > > 'internal' policy instead. If your gateway doesn't register, configure
> > > > it as a "permanent endpoint". See the manual for details.
> > > >
> > > > 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
> > > >
> > > >
> > > > Maulik Shah wrote:
> > > >> Hi All
> > > >>  Am a newbie to GnuGK and have looked through the aliases and a little
> > > >> lost on a couple of items:
> > > >>
> > > >> 1. The Manuals on gnugk show they are for version 3.1 but the latest
> > stable
> > > >> version is 3.0.1 for Linux (Ubuntu apt-get is at 2.3.x) - how can I
> > get a
> > > >> Linux 64 bit tar for version 3.1?
> > > >>
> > > >> 2. Our basic use case for GnuGK is to act as a very simple dir GK:
> > > >>
> > > >> Receive LRQ from anonymous video GKs (such as Tandberg VCS) for our
> > domain
> > > >> (say user@xxxxxxxxx) and sent back an LCF with the host@GWIP port
> > 1720. I
> > > >> was going to use the CatchAll routing policy but when i add that to
> > the
> > > >> gatekeeper.ini config, I get an error saying the policy is unknown. I
> > > >> cannot have our GW register as it does not support RAS, is there any
> > way to
> > > >> configure this on the GnuGK without CatchAll?
> > > >>
> > > >> Appreciate the help in advance
> > > >>
> > > >> Thanks
> > > >> Maulik

-- 
Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________________

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/


[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux