RE: [Enum] RE: Draft IETF ENUM usage scenarios

["Zmolek, Andrew (Andy)" <zmolek@avaya.com>]

There are several possible methods of going to a PSTN/E.164 number from a SIP address, but in general ENUM has nothing to do with this:

- Your home SIP redirect server could provide a tel: URI to the SIP originator and effectively force it to find a PSTN gateway to complete the call (not sure if this is "legal" in SIP, though)

- Your home SIP proxy/gateway could complete the SIP session by transparently gatewaying the call over the PSTN (Or PBX system, which is how my SIP address rings my regular desk phone)

- You could create a registry similar to enum that maps a SIP URI to an E.164 address

The latter requires a lot of agreement among many parties (vendors, developers, end-users, etc.) and would not happen very soon. But gatewaying SIP calls back to the PSTN or private PBX or POTS lines is easy enough to do today.

--Andy Zmolek 
    Senior Security Consultant 
      Network Consulting Services 
        Avaya Inc. 

            zmolek@avaya.com 
              +1 720 444 4001 
                sip:zmolek@avaya.com


> -----Original Message-----
> From: Lind, Steven D, ALASO [mailto:sdlind@att.com]
> Sent: Wednesday, October 16, 2002 8:21 AM
> To: Keats, Evan
> Cc: enum@ietf.org
> Subject: [Enum] RE: Draft IETF ENUM usage scenarios
> 
> 
> Evan,
> 
> No, tht's not a scenario I/we have considered. It sounds like 
> an interesting scenario and I'd like to think about it some.
> 
> The ENUM WG is starting out with the premise that one only 
> knows an E.164 telephone number instead of an email address. 
> One could imagine that instead of a number, you could use a 
> unique FQDN, e.g., steven.d.lind.name, that could point to 
> the various NAPTR records. That would require the application 
> software to behave differently than looking up a telephone 
> number. And the problem with uniqueness of the names would 
> not guarantee that you've reached the right steven.d.lind (I 
> know of several Steven Linds, not sure about those with same 
> middle initial).
> 
> Steve
> 
> --------------------------------------------------------------
> ------------------
> Steven D. Lind                                Tel: 973-236-6787
> 180 Park Avenue, Bldg. 2                Fax: 973-236-6453
> Room 2G25                                    sdlind@att.com
> Florham Park, NJ 07932
> --------------------------------------------------------------
> ------------------
> 
> 
> -----Original Message-----
> From: Keats, Evan [mailto:evan.keats@nz.unisys.com]
> Sent: Wednesday, October 16, 2002 5:17 AM
> To: Lind, Steven D, ALASO
> Subject: Draft IETF ENUM usage scenarios
> 
> 
> 
> I have just read your draft document with great interest.
> 
> I am interested in the following  IP origination - PSTN 
> termination scenario
> 
> Jenny Jones with her SIP client wants to call Evan Keats.  
> Knowing that my
> email address is evan.keats@nz.unisys.com, she tries
> sip:evan.keats@nz.unisys.com.   
> 
> However, rather than answering the call with a SIP client,  I 
> would like to
> take the call on my landline [one phone on my desk is quite 
> enough :) ]
> 
> I have been trying to fathom out how we could use ENUM to 
> allow me translate
> sip:evan.keats@nz.unisys.com to 
> 6.4.4.4.6.2.2.0.5.5.e164.arpa, but have not
> made tangible progress.
> 
> Is this a scenario you have considered, or would consider for 
> you document ?
> 
> Or am I missing something ridiculously obvious ?
> 
> Thanks.
> 
> Regards,
> Evan Keats
> 
> Unisys
> Unisys New Zealand
> Ph: 64-4-462 2055
> Fax: 64-4-462 2127
> Net2: 848 2055
> evan.keats@nz.unisys.com
> 
> 
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://www1.ietf.org/mailman/listinfo/enum
> 
_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum