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.

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. I asked a VERY specific question about
outbound trunks. If you don't know the answer, don't post a followup.

Of course, trunks still have _circuit_ numbers for tracking and billing
purposes, but those are not dialable _directory_ numbers, which is what
we were discussing. For POTS lines, the directory number _is_ the
circuit number.

Why would you go off on a tangent about how outbound trunks aren't
dialable?

No ****!

ANI is about billing. 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.

Inbound calls to a number (or set of numbers, eg. DID) are routed to any
available trunk in the trunk group.

Right. ANI must be passed along to the PBX so it knows what extension
to connect to.

DNIS (called number) is the opposite of ANI (calling number).

Pardon my error.