Tilghman Lesher wrote:
On Saturday 30 April 2005 05:04, Olle E. Johansson wrote:
Since it's obvious that this is an unresolved issue, we should
avoid the issue at this juncture in the IAX2 spec and simply
specify that ASCII is the character format. If at some point in
the future these arguments are resolved, then at that time a
revision may be made to the IAX2 specification allowing UTF-8 or
another character set.
If you actually read my proposal, your proposal is in line with
mine, but I limit it a bit more. I am saying that for
extensions/dial strings, let's stick to numbers.
I'm afraid that's a non-starter; we already have support in IAX2 for
letters/numbers; rolling back the current featureset seems like a
sure way to cause all sorts of future incompatibilities.
And for Caller ID
names outside of SIP, let's stick to whatever the PSTN standardize
on. On top op this, add a layer that properly supports SIP UTF8
international caller ID names and named extensions.
Hang on; we're talking about IAX2, not SIP. Don't confuse the issue
by intermingling the two. Just because SIP supports something doesn't
mean IAX2 has to.
As I said "If you actually read my proposal" :-)
My proposal, which started this thread that you are commenting in,
talks about how to handle both SIP, IAX2 and other strings in Asterisk.
Please read it before you make more comments and try to change the topic.
/O
_______________________________________________
Asterisk-Dev mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
