VoIP Mailing List Archives

[ajlong at worldlink.net]

I am trying to setup a couple of gateways on my external profile that do not user usernames or passwords .
How can I setup these gateways to match based on originating IP address?
At the moment I have them defined in separate xml files in the sip_profiles/external directory.

I am using the default external.xml
I would like to be able to dial via this gateway and receive calls from these gateways.

For example NYGW1.xml ------- >

<include>
<gateway name="NYGW1" cidr="10.10.10.1/32" description="Cisco Gateway Connected to Level3 PRI">
<param name="register" value="false"/>
<param name="username" value="none"/>
<param name="password" value="none"/>
<param name="realm" value="10.10.10.1"/>
<param name="proxy" value="10.10.10.1"/>
<param name="from-domain" value="oneofmydomains.com"/>
<param name="extension" value="inbound_oneofmydomains"/>
<param name="caller-id-in-from" value="true"/>
<param name="ping" value="25"/>
</gateway>
</include>

When I remove the username/password params or set them to “” FreeSWITCH refuses to load the gateway.
I tried adding the cidr=”” to the gateway but no luck.

Really all I want is for calls flowing in from 10.10.10.1 --- > FreeSWITCH External SIP Profile ---- > Match to NYGW1 --- > Dump into a context or extension from where I can route them as I please.

Kind of how an Asterisk sip “peer” is matched on IP and routed to a context.

Any ideas greatly appreciated!

[josephbajin at gmail.com]

You don't need to define a gateway if you are trying to limit incoming calls by a particular IP. You can do it two ways, first by using an ACL to only allow that traffic. Or you can create a dialplan that looks for that particular IP and then sends it to a particular context based on that IP. There are great examples on the wiki.






On Mon, Jan 19, 2009 at 5:03 PM, Adam Long <ajlong@worldlink.net (ajlong@worldlink.net)> wrote: