Juha Heinanen wrote:
Klaus Darilion writes:
What it still do not like on sems that it reuses parts of (open)ser (fifo communciation ...) - or has this changed?
sems/openser communication is based on unix sockets. you can take conf_auth application, remove most of its lines, and you have an application that disconnects the call after a given period. period can can be given to the application on a call-by-basis, for example, in some P header, queried from database, radius, etc.
Sounds interesting. Is it a "real" B2BUA (2 different dialogs, different call ids/tags on the 2 call legs, no "privacy" data in one leg can be seen in other leg?)
Does it support RTP/RTCP relaying with multiple streams?
Does it support NAT traversal or is still nathelper+rtpproxy necessary?
Does it work out of the box with openser1.1?
thanks klaus