[SR-Users] Fwd: [RAI] SIPit 28 summary

Olle E. Johansson oej at edvina.net
Sun Apr 17 08:30:15 CEST 2011


16 apr 2011 kl. 20.27 skrev Daniel-Constantin Mierla:

> 
> 
> On 4/16/11 7:30 PM, Olle E. Johansson wrote:
>> 16 apr 2011 kl. 15.59 skrev Iñaki Baz Castillo:
>> 
>>> 2011/4/15 Klaus Darilion<klaus.mailinglists at pernau.at>:
>>>> Support for various items in the proxy/registrars:
>>>>  50% path
>>>>  50% outbound
>>>>  33% sip/stun multiplexing
>>>>  20% diversion
>>>>  18% gruu
>>>>  17% history-info
>>>>  17% service-route
>>> Correct me if I'm wrong:
>>> 
>>> Items implemented in Kamailio/sip-router:
>>> - path
>>> - diversion
>>> 
>> Yes, Kamailio is behind and after focusing so much on the merger of the code I think it would be good to plan some new features for a coming release.
> I think this statement is not true. While a lot of work was indeed done on merging code, there were a lot of new featured added, much more than we had we previous major releases, many based on standardizations (e.g., presence extensions to conference, dialog info, xcap, a.s.o).
> 
> The the core supports processing stun, see ser_stun.{c,h} - the guys at ser added that very long time ago.
> 
> As for next release, there are lot of features added (http://sip-router.org/wiki/features/new-in-devel), more to come, but I think most of developers here got tired hunting the ghosts of IETF specs that never were any useful nor had a touch with the reality.
> 
> As of myself, I really work now on what is demanded, there is no time to jump and implement any rfc/draft published based on theories elaborated by guys that never implemented their specs. Moreover, some of them are now in different boat and make "incredible" statements about sip considering their role in the past with this protocol...

That's good feedback. I meant that we're behind the IETF. But so are most implementations out there... 

Sorry if I upset anyone. That wasn't my intention.


/O


More information about the sr-users mailing list