Re: [Ekiga-list] Bug prevents VPN use

[Konrad Karl <kk_konrad gmx at>]

On Wed, Oct 02, 2013 at 09:43:33AM +0200, Damien Sandras wrote:
> Le 01/10/13 20:17, Konrad Karl a ?crit :
> > Hi,
> >
> > On Sun, Sep 29, 2013 at 05:53:58PM +0200, Damien Sandras wrote:
> > > What Ekiga is supposed to do, is to send one message per interface
> > > with the interface IP address as source. If your routing is well
> > > configured, then only one of the various SIP messages should reach
> > > the remote user.
> > is this behaviour required by the SIP protocol?
> >
> > (I also want to restrict all ekiga traffic to one specific
> >  openvpn interface at times - direct ip call w/o registration)
> >
> > A short explanation will be appreciated.
>
> Not specifically required. The standard says nothing about multiple
> interfaces handling.
> It is just a question of routing after that point. You can see this
> as a kind of fork of SIP requests.
> If you have two routes to the same destination, through 2 different
> interfaces, it should work too, but both routes have to work both
> ways : ie, if you can send a SIP PDU, you should be able to receive
> incoming requests and responses through that route too.
Thanks for explanation, Damien!

A question still remains for me: why is this done the way it is?
If I e.g telnet some.ip.add.ress then routing rule apply and all
traffic will go over the vpn interface (tun0 or such). 

Why not do the same with SIP? (or at least have one option for that)
(confessing I am a SIP noob :-) In my case there is exactly one way
to reach the destination and that is VPN.

Greetings,

Konrad