Two gatekeepers (public/private) sharing same prefix?

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

 



Dear All, having looked through the documentation and faqs and 
searched this mailing list archives without luck, I'm now appealing 
to the collective wisdom for suggestions.
We used gnugk for a few years without firewall and without problems.
Now we installed a firewall at last. I have an external gatekeeper in 
the dmz (full proxy) and and internal one in the loc zone. Both gnugk 
2.2.7 on Debian.
What I want to achieve:
internal users register on the internal gatekeeper and they can call 
outside AND be called at the e.164 number space we are allocated (the 
same as our phone numbers, 00390xxxxxx2yy, where yy is the same as 
the phone extension). External users can register on the external 
gatekeeper and call and be called on the SAME address space 
(00390xxxxxx2yy).

What I could achieve so far in all my attempts:
a) The internal gatekeeper is registered as a child of the external 
one, I add a fake number to our
prefix, turning it into 00390xxxxxx29yy, delegate the whole 
00390xxxxxx29 prefix to the internal gatekeeper.
The result is the behaviour I want for external users, whereas 
internal ones can call outside,
but of course can only be reached at the e.164 numbers 
00390xxxxxx29yy, which is far less than convenient.
If I don't do the delegation and stick to the "proper" numbers, (i.e. 
parent and child share the same address space) incoming calls for 
endpoints registered with the internal gatekeeper are rejected 
(unregistered endpoint) even if I modified the routing to 
internal,neighbor and configured the two neighbours of the external 
gatekeeper (the parent gatekeeper, root of the national hierarchy we 
belong to, and our internal gatekeeper) so that the prefixes that 
belong to us, i.e.
2 (internally generated),0xxxxxx2,00390xxxxxx2 are not routed to the 
parent gatekeeper whereas the child accepts only them.

b) I tried defining the internal gatekeeper as a neighbour of the 
external one, but is does nowt work even for calling outside, since 
the external gatekeeper does not act as a proxy, and sends the parent 
gatekeeper a message including caller and called addresses. Of course 
the parent gatekeeper rejects that since the caller address (the 
internal gatekeeper) is in private address space.

?

Grateful for any suggestions...
Thanks to all
Alessandro

-- 
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________________

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