Hello,
On 9/14/11 9:40 AM, Carsten Bock wrote:
Hi Olle,
it added support for URN-URI's and for CID-URI's. I think it is limited to support only few URI schemes for performance reasons.
the performance reasons are for well-known/very common values, but we should support the other as well. It is the same with SIP methods.
Cheers, Daniel
Carsten
2011/9/14 Olle E. Johanssonoej@edvina.net:
14 sep 2011 kl. 09:09 skrev Carsten Bock:
Hi Klaus,
The problem is not the TM-Module, but the URI-Parser of the core which does not support URN's. The OpenIMSCore has support for URN-URI's, I've ported the support to my carstenbock/ims branch; i will try to add the support for URN's to the trunk-version this week.
Does this mean ONLY URN's or a generic support for *any* URI scheme?
/O
Regards, Carsten
2011/9/14 Klaus Darilionklaus.mailinglists@pernau.at:
On 13.09.2011 22:12, Olle E. Johansson wrote:
13 sep 2011 kl. 22:10 skrev Iñaki Baz Castillo:
2011/9/13 Daniel-Constantin Mierlamiconda@gmail.com: > you started the discussion when many of us were partying for 10 years > celebration :-) so it got lost -- reminders are recommended always. > > There is no real good reason why not accepting unknown transport > protocols > non-top Vias. The limitation is coming from implementation of the > parser, > but should be relaxed. > > The best would be to introduce PROTO_OTHER in the enum of protocols > (ip_addr.h, enum sip_protos) and in case this type is encountered, read > the > string value of the protocol. > > Via parser is using quite a lot of states, so if you look to update it, > when > it gets to the state where the transport (proto) part starts, if does > not > match UDP, TCP, TLS or SCTP, then set vb->proto=PROTO_OTHER and start > and > length of the token in vb->transport. Should not be very complex to > enhance > once you get into via parser states. > > I may fix it before 3.2.0 is out if you are not doing it meanwhile, but > cannot give you a timeline for it right now.
Thanks a lot Daniel !
I will try to do it by myself by following your useful indications. If I get it I will announce prior to commiting it.
That reminds me of my favorite issue: Is it possible to get Kamailio to accept other URI schemes than SIP and SIPS?
Oh yes, tm module fails for example if RURI is a service URN.
regards klaus
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Carsten Bock CEO (Geschäftsführer)
ng-voice GmbH i. Gr.
http://www.ng-voice.com mailto:carsten@ng-voice.com
Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
- Olle E Johansson - oej@edvina.net
- Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev