Re: 2 gnu gatekeepers working as neighbors

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

 



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/

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

  Powered by Linux