From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SIP, NAT, and load balancing problems
Date: Wed, 13 Dec 2006 21:57:44 +0000 [thread overview]
Message-ID: <45807758.7000702@riverviewtech.net> (raw)
In-Reply-To: <457EC047.7090404@wirelessmundi.com>
Rangi Biddle wrote:
> What do you think of perhaps Francois using SER?
Well, I don't have a problem with SIP Express Router and / or / verses
Asterisk (or any other SIP Soft Switch for that matter), however, I
think the OP will still be facing the same problem.
That problem being binding a daemon to a single IP address and routing
traffic to / from it with out messing up the packets. I am going to
presume that Asterisk and / or SER will only be bound to a specific
interface, not all of them. I'm not sure why the OP only wants to bind
Asterisk to a single interface verses all of them, though I'm going to
guess that s/he has a good reason for doing so.
It may be a case that Asterisk as the soft switch should be bound to the
internal interface and SER bound to the external interface. This way,
the SIP traffic can be passed through both interfaces natively, via both
daemons. However, I think this would be more undo complexity for very
little gain.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-12-13 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 14:44 [LARTC] SIP, NAT, and load balancing problems François Delawarde
2006-12-12 19:54 ` Andrew McGill
2006-12-13 6:40 ` Grant Taylor
2006-12-13 10:12 ` François Delawarde
2006-12-13 10:33 ` François Delawarde
2006-12-13 15:30 ` Taylor, Grant
2006-12-13 20:48 ` Grant Taylor
2006-12-13 21:57 ` Grant Taylor [this message]
2006-12-13 22:44 ` Grant Taylor
2006-12-13 22:57 ` Patrick McHardy
2006-12-14 11:44 ` François Delawarde
2006-12-14 11:59 ` François Delawarde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45807758.7000702@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.