I can't really argue with that. Having something in the middle to actually enforce session timers seems like the key to limiting financial exposure
What I meant before was that I have hacked Kamailio in the past to basically do this UA functionality despite it being very much a UA and not proxy thing to do. It originated and absorbed special re-INVITEs that were spoofed and basically did dlg_bye() if no response. Nasty, I know. In the open source cottage industry world, what B2BUA do you recommend for high-volume applications of this? Yate perhaps? -- Sent from mobile device On Apr 29, 2009, at 3:33 AM, Iñaki Baz Castillo <[email protected]> wrote: > El Miércoles, 29 de Abril de 2009, Alex Balashov escribió: >> I agree; nothing can be forced. And yes, I do think proxy billing >> has >> vulnerabilities and technological limitations. >> >> But the benefit of simplicity and QOS should also be considered in a >> commercial environment. There is not a convincing reason to be >> handling media if you are an ITSP / arbitrage call shop. Yes, if you >> are running your own interconnected voice core, might as well, but >> otherwise I think the costs and path cannot be justified. >> >> I actually find the opposite of what Paul says to be true; most >> people >> seem to think media bridging is required for accurate billing and I >> have to convince them otherwise, whether by proxy or B2BUA means. > > I also agree on the no requeriment of handling media in order to > billing. But > I expect that a B2BUA (doing SST for leg_A and leg_B) is the only > accurate and > secure pure SIP accounting way. > > Best regards. > > > -- > Iñaki Baz Castillo <[email protected]> > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
