Stefan Sayer writes: > most probably someone else will also need other call control policies, > so please keep the actual call control logic out of the sbc module. > performance-wise it's very little overhead calling a DI function.
i already implemented simultaneous call control in SBC.cpp and i'm currently testing it. why is prepaid in SBC.cpp, because it is a single very specific application. it passes lots of params to getCredit that i don't need in simultaneous call control; 402 reply string does not match simultaneous call control needs; connectCall di call that has lots of params is not needed in simultaneous call case. it is thus too far fetched to try to use it for limiting simultaneous calls. > what in the API i proposed does not fit your needs? as i mentioned, i didn't understand your proposal. if there is a way to generalize prepaid so very little extra stuff is imposed on other call control needs, then it is fine with me to use that generalized api. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
