Mailing List Archive

CallerID conundrum...
when calls are made from a voip phone to a Cingular or AT&T cell phone,
the callerid shows up just peachy. when made to a Verizon phone, the
recipient gets "Unknown Number". my router shows:


voicegw-1.corp#sho isdn active
--------------------------------------------------------------------------------
ISDN ACTIVE CALLS
--------------------------------------------------------------------------------
Call Calling Called Remote Seconds Seconds Seconds Charges
Type Number Number Name Used Left Idle
Units/Currency
--------------------------------------------------------------------------------

Out 80569xxxxx 698xxx 0 Unavail - 0


(numbers x'd to protect the innocent)

so I'm thinking that i'm doing everything right from the CM/router side.
can anyone shed any light on why some providers would have this number
show up as unknown??

any help greatly appreciated...


:wq
Jeff Behl
Network Engineer
Expertcity
(805) 690-5743
Re: CallerID conundrum... [ In reply to ]
Jeff,

The Calling Party Number (as well as Called) information element has
a great deal more in it than "80569xxxxx". The Nature of Address
indicators tell the network a lot about what the digits really
represent and how to deal with it. For instance there is the
presentation indicator:

Presentation indicator (octet 3a)

Bits
----
7 6 Meaning
0 0 Presentation allowed
0 1 Presentation restricted
1 0 Number not available due to interworking
1 1 Reserved

But in your case it's much more likely that the Type of Number and
Numbering Plan indicators are the issue:

Type of number (octet 3) (Note 1)

Bits
-----
7 6 5
0 0 0 Unknown (Note 2)
0 0 1 International number (Note 3)
0 1 0 National number (Note 3)
0 1 1 Network specific number (Note 4)
1 0 0 Subscriber number (Note 3)
1 1 0 Abbreviated number (Note 5)
1 1 1 Reserved for extension



Numbering plan identification (octet 3)

Numbering plan (applies for type of number = 000, 001, 010 and 100)

Bits
-------
4 3 2 1
0 0 0 0 Unknown (Note 6)
0 0 0 1 ISDN/telephony numbering plan (Recommendation E.164 [19])
0 0 1 1 Data numbering plan (Recommendation X.121 [21])
0 1 0 0 Telex numbering plan (Recommendation F.69 [22])
1 0 0 0 National standard numbering plan
1 0 0 1 Private numbering plan
1 1 1 1 Reserved for extension



If you don't send reasonable values for these the information element may
be ignored. There is also the screening indicator:

Screening indicator (octet 3a)

Bits
----
2 1
0 0 User-provided, not screened
0 1 User-provided, verified and passed
1 0 User-provided, verified and failed
1 1 Network provided


If it's not "Network provided" it may be ignored. Certainly you couldn't
blame them for ignoring it if it's "User-provided, verified and failed". :)

-Vance

Vance Shipley
Wanspot Inc.
vances@wanspot.ca

On Fri, Aug 22, 2003 at 12:20:00PM -0700, Jeff Behl wrote:
}
} when calls are made from a voip phone to a Cingular or AT&T cell phone,
} the callerid shows up just peachy. when made to a Verizon phone, the
} recipient gets "Unknown Number". my router shows:
Re: CallerID conundrum... [ In reply to ]
Thanks much Vance. It turned out it was the Calling Numbering Plan;
changing it to ISDN fixed the problem.

My indoctrination into the world of voice continues...

Jeff

Vance Shipley wrote:

> Jeff,
>
> The Calling Party Number (as well as Called) information element has
> a great deal more in it than "80569xxxxx". The Nature of Address
> indicators tell the network a lot about what the digits really
> represent and how to deal with it. For instance there is the
> presentation indicator:
>
> Presentation indicator (octet 3a)
>
> Bits
> ----
> 7 6 Meaning
> 0 0 Presentation allowed
> 0 1 Presentation restricted
> 1 0 Number not available due to interworking
> 1 1 Reserved
>
> But in your case it's much more likely that the Type of Number and
> Numbering Plan indicators are the issue:
>
> Type of number (octet 3) (Note 1)
>
> Bits
> -----
> 7 6 5
> 0 0 0 Unknown (Note 2)
> 0 0 1 International number (Note 3)
> 0 1 0 National number (Note 3)
> 0 1 1 Network specific number (Note 4)
> 1 0 0 Subscriber number (Note 3)
> 1 1 0 Abbreviated number (Note 5)
> 1 1 1 Reserved for extension
>
>
>
> Numbering plan identification (octet 3)
>
> Numbering plan (applies for type of number = 000, 001, 010 and 100)
>
> Bits
> -------
> 4 3 2 1
> 0 0 0 0 Unknown (Note 6)
> 0 0 0 1 ISDN/telephony numbering plan (Recommendation E.164 [19])
> 0 0 1 1 Data numbering plan (Recommendation X.121 [21])
> 0 1 0 0 Telex numbering plan (Recommendation F.69 [22])
> 1 0 0 0 National standard numbering plan
> 1 0 0 1 Private numbering plan
> 1 1 1 1 Reserved for extension
>
>
>
> If you don't send reasonable values for these the information element may
> be ignored. There is also the screening indicator:
>
> Screening indicator (octet 3a)
>
> Bits
> ----
> 2 1
> 0 0 User-provided, not screened
> 0 1 User-provided, verified and passed
> 1 0 User-provided, verified and failed
> 1 1 Network provided
>
>
> If it's not "Network provided" it may be ignored. Certainly you couldn't
> blame them for ignoring it if it's "User-provided, verified and failed". :)
>
> -Vance
>
> Vance Shipley
> Wanspot Inc.
> vances@wanspot.ca
>
> On Fri, Aug 22, 2003 at 12:20:00PM -0700, Jeff Behl wrote:
> }
> } when calls are made from a voip phone to a Cingular or AT&T cell phone,
> } the callerid shows up just peachy. when made to a Verizon phone, the
> } recipient gets "Unknown Number". my router shows:

--
:wq
Jeff Behl
Network Engineer
Expertcity
(805) 690-5743