[asterisk-users] Trunk with multiple IPs?

[Rich Adamson]

I'm thinking I used deny and permit statements on broadvoice.com way 
back when, and the configs/sip.conf.sample suggests its still valid for 
v1.2.10 code.

You might take another look at that for sip.

Benjamin Lawetz wrote:
> Agreed that with a other IAX and SIP that have registration information and
> secrets that works.
> 
> The problem is when you have a provider that just sends you a SIP call and
> the only way to identify it is by IP address. In those cases (if I
> understand correctly) we need a host line don't we? (Or at least I remember
> when I was testing a while back that it wouldn't work with deny and permit)
> 
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Rich Adamson
> Sent: August 23, 2006 10:00 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] Trunk with multiple IPs?
> 
> Benjamin Lawetz wrote:
>> Still no answers huh?
>>
>> I've asked a couple of time how to do this, and by the lack of 
>> answers, I'm guessing there is no way.
>> The workaround unfortunately is to create an entry for each IP address 
>> in the range (I hope you don't have to open up a whole C class)
>>
>> -----Original Message-----
>> How do I enter a trunk with multiple IPs.
>>
>> xyz voip provider has 4 IPs and I want to allow incoming from any of
>> them: 1.1.1.1, 1.1.1.2, 1.1.1.3 and 1.1.1.4
>>
>> Do I put 4 separate host= lines, do I put a single host=line that is 
>> comma separated or do I have to set up 4 separate incoming trunks?
>>
> 
> Here's an iax.conf example of what I'm using:
> [teliax]
> context=teliax-incoming
> type=user
> auth=md5
> secret=mysecret
> jitterbuffer=yes
> disallow=all
> allow=gsm
> deny=0.0.0.0/0.0.0.0
> permit=207.174.202.0/255.255.255.0
> 
> The last two statements essentially restrict incoming calls from teliax to
> one of their class-c networks (regardless of how many servers or IP's they
> have).
> 
> Note that on incoming calls the host= line is not used.
> 
> If you're really asking how to do that for outgoing calls, you'll probably
> have to do it through three/four sections (type=peer) and deal with those
> sections in your dialplan.
> 
> As a side note, there are a large percentage of * implementors that don't
> understand the search terms when an incoming call is being negotiated (eg,
> is host= used, is secret= used). Without that understanding, calls likely
> come into different sections then what the implementor actually expected.
> The deny & permit statements are very useful to tighten down security for
> each incoming context.
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> 
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users