| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | none |
CS> *** Quoting mark lewis from a message to Ward Dossche ***
WD> ZC/3 on the other hand does consider the "000"-matter
WD> potentially disastrous and does not support its usage in the
WD> nodelist. As fellow ZC's the least what we can do is to
WD> respect such a wish of a colleague-ZC.
ml> seems to me that those in Z3 who raised this argument did not consider
ml> the international dialing code that must be dialed before getting to t
ml> part of the number that might cause this percieved problem...
CS> Huh? They dont use an international dialing code in Z3 to reach
CS> 000 (emergency like 112 or 911 in other places).
correct, but they do have to if the 000 is the _country code_ in a
listing... remember how phone numbers are laid out...
countrycode-areacode-citycode-restofnumber
1 - 800 - 555 - 0100
000 - 192 - 168 - 2 - 1
and again, this all goes back to "properly configured mailer" and
that includes a properly set up "dialing translation table"...
that's where you tell the mailer what areacodes are local calls...
everything else is not local and would get the national or the
international dialing code prefixed to it... and that, right there, is the
point at which it stops being a problem...
)\/(ark
* Origin: (1:3634/12)SEEN-BY: 633/267 270 5030/786 @PATH: 3634/12 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.