Avaya S8700 - BRI Lines for Video Conf on T556D circuit pack

[jke55]

Someone please tell me how to program ISDN lines for h.320 video conferencing in the Avaya S8700.
I programmed them as data modules with one DID number on link 1 and the 2nd DID on link 2 on each port on the T556D card. I don't see that I have 2B+D because I don't see the D channel portion for each bri port.
I can connect between 2 video conf systems with Avaya ISDN lines station to station, built as stated above, but when I try to dial a long distance video system, I get an error message on my Polycom viewstation stating it appears I am dialing an analog line.
I know the system I am dialing is ISDN 2B+D. I think the problem is in the Avaya S8700 configuration.
Here is the current config for one B-channel of the first ISDN line:

DATA MODULE

Data Extension: 79001 Name: Video BRI1 B1
Type: wcbri COS: 1
Port: 02A1401 COR: 16 Multimedia? n
TN: 1


ABBREVIATED DIALING
List1:

SPECIAL DIALING OPTION:



CIRCUIT SWITCHED DATA ATTRIBUTES
Default Duplex: full Default Mode: sync Default Speed: 64000

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

DATA MODULE


BRI LINK/MAINTENANCE PARAMETERS

XID? y Fixed TEI? n
Country Protocol: 1 Endpt Init? y SPID: XXX-XX79001 Endpt ID: 01

 

[lopes1211]

Do you have ISDN-PRI outbound trunks? If so, what vendor? -CL

 

[jke55]

Yes, SBC. We have other ISDN lines off of a Nortel PBX that we do not have any trouble with video conferencing out of the SBC PRI's.
Does the config look correct on the BRI lines?

 

[lopes1211]

The BRI's look fine. It's probably your trunk group or route pattern setup. Make sure ITC on the route pattern form is set to "both" not "rest". Also, what LD vendor is the SBC group PICC'ed to? -CL

 

[jke55]

AT&T is the LD carrier. So, should we build a different route pattern for the ISDN calls. The existing route patterns that are for phone calls have ITC all rest.

 

[lopes1211]

If you only have the 1 group, just change ITC to "both" and it will work for voice and video. If you utilize some non-PRI and other services, you'll get into some issues with needing seperate partition groups so video only uses the PRI routes. Make sure you've registered the SBC BTN with the AT&T SDS group or it will only work for a month or so before AT&T suspends your SDS service. AT&T requires all lines making SDS calls to be registered. -CL

 

[Mitch672]

You need to change your outbound ARS routes. Make sure the ISDN PRI trunk group selection has the "ITC BCIE" set to "bothept". Also make sure the BCC1 and BCC4 value for non-isdn trunks in that route are set to a "n".

Also, many, many carriers cannot pass 64K data calls. AT&T and Sprint seem to have the fewest problems with this...

You might want to do a "list trace station xxxx" where the xxxx is BRI #1's data module. See what type of ISDN Reject you are getting.

ALso, on the WCBRI modules I have the default data application set to "M0", and "endpt Init" set to "n", its not usually needed on a PBX.

Mitch