ISDN

[rob2038]

Hi Folks;
We have a Definity ISDN board running NI-2 (network side) hooked up to a Dialogic ISDN card, running user-side NI-2. The D channel seems to come up properly, all B channels in service, but the Definity identifies all channels as busy.

Any ideas? card has been setup, signalling group, etc.

Also, when configuring the B channels as 'extensions', what is the proper technique? I.e., if we want to send voice calls to the ISDN card B channels to be handled by the Dialogic platform.

Thanks in advance.

Cheers,
Rob

 

[rob2038]

One thing I might add is, what is the equivalent of setting up a station with an extention that resolves to a B channel serviced by this card?
Cheers,
Rob

 

[Phoneman2]

You might be past this....but did you release the board? Look!!! New Buttons
Same amount of time!

Thanks All Phoneman2

 

[lopes1211]

If I'm understanding you correctly, you are trying to setup the B channels as stations? If so, you don't want PRI. You want a robbed-bit setup and you just do an "add station" using a set type of DS1FD and a port off of the DS1 for each station. -CL

 

[Definity]

Rob,
Lopes is right, you can configure the T1 as robbed bit with stations configured as DS1FD.. Attached is the DS1 config. if you like..

BIT Rate: 1.544 Line Coding: AMI-BASIC

Line Compensation: 1 Frame Mode: d4

Signaling Mode: robbed-bit

Idle Code: 11111111

Maintenance Parameters

Slip Detection? N Near CSU Type: other

Regards,

 

[rob2038]

Hi Folks;
Thanks for the feedback. So is it the case then that there is no way to achieve this with ISDN? (this is preferred in our case for a couple of reasons, but we would like to be able to have each port have an extension for CTI purposes).

Cheers,
Rob

 

[lopes1211]

What is the application? Why do you need a different extension per port? Limitting your system in this way is a little strange. A preferable solution would be to build the PRI as a 23 member trunk group and route an entire range of extensions to the trunk group via UDP. Your device on the other end should be able to do it's specific application/routine based on the incoming digits rather than which port the call came in on. -CL

 

[rob2038]

Hi;
Sorry for the delay in responding to this.

The reason our developer would like a per-extension method is to support CTI (i.e., the extension is used as the device). So when the call is handled, it is registered with the extension device, etc., and application server side stuff can use this to track the call.

I believe that they are pursuing the UDP option as well. In this case, a set of extensions would be routed to this trunk group, right? Does the inbound DNIS then show up as the extension number?

Thanks for your help!

Cheers,
Rob

 

[lopes1211]

Correct, the switch would send the DNIS info to the endpoint device. In this type of UDP scenario, you could designate as many extensions as you want utilizing as many different applications as you want. A per channel method would restrict you to only 23 different phones per T-1 even if they weren't all being used at the same time. -CL