Polycom Viewstation H.323 on a Prologixs

[vulcanccit]

Thank you to those that helped me on wiring! Ok Best I can tell I have 4 ISDN channels running on the Viewstation from the Avaya Prologix, but, I am not so certain its REALLY working. ON the viewstation I am using the AT&T 5Ess ptop emulation, and on the switch side I am using the WCBRI, Country Code1, and a N on the endpoint question (no spids). Anything else seems to not work. I have a in service/Idle on all 4 channels. However I called the Polycom Test numbers and I get an error code 88. Some error saying im not calling a device that accepts this tye of call. I am not so certain if our long distance supports Data calls, but I am going to have some people dial into it. I did do a Status Data 737 (one of the extentions) as it was dialing polycome and it still said in service Idle, so im not so sure it is working.

Can any of you tell me what you use for yoru station side data page set up and what you used on the polycom side?

Thanks all!

 

[dufus2506]

The code you're getting could be coming from a number of places. One could be your own PBX if you're route patterns are not setup correctly.

Have you checked your route pattern? Is it routing the call over an ISDN circuit for you? You can't route ISDN calls over analog or standard T1 circuits.

You'll also want to make sure your BCC values, ITC setting and BCIE setting on the route pattern are correct to allow something with the bearer class that the video system has to setup correctly.

Carpe dialem! (Seize the line!)

 

[vulcanccit]

We just have a standard Voice PRI, so I am not sure if any special routing is set up... I have done VOICE isdn on standard lines with no problem, but not video...

 

[dufus2506]

Voice ISDN doesn't need any special setup.

Check the bottom of the route pattern form for the route your call would take.

Make sure you have the BCC, ITC, and BCIE settings correct for an ISDN setup to occur across your ISDN PRI.

Carpe dialem! (Seize the line!)

 

[lopes1211]

Who is your LD carrier? MCI/ATT/SPRINT are the only ones I know of that support SDS. You also need an SDS account (1st few may go through, then the carrier will block due to not having an account). This is seperate from the voice account even if the call is placed over the same PRI.

-CL

 

[vulcanccit]

im not sure but I can bet its not one of those ...I had this issue once with voice ISDN...I am going to try to PICK over to ATT or Sprint...but I am having our other offices DIAL me up tomorrow, if they can dial me, im good to go...I dont really need to dial them.

 

[vulcanccit]

Well as I had hoped, when London called me here in Phoenix...it worked...KIND OF.. for seome reason when they called the FIRST number on Line 1, only B1 picked up, and none of the other lines...

He then called I think Line 2... all 4 lines picked up but when I checked network stats it said only B1 was connected, not B2.

but it did show all 8 of those little green balls lit on the screen so this tells me that I do not have something configured in the definity correctly to use both channels on each line.

Here is my setup on line 1:
DATA MODULE

Data Extension: 737 Name: Video Conference Line 1
Type: wcbri COS: 1
Port: 01A1001 COR: 1 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

Page 2:


BRI LINK/MAINTENANCE PARAMETERS

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





what do I need to change? or would this be on the trunk form?

I know you all suggested changes on that form, but I thought that only had to do with calling out?