61 replies to this topic

[Strom Carlson]

We've been needing one of these for a long time now:

877-823-2565 (easy to remember as 877-TADA-LOL)

I know it works correctly for regular POTS lines (00), mobile phones (61, 62, 63), and coin phones (27, 70). I haven't been able to test it with other sets of ANI II digits though; if you find one that this number doesn't read back correctly, let me know

[GIJoe]

Will it not accept 02 for an ANI II? I could only get busies the few times I tried.

[Strom Carlson]

how are you routing it to try and deliver 02?

[pbx43k]

mobile phones (61, 62, 63)

My cell comes up 23. Is that normal?

::edit::
Found ANI II list

23 

Coin or Non-Coin - on calls using database access, e.g., 800, ANI II 23 is used to indicate that the coin/non-coin status of the originating line cannot be positively distinguished for ANI purposes by the SSP. The ANI II pair 23 is substituted for the II pairs which would otherwise indicate that the non-coin status is known, i.e., 00, or when there is ANI failure.

ANI II 23 may be substituted for a valid 2-digit ANI pair on 0-800 calls. In all other cases, ANI II 23 should not be substituted for a valid 2-digit ANI II pair which is forward to an SSP from an EAEO.

Some of the situations in which the ANI II 23 may be sent:

    * Calls from non-conforming end offices (CAMA or LAMA types) with combined coin/non-coin trunk groups.
    * 0-800 Calls
    * Type 1 Cellular Calls
    * Calls from PBX Trunks
    * Calls from Centrex Tie Lines

Must be a 'Type 1 Cellular Call'.

Edited by pbx43k, 22 March 2005 - 05:18 PM.

[Strom Carlson]

23

Coin or Non-Coin - on calls using database access, e.g., 800, ANI II 23 is used to indicate that the coin/non-coin status of the originating line cannot be positively distinguished for ANI purposes by the SSP. The ANI II pair 23 is substituted for the II pairs which would otherwise indicate that the non-coin status is known, i.e., 00, or when there is ANI failure.

[pbx43k]

I guess so.

[marks]

Yes, Yes, Im a n00b, I come up as 00...

*on my mobile*..

[Strom Carlson]

my mobile also comes up as 00. I wonder if it's a t-mobile thing.

[marks]

And ATT/Cingular... Thats what I am on.

[pbx43k]

I'm Cingular, and as discussed previously, come up as 23.

[GIJoe]

I tried to get 02 by just opdiverting to it

I also have T-Mobile (prepaid), and got a 62.

[Murd0c]

Back on the 800-555-1140 number, my AT&T cellphone would constantly give off an 00. I could never figure out why.

[Strom Carlson]

I tried to get 02 by just opdiverting to it

I also have T-Mobile (prepaid), and got a 62.

opdiverting how? AT&T opdiverts always used to give 23 in the 555-1140 days.

[doug]

certain odd areas and mixed with odd carriers wont give the proper II digits, so they'll send a 00 or 23. With the world of crappy GSM there's no sure thing.

[TelcoBob]

opdiverting how?  AT&T opdiverts always used to give 23 in the 555-1140 days.

i tryed to AT&T opdivert and each time all i'd get was a busy signal

Edited by TelcoBob, 22 March 2005 - 09:32 PM.

[P(?)NYB(?)Y]

my mobile also comes up as 00. I wonder if it's a t-mobile thing.

well, i run on a smaller provider called metroPCS, and i get 00 as well

[doug]

metropcs is leet!!, but really sketchy sometimes. I wish we could get that out here in LA. I know people in san fransisco that have that.

[greyarea]

as I recall if this is the same number its serviced by SBc,Whered you come across the number?

When I tried to SE SBC they just gave me the BTN Verification number.

[P(?)NYB(?)Y]

metropcs is leet!!, but really sketchy sometimes. I wish we could get that out here in LA. I know people in san fransisco that have that.

yeah, i must say, the service can get kind of shaky sometimes, but overall i've not had a problem with the service or the employees.

[doug]

can you roam nationally with your metropcs or do you have to be in your county to keep it unlimited?