Re: about the incoming call of a terminal behind NAT Thanks!

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

 



Hi,

to GnuGk it shouldn't make a difference with signal port you use (and
in current releases 1720 is the default).

Maybe you have a firewall in the path that thinks it knows H.323 and
treats traffic on port 1720 differently and breaks H.460.18 ? Cisco
ASA ?

I would check the GnuGk trace if a.) GnuGk accepts the H.4601.8 feature
in the endpoint registration and b.) if it tries to send out an SCI
when the endpoint is called.

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

Bo Xu wrote:
> Hi,
> 
> I just change CallSignalPort back to 1721(1721 is its default value, but
> normally we set it as 1720 so when terminal dial GnuGK we don't need to
> specify the prot 1721), now  terminal-B can call terminal-A(NATed) fine as
> the following:
> I saw after terminal-A(NATed) sent facility message to GnuGk's port-1721,
> GnuGK sent back setup message
> 
> could you tell me why there is no setup message sent back from GnuGK if I
> set CallSignalPort as 1720 in the gatekeeper.ini? if I still want to use
> 1720 as CallSignalPort how to do that Thanks!
> 
> Regards,
> Bo
> 
> 
> 
> On Thu, Apr 2, 2015 at 4:20 PM, Bo Xu <boxuscience@xxxxxxxxx> wrote:
> 
> > Hi,
> >
> > I have a GnuGK with H.460.18 enabled, and terminal-A and terminal-B all
> > register to that GnuGK, and terminal-A is behind NAT.
> >
> > when terminal-A(NATed) calls terminal-B everything works fine, but when
> > terminal-B calls terminal-A(NATed), from the wireshark in terminal-A, I saw:
> > GnuGK sent SCI to terminal-A(NATed)'s 1719-port
> > terminal-A(NATed) sent SCR to GnuGK's 1719-port
> > then terminal-A(NATed) sent facility to GnuGK's 1720-port(I set GnuGK use
> > 1720 as CallSignalPort)
> >
> > but after that, GnuGK didn't sent Setup messge back to terminal-A(NATed)
> > as mentioned here:
> > http://www.gnugk.org/nat-traversal.html
> >
> > I guess the facility massage terminal-A(NATed) sent to GnuGK might not be
> > correct so GnuGK refuse to sent Setup back, could you give me a sample of
> > the correct facility messge?  is there other issue in what I did in the
> > above? it is right for terminal-A(NATed) sent facility-message to GnuGK's
> > 1720-port? Thanks!
> >
> > Regards,
> > Bo Xu

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________________

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