Hello,
later this week, on Thursday, Dec 17, I am planning to release a minor
version based on branch 4.2, respectively 4.2.7 -- it's been a while
since v4.2.6.
As usual, if there are issues not yet reported or patches to be
backported, write to sr-dev mailing list.
If time allows, in the same day or next days, I plan to do the last
release of branch 4.1 to mark the end of official packaging in 4.1
series. At this moment, the last two stable branches are 4.3 and 4.2.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
Hello,
based on the feedback after the proposal, there were no voices against
the new logo. Therefore, as of today, Kamailio project is officially
using the new logo -- see it at:
- http://www.kamailio.org/w/2015/12/new-logo-for-kamailio-project/
If you display one of the old Kamailio logos, we would encourage to use
the new one at your earliest convenience. That will help to propagate it
faster. Posting about the change on blogs, forums or social media
channels would be appreciated as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
Hai Team,
We have a customized sip routing script in opensip 1.11 now for good
performance and stability we
are moving to kamailio 4.1 .
So here am facing some issues related to kamailio module and funciotns
,with opensip
I Like to know the function using in kamailio that same in opensips
Like
fix_route_dialog()=OPESIPS
match_dialog()=OPENSIPS
Let me know how to use this above functions in kamailio ,or which one are
same functions am very confusing
Thanks
Yasir
Hello,
I am under the impression that the name dialog_ng creates confusion out
there and some people are using it instead of the classic dialog module.
Although it was started with goals of reworking dialog module with a
different concept (which was discussed mainly by some guys that
afterwards changed their job to non-voip area), dialog_ng ended up to be
tailored for IMS needs.
Probably we should do that refactoring of the dialog module, but
meanwhile dialog_ng doesn't refect that and some people are confused by
the current naming of the two modules.
Practically is more about convenience at this moment and if IMS
developers and users think it is not going to be a big overhead for
their deployments to be upgraded, I can take care to rename it. So,
while general opinion matters, I think we should see first what IMS devs
prefer.
I am personally not affected that much, so I am fine to keep it like it
is now -- in that case, proper notes should be added to documentation,
stating that dialog_ng must be used only for IMS (or when the config
writer knows very well what she/he is doing).
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu