Re: dual-homed proxy but only unidirectional RTP streams

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

 



Am Donnerstag, den 04.11.2010, 08:13 +1000 schrieb Simon Horne:

-----Original Message-----
> From: Martin Vogt [mailto:dekkart@xxxxxxxxx] 
> Sent: Wednesday, November 03, 2010 7:39 PM
> To: GNU Gatekeeper Users
> Subject:  dual-homed proxy but only unidirectional
> RTP streams

I had nearly the same problem only yesterday, so maybe I may share some
insight.

Depending on the configuration I got different "Q931d Could not
open/connect socket at a.b.c.d:e" errors.

In my setup, I had a machine with two interface addresses plus one
loopback address. What I wanted to achive is simply to accepting calls
coming from the one interface (but directed to the loopback address) and
to proxy them over the other interface -- kind of what a Cisco "Router"
does.

> The best place to start is the simplest. 

You're (almost) right here.

> Your setup is quite simple. Remove
> all the extra settings for proxy and let GnuGk work it out.
> 
> I would comment out.
> [Gatekeeper::Main]
> ;;Home=171.42.1.212,175.193.73.212
> ;;Bind=171.42.1.212

Strangely yesterday with these lines it did not work for me (error on
Q931 channel setup), without it did not work either (RTP channel
negotiation failed). Today it works with or without those settings ...
Oh how I love those non-reproducible problems :-(

What worked even yesterday was setting the "Bind" address to the
Loopback address, while not setting the "Home" parameter. Which leads to
the question what differences there are between "Home", "Bind" and
"Network Interfaces" and how they interact.

My understanding is as follows:
Home: Listen and accept calls from there.
Bind: Use this as source address for outgoing connections.

> [Proxy]
> ;;InternalNetwork=171.42.0.0/16

I used "InternalNetwork" and "ProxyAlways".

> Gatekeeper(GNU) Version(2.3.2)

Dito, from recent Debian testing package.

> schematic setup: http://pastebin.com/0ektd8nE

Just add a well-known loopback address and it will be the same as mine.
RAS was not used. So as I mentioned already it works like a ipv4
dial-peering Cisco "router".

Regards

David

-- 
David Dahlberg <david.dahlberg@xxxxxxxxxxxxxxxxxx>    

Fraunhofer FKIE, Dept. Communication Systems (KOM) | Tel: +49-228-9435-845
Neuenahrer Str. 20, 53343 Wachtberg, Germany       | Fax: +49-228-856277


------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________________

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