|In article , |Dan Lanciani wrote: |> email@example.com (Robert Bonomi) wrote: |>
|[[.. sneck ..]] |>| |>|One that only understands NANP format numbers -- and chokes, and therefore |>|doesn't display anything, when confronted with something 'foreign'? |>| |>|In years past, I've encountered a lot of budget CPE gear that was very |>|US-centric. |>
|>What about stupid land-line switch (or perhaps "helpful" programming)? |>
|>I have some phones set up in an internal VOIP system. The number of |>one such phone is "2". I can dial out to the PSTN via a VOIP gateway |>service. When I call my POTS land line from "2" the caller ID is |>out-of-area. I always assumed that either the gateway doesn't trust |>me or the network doesn't trust the gateway. One day for some reason |>I called my ISDN land line from "2" and was surprised to see "2" come |>through as the caller id. I temporarily changed the station name of |>"2" to something that looked like a normal 10-digit US phone number and |>sure enough it showed up on my POTS land line caller ID. I suppose this |>is all illegal now, at least in Mississippi. :) | |'out of area' is displayed for CID data fields that the display box |"doesn't understand". Symptomatic of idiot-level programming in the |ID display.
No, in this case it is happening at the CO. I use RS232 CID dongles which are little more than Bell 202 AFSK receive-only modems. They give me the unaltered bit stream as sent by the CO. With my station ID set to "2" the CO sends my POTS line a CID multi-part message with reason for no number "O" and reason for no name "O". My ISDN line gets the "2".
Dan Lanciani ddl@danlan.*com