| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | none |
mark lewis -> David Drummond wrote: RC>>> Nope. The same rules would apply to Z1 as Z3. After all, this was RC>>> already an issue in Zone 1. Or do you forget the India problem? DD>>> What India problem? I've never had any problems with India... CS>> New Dehli, 91-1- phone code . No nodes there now so it's moot but CS>> used to have a small thriving community. DD>> How did anyone in USA contact them? ml> I N T E R N A T I O N A L D I A L I N G P R E F I X ml> ie: in my case, from Z1... ml> 1010288-011-91-1-xxxxxxxxxxxxxxx ml> 1010288 forces AT&T to be used... ml> 011 is the international dialing prefix ml> 91 is the country code ml> 1 is the city code (or whatever their breakdown is) ml> i could easily remove the 1010288- portion and still get there from here ml> by using my default longdistance carrier... It's a non-issue now that Z1 is moving it's IP contact info to the INA flag... -- regards David ---* Origin: So where the bloody hell are you? (3:640/305) SEEN-BY: 633/267 270 5030/786 @PATH: 640/305 280/5555 123/500 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™.