Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <CACEoiQF69=cj3EMufXk4-12r=8szwr+zyb85sbc30f0emlm...@mail.gmail.com> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <66558> Message-ID: <[email protected]>
Ok, That's interesting. So if I read you correctly; sipXecs is a stateless proxy only? Similar in objective to SER and its derivative projects? I tried Freeswitch for this application, but although it works, I wasn't impressed on how it rewrites SIP messages and related SDP; thus searching for a 'pure sip' implementation that lead me to sipXecs. The SBC used in this case can process the REFER; but in doing so it means the From: and To: headers won't be rewritten by sipXecs as it's done on INVITEs. Also, if sipXecs won't intervene in putting calls on/off hold; what's the purpose of the MOH implementation within sipXecs? How is a typical implementation supposed to work? Somehow I expected sipXecs would be stateful; although not necessarily a B2BUA as stated in the 'why-sipxecs' page on the sipfoundry portal; thus being able to handle basic PBX functionality internally. Perhaps an example would be appropriate. Is there a sort of showcase implementation that mentions the role of different network elements in relation to sipXecs? Like the handling of call transfers and MOH. Regards _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
