On 2018 Jul 02 20:17:00, you wrote to me:

 MV>>> Ok, so maybe the example I gave was to complicated for you. How
 MV>>> about a minimalistic example. One that will still allow an Aussie
 MV>>> POTS node to dial his/her NC and dial 000 from the nodelist?

 MV>>> DIAL
 MV>>>  61- 0
 MV>>> END

 ml>> that won't work... a local has the 61-x stripped off... the above
 ml>> doesn't do that so at best they'll be trying to dial a LD domestic
 ml>> number... our system over here tells you you don't need to dial those
 ml>> extra leading digits and then hangs up... so no collection even over
 ml>> the LD wires which could cost more...

 TL> Actually, you can dial a local number with the area code.  In fact, on
 TL> my VoIP service, one _has_ to.

our service has changed here in the last years, too... we're also required to
dial the areacodes, now...

 TL> On a standard POTS line from here, I could dial 03 5432 1234 or 5432
 TL> 1234 and get the same result.

yeah, we didn't have that capability on wired lines... only on cellphones and
the cell service was smart enough to keep the areacode or drop it if it wasn't
needed... now that cellphones have pretty much taken over, all numbers have to
use the areacode because the exchanges are now duplicated across areacodes...

 TL> But on the VoIP service I have now, only the first example will work.

yep, same a cellphones...

 TL> FYI, my area code is 03, and numbers starting with 03-54 are local to
 TL> this area (at least within 100km).

this is one of those things, kinda like above and other discussions, where
knowing the local phone operation is manditory... especially for creating
something like a dial translation table... someone in the US or Nederlands
likely won't have that information...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... If at first you don't succeed, you'll get a lot of advice.
---