Subject: RE: [Sipping] Re: draft-sinnreich-sipdev-req-06.txt

From: "Francois Audet" <[email-masked]>
Date: Wed, 18 May 2005 19:37:03 -0400

Right.

And more importantly, things like internal corporate numbering 
plans don't really necessarily have a +1212 equivalent to map
to:

tel:4441234;phone-context=corporation.net
sip:4441234;phone-context=[email-masked];user=phone

(Where 444 is the corporate location code, unique in corporation.net)

And

tel:1234;phone-context=ny-office.corporation.net
sip:1234;phone-context=[email-masked];user=phone

(Where 1234 is unique in ny-office.corporation.net).

> -----Original Message-----
> From: Paul Kyzivat [mailto:[email-masked]] 
> Sent: Wednesday, May 18, 2005 13:03
> To: Christian Stredicke
> Cc: Audet, Francois [SC100:9T51:EXCH]; Johnston, Alan; 
> [email-masked]
> Subject: Re: [Sipping] Re: draft-sinnreich-sipdev-req-06.txt
> 
> 
> 
> 
> Christian Stredicke wrote:
> > About the dial plan discussion: Friends, please lets not 
> forget this 
> > is just a requirement. In this document we cannot nail down the 
> > details. Lets just mention that the phone (*if* it support a dial 
> > plan) is able to generate all kinds of URI. Practically, 
> that will be 
> > done by generating text with some ERE-matching scheme (see for an 
> > example http://snom.com/whitepapers/FAQ-04-03-27-cs.pdf). 
> But we don't 
> > have to solve this problem here in this document.
> 
> Yes, one can get carried away, and I don't want to do that. 
> OTOH, when trying to turn requirements into standards it is 
> not unusual 
> to have someone say "why do you specify XYZ when there is no 
> requirement 
> justifying that?"
> 
> Maybe some examples of the kinds of transformations that should be 
> possible would be better. E.g. dialed digits "5551234", based on 
> different configs should be able to end up as:
> 
>    tel:+12125551234
>    sip:[email-masked];user=phone
>    sips:[email-masked];user=phone
>    sip:[email-masked]
>    sips:[email-masked]
>    tel:5551234;phone-context=nyc1.example.net
>    sip:5551234;phone-context=nyc1.example.net
>             @example.net;user=phone
>    sips:5551234;phone-context=nyc1.example.net
>             @example.net;user=phone
>    sip:5551234;phone-context=nyc1.example.net
>             @example.net;user=dialstring
>    sips:5551234;phone-context=nyc1.example.net
>             @example.net;user=dialstring
>    tel:5551234;phone-context=+1212
>    sip:5551234;phone-context=+1212
>             @example.net;user=phone
>    sips:5551234;phone-context=+1212
>             @example.net;user=phone
>    sip:5551234;phone-context=+1212
>             @example.net;user=dialstring
>    sips:5551234;phone-context=+1212
>             @example.net;user=dialstring
> 
> In the simplest devices there may be only one transformation for all 
> dial strings, while for smarter devices the transformation may be a 
> function of the digits dialed, but the same range of possibilities 
> should be there in all cases.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP