sipwitch-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sipwitch-devel] network configuration


From: Lee Azzarello
Subject: Re: [Sipwitch-devel] network configuration
Date: Tue, 28 Feb 2012 14:49:23 -0800
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20111010 Icedove/3.1.15

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/28/2012 01:05 AM, David Sugar wrote:
> I think some confusion is caused by not being able to know how exactly
> sipwitch believes the network is configured.  sipwitch does this through
> a list of cidr access policies and stack rules which may be applied to
> them, such as "trusted" and "restricted".  However, sipwitch can
> auto-generate cidr access policies based on local subnet detection, and
> if you do not even know what cidr access policies it has generated, you
> cannot be certain your own policy rules are being correctly applied.
> 
> To resolve this, I am going to add a new command to the "sipwitch"
> binary to dump the sipwitch cidr/access table, so that one can more
> easily see what the local configurations actually look like (since some
> are created by auto-configuration by default).  I am also going to add a
> command to get what sipwitch currently "thinks" its peering address is.
>  This I think will make it easier to understand what sipwitch itself
> thinks is going on.

Hello David,

I'm new to the list. I've been evaluating Sipwitch for a contract
project. I think this idea is a good one. I had to read the source code
to determine the auto-configure access rules and overlay them with the
default configuration XML in my head to understand what was going on.
This is far from an intuitive process.

Other than that I found the Sipwitch configuration process not bad
compared to Asterisk, though call authorization was much more
complicated than I expected. Eventually I discovered I had to add my IP
address on the public Internet as the SIP "Realm" configuration to
authorize two registered clients to call each other.

I'm experimenting with Freeswitch for the next few weeks so I won't have
much more to contribute here until next month.

Thanks for your hard work,
Lee
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPTVnyAAoJEKhL9IoSyjdlgTYP/3ALjCQSGUd5t+DTrX+bSyde
lQV/mznh96AAbMlCrqEEZ6BJB6brh1HJhBKAOS7UAPaVigmuPdqkMqBcCmMWp/2m
+iTFQZt3Gv8I6zdwIncsxyX8S+PDkiSyCApu/fU9lE7HOe2FqnmVsGst0M4SkA/p
EMd3TWCFLoWaQKPNlDrJw53DJO+nDE2+o3M7WDJUR9L0L9b8CtuGhMeHjdcUI5K/
HsECmAZqm8+FgnMaE/I0UwVrzvOKMbGWY+f67Tl8eZUhDJiL/thO9vW/120g41J9
YzarllPVauMNdniFwozQdaLniodQsUoxUhajTBL/UlISKH5NZI2RxdA4L6MRrvkj
G+qagTZD2NRMF9ha2/5gajYh+2RA59mgOdEAnbnR2k5cC7Kc48imEjSfKUnwJ+5v
02sI/nRYv/7UrLGgIQtWvPkDyG0WzzCpKRZkdSbekz9SrIRtJeYdeM686Rq3MKmh
eEbHz6we+G0fwmeuQuDTJngep5o1Zzz7cx4RdL9JOiRF0pqJ8pL66lVr5f+Xyrcw
aotc46GkuxryQCb+i847o9oE5pmbFkWIJ41YnMwyCuJ2h5M4jAzii2DCh0OarPzM
JuPMU9dTuhhtEUJtNDdrCy7cCGyBbtygUc7GSqZgs48Dn163EwoD9wPstT4dZCq7
Bb7fnj0X3FupaXAnT6Bw
=MM5X
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]