On 11/20/14 1:38 AM, Ambrish Kumar wrote:
Hi All,
We read the RFC 3966 and understood that the global number should be
prefixed with “+” and if it is not prefixed with “+” then it is considered
to be a local number and a phone-context is a MUST.
But the section 7.4 is a bit confusing to the ABNF syntax of global number.
Does it mean that, if the user dials “00” prefix as an example
(“00919840012345”) and it reaches the server without a phone-context, do we
still need to consider it as a global number in the server side..?
I agree with Brett. If the user dialed “00919840012345” then your only
valid way to form it into tel URI format is to reformat it into global
number format ("+1919840012345") before sending to the server.
While you could *syntactically* form it into local-number format, such as:
tel:00919840012345;phone-context=+1
that violates the semantic rule that it must be formatted as a global
number if that is a valid representation.
If you can't do the global number conversion locally, then you can
format it as a sip URI in dialstring format [RFC4967]:
sip:00919840012345;phone-context=+1...@example.com;user=dialstring
If we consider that way, the ABNF syntax is contradicting.
Kindly clarify the section 7.4 RFC 3966:
7.4. Do Not Confuse Numbers with How They Are Dialed
As an example, in many countries the E.164 number "+1-212-555-3141"
will be dialed as 00-1-212-555-3141, where the leading "00" is a
prefix for international calls. (In general, a "+" symbol in E.164
indicates that an international prefix is required.)
This is telling you that dial strings need to be reformatted to put them
into tel format.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
