I don't think it's as easy as you suggest... if you map all inbound 5060 to 5080 it won't work. You would have to map all of a source IP of your ITSP to destination 5060/udp in to 5080/udp.
Joegen has something coming for that... i don't think it made it to 4.4. I think there was a conflict in freeswitch that was breaking other things and we had to pick our battles. Joegen can speak up if I got it wrong. Mike On Sun, Apr 17, 2011 at 3:12 PM, Michael Scheidell < [email protected]> wrote: > On 4/17/11 8:20 AM, Michael Picher wrote: > > There are a couple other initiatives that will also help address this: > > http://track.sipfoundry.org/browse/XX-9447 > - We just couldn't get this in to 4.4... but hopefully will be in the > soon to follow 4.6 > > http://track.sipfoundry.org/browse/XX-9435 > > should we add one to PAT inbound port 5060 to port 5080 on trunks? :-)? > > > > > -- > Michael Scheidell, CTO > o: 561-999-5000 > d: 561-948-2259 > ISN: 1259*1300 > > *| *SECNAP Network Security Corporation > > - Best Intrusion Prevention Product, Networks Product Guide > - Certified SNORT Integrator > - Hot Company Award, World Executive Alliance > - Best in Email Security, 2010 Network Products Guide > - King of Spam Filters, SC Magazine > > > ------------------------------ > > This email has been scanned and certified safe by SpammerTrap®. > For Information please see http://www.secnap.com/products/spammertrap/ > ------------------------------ > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected]
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
