and to be a little more picky about "why" port forwarding does not actually change the destination of the sip message.when you have an invite to port 5060 and forward it to port 5080 in your firewall, the original sip message and header is stills saying port 5060. so unless you have a way to intercept and rewrite the actual sip messages, finding an itsp that can send you calls on port 5080 might actually be easier.
On Sat, Jul 9, 2011 at 6:14 AM, Michael Picher <[email protected]> wrote: > Tony has it right... > > Don't confuse how you initiate a SIP conversation vs. how the itsp > initiates a SIP conversation. > > You can initiate and send to them on 5060 and your firewall remembers > what's going on. > > The need to send to you on 5080 for sipXbridge. They can send from > whatever port they'd like. > > Mike > > > On Sat, Jul 9, 2011 at 4:56 AM, Tony Graziano < > [email protected]> wrote: > >> to clear this up... >> >> if you register from sipx, unless you change the defaults, it will >> register on port 5080. The ITSP "should" follow your registration port and >> send the calls on the same port. The cal from the ITSP will originate from >> port 5060 and have a destination of 5080. At the same time, calls FROM sipx >> will originate and have a destination port of 5060 (by default). >> >> >> On Fri, Jul 8, 2011 at 10:17 PM, Todd Hodgen <[email protected]>wrote: >> >>> Maybe I'm mistaken, but I think there is an error in this response. >>> >>> " note: if you send REGISTRATION to the itsp, it will come >>> FROM port 5080, and they should RESPON on port 5060. >>> if you use ip based authentication, and not registration, >>> set everything on sipx back to normal (might need to delete >>> gateway), ask them to send trunking to 5080, and see what >>> happens." >>> >>> I believe it should read that "if you send registration to the ITSP, it >>> will >>> come from Port 5060, and they should Respon on 5080." The ports are >>> reversed. >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Michael >>> Scheidell >>> Sent: Friday, July 08, 2011 1:36 PM >>> To: [email protected] >>> Subject: Re: [sipx-users] ITSP signalling problem 32 second cut off >>> >>> >>> Content-Type: text/plain; >>> charset="utf-8" >>> Content-Transfer-Encoding: 8bit >>> Organization: SipXecs Forum >>> In-Reply-To: <[email protected]> >>> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <61367> >>> Message-ID: <[email protected]> >>> >>> >>> >>> it sounds like your itsp wants to send trunking to port >>> 5060, when sipx wants it on 5080. it also sounds like you >>> (patted) port natted inbound 5060 to 5080, and expected it >>> to work. >>> (it won't work like that on pfsense). >>> >>> and/or, you tried to set the trunk port to 5060 on one of >>> the sipx configuration screens (that won't work either), >>> sipx is toying with the idea of making this work right in >>> sipx 4.6. >>> >>> if I misunderstood your steps, sorry, but I have fought this >>> issue for over a year. >>> >>> the recommend way to fix it is get an sbc that will answer >>> on 5060, but proxy it to sipx on 5080. >>> >>> I DO have a firewall in place that will PAT inbound 5060 to >>> 5080, but its tricky, doesn't seem to work for everyone, so >>> its a 'ymmv'. >>> >>> other issues might be that you don't have your fireall with >>> 'alg' turned off, and/or you might be using some firewall >>> with 'sip helpers'. >>> >>> sipx doesn't like alg, or sip helpers. sipx wants to do all >>> the heavy lifting themselves. >>> >>> so, you might have multiple problems, compounded by trying >>> to PAT 5060 to 5080, >>> >>> note: if you send REGISTRATION to the itsp, it will come >>> FROM port 5080, and they should RESPON on port 5060. >>> if you use ip based authentication, and not registration, >>> set everything on sipx back to normal (might need to delete >>> gateway), ask them to send trunking to 5080, and see what >>> happens. >>> >>> we do like the features of sipx, and they really can't be >>> beat, even if you needed to pay for it!. >>> >>> >>> >>> -- >>> -- >>> Michael Scheidell, CTO >>> SECNAP Network Security Corp >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> ----- >>> No virus found in this message. >>> Checked by AVG - www.avg.com >>> Version: 10.0.1388 / Virus Database: 1516/3751 - Release Date: 07/08/11 >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> ====================== >> >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.326.5325 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> <http://support.myitdepartment.net>Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > Michael Picher > eZuce > Director of Technical Services > O.978-296-1005 X2015 > M.207-956-0262 > @mpicher <http://twitter.com/mpicher> > www.ezuce.com > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
