I actually wanted to use +3314529!****! as example.
But then as per your interpretation too it's not allowed.
Also, please refer to the specification below:
3GPP 23003-830: [Section 13.5 Public Service Identity (PSI)]
A wildcarded PSI consists of a delimited regular expression
located either in the userinfo portion of the SIP URI or in the
telephone-subscriber portion of the Tel URI.
TISPAN 182 025: [Section 6.1.2 Identification]
The wildcarded public user identity consists of a delimited
regular expression located in the telephone-subscriber portion of a tel URI
(e.g. tel: +3314529!****!) or in the user portion of a SIP URI (e.g.
sip:*[email protected]).
Our point of contention is that the TEL Uri is modified as per the text
given in above mentioned specifications.
So do we have any parallel draft in IETF to apply these modification to Tel
Uri ??
How are we supposed to handle scenarios like this ?
Regards,
Harbhanu
-----Original Message-----
From: Iñaki Baz Castillo [mailto:[email protected]]
Sent: Saturday, February 28, 2009 6:19 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [Sip-implementors] Tel URI query
2009/2/27 harbhanu <[email protected]>:
> Example: The following PSI could be stored in the HSS -
> "sip:[email protected]".
>
> "
>
> As per the above statements, the same example there would hold true for
tel
> uri too. Such as:
>
> tel:[email protected]
>
>
>
> But after referring to the ABNF defined by RFC-3966 I believe the same is
> not supported.
The above TEL uri is fully invalid. Basically a TEL uri can be:
- Local number:
tel: + 0123456789aBCDEF-,() + ;phone-context=XXXX
- Global number:
tel: + "+" 0123456789-,()
A tel URI number cannot contain other symbols. Also, note that in case
of a local number (so doesn't start by "+") then "phone-context"
parameter is mandatory.
Regards.
--
Iñaki Baz Castillo
<[email protected]>
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip
