On Wed, 17 Sep 2008, Jared Smith wrote:
On Wed, 2008-09-17 at 19:58 +0200, Remco Barendse wrote:
Why doesn't Asterisk allow both usernamepass as well as setting an ip
adress on a sip.extension?
It does. To enforce ACLs on a SIP user or peer or friend, simply use
permit and deny statements
Remco Barendse schrieb:
Suprising that this feature isn't used much, i would suspect that many
asterisk installations (including mine) have very simple (short) extension
numbers which makes brute forcing them rather easy.
Extension numbers and SIP account basically have nothing to do with
Maybe a bit silly question, but why doesn't Asterisk accept if you set
both a usernamepassword as well as an ip address for a phone?
My fixed phones in my home all have a fixed ip address, but i also have 2
Nokia GSM phones that can talk sip wich i would like to use from public
wifi.
It's
Maybe a bit silly question, but why doesn't Asterisk accept if you set
both a usernamepassword as well as an ip address for a phone?
but it does accept!
in a peer definition:
[user]
type=user (or better friend)
username=user
secret=secret
host=10.0.0.1
[snip]
It's obvious that the more
On Wed, 2008-09-17 at 19:58 +0200, Remco Barendse wrote:
Why doesn't Asterisk allow both usernamepass as well as setting an ip
adress on a sip.extension?
It does. To enforce ACLs on a SIP user or peer or friend, simply use
permit and deny statements to allow and disallow various IP
addresses
It will syntactically take that definition, but it's nearly pointless. I
suspect he is encountering a problem I have found:
It doesn't do full support static and registration simultaneously.
Most notably, at least in 1.2 (and probably 1.4) if you create a
registrable peer it is NOT monitorable
