Instead of host=dynamic, use host=1.1.1.1, or
host=1.1.1.0/255.255.255.0.
Thanks,
--Warren Selby
On Jan 12, 2010, at 11:16 AM, Aggio Alberto
<alberto.ag...@loquendo.com> wrote:
Hi guys,
I recently faced an issue regarding SIP registration: I have a 2-NIC
Linux PC, with eth0 set to address 192.168.1.1 (NATted over public
network, with address 89.X.Y.Z) and eth1 set to address 1.1.1.1. In
[sip.conf] I set general option
bindaddr=0.0.0.0 ; IP address to bind to (0.0.0.0
binds to all)
Then I have configured an account as following:
[999]
type=friend
username=999
host=dynamic
port=5080
context=sipfrom
nat=no
canreinvite=no
call-limit=8
videosupport=no
disallow=all
allow=alaw
qualify=15000
So far, so good.
Now, I have an internal process (onto Linux PC) which is a SIP
endpoint and should register to Asterisk as 1.1.1.1:5080, but an
external entity (i.e. a SIP endpoint over public Internet) is trying
to register to Asterisk as 9...@89.x.y.z:5060 and the registration
SUCCEEDS! When I launch the CLI command sip show peers, I see a row
like this:
999/999 1.1.1.1 5060 OK
(3 ms)
Can someone explain me this kind of behaviour? Is it normal? Can I
restrict registration of 999 peer only to SIP UA from network 1.1.1.X?
Thanks for your help! Regards,
Alberto Aggio
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
