On Sunday 06 May 2007, Christopher Aloi wrote:
> On 5/5/07, Tilghman Lesher <[EMAIL PROTECTED]> wrote:
> > On Saturday 05 May 2007, Sergey Okhapkin wrote:
> > > Yes, it's the expected IP stack behavior when the service is bound to
> > > 0.0.0.0. Asterisk sends the repy to the address from which t
So what your saying is that my ultimate goal (2 ip's on different networks) is
obtainable; but that I should be looking into my route table and not Asterisk,
am I following correctly?
I wasn't able to find a bug report indicating this behavior, do you think this
is something I should open f
On Saturday 05 May 2007, Sergey Okhapkin wrote:
> Yes, it's the expected IP stack behavior when the service is bound to
> 0.0.0.0. Asterisk sends the repy to the address from which the request
> came, it has no control which src address to use.
Actually, it does control it; it uses the Linux routi
Yes, it's the expected IP stack behavior when the service is bound to 0.0.0.0.
Asterisk sends the repy to the address from which the request came, it has no
control which src address to use.
On Saturday 05 May 2007 12:47, Christopher Aloi wrote:
> Hello -
>
> Well I've been able to find a bit mo
Hello -
Well I've been able to find a bit more about my problem.
Again - I am not bound to a specific interface (0.0.0.0)
When a SIP invite addressed to the .36 address, Asterisk replies FROM the
.38 address. Is this the expected behavior?
Wouldn't it make sense for Asterisk to reply on FROM
