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/
