Question:
I am looking for a clear answer
regarding the ability of a T1 that
is NOT a PRI to accommodate BOTH
Caller ID and DID.
I am being told that both an Avaya
Magix and an IP Office MUST be connected
to a PRI in order to get either
of them. I was always pretty
sure that you could get at least
one at a time over a regular T1.
I suppose the confusion could be
related to the ability to get BOTH
at the same time, and that you need
the out of band signaling of a PRI
D-channel to get both.
I'm so confused and I haven't even
asked about the real difference
between DID and DNIS or ANI and
Caller ID Maybe some one could recommend
a good resource for these questions
that is more than just a definition
but also does not need an EE degree
to understand.
Answer:
Some telephone systems do have the
ability to accept Caller ID information
as part of the DID string.
Let's say that you have 4-digits
being passed for DID .the CO would
pass xxxxyyyyyyyyyy. Where
xxxx=the 4 digit DID number and
yyyyyyyyyy=the caller ID information.
Your telephone system needs to have
the ability to break out the digits
received and identify the digits
for DID routing and Caller ID information.
I have worked with the Fujitsu F9600,
which has this capability, but not
sure of others.
In addition, you need to find a
telco that will provide this service.
I have been asking Verizon
to do this for a couple of years,
and they will not.
I am looking for a clear answer
regarding the ability of a T1 that
is NOT a - PRI to accommodate BOTH
Caller ID and DID.
I am being told that both an AAA
Magix and an IP Office MUST be connected
- to a PRI in order to get either
of them. I was always pretty
sure that you - could get at least
one at a time over a regular T1.
I suppose the confusion could be
related to the ability to get BOTH
at the - same time, and that you
need the out of band signaling of
a PRI D-channel to - get both.
I'm so confused and I haven't even
asked about the real difference
between - DID and DNIS or ANI and
Caller ID Maybe some one could recommend
a good - resource for these questions
that is more than just a definition
but also - does not need an EE degree
to understand.
Technical
facts:
You are using what is known in the
industry as a "Channelized
T1" aka CT1 - A CT1 is a "dumb"
connection, emulating conventional
telephone lines. - As such, only
"in band" signaling (usually
DTMF, sometimes MF) is available.
- DNIS/DID services require the
individual channels or "lines"
to be properly configured
at both the phone systems and C.O.sw
itch, generally by using
"wink start" or "wink-wink"
signaling, as opposed to ground
start or loop start operation
commonly provisioned by default.
- Not all carriers and/or phone
systems are prepared to configure
DID/DNIS trunks for "two
way" operation, many require
the CT1 to be divided up
with certain channels in the CT1
used for an "inbound
only" trunk group. - Outbound
caller id is only available using
a single fixed number for the
entire trunk group. In most cases,
it will be marked as "UNAVAILABLE"
and the carrier or telco
will swear it can't be changed.
It can be, the number is
part of the central office trunk
group's configuration but
it will take a great deal of work
to get them to do it.
Operational considerations:
DID/DNIS/PRI signaling on a CT1
will be constrained by the type
of phone line your CT1 is
configured to operate as, between
your phone system and your
LEC (local phone co.) or IXC (long
distance co.) - The capabilities
of your telephone system will also
dictate what you can do,
e.g. your phone system may or may
not be able to receive CNID
via DTMF - The capabilities and
willingness of your telco or carrier
system will also dictate
what you do. Most telcos and carriers
will not send CNID via DTMF
on CT1 but may or may not be willing
to provide DID or DNIS. - In some
cases, the phone system and carrier
can provide the service, but
may or may not be compatible due
to sequence or format incompatibilities.
What you can do:
- Talk to your phone vendor about
practical considerations for adding
a DID group on your existing
CT1. Ask if two way "wink-wink"
start trunks with DID and/or
DNIS using inband DTMF can be accommodated.
- Have the same conversation with
your CT1 provider. (Assuming
you can find someone there
who knows about this. They have
the sales engineers. Ask.)
- Setup a conference call with your
vendor and the provider to work
out the practical aspects
of getting this done.