Re: [reSIProcate-users] Uri and user parameters (if you do anything with user parameters, please read, or I will break your code)
>> Would you even need a getUserAsTelephoneSubscriber()?
> It would be very nice to have in either solution. Without it, to get
the phone-context param from
sip:2145551234;phone-context=+1@xxxxxxxxxxx;user=dialstring, you'd need to have
the app writer implement parse code to extract the parameter from mUser or
mUserParameters (depending on the solution we settle on). We already have this
parse code.
Oh, it seems I misunderstood your initial description: I got the impression
that by feeding the entire "2145551234;phone-context=+1" to a Token
constructor I would get the parameter from Token::param() and the number from
Token::value(), i.e. Token would do the parsing. This would of course require
that user() returns the complete string. If that's not the case I understand
the need.
(As you can see I have not really studied how the parsing works - that it does
has been sufficient …)
> user=dialstring is also fair game (RFC 4967). Although it appears that
> my example misuses it. :/
Ah, a cursory look at that RFC does indeed indicate a slightly wider scope than
the tel URI.
Rgds,
Mats