Realize this is all because you are using an "inflexible" ITSP. Siproxd is not flexible or elegant.
We use ingates all the time in front of sipx for itsp and re$otes both on port 5060. Opensbc is a beast to configure. I use polycoms all the time remotely, so YEAH it is probably the remote users fireall that needs alg or spi turned off. That being said, use an sbc that is capable and configured properly and you'll be all right. I wouldn't use above firmware 3.1.3 on a remote polycom at this time. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Fri Aug 20 21:23:38 2010 Subject: Re: [sipx-users] SIMPLE SOLUTION FOR ITSP'S WHO SEND TO PORT 5060 Re: iptables experts: port forwarding. On 8/20/10 7:24 PM, Martin Steinmann wrote: > > Joegen > > I think a possible solution close to what you are suggesting is > captured here. This would likely be the most elegant solution. > > http://track.sipfoundry.org/browse/XX-5010 > > Solving the problem described here might be easier and get us part of > the way. Eventually we will need to address both. > > http://track.sipfoundry.org/browse/XX-4818 > > http://track.sipfoundry.org/browse/XX-8692 > > to further complicate matters are pure sip url calls from 'the world'. If you are forwarding 5060 -> sipxbridge:5080 and 5061 ->sipxbridge:5060, what happens when I make a sip:[email protected] to you? do I have to use sip:[email protected]:5061? I assume all this goes away if we put a REAL sbc in front of sipx? anyone know if the freeswitch package for pfsense can be used to do this? or sipproxyd? this is what you are talking about. so, bottom line, if the ITSP wont' signal on port 5080, its a no go for now, right? ps, remote users: I am not convinced this works. I tried a cisco (you yelled at me) I bought two polycom phones to test. still can't get remote to work right. will document that later . polycom 335. 3.2.1 firmware (no choice) you put a call on hold, you can't pick it back up (no audio). you transfer a call (which puts it on hold), you lose audio. firewall problem? yeh, right. blame the firewall now. the cisco remote didn't have those problems. all the cisco did was lose audio after 5 mins. must be the firewall. -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 ISN: 1259*1300 > *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best in Email Security,2010: Network Products Guide * King of Spam Filters, SC Magazine 2008 ______________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). 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/
