Thank you, all is working much better now.
On Wed, Apr 30, 2008 at 6:14 AM, Anthony Minessale <
[EMAIL PROTECTED]> wrote:
> it seems a bit confusing but if you want to do ip auth the way you
> describe, you actually have to disable the digest auth so that the other end
> is not challenged for aut
I have added this ACL topic to the meeting today so we can make sure
its documented better on the wiki.
1pm CST sip:[EMAIL PROTECTED]
/b
On Apr 30, 2008, at 8:14 AM, Anthony Minessale wrote:
it seems a bit confusing but if you want to do ip auth the way you
describe, you actually have to di
it seems a bit confusing but if you want to do ip auth the way you describe,
you actually have to disable the digest auth so that the other end is not
challenged for auth credentials on top of the ip auth.
search your profile for this:
and comment it by encapsulating it in
then add this line:
Jed,
here are the list of things you can do:
1. sip_profiles/default.xml -> change context to default and set auth-
calls=false
2. Then you can use ${network_addr} in your conditions or the ${acl()}
function an example is in the default.xml dialplan.
/b
On Apr 29, 2008, at 4:44 PM, J
This feel's like a very stupid question, but i've scoured for hours through
the documents, and samples I can find without finding an answer. I'm
assuming I'm missing something very obvious.
I'm just trying to have freeswitch accept a call from a static IP address,
then forward that call to a provid
