If it were me, and it's not I would prefer to use the template for bandwidth.com and simply edit the gateway names...
===================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.326.5325 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/ tony-graziano/14/4a6/7a4 On Apr 14, 2011 1:08 PM, "Tim Byng" <t...@missioninc.com> wrote: > On Thu, Apr 14, 2011 at 9:55 AM, Michael Scheidell wrote: > >> and remember: they send to port 5060, and sipx wants it on 5080. >> you will need to 'pat' or port translate inbound from their ip:5060 to >> sipx:5080. >> >> (outbound xlation not needed) >> seems to work, despite the layer7 (application) issues. just seems to >> work. >> > > I think I'm almost there. I can make outbound calls, but cannot receive > inbound calls. > > At voip.ms I set up a new sub account with authentication type set to static > IP authentication, IP address set to my public IP address, and NAT set to > No. > > In pfSense I added an alias for all of the voip.ms server IP addresses. I > then created a new NAT Port Forward rule with source type set to "Single > host or alias", source address set to the voip.ms servers alias, destination > port range set to 5060 and redirect target port set to 5080. > > In sipXecs, I edited my voip.ms gateway and removed the username and > password and I unselected register on initialization (I saw this recommended > in a couple of mailing list posts). I also tried with my username set to my > voip.ms sub account username, but the result was the same. > > Is there anything I'm missing here? I looked through old mailing list posts > and found a few instances where people were having issues with voip.ms and > IP authentication. I didn't see any resolution mentioned. BTW, I am using > sipXecs 4.2, not 4.4.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
