When using the siputils function encode_contact() on a message that
contains a user parameter e.g.
<sip:XXXXX00015;phone-context=national@10.YYY.1.92;user=phone>;tag=88930
it encodes fine e.g.
<sip:natted_ua*sip:XXXXX00015;phone-context=national**192.168.242.102*5080*udp@10.YYY.70.100
>
but decode_contact() errors due to the ";" (there is an explicit check for
it in the code)
I am currently working round this using
$rU = $(rU{s.replace,;,:});
to remove the ; as the user part is not needed for my application.
Would it be safe to remove the check for ";" ?
Gareth
Another year getting to its end! Looking back, looks like one with the
greatest achievements in the development of the project so far. Year is
not done, so I save that summary for one week later, there is still
stuff on its way to our source code repository.
Now I want to thank to everyone promoting and contributing to the
project, from developers to community members, and wish Merry Christmas
and great winter holidays to all supporters of our project!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hello,
I'm forwarding registrations to Freeswitch and adding a Path header using add_path_received() for endpoints behind NAT. When TCP is used, this results in a header like this:
Path: <sip:a.a.a.a:5070;lr;received="sip:b.b.b.b:35430;transport=tcp">
Freeswitch doesn't like the transport protocol inside the quotations and refuses to route a call to the registered user.
Constructing the header manually without the quotes such as:
append_hf("Path: <sip:$Ri:$Rp;lr;received=sip:$si:$sp;transport=$pr>\r\n");
solves the problem.
Is there a reason for the quotes?
Best Regards,
Spencer
Hello,
based on last irc devel meeting and feedback afterwards, most of the
people seem to be fine releasing next major release a bit earlier, in
order to:
- make websockets support and the other new features available in a
stable version
- allow proper development time frame for other planned new features
that wouldn't have been ready if the release would be 1-2 months later
So, considering the winter holidays, I propose to freeze development on
January 7, 2013, with full release about one month later.
It seems that many people are already using devel version to play with
websockets, meaning that we are staying very well with testing.
Other opinions?
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi,
I entered the command "kamailio -v" instead of "kamailio -V".
It looks like it starts kamailio again even that it was running....
the problem is that the kamctl_fifo and kamctl_ctl file are gone now. how
do i create the files again without restarting kamailio?
Thanks,
Uri
This was it for 2012, one of the greatest years in the history of the
project! One major release was done in the summer (version 3.3.x),
another one is few days before testing phase, most probably to be out by
mid of February.
The next major release includes several great features and edevelopments:
- support for websockets
- IMS extensions in the main GIT branch
- no more duplicated modules, integration of Kamailio and SER ended
There are big plans for 2013. First is the next major release, together
with participation at FOSDEM conference in Berlin. A bunch of other
events will open the path to our first dedicated conference for Kamailio
project - Kamailio World.
We hope to meet many of you at Kamailio World conference, in Berlin,
Germany, during April 16-17. Last organizing bits were sorted out and
registration will open in the first days of 2013 -- you can see more
details at:
- http://conference.kamailio.com
Looking forward to a great 2013 for Kamailio and everyone involved in
the project, from developers to community members!
All the best! Happy New Year!
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi,
I m a new kamailio user. Kamailio version is 3.3. I want to enable kamailio's tls support. I fallowed instructions from this link :
http://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates
And I also enabled tls module in the kamailio.cfg file. (definig WITH_TLS and adding listen=tls:myIP:5061 command) But after trying to start kamailio i got "failed to start" error. When I checked the logs there is nothing about tls or ssl. Actually I got an error while fallowing the link above. "openssl s_client -connect localhost:5061 -tls1" command returns connection failed 111 error. I thought that this is the reason failed to start. But where or what am I doing wrong? I searched the web and hear about SRV records. But there is no explanations about this, on your guide/wiki. I also read this link too but cant get my answer : http://sip-router.org/docbook/sip-router/branch/master/modules/tls/tls.html
Is there any idea or a better well-explained user guide about tls support?
Regards,
Burak
Hello,
My IP is 192.168.1.25 and I have added left zero padding i,e:
192.168.001.025 in the configuration file and try to start kamailio, it
works.. but along with that rtpproxy does not start. Once I revert back it
works. My script requires to add zero left padding for a specific purpose
and for that I cannot remove the left zero padding. Any solution to get
this work?
Regards
Selvam
Hello,
in November 2008 was decided to start integration of kamailio and ser
project, to get to same source code. About one year later, there was a
single source code tree, but there were several duplicated modules that
kept some confusion around the two projects.
As the time passed, it was shown better what modules are in the focus,
making the decisions to sort them out easier. The past weeks were
dedicated to removing duplicated, process that just ended -- at this
moment there is no duplicated module, all of them being integrated.
In summary, the modules from ser that had no conflict were moved as is
to modules folder, eventually after rename. The modules with conflicts
were merged, adding missing features to the most developed ones, moving
the others to obsolete folder. It happened that kamailio version of the
modules stayed in the majority of the cases, because they had larger set
of features (the core in v3.0.0 was kept from ser).
Please note that the extra features from ser modules might not be in the
same form, but alternatives that should offer same functionality at the
end. People using ser flavour so far should start testing the master
branch.
Do ask questions on the mailing lists if something that you used to have
in config is not longer available, so we can assist in migration and,
hopefully, create a migration guide on wiki.
There might few bits and pieces to tune here and there, soon we will get
into code freezing period for testing the next major release, a good
time for such adjustments. It is important that everyone using former
ser modules to report the issues that are found.
Many thanks to all those involved in integration efforts as well as in
new developments that kept the project flying!
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
