On 06.08.2009 10:43 Uhr, Martin Hoffmann wrote:
Iñaki Baz Castillo wrote:
The current "support" of TEL uri is also a "hack", since after parsing
a TEL URI what we have is:
- $rU = null
- $rd = the TEL number
(note: parhaps is the opposite)
I'd realy would like to have something as:
- $rtU = RURI TEL number
- $rtparams = RURI TEL parameters
Call me biased, but I do prefer the select stuff:
@ruri.type -> "tel"
@ruri.user -> number
@ruri.params -> parameters
@ruri.params["phone-context"] -> phone-context parameter
in K there are transformations that can be used as well for other
variables that contains URI:
$var(x) = "sip:dan...@xyz.com";
$(var(x){uri.user})
http://www.kamailio.org/dokuwiki/doku.php/transformations:1.5.x#uri_transformations
Cheers,
Daniel
The only thing I always need to look up is whether it is user or
username. One could probably add a sub-select "number" which is only
valid if the type is "tel" or if the username part of the URI consists
of characters valid in a TEL URI.
I know C people like their functions and variables to have cryptical
names for hyst[eo]rical reasons, but this is so 20th century.
Regards,
Martin
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
* SIP Router Bootcamp
* Kamailio (OpenSER) and Asterisk Training
* Berlin, Germany, Sep 1-4, 2009
* http://www.asipto.com/index.php/sip-router-bootcamp/
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
