watasav

Has anyone tried using the TN556B for video conferencing? I have a solution to use a PRI to an Adtran 550 but another engineer asked about using the TN556B from a PRI to give the video units BRI. Has any one had experience with this. It's an S8710 v3 going to Polycom VSX3000 (desktop video units with the BRI module)

nstephens8

I have configured TN556 for ISDN-BRI to a Polycom FX.

You will need to port 2 data modules to each port.
I assume you will use at least 3 BRI lines.
So you would need to create 6 data-modules ported to 3 ports on the TN556

So you create 2 data modules (ie: 4380 & 4381)

display data-module 4380 Page 1 of 2 SPE B
DATA MODULE

Data Extension: 4380 Name: Polycom1
Type: wcbri COS: 1
Port: 01A0401 COR: 30 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: restricted Default Data Application: M2_A

display data-module 4380 Page 2 of 2 SPE B
DATA MODULE


BRI LINK/MAINTENANCE PARAMETERS

XID? n Fixed TEI? n
Country Protocol: 1 Endpt Init? y SPID: xxx4380 Endpt ID: 01


display data-module 4381 Page 1 of 2 SPE B
DATA MODULE

Data Extension: 4381 Name: Polycom2
Type: wcbri COS: 1
Port: 01A0401 COR: 30 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: restricted Default Data Application: M2_A

display data-module 4381 Page 2 of 2 SPE B
DATA MODULE


BRI LINK/MAINTENANCE PARAMETERS

XID? n Fixed TEI? n
Country Protocol: 1 Endpt Init? y SPID: xxx4381 Endpt ID: 02

PBXtech.info

 

watasav

How did you cable the BRI out from the TN556. What pairs from the amph did you pin to the jack

martinyoung

The TN556 is a 12 port card using two pairs in sequence per port. Blue/orange, green/brown, etc.

__________________
Marty
Retired Avaya DSIC tech

watasav

If I take WB,BW, WO,OW. What pins on the RJ45 would I connect to a BRI port. Is it one for one? Or am I only using certain pins.I using this on a Polycom camera.

martinyoung

W/B - 5
B/W - 4
W/O - 1
O/W - 2

__________________
Marty
Retired Avaya DSIC tech

PBXtech.info

 

liquidvw

I don't think so. I believe it is USOC.

5 - W/B
4 - B/W
3 - W/O
6 - O/W

martinyoung

According to the Integrator's Guide on the Polycom web site you can use BRI or PRI interface. The RJ45 jack on their equipment has the standard 568B pinout. 1 & 2 receive and 4 & 5 transmit.

Here is the link to the page with all the VSX3000 documentation.

http://www.polycom.com/resource_cent...3-6197,FF.html

The pinout is shown at the bottom of page 2-2 of the Integrator's manual.

Looking at the admin manual, I see that a PRI connection is not available, only BRI or IP (admin manual page 2-11) for the VSX3000.

__________________
Marty
Retired Avaya DSIC tech

pmealey

I have purchased a TN556C to provide BRI circuits to a Polycom video conferencing system and I have received conflicting information from the reseller that I bought the card from and the video conferencing system vendor. My question is, do I need to talk to my PRI provider about anything? For example, do they need to do any programming changes, give me some additonal DID numbers, pass different digits when I receive a call on the ISDN #, etc.?

FYI: I have a full T1 PRI with a block of 100 DID numbers assigned to it.

liquidvw

You should check with your provider to make sure the PRI can hanel video. Usualy they provision that from day one, but it doensn't hurt to ask. Also AT&T maintains a global video conference data base, if you are using AT&T and having problems, it might be a good idea to have your DID's added to this data base.

On another note, I created a wiring document on how to wire this configuration up.

Attached Files

wiringpolycomtoG3orS8XX0.doc (2.76 MB, 37 views)

oozenoz

Two part question, reverse order and in three parts. ;)

a) The PRI you reference is local telco service, correct? If this is the case the availablity of DID numbers only applies if you plan to be able to accept calls into your Polycom. If you will only make outgoing calls, you can safely use internal extentions when provisioning the BRI connecting to your Polycom.

b) Follow liquidvw's instructions and contact your LSP. Unless things in the CO world have changed since I worked for telco, a North America PRI is usually provisioned B8ZS/ESF and is provided voice AND data switched service capability. The B8ZS part is essential as it will give you 64K clear channel service - the data part is absolutely required to ensure that your calls will be delivered... in the ISDN world there are three basic types of service that can be called when setting up a call - 3.1 Khz voice, 56K voice, and 64K data. 3.1 Khz is POTS grade, 56K is best for modems. 64K is used for data calls - the type used for switched videoconference calls. If your PRI is not set for data service, any inbound calls would be rejected with a 'service not available' cause code being returned to the caller. It would also prevent you from making them for the same reason.

c) Contact your LD vendor as well, if you plan to make any LD voice conference calls (especially if you plan to call inertnational!) Depending on how your LD's network is set up, you may also need to prefix a specific PIC code (using 1010xxxx) to ensure you hit your carrier's all-digital network, as well as registering the number. For example, Cable and Wireless used to use ANI to filter access; while AT&T, MCI, and even Sprint used to have a separate PIC. (That was more than a few years ago, though, and things may have changed.)

__________________
- calvin

pmealey

oozenoz

Switchtype must exactly match the programming in your PBX. If the PBX is set for National ISDN, set the Polycom to NI-1. The format of the SPIDs does not matter as long as what you program is distinct for each extension.

__________________
- calvin

pmealey

martinyoung

Yes, protocol version b is NI2.

__________________
Marty
Retired Avaya DSIC tech