Help setting up Tandberg Video to Definity via BRI

[ccctech]

I have a customer with a Tandberg 880MXP that has BRI lines provided by the the Telco. In an effort to cut costs they would like the PBX to provide the BRI lines. They have a Definity si Release 12, ISDN PRI trunks (I have verified with provider they are setup to transmit video), TN556D BRI card. I have setup the BRI lines as a Data Module configured as WCBRI similar to other posts. Wired two pairs from ports directly Tandberg BRI ports (bypassed the NT unit provided by telco). When statusing the Data Mod it shows inservice/idle. Using 'list trace data xxxx' I see not activity when trying to make a test call. However the Tandberg show error code 102. The Tandberg's BRI is set to ITR6. I am hoping someone out there has a similiar setup that can direct me to proper settings.
Thanks...Jon

 

[dufus2506]

You would also need to ensure you have PRI's that are setup as CBC, and route plans setup to manage that bearer class.

It's not easy, but you might consult Tandberg. They've probably been through this before, and may have a whitepaper to help you with the setup.

Carpe dialem! (Seize the line!)

 

[ccctech]

Thanks for the reply. Unfortunately Tandberg has not been much help at all. Their stance is that it is compatible with BRI, it would be up the PBX manufacture to supply the proper configs. The PRI trunk group is set to CBC and I have config the route pattern similar to what I have found on these forums.

 

[dufus2506]

Ok... It's important to note that if you setup the stations as data, then any destination you call would also have to have a data Bearer Class. If you call another system that is configured as ISDN voice, it won't answer.

Carpe dialem! (Seize the line!)

 

[ccctech]

Wouldn't the video transmitted be considered data? If not should I setup BRI stations to be connected to the Tandberg.
Thanks

 

[dufus2506]

ISDN was setup so that channels on the cirucit would be tagged about the type information it was carrying in the payload section of it's packet. Each BRI had two channels. You can tag them as both voice, both data, or one of each.

If you hook up an ISDN phone to an ISDN line, and try to dial a phone number for a data device that is also on an ISDN line, the system would not complete the call. It's specifically designed that way. Voice objects connect to voice objects, and data to data. The specific tag is carried in the BCC (Bearer Capability Class).

If you setup your end to be a BCC of data, and the distant end setup theirs as voice, you'll never get the two devices to talk. You'll want to match whatever the distant end is.

Even your trunk groups have a BCC. They might be connected to a voice network, or they might be connected to a data device. (Say, a terminal controller.)

A CBC trunk group evaluates each call that comes across and dynamically allocates the trunk ports to be either voice or data to satisfy the ISDN Bearer Class of the originating station.

It should be noted that it's not enough for you to set the trunk group on the PBX to be CBC. Your provider has to be configured in a similar way.


Carpe dialem! (Seize the line!)

 

[inerguard]

Set your data modules as follows:

change data-module 8791 Page 1 of 2
DATA MODULE

Data Extension: 8791 Name: Video Conference 1
Type: wcbri COS: 0
Port: 01B0705 COR: 0 Multimedia? n
TN: 1


ABBREVIATED DIALING
List1:

SPECIAL DIALING OPTION:



CIRCUIT SWITCHED DATA ATTRIBUTES
Default Duplex: full Default Mode: async Default Speed: 1200

DATA MODULE CAPABILITIES
Default ITC: unrestricted Default Data Application: M2_A

BRI LINK/MAINTENANCE PARAMETERS

XID? n Fixed TEI? n
Country Protocol: etsi Endpt Init? n

Works for me but I'm in Scotland, so probably different if you're in the U.S.


[Started on Version 3 software 15 years a go]

 

[ccctech]

Thank you both for your help. inerguard are you connecting your PBX to a Tandberg. If so, how is your Tandberg ISDN BRI settings configured? Thanks