From: "Lewis G Rosenthal" Received: from [192.168.100.201] (account lgrosenthal HELO [192.168.200.12]) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 2062482 for os2-wireless_users@2rosenthals.com; Fri, 26 Sep 2008 15:23:33 -0400 Message-ID: <48DD36AD.1000209@2rosenthals.com> Date: Fri, 26 Sep 2008 15:23:25 -0400 Organization: Rosenthal & Rosenthal, LLC User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.15) Gecko/20080621 MultiZilla/1.8.3.5c SeaMonkey/1.1.10 MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless] OT: access behind router question References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 09/26/08 02:54 pm, Stuart Gray thus wrote : > It's all in the router configuration. You assign a port to a machine, so if your address at (say) DynDNS is JeffreyRace.com, you might assign www.jefferyrace.com:5400 to point at the internal IP of the voice gateway server. > > Stuart, I think the port in the url should only be necessary if going into it from a web browser or something. Typically, the VoIP stuff runs over a set of standard ports, or at least the ports are configured elsewhere in the devices, as in: gateway url: port1: port2: option1: option2: etc. I am more familiar with H.323 devices (Nortel Unified Messaging systems, mainly), but I think this is fairly standard. Leon Zetekoff is on this list and is probably more familiar with the Asterisk (SIP) stuff than I. Let's see if he has a comment on this concerning the need for the port in the url vs separate configuration. -- Lewis ------------------------------------------------------------- Lewis G Rosenthal, CNA, CLP, CLE Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com Treasurer, Warpstock Corporation www.warpstock.org -------------------------------------------------------------