[Devel] discussion of roadmap for 1.3

[Victor Gamov]

Klaus Darilion wrote:
> 
> 
> Victor Gamov wrote:
>> Dialog-based extensions which may be useful:
>>
>> -- allow to destroy dialog from MI with accounting generating.
>> -- try to find idle or disconnected dialog (ping-like, get statistic 
>> from rtpproxy or some other method) and close it with accounting 
>> generating
>>
>> This features usefull for example in next situation:
>> A calls B. When conversation complete A and B disconnects from network 
>> (unplug cable for example) and OpenSer  never gets "BYE" and this call 
>> cann't be acounted properly.
>>
>> -- allow Openser to be SBC. Now we can use OpenSER for this with some 
>> gymnastic in rewriting of request and response body using avpops 
>> module, But it's really difficult to write and support this config.  
>> New OpenSER module (may be) called SBC can do all this work with 
>> interaction some other modules (RR, TM and others). This module must 
>> rewrite SIP messages to mask all internal resources for outgoing 
>> (relative to OpenSER) messages and rewrite all incoming messages to be 
>> appropriate of outgoing messages.
> 
> What do you mean with SBC? SBC typically have dozens of features (NAT, 
> ...). Do you mean topology hiding or an other feature?

The primary goal is to hide topology and send all SIP traffic through 
OpenSER. Now we can rewrite Contact: (not only for NATed devices but for 
all), RURI and some over headers from config and mask addresses in this 
way. We can add RR also. But it's really difficult and sometimes 
impossible to rewrite all headers. Smart module which allow to work 
OpenSER in SBC-only mode and do it automatically may be useful in this 
situations.

>> -- (dreams) SIP-H.323 converter. I know that many of such converters 
>> exists in real world (one of famous and commonly used is Asterisk). 
>> But I think that native OpenSER SIP-H.323 converter can helpto OpenSER 
>> to be more useful. If somebody familiar with H.323 he can write this 
>> module based on OpenSER Dialog module
> 
> There is already Asterisk, yate, freeswitch ... this IMO we should fokus 
> on SIP.

yes, you are right. We must do one thing but do it perfect.
My idea is convert SIP-H323 on one hop/host and don't use anything over 
OpenSER

Thanks

--
CU,
Victor Gamov