On Sun, 2010-01-31 at 15:50 -0600, Eric Varsanyi wrote: > I cannot establish a voice path with any of the polycoms and the talk > path to the IVR only works for about 30 seconds or so. .... > so I believe the firewall and its SIP support are roughly working.
Those two statements don't seem to go together... 'roughly working' ~= 'roughly not working' > I've seen a bunch of traffic on the list implying that to use an ITSP > you have to turn off 'Internet calling'. If you are using sipXbridge to connect to your ITSP, then you should turn off the 'Internet calling' checkbox - it is for configuring an external SBC (we're trying to work out a clearer set of configuration screens for all this). > Should I be able to follow the cheat sheet on the wiki wrt remote > workers and have it not break my ITSP functionality or these mutually > exclusive? > > FWIW I already have the ports forwarded in the (SIP aware) firewall > and my bridging working to voip.ms, It's hard to guess what the right thing to do is, since you have not described your configuration. In general, I strongly suggest that people _not_ use any other "SIP aware" firewall features. Experience suggests that they do more harm than good. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
