Hello,
Inaki, I pinged you since you may be more familiar with procedures about
all this IETF output, but maybe others here can provide useful
information as well.
At this moment the parser in Kamailio for Diversion header considers it
as with similar format as To header.
Diversion (defined in an *Historic* rfc5806) is obsoleted by
History-Info(*Standard track* rfc4244). Its definition in rfc5806 is:
Diversion = "Diversion" ":" 1# (name-addr *( ";" diversion_params ))
and it is like To header. However, a newer *Informational* rfc6044,
redefines Diversion as:
Diversion = "Diversion" HCOLON diversion-params
*(COMMA diversion-params)
diversion-params = name-addr *(SEMI (diversion-reason /
diversion-counter / diversion-limit /
diversion-privacy / diversion-screen /
diversion-extension))
So in rfc6044, the sintax allow comma separated bodies for one Diversion
header, which was not in rfc5806. Obviously, the current diversion
parser throws error, so I guess it has to be updated to accept a format
similar to Route headers.
My question is, apart of rfc number and the policy more recent (bigger
values) obsoletes older (lower value) specification, does the
Informational or Historic category to set some extra rules?
Btw, are people here still using (or ever used -- I didn't so far)
Diversion?
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hello,
Claudio Furrer <elcaio(a)gmail.com> has now git commit access for his work on
gentoo packaging. He create several patches and extensions for our gentoo
package files in the last months and also maintain an own unofficial portage
overlay tree at http://gpo.zugaina.org/net-misc/sip-router since some time.
He just updated the gentoo packages in git master today, so if you're an
gentoo user why not just give it a try - he is looking forward to your
feedback.
Welcome Claudio!
Best regards,
Henning
Hello,
I would like to package 3.2.2 on the same day with IRC devel meeting
announced in the previous email (if is is happening this month) -- it is
getting close to 2 months since v3.2.1.
If you are aware of issues, report them on bug tracker to see what can
be done before 3.2.1.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda -- http://twitter.com/miconda