I restart FS and initiate an incoming call (trunk is registered at the
SIP provider).
This is what I see on the console:
.
.
.
2009-04-02 23:39:16 [DEBUG] mod_event_socket.c:2224
mod_event_socket_runtime() Socket up listening on 0.0.0.0:8021
2009-04-02 23:39:16 [NOTICE] switch_core.c:981
switch_lo
look at the debug log and see what happens?
On Thu, Apr 2, 2009 at 3:34 PM, Peter P GMX wrote:
> My ACL contains:
>
>
>
>
>
> So this should be fine, right? However it doesn't work.
>
> Best regards
> Peter
>
>
> Brian West schrieb:
> > We use the true network ip the invite c
My ACL contains:
So this should be fine, right? However it doesn't work.
Best regards
Peter
Brian West schrieb:
> We use the true network ip the invite came from NOT the one in the sip
> headers. Not very trust worth to do that you think? ;)
>
> So if your ACL is corre
We use the true network ip the invite came from NOT the one in the sip
headers. Not very trust worth to do that you think? ;)
So if your ACL is correctly setup to 62.65.128.62 it would let them in
please verify your ACL is correct...
/b
On Apr 2, 2009, at 3:07 PM, Peter P GMX wrote:
He
acl uses the remote addr from the socket connection, not anything from the
sip message.
On Thu, Apr 2, 2009 at 3:07 PM, Peter P GMX wrote:
> Hello,
>
> I am using a SIP account from Netvoip CH. I try to receive inbound call
> from this SIP trunk. I discovered that, when they sent an invite, the
Hello,
I am using a SIP account from Netvoip CH. I try to receive inbound call
from this SIP trunk. I discovered that, when they sent an invite, the
IP-Adress of the to: is their own IP address.
There fore ACL doesn't work and FS asks for authorization, which then fails
I receive the following me
