Displaying 3 results from an estimated 3 matches for "genearlly".
2015 Apr 02
0
Update peer IP address
That sounds like asterisk was working 100% correctly. If you receive an
INVITE from an unknown IP address, then it should fail. Unless you want to
allow anonymous, which is genearlly a very bad idea.
If you are registering to IP X, but the provider may be transmitting
invites from any number of other IP addresses, then you need a list of IP
addresses, and have a trunk configuration set up for each one so that they
are all recognized (with insecure=port,invite).
If the provide...
2015 Apr 02
2
Update peer IP address
Okay, Scott, I think we are on the wrong path. Maybe I'm wrong though.
I will summarize again briefly the problems together:
The peer ip address could be another than the ip address of incoming invites
After an re-register the REGISTER is send to the new SIP server, answered with OK. But the peer ip address is still the old one (sip show peers).
If now is a INVITE, the request is answered
2015 Apr 02
3
Update peer IP address
...ost=217.0.18.36
etc.
> Am 02.04.2015 um 23:21 schrieb Scott Griepentrog <sgriepentrog at digium.com>:
>
> That sounds like asterisk was working 100% correctly. If you receive an INVITE from an unknown IP address, then it should fail. Unless you want to allow anonymous, which is genearlly a very bad idea.
>
> If you are registering to IP X, but the provider may be transmitting invites from any number of other IP addresses, then you need a list of IP addresses, and have a trunk configuration set up for each one so that they are all recognized (with insecure=port,invite).
>...