Stephen Sprunk wrote:
On 04-Apr-12 12:51, Adam H. Kerman wrote:
Stephen Sprunk wrote:
On 04-Apr-12 03:14, Adam H. Kerman wrote:
Stephen Sprunk wrote:
On 03-Apr-12 14:49, Adam H. Kerman wrote:
Stephen Sprunk wrote:

PBX trunks aren't numbered.

If outbound trunks aren't numbered, how does ANI work?

For a trunk, both called and calling number are explicitly signaled at
the start of each call in either direction.

So they are numbered.

There is not a 1:1 correspondence between trunks and numbers, as there
is with POTS lines. That is what makes them trunks!

I thought it was the bit that the PBX selects it for the outbound call,
possibly on a least cost routing basis.

Huh? I don't see the relevance of that comment.

A PBX may have one trunk or multiple trunks. Multiple trunks may be to
the same carrier or to multiple carriers for redundancy or to take
advantage of cost differences. Multiple trunks to the same carrier will
usually be arranged in a trunk group, with all trunks within a group
being equal.

The customer can use _any_ of their numbers on _any_ of those trunks.

The subscriber CANNOT set the number of the trunk that's sent in ANI.
If he could, phone companies would have a hell of a time billing.

If I have a block of 1000 directory numbers, all of them are routed to
the entire trunk group, so no trunk can be said to have any particular
number. Same if I only have one (high-volume) number: it is routed to
the entire trunk group, so all trunks have the "same" number, which also
means they don't have unique numbers.

Now you're moving the goal posts.

No, I'm attempting to explain to you my original point that trunks are
not numbered, which you still don't seem to get.

I didn't ask you about inbound trunks, Stephen. What I asked is quoted
above.

ANI is about billing.

No, it is not.

Yes it is.

ANI provides an Inward WATS (aka toll-free) customer with the caller's
number so they can do intelligent things with it, like connect them to
the nearest store location.

That works only if it's passed along PRI-ISDN or some similar digital
line. Analog? No real-time ANI, but it was logged on the bill.

The outbound trunk has to have a number, else the call can't be billed.
As far as I know, each outbound trunk has its own number allowing
specific calls to be logged to the specific trunk.

Um, no.

Billing for outbound calls is _not_ based on the calling number (CNIS);
there is one bill is for all calls on the entire trunk group, with the
rate for each call determined by the called number (DNIS).

One bill? No ****. You don't believe the carrier logs which trunk was
used regardless of whether it's reported to the subscriber on the bill?
You're wrong.

CNIS isn't the trunk number. For gawd's sake, will you knock off
these tangents?