2 gnu gatekeepers working as neighbors(FOR STEWART)

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

 



Hi stewart,

Yes, both gatekeepers works behind nat.(therefore they actually have a
private ip).
The two gatekeepers are situated in two different network, so they are
behind two differnt router/nat.

Like i supposed, the error i told you last time, was a bug in the 2.2.3
version of the gnugk.
In fact, now i've passed to the 2.0.9 version and all are working good.
I make call from my two zones, i'm able to do audio,video and dati.... it's
great.
..I'm very happy.

Yes, the 10049 error, is shown from gk1's log...  in my example the log
were:
"could not open/connect socket at 62.101.106.41:0 - WIN32 error 10049"
where 62.101.106.41 is the ip address of the gk1's nat.

Regards


> Hi Lua,
>
> When you said "Both gatekeepers have a public ip address" I assumed
> that each gatekeeper has two NICs, one of which is a public IP.  Or,
> at least, the public IP is an address listed by ipconfig.  But from
> your .ini file, it seems that the gk's are behind NATs.  Is that correct?
> If so, I don't know if what you are trying to do with LRQ/LCF is
> supported -- I have not tried this myself, nor have I seen any posts
> from others having succeeded.
>
> When you get the 10049 error, is the address printed that for gk1?
> If so, it is probably trying to bind to that address, which may be a
> bug in the code.  Perhaps Michal can comment on this.  If it's the
> address for gk2, you might try adding some debugging statements, so
> we know why the system call is being rejected.
>
> Running a gk on a dynamic IP is not a big problem, if your IP changes
> only once or twice a year as a result of a network outage.
> But if your provider purposely changes your address (some do it
> every day) you will have trouble.  Not only will all calls be dropped
> when the address changes, but you won't be able to call back right
> away, because it will take a while for dynamic DNS to propagate, and
> clients to realize the address to which they must register (or send
> LRQ).
>
> Regards,
>
> Stewart
>
> ----- Original Message ----- 
> From: "-Luca-" <noceluca@xxxxxxxxxxx>
> To: <openh323gk-users@xxxxxxxxxxxxxxxxxxxxx>
> Sent: Tuesday, October 04, 2005 10:38 PM
> Subject: Re:  2 gnu gatekeepers working as neighbors
>
>
> Hi stewart,
>
> I've observed LRQ and LCF messages, and they are correct,  the telephony
service and the firewall
> are unable.
> I see that LCF is correctly read from gk1.
> I also keep a check of my gatekeeper.ini file  :-)
> The ip 62.101.106.41 that you've tried connect to, is an ip that my
provider dynamically assign to
> me.
>
> "I assume that the :0 means that gk1 was trying to connect to
>  port 0, which was rejected by the OS"
> Well, i have tried to run the 2 getekeepers and the 2 clients in the same
local lan, in this case
> all worked fine.(audio and video too)
> But i've see that when the gk1 open tcp to the gk2, the log show:
> Connect to 192.168.1.82:1721 from 192.168.1.81:0
> Where
> gk1=192.168.1.81
> gk2=192.168.1.82
>
> I read in the manual this words:
> "Note to make proxy work, the gatekeeper must have direct connection to
both networks of the caller
> and callee."
>
> So,I want to ask you, do you knows if is possible my configuration?
>
> PS: i made my test only with the 2.2.3 version of gnugk, tomorrow i'm
trying with 2.0.9 version.
>
> I'm attaching my two gatekeeper.ini files.
>
> Thank you,stewart.
>
>
>
>
> ----- Original Message ----- 
> From: "Stewart Nelson" <sn@xxxxxxxxxxx>
> To: <openh323gk-users@xxxxxxxxxxxxxxxxxxxxx>
> Sent: Monday, October 03, 2005 3:48 AM
> Subject: Re:  2 gnu gatekeepers working as neighbors
>
>
> > Hi,
> >
> > I assume that the :0 means that gk1 was trying to connect to
> > port 0, which was rejected by the OS.  Use ethereal or the
> > trace to see if the correct call signal address and port
> > (that of gk2) is in the LCF.  That should at least tell
> > you which end the trouble is at.
> >
> > Make sure that Telephony service is not running, and that
> > Windows firewall or other software firewall is not
> > butchering the packets.
> >
> > You should also check that gk2 is actually listening
> > on its public IP; I couldn't connect to 62.101.106.41
> > port 1720 or port 1721.  Of course, that may be because
> > of a firewall, it's on a non-standard port,
> > or gk2 wasn't running when I wrote this.
> >
> > --Stewart
> >
> > ----- Original Message ----- 
> > From: "-Luca-" <noceluca@xxxxxxxxxxx>
> > To: <openh323gk-users@xxxxxxxxxxxxxxxxxxxxx>
> > Sent: Saturday, October 01, 2005 2:59 AM
> > Subject:  2 gnu gatekeepers working as neighbors
> >
> >
> > Hi all,
> >
> > I'm trying to make calls from 2 client registered at two different
gnugks.
> >
> > ---------------------------                ---------------------
> > |   Lan 1                          |                  |   Lan 2
|
> > |                                      |                  |
|
> > |
|
> > | (client1) ----->     (gk1)  <------>    ( gk2) <---- (clientt2) |
> > |
|
> > |                                      |                  |
|
> > |                                      |                  |
|
> > ---------------------------                  --------------------
> >
> > Both gatekeepers have a public ip address and work in full proxy
mode(h225 routed + proxy enable).
> > Both clients have private ip address.
> > When client1 try calling client 2, gk1 sends a LRQ message to gk2, and
gk2 reply with LCF.
> > Then gk1 must forward setup message (sent from client1) to gk2...
therefore gk1 try to open a tcp
> > connection to gk2,
> > at this point the gk1 log show this error:
> >
> > could not open/connect socket at 62.101.106.41:0 - WIN32 error 10049
> >
> >
> > Does anyone knows what it's means?... or anyone that has already did a
similar configuration?
> >
> >
> > Thanks a lot.
> >
> >                     -Luca-
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________________
>
> Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
> Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
> Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
> Homepage: http://www.gnugk.org/
>


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________________

Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
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