On 20/08/2010, at 6:19 PM, Tony Graziano wrote: > Revisit your firewall please... after you can confirm the ITSP sees you > registering or is sending you calls on port 5080...
The ITSP has confirmed they see both accounts registering, and they are sending calls through on port 5080. > > You say you are using pfsense. pfsense needs to have "firewall, nat, outbound > set to Manual Outbound NAT rule generation (Advanced Outbound NAT (AON))", > and your existing rule also needs to have static port yes for the WAN <source > is subnet where sipx is on>. Yep, we have "Manual Outbound NAT rule generation (Advanced Outbound NAT (AON))" enabled. And there is one outbound nat rule for our main LAN subnet which has 'Static-port' ticked under Translation. > > Did you follow this tutorial for pfsense? > > http://blog.myitdepartment.net/?p=37 Yes, Shane who set it up has confirmed he used the instructions on your blog to set up our pfsense for sipx. He reckons he had this before with two Internode accounts in version 4.2, but with two different ITSP's it worked fine. Another thing I've found that happens is quite interesting. The internal extension rings for a time, then it's second line starts ringing before the first one stops ringing. And a third line starts ringing a short while later then the first two lines stop ringing, and so on until Internode eventually block our IP because of all the 'loop detect' messages they receive from us. Something is looping in sipxbridge or sipxproxy I think and spawning multiple calls from the one incoming external call. Cheers Jesse
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
