cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
724
Views
5
Helpful
11
Replies

Video Conf unit connected to BRI interfaces

richardbuxton
Level 1
Level 1

Hello,

I have a 2851 router with E1 interface connected to an ISDN network provider and a BRI interface connected to a Sony PCSA-B384S Video Conferencing unit.

I want the VC unit to be able to dial via the BRI circuits and "break out" through the E1 (ie. an ISDN call all the way through the router).

I have a layer 1 connection between the VC unit and the BRI, but the VC cannot establish a call.

I have attached a config file.

I know that q931 debugs would be useful and I will try to obtain these shortly, however, any help you could give based on the attached config would be much appreciated

Thanks

Richard

11 Replies 11

paolo bevilacqua
Hall of Fame
Hall of Fame

Have you used crossed BRI cables as detailed at:

http://www.cisco.com/en/US/tech/tk652/tk653/technologies_configuration_example09186a008010ef6c.shtml

Note:

- missing network-clock-select for E1 interface

- BRI wic must also network-clock-participate

- you don't need power-inline under bri interfaces.

- depending on how the video unit is set, you may or may not need isdn static-tei 0

- suggest you put both bri in trunk-group and reference the latter with a single DP, for ease of configuration and control.

- said DP will likely need "forward-digits all", else no calling number will be sent.

After that, if still doesn't work, debug isdn q931 is definitely needed.

Hi - thanks for your quick response.

I have configured the network-clock as suggested and removed the power-inline and static-tei commands.

The situation is now much better - I have Layer 2 established on the VC unit BRI0/2/1(see attached).

However, when I dial into any VC test numbers the call connects but then is disconnected within a few seconds (before any video is sent/received).

The Q931 trace is also attached (VC Debug.txt)

Any suggestions?

Regards

RIchard

Hi, the device attached to BRI is disconnecting:

130317: May 27 12:50:17.003 BST: %ISDN-6-CONNECT: Interface Serial0/0/0:12 is no

w connected to 01753723849 N/A

130318: May 27 12:50:17.007 BST: %ISDN-6-CONNECT: Interface BRI0/2/1:1 is now co

nnected to N/A N/A

130319: May 27 12:51:11.059 BST: ISDN BR0/2/1 Q931: RX <- DISCONNECT pd = 8 cal

lref = 0x0C

Cause i = 0x8090 - Normal call clearing

Please send output of "show network-clocks" to eliminate any possible problem in that area.

Beside that, you should find from the device why it is disconnecting.

Hi,

See ISDN and clock status below.

It does seem like the VC unit is disconnecting the call. The VC unit works fine if it is connected to a public ISDN network (ie. not through the VGW).

I will see what debug is available on the VC unit - it seems a little limited!

Regards

Richard

Global ISDN Switchtype = primary-net5

ISDN Serial0/0/0:15 interface

dsl 0, interface ISDN Switchtype = primary-net5

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

2 Active Layer 3 Call(s)

CCB:callid=9329, sapi=0, ces=0, B-chan=14, calltype=VOICE

CCB:callid=932A, sapi=0, ces=0, B-chan=13, calltype=VOICE

Active dsl 0 CCBs = 2

The Free Channel Mask: 0x80000FFF

Number of L2 Discards = 0, L2 Session ID = 105

ISDN BRI0/2/0 interface

******* Network side configuration *******

dsl 4, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 4 CCBs = 0

The Free Channel Mask: 0x80000003

ISDN BRI0/2/1 interface

******* Network side configuration *******

dsl 5, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 5 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 2

TETBURY_ROAD-VGW-01#show network-clocks

Network Clock Configuration

---------------------------

Priority Clock Source Clock State Clock Type

1 E1 0/0/0 GOOD E1

10 Backplane GOOD PLL

Current Primary Clock Source

---------------------------

Priority Clock Source Clock State Clock Type

1 E1 0/0/0 GOOD E1

Hi, sorry I should have asked if you have:

network-clock-participate wic 2

Problem might be limited to that.

Hi,

Yes, this was already switched on.

network-clock-participate wic 0

network-clock-participate wic 2

network-clock-select 1 E1 0/0/0

The VC unit disconnects and gives a message along the lines of "remote terminal not compatible with this bbonding method"

Thank you

Richard

I'm not sure, b-bonding presupposes multiple calls, but only one is seen from the VC.

I don't think the cisco config can be improved from what you have.

We are going to see what options are available on the VC unit - maybe something on here causing the problem.

We are much further forward with this issue thanks to your assistance - thank you very much.

Regards

Richard

Thanks for the appreciation and good luck!

Hi Richard,

I've been asked to do the same thing for one of our clients. Just wondering how you got on - did you get the problem resolved in the end?

Hi John,

Unfortunatley not! With the help of the forumn I managed to get the BRI layer 1 and 2 established, but when the VC unit tries to establish a call it clears after about 20 seconds with a message "not compatable with this bonding method".

If you find a solution, please let me know!

Regards

Richard

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: