On Thursday 16 October 2008 13:59:46 Karl Fife wrote:
> On Thu, 16 Oct 2008 11:47:15 -0500, "Tilghman Lesher"
>
> <[EMAIL PROTECTED]> said:
> > If you could explain what ISN is, that might help.
>
> an ISN, stands for ITAD Subscriber Number, which in turn stands for
> 'Internet Telephony Administrative Domain Subscriber Number'.
> Essentially it is a very clever way of resolving numeric strings (easily
> be entered on a twelve-key numeric keypad) to full SIP uri's.
>
> for example [EMAIL PROTECTED] would be hard to enter on a telephone
> keypad.  ISN (available through Freenum.org) offers a solution.
>
> sip.ucla.edu is assigned the resolvable numeric string '269'.  The
> extension '1234' is already numeric.  The @ sign in the SIP uri is
> replaced by *.
>
> 1234*296 is dialed on the keypad, which resolves to [EMAIL PROTECTED]
> The call is completed bypassing the PSTN.
>
> Back to the main idea:
>
> The ISN is unambiguous.  There are no other dial strings that have a
> single * somewhere between position 2 and length-3
>
> It seems silly and kludgey to have to use an ISN prefix to recognize the
> ISN, so that it can be sent to the resolver, so that it can be routed,
> but I suspect that there's no way to differentiate that format with the
> parser as it currently functions.

In that case, yes, the Incomplete app could be used for that purpose.

-- 
Tilghman

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to