The issue with FreeSWITCH is just that 3pcc callflows (including invite w/o sdp) are disabled by default, they are certainly supported with a simple config change.
Mike On Nov 11, 2009, at 9:09 AM, Scott Lawrence wrote: > On Wed, 2009-11-11 at 08:24 -0500, M. Ranganathan wrote: >> Hello, >> >> In order to support late conference joins from sipxOpenfire, I am >> working on implementing Flow 4 of RFC 3725 in sipxCallController. >> >> This requires that the callee endpoint be able to respond sensibly to >> an out of dialog INVITE (no sdp) in arc 4 Figure 4 of RFC 3725. Are >> endpoints generally capable of such things or should I plan on >> throwing in and additional INVITE (DUMMY SDP) and sned the INVITE (NO >> SDP) in the established dialog ? I seem to recall some issues with >> FreeSwitch in this context so I thought it would be wise to inquire. > > Being able to respond to an INVITE that has no SDP is pretty basic. If > a phone can't support that, I suspect that it will have other problems > that make it difficult to use with sipXecs. > > That having been said, only testing will tell... > > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
