it should be possible to define more than one sbc profile for the same request. for example, there may be need to limit the number of simultaneous calls from an uri AND to an uri. at the same time, from uri may need to be anonymized and the request may need to be accounted for. it is very inefficient and cumbersome if sip proxy needs to route the same request four times to sems in order to achieve the goals of this example.
how about allowing more that one active sbc profile to be specified for the request, for example, allowing more than one P-App-Param header, where each header describes one profile for the request: P-App-Param: profile=call_control;uuid=$fu;max_calls=1 P-App-Param: profile=call_control;uuid=$ru;max_calls=3 P-App-Param: profile=anonymizer P-App-Param: profile=accounting;uuid=$var(calling_user) without this kind of capability, i don't see it possible to use sems sbc in other than very simple applications. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
