<br><br><div class="gmail_quote">On Mon, Mar 14, 2011 at 10:07 AM, Mario G <span dir="ltr"><<a href="mailto:mario_fs@mgtech.com">mario_fs@mgtech.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'll tell you what I know/observed: Based on web searches you need address and port. Here is an example of what happened to me during testing:<br>
<br>
I have multiple user IDs on my internal phone, so each phone registers multiple times, one for each extension. When I configured the phone (SPA962) to use the same port (5060) for all extensions the phones had problems such as not ringing when they should. When I gave each extension its own port and problems solved.<br>
<br>
As for ITSPs, I remember that I could not get the ITSP that had 2 accounts working right until each account had its own port. My guess is that the connection between the ITSP is registered with the user ID, but then that ID is no longer used, just the IP and port. Since FS had the same ip addr and port for both accounts there is no way to know what data belonged to what account. Making separate ports fixed the problem.<br>
<br>
I also am very confused about FS ports. In vars.xml there is only one port that can be setup for internal and external. However, I have separate external profiles each with its own port that is required to make things work. But.... I only have 1 internal profile and yet all extensions work even though they are setup with different ports for each extension. You would think FS would require different internal profiles for each ID as it does for external. Go figure.... Hope this helps a little.<br>
</blockquote><div><br></div><div>Keep in mind that the ports specified in vars.xml are for the SIP profiles. Each SIP profile is a user agent. A user agent can service exactly one IP:Port. So if your internal profile is set with IP of 10.10.1.1 and port 5060, then that's where internal is listening and responding. So, the internal profile is listening for traffic coming into <a href="http://10.10.1.1:5060">10.10.1.1:5060</a> and responds from the same IP:port. The phones in the above scenario have their own user agents who are doing the same thing with their own IPs and ports. So you could have line key 1 listening/responding on <a href="http://10.10.1.2:5060">10.10.1.2:5060</a> and line key 2 listening/responding on <a href="http://10.10.1.2:5062">10.10.1.2:5062</a>. They both send their SIP traffic *to* <a href="http://10.10.1.1:5060">10.10.1.1:5060</a> (FS, internal profile) and FS knows which IP:port to use for responding to traffic "from" each line key. That's an imperfect explanation, but I hope it illustrates the point.</div>
<div><br></div><div>-MC</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
As for using port in registrations I am not sure. The reason is while testing dual WAN I had a call going on one WAN then pulled the plug. The other took over and FS kept the conversation going. So in that case even the IP address changed! But... I am having other major FS problems trying to get a working backup so had to abandon the FS dual wan setup and stick to 1 wan connection for FS.<br>
<font color="#888888"><br>
Mario G<br>
</font><div><div></div><div class="h5"><br>
<br>
On Mar 14, 2011, at 2:03 AM, Johan Helsingius wrote:<br>
<br>
>> I remembered why I needed to use different ports in one case: Two<br>
>> of the three accounts are at the same ITSP, in this case since the<br>
>> IP address is the same on the two accounts you need to use different ports.<br>
><br>
> Ah, I have sort of the same case - 4 accounts with one ITSP providing<br>
> 4 different incoming DID's (replacing an old ISDN connection), and<br>
> 2 separate single ITSP accounts for international calls.<br>
><br>
> But I am still very confused about the need for different ports.<br>
> This is not a complaint, just an observation, but I do think the<br>
> multiple port thing is one of the more confusing aspects of FS,<br>
> and something other SIP switches seem to do without.<br>
><br>
> On outgoing connections, we register with the ITSP gateway (by the<br>
> way, does the SIP registration register both an ip address and<br>
> a port number, or just the ip address?), and on incoming connections<br>
> they either have a destination number/DID that routes them to the<br>
> right place in the dialplan, or they register with us (using<br>
> username/password) in the case of SIP clients. Security can be<br>
> handled with ACL's. So I can't get my head around to why separate<br>
> ports are needed - maybe someone can point out what I am missing?<br>
><br>
> Julf<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>
<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>
</div></div></blockquote></div><br>