I have no doubt that it will work with freeswitch when running through the patch. Same thing with YaTE.
I don't think my FreeSWITCH settings would be a good thing to post on the wiki because I essentially turned off all SIP security settings in an effort to get it working. YaTE, on the other hand, was actually pretty simple to get working and the security settings are simple too. If either of them properly supported all facets of REFER I would be posting my howto's here but seeing that they don't, I'm better off running straight to my Adtran router. I will try patch21 and report my findings. I will also, if necessary, post a bug with a snapshot detailing my issues. Tony Graziano wrote: > Thanks for the update Ranga. > > Josh, if you do apply patch21.zip and have this working with > freeswitch on pfsense, please let the list know. I would suggest using > a separate posting. Perhaps a write-up for the wiki so others can > follow as well if you have the time and get that far, with an example > config. > > Tony > > > > On Sat, Nov 14, 2009 at 11:07 AM, M. Ranganathan <[email protected] > <mailto:[email protected]>> wrote: > > On Sat, Nov 14, 2009 at 1:00 AM, Josh Patten <[email protected] > <mailto:[email protected]>> wrote: > > It also appears that YaTE is the same way. that one was a little > easier to > > set up, but it's the same old song and dance: REFER trips it up > every time. > > > > I really wish sipXbridge was stable for me. Even with patch20 I > drop to one > > way audio on my local LAN after about 5 minutes and locations > that are just > > a couple of milliseconds ping away from the bridge software drop > calls > > completely after a couple of minutes, and it's not my Adtran > router, even > > when I'm bridging to other SIP devices this happens. I've sent > Ranga a > > snapshot before but because we thought it was my Adtran router > it never went > > anywhere. perhaps I should submit a bug with , or do you still > have my > > original snapshots Ranga? > > > > Disclaimer: One should note that until our QA signs off on any given > version, that is to be thought of as a development versions that are > placed at your disposal for early testing. These snapshots are > unofficial updates to help those who do not wish to build source code. > > We had recently made several changes as a result of interop testing > with Nortel CS1K and hence the inevitable regression that followed. It > might be that you hit something like that. It is going through QA and > I updated the patch again. ( Our QA is pretty thorough but the nature > of problem is that it is very laborious and takes a while to do. > Thanks for bearing with us on that. ) > > Please feel free to send me a sipx-snapshot ( see instructions on > trouble shooting on the SIpXBridge wiki page ) after checking the logs > to make sure it is not something obvious on your end. > > > Regards, > > Ranga. > > > > > > > -- > M. Ranganathan > _______________________________________________ > sipx-users mailing list [email protected] > <mailto:[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/ > _______________________________________________ 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/
