The DS1FD configuration

[BikeTours]

DS1FD configuration used on the Avaya.

We have a customer who will be replacing equipment from a now bankrupt vendor with ours.

They would like to use the same configuration on their PBX as they now use to the current equipment.

I understand that they have deployed a T1 optioned as a robbed bit trunk with extension numbers optioned as DS1FD.

I have some general familiarity with how Avaya programs and configures their PBXs, and I have been doing some investigation around this DS1FD configuration.

It appears that this configuration allows an extension/station number to be associated directly to the channel on a DS1 circuit, without having to define Trunk Groups etc. In most DS1FD examples the connection is to an IVR platform.

All the example configurations I have seen to this point in use a robbed bit configuration on the T1, although I haven’t seen any documentation that indicates that PRIs are NOT used. The typical Avaya PRI configuration requires you define the D-channel in the Signaling group form and the ISDN protocol type in the trunk group. If the DS1FD configuration is simplified and you don’t define trunk groups I can see why the more basic T1 robbed bit configuration is used.

That being said trunk group forms are used in Avaya configurations to define the signaling on the T1 robbed bit circuit as well… wink start of various types, loop start etc.

Question 1: is the DS1FD configuration only supported on Robbed bit circuits?

Question 2: What type of signaling is used on the DS1FD, or am I off base here, that in fact some kind of auto answer feature is assumed on these DS1FD connections such that when the station number that maps to a T1 channel is dialed the AB [for D4] or ABCD [for ESF] bits on the circuit are simply seized.


I have a concern that if the logics in the PBX are such that

DS1FD station number X - maps - DS1-channel 1

In a hard coded arrangement that the dialed number won’t be passed across the channel. The PBX assumes it will be connecting to a device that understands this “hard” mapping so the station number won’t be passed. That being the case I wouldn’t expect the calling number [ANI] to be passed either.

Question 3:

So… does DNIS or ANI get passed across those DS1FD channels?

 

[Mitch672]

A1: as far as I know, I have only used DS1FD with robbed-bit T1's, as you are mapping individual channels, so the D-Channel has no use, really

A2: robbed-bit signalling is used

no ANI is passed, or can be passed. you would usually assign the DS1FD station to be a "bridged appearance button n" of another station... to get multiple call appearances, you need to have multiple DS1FD stations, and take up multiple DS0's on the robbed-bit T1.

This is typically used as an "upgrade" to connecting to an IPC turret, for example, from analog station integration... the next step up would be a full Qsig PRI.

In general it works fine, but its limited to the # of users you can get on it, because each user in geenral needs 2 or morre call appearances, so 8 users might be the practical limit with 3 appearances each...

mitch


AVAYA Certified Specialist

 

[BikeTours]

So with this hard mapping do you even get the called number going across the trunk channel?

 

[Mitch672]

you get nothing. it's like an analog station (without caller ID).

mitch


AVAYA Certified Specialist

 

[inerguard]

I've used a setup like this to connect to an IVR.

You add the station type as DS1FD as you are doing, and allocate the port number from the DS1.

Exmaple : - Station number 1234 using port 02B0401

Now create a hunt grop (e.g. 90) and set AAS to Y. Also set the group as an ead-mia type with ACD,Vector,Queue,Skill all set to Y as well.

You now need to create an agent login id (eg. 2468)and change the AAS field to Y. Once you do this another field will appear called "Port Extension". In this field put the station number you just created, eg. 1234.

Now put the skill number on the login id you just created. e.g. 90 for the skill number (the hunt group you just created)


This means you have station 1234 with login id 2468 always logged in and always available in skill 90.

To access this group from a vector, use the

converse on skill 90 pri m passing none and none

You also need to set the Feature access code eg. *90 for "Converse Data Return Code"


Hope this helps.



Derek

[Started on Version 3 software 15 years a go]