What you are doing is correct.<br><br>In FS gateways only represent a set of credentials that the profile uses to authenticate to another sip UA<br>The actual UA is the sofia profile and the gateways are assumed identities to deal with challenges.<br>
<br>Also to manage everything from the same place,<br>you can put the <gateways> tag inside the <user> tag in the directory then<br>tell sofia to parse the whole domain for gateways in the profile <br><br>in <domains> section of your sofia profile <br>
add<br><domain name="<a href="http://domain.com">domain.com</a>" parse="true"/><br><br>this will tell FS to open that domain in the user directory and check every user<br>for <gateways> and parse them all.<br>
<br><br><br><br><br><br><div class="gmail_quote">On Tue, Jan 13, 2009 at 10:45 AM, Apostolos Pantsiopoulos <span dir="ltr"><<a href="mailto:regs@kinetix.gr">regs@kinetix.gr</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think one of the most difficult ideas to grasp when someone<br>
migrates to FS from other soft-switches is the definition of<br>
endpoints (in the generic meaning of the word) i.e. other gateways<br>
that your FS gateway will exchange traffic with. From what I<br>
understood from the wiki :<br>
<br>
a user (directory) is an entitiy that defines our subscribers (with<br>
registration or not)<br>
<br>
a gateway is another VoIP gateway that we use to send traffic to<br>
(provider) and sometimes receive traffic from<br>
<br>
(correct me If I am wrong this far)<br>
<br>
Now, I have the following scenario :<br>
<br>
I have an FS box that will exhchange traffic with certain gateways.<br>
Sometimes a gateway will act as a client (customer) or a provider,<br>
depending on the traffic direction.<br>
<br>
1st approach :<br>
<br>
The first plan I tried, was to use the directory to "define" these<br>
other gateways since they are clients. I turned off registrations<br>
in my SIP profile (because I don't need any), I wrote an xml file<br>
for each gateway in the directory with the appropriate cidr and that<br>
was it.<br>
<br>
I then realized that I could not use my definitions in the users directory<br>
so that I can send a call to that client. In order to do so, I had to<br>
define<br>
that particular IP as a gateway in my SIP profile <gateways> section.<br>
<br>
2nd approach :<br>
<br>
I forgot all about the directory thing (after all I needed not any<br>
mailboxes or registrations) and tried to implement the same scenario<br>
by just using gateways. I declared the gateways in my SIP profile and<br>
was able to dial out to them just by using :<br>
<br>
<action application="bridge" data="sofia/gateway/<gw_name>/$1"/><br>
<br>
which was fine. But when I got an inbound call from that gateway<br>
I realized (1) that I had to define this gateway in an acl and (2) the<br>
dialplan used (context) was always the inbound one since there is no<br>
way of telling a gateway which context to use when accepting a call.<br>
I found a way in the wiki that suggests using DIDs to accomplish that,<br>
but I find it this to be not a very elegant solution because I don't<br>
want to use<br>
prefixes or DIDs to accomplish my goal. I want to be able to define a<br>
gateway using a gateway name (label) of my choice and an IP address,<br>
so when I come to the point of having 100+ gateways i won't<br>
have to search wich DID to use for a new one.<br>
<br>
3rd approach :<br>
<br>
Use a combination of the above. Declare a gateway that receives and<br>
sends traffic twice. Once as a<br>
user in the directory and once in the gateways section of my profile.<br>
<br>
Does all these sound correct to you? Am I missing something? Which<br>
approach is the best?<br>
Please send me your feedback. Inline comments would be ideal.<br>
<br>
--<br>
-------------------------------------------<br>
Apostolos Pantsiopoulos<br>
Kinetix Tele.com R & D<br>
email: <a href="mailto:regs@kinetix.gr">regs@kinetix.gr</a><br>
-------------------------------------------<br>
<br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>