Hi,

I have an old INDEX (i have a feeling it's software rev 8) that i've
just terminated a BT BRI onto I'm having trouble translating the MSN's
to extensions.

If i set the trunk to DDI (which from my reading is necessary to use
ARS) it rejects all calls (on that trunk).

I've tried adding various things in the ARS, and am going round in
circles.

This is the first Index i've worked on so it's not quite home yet!!!.

I can route the device to an extension but not the MSN/DDI's i'm
probably missing something obvious..... but if anyone out there has
any pointers it'd be appreciated.

Thanks
Bryn

Bryn pretended :
> Hi,
>
> I have an old INDEX (i have a feeling it's software rev 8) that i've
> just terminated a BT BRI onto I'm having trouble translating the MSN's
> to extensions.
>
> If i set the trunk to DDI (which from my reading is necessary to use
> ARS) it rejects all calls (on that trunk).
>
> I've tried adding various things in the ARS, and am going round in
> circles.
>
> This is the first Index i've worked on so it's not quite home yet!!!.
>
> I can route the device to an extension but not the MSN/DDI's i'm
> probably missing something obvious..... but if anyone out there has
> any pointers it'd be appreciated.

In my experience, if you have MSNs, your ISDN2e line will be set up for 
Point-to-Multipoint.

If you have DDIs, the line will be set up for Point-to-point.

MSNs & DDIs are never provided together on the same circuit.

I have NO experience of the Index, however, on a Panasonic, or NEC, 
calls will not route properly (if at all) if the line card is set to 
the wrong protocol - P2P, or P2MP)

On 8 May, 23:38, Jono <notha...@blueyonder.invalid> wrote:
> Bryn pretended :
>
>
>
> > Hi,
>
> > I have an old INDEX (i have a feeling it's software rev 8) that i've
> > just terminated a BT BRI onto I'm having trouble translating the MSN's
> > to extensions.
>
> > If i set the trunk to DDI (which from my reading is necessary to use
> > ARS) it rejects all calls (on that trunk).
>
> > I've tried adding various things in the ARS, and am going round in
> > circles.
>
> > This is the first Index i've worked on so it's not quite home yet!!!.
>
> > I can route the device to an extension but not the MSN/DDI's i'm
> > probably missing something obvious..... but if anyone out there has
> > any pointers it'd be appreciated.
>
> In my experience, if you have MSNs, your ISDN2e line will be set up for
> Point-to-Multipoint.
>
> If you have DDIs, the line will be set up for Point-to-point.
>
> MSNs & DDIs are never provided together on the same circuit.
>
> I have NO experience of the Index, however, on a Panasonic, or NEC,
> calls will not route properly (if at all) if the line card is set to
> the wrong protocol - P2P, or P2MP)

For a start the incoming BRI must be set by BT to System Access only
(point to point) and so MSN's will not work, you will need a block of
DDI's or SDDI's . The index is quite good at routing calls
automagically by matching the presentation digits to the extension
numbers.

This post is going to get a bit big now but here is a copy of the
relevant section from the SDX (oops, I mean Avaya) INDeX programming
manual, it's from level 9.1 which is the oldest I have, seem to have
"archived" the previous manuals and can't find them any more! Hope
this helps, give me a shout if you need more:

How the INDeX Routes DDI Calls
DDI (Direct Dialling Inwards) uses digits received with an incoming
PSTN call to
route the call on the INDeX. The number of digits received, the range
of digits and
the lines on which they are received is arranged with the PSTN line
provider.
The INDeX supports DDI on PRI, DASS, BRI and AC15 trunks (INDeX 30
only
supports BRI). Note that trunks set to DDI operation cannot then
receive non-DDI
calls.
The INDeX use the following DDI routing options in sequence:
1. Check for an ARS String Analysis Match :
If the DDI digits match a string in ARS, the call follows the ARS
instructions.
The only DDI restriction is that if directed to a route list, it can
only use the first
route. Using ARS allows you to apply digit translation to DDI calls
and to route
them on switch, via network links or off-switch.
2. Check for a Pilot Number Match :
If the DDI digits match a pilot number set on the INDeX, the call uses
the
settings of the Call Control Plan associated with pilot number. Pilot
numbers
use directory numbers. This method treats the DDI call as a normal
incoming
call, applying ACA, diversions, and dispositions, etc (see “Setting Up
Pilot
Numbers” on page 40).
3. Direct to the Matching Directory Number :
If no ARS or pilot number matches the DDI digits, the INDeX routes the
call to
the matching directory number, i.e. user or group directory number.
Each user
has a number of settings to handle the redirection of DDI calls when
busy (see
page 39).
DDI Calls on the Operators Console :
Any DDI calls received at an operator's console appear in External
Queue 3,
regardless of the settings of any Call Control Plan. This applies to
all DDI calls
regardless of the method of routing and whether they have been
transferred or
diverted.
DDI Calls to Voice Mail :
A DDI call can be made to the Voice Manager group number (see page
18), such
that external callers can, by entering their ID and passcode and
access their voice
mail.
DDI & Pilot Numbers The DDI Directory & DDI Names - Page 37
Programming Manual DDI & Pilot Numbers - Page 37
INDeX 9.1 38DHB0002UKDJ – Issue 3 (12/00)
The DDI Directory & DDI Names
The INDeX supports a DDI directory for DDI numbers. The DDI directory
is
separate from the INDeXs own directory numbers.
The DDI directory allows DDI numbers to be given a directory name.
That name is
then carried with the DDI call and takes precedence over any Pilot
number or Trunk
name that may be associated with the call (see page 95).
The DDI directory allocates DDI numbers in blocks with a starting
number and a
block size. This reflects the way in which PSTN providers allocate DDI
numbers.
The INDeX DDI directory contains and names DDI numbers of up to eight
digits.
Some ISDN services present DDIs of more than eight digits. For DDI
naming, the
INDeX matches DDIs to its DDI directory using the last eight digits of
a DDI. For
DDI routing it uses all the digits of the DDI received.
To add a set of DDI numbers :
1. From the Administration menu select Directory and then DDI numbers.
2. Select Add number block. Enter the starting DDI number and then the
block
size.
To edit DDI numbers :
1. From the Administration menu select Directory and then DDI numbers.
– To remove a block of DDI numbers select Delete number block and
names and enter the first number.
– To change a block size select Change number block.
To name a DDI number :
1. From the Administration menu select Directory and then DDI numbers.
2. Select DDI names and enter the DDI number (it must be already
defined within
a DDI block).
3. Select Name and enter a name (up to 16 characters).
4. To name another DDI number either use Select new target and enter
the
required DDI number or use the left and right cursor keys to show the
previous
or next DDI number.
Page 38 - Enabling DDI on a Trunk DDI & Pilot Numbers
Page 38 - DDI & Pilot Numbers Programming Manual
38DHB0002UKDJ – Issue 3 (12/00) INDeX 9.1
Enabling DDI on a Trunk
For an incoming call to ignore the trunk menu settings and use DDI
routing, you
must specify that trunk as a DDI Line. The trunk provider must also
set that trunk to
provide DDI digits.
To set a trunk to DDI operation :
1. From the Administration menu, select Trunk and enter the trunk's
directory
number.
2. Select DDI Line and set this to yes for DDI trunks.
3. For R2 DDI trunks select DDI digit count and enter the number of
DDI digits
that should be passed through. Leave this field blank for non-R2 DDI
trunks.
4. You may want to restrict the DDI trunk to incoming calls only, if
so select Type
and set this to Incoming.
Trunk ARS Settings
The INDeX routes DDI through ARS if the DDI digits match a string in
ARS String
Analysis.
If the ARS processing goes to plan based analysis (see page 57), the
Dialling
Plan number used is taken from the DDI trunk’s associated Call Control
Plan (see
page 41).
To set a trunk's dialling plan number :
1. From the Administration menu, select Call control plan and enter
the
number of the trunk's associated call control plan.
2. Select Dialling plan and enter the required plan number.

On 9 May, 10:12, Galileo  wrote:
> On 8 May, 23:38, Jono <notha...@blueyonder.invalid> wrote:
>
>
>
> > Bryn pretended :
>
> > > Hi,
>
> > > I have an old INDEX (i have a feeling it's software rev 8) that i've
> > > just terminated a BT BRI onto I'm having trouble translating the MSN's> > > to extensions.
>
> > > If i set the trunk to DDI (which from my reading is necessary to use
> > > ARS) it rejects all calls (on that trunk).
>
> > > I've tried adding various things in the ARS, and am going round in
> > > circles.
>
> > > This is the first Index i've worked on so it's not quite home yet!!!.
>
> > > I can route the device to an extension but not the MSN/DDI's i'm
> > > probably missing something obvious..... but if anyone out there has
> > > any pointers it'd be appreciated.
>
> > In my experience, if you have MSNs, your ISDN2e line will be set up for
> > Point-to-Multipoint.
>
> > If you have DDIs, the line will be set up for Point-to-point.
>
> > MSNs & DDIs are never provided together on the same circuit.
>
> > I have NO experience of the Index, however, on a Panasonic, or NEC,
> > calls will not route properly (if at all) if the line card is set to
> > the wrong protocol - P2P, or P2MP)
>
> For a start the incoming BRI must be set by BT to System Access only
> (point to point) and so MSN's will not work, you will need a block of
> DDI's or SDDI's . The index is quite good at routing calls
> automagically by matching the presentation digits to the extension
> numbers.
>
> This post is going to get a bit big now but here is a copy of the
> relevant section from the SDX (oops, I mean Avaya) INDeX programming
> manual, it's from level 9.1 which is the oldest I have, seem to have
> "archived" the previous manuals and can't find them any more! Hope
> this helps, give me a shout if you need more:
>
> How the INDeX Routes DDI Calls
> DDI (Direct Dialling Inwards) uses digits received with an incoming
> PSTN call to
> route the call on the INDeX. The number of digits received, the range
> of digits and
> the lines on which they are received is arranged with the PSTN line
> provider.
> The INDeX supports DDI on PRI, DASS, BRI and AC15 trunks (INDeX 30
> only
> supports BRI). Note that trunks set to DDI operation cannot then
> receive non-DDI
> calls.
> The INDeX use the following DDI routing options in sequence:
> 1. Check for an ARS String Analysis Match :
> If the DDI digits match a string in ARS, the call follows the ARS
> instructions.
> The only DDI restriction is that if directed to a route list, it can
> only use the first
> route. Using ARS allows you to apply digit translation to DDI calls
> and to route
> them on switch, via network links or off-switch.
> 2. Check for a Pilot Number Match :
> If the DDI digits match a pilot number set on the INDeX, the call uses
> the
> settings of the Call Control Plan associated with pilot number. Pilot
> numbers
> use directory numbers. This method treats the DDI call as a normal
> incoming
> call, applying ACA, diversions, and dispositions, etc (see “Setting Up
> Pilot
> Numbers” on page 40).
> 3. Direct to the Matching Directory Number :
> If no ARS or pilot number matches the DDI digits, the INDeX routes the
> call to
> the matching directory number, i.e. user or group directory number.
> Each user
> has a number of settings to handle the redirection of DDI calls when
> busy (see
> page 39).
> DDI Calls on the Operators Console :
> Any DDI calls received at an operator's console appear in External
> Queue 3,
> regardless of the settings of any Call Control Plan. This applies to
> all DDI calls
> regardless of the method of routing and whether they have been
> transferred or
> diverted.
> DDI Calls to Voice Mail :
> A DDI call can be made to the Voice Manager group number (see page
> 18), such
> that external callers can, by entering their ID and passcode and
> access their voice
> mail.
> DDI & Pilot Numbers The DDI Directory & DDI Names - Page 37
> Programming Manual DDI & Pilot Numbers - Page 37
> INDeX 9.1 38DHB0002UKDJ – Issue 3 (12/00)
> The DDI Directory & DDI Names
> The INDeX supports a DDI directory for DDI numbers. The DDI directory
> is
> separate from the INDeXs own directory numbers.
> The DDI directory allows DDI numbers to be given a directory name.
> That name is
> then carried with the DDI call and takes precedence over any Pilot
> number or Trunk
> name that may be associated with the call (see page 95).
> The DDI directory allocates DDI numbers in blocks with a starting
> number and a
> block size. This reflects the way in which PSTN providers allocate DDI
> numbers.
> The INDeX DDI directory contains and names DDI numbers of up to eight
> digits.
> Some ISDN services present DDIs of more than eight digits. For DDI
> naming, the
> INDeX matches DDIs to its DDI directory using the last eight digits of
> a DDI. For
> DDI routing it uses all the digits of the DDI received.
> To add a set of DDI numbers :
> 1. From the Administration menu select Directory and then DDI numbers.
> 2. Select Add number block. Enter the starting DDI number and then the
> block
> size.
> To edit DDI numbers :
> 1. From the Administration menu select Directory and then DDI numbers.
> – To remove a block of DDI numbers select Delete number block and
> names and enter the first number.
> – To change a block size select Change number block.
> To name a DDI number :
> 1. From the Administration menu select Directory and then DDI numbers.
> 2. Select DDI names and enter the DDI number (it must be already
> defined within
> a DDI block).
> 3. Select Name and enter a name (up to 16 characters).
> 4. To name another DDI number either use Select new target and enter
> the
> required DDI number or use the left and right cursor keys to show the
> previous
> or next DDI number.
> Page 38 - Enabling DDI on a Trunk DDI & Pilot Numbers
> Page 38 - DDI & Pilot Numbers Programming Manual
> 38DHB0002UKDJ – Issue 3 (12/00) INDeX 9.1
> Enabling DDI on a Trunk
> For an incoming call to ignore the trunk menu settings and use DDI
> routing, you
> must specify that trunk as a DDI Line. The trunk provider must also
> set that trunk to
> provide DDI digits.
> To set a trunk to DDI operation :
> 1. From the Administration menu, select Trunk and enter the trunk's
> directory
> number.
> 2. Select DDI Line and set this to yes for DDI trunks.
> 3. For R2 DDI trunks select DDI digit count and enter the number of
> DDI digits
> that should be passed through. Leave this field blank for non-R2 DDI
> trunks.
> 4. You may want to restrict the DDI trunk to incoming calls only, if
> so select Type
> and set this to Incoming.
> Trunk ARS Settings
> The INDeX routes DDI through ARS if the DDI digits match a string in
> ARS String
> Analysis.
> If the ARS processing goes to plan based analysis (see page 57), the
> Dialling
> Plan number used is taken from the DDI trunk’s associated Call Control
> Plan (see
> page 41).
> To set a trunk's dialling plan number :
> 1. From the Administration menu, select Call control plan and enter
> the
> number of the trunk's associated call control plan.
> 2. Select Dialling plan and enter the required plan number.

That was pretty thorough, i'm just waiting on BT sorting out DDI's as
opposed to MSN's...... Thanks for your help