cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1158
Views
0
Helpful
3
Replies

Video bonding over T1 PRI

noname2010
Level 1
Level 1

Hi everyone

my connection like

Tanberg1--------IP--------Gatekeeper---------CUCM----------2811-----------PRI----------PSTN----------Tanberg2

2811 use most recent IOS 12.4(24)T3

the Tanberg1 doesn't have any BRI/PRI on it, IP only, it register with gatekeeper, from Tanberg1 I can make voice call over PSTN, so call routing part is working, the tanberg1 also can call an internal tanberg, all video call over IP is working

furthermore, Tanberg1 can call tanberg2 by bonding 6*B channels, however, as soon as the 6 calls answered, it disconnected immeidately, on tanberg2 I saw the incoming calls, but video never works, the return error code is 47 which indicate invalid resource

ISDN Serial0/0/1:23 interface
        dsl 1, interface ISDN Switchtype = primary-dms100
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        5 Active Layer 3 Call(s)
        CCB:callid=804D, sapi=0, ces=0, B-chan=13, calltype=VOICE
        CCB:callid=804E, sapi=0, ces=0, B-chan=14, calltype=VOICE
        CCB:callid=804F, sapi=0, ces=0, B-chan=15, calltype=VOICE
        CCB:callid=8050, sapi=0, ces=0, B-chan=16, calltype=VOICE
        CCB:callid=8051, sapi=0, ces=0, B-chan=17, calltype=VOICE
        CCB:callid=8052, sapi=0, ces=0, B-chan=18, calltype=VOICE

0/0/1:23.13     h320p      n  S_CONNECT             S_TSP_CONNECT           
0/0/1:23.14     h320s      -  S_CONNECT             S_TSP_CONNECT           
0/0/1:23.15     h320s      -  S_CONNECT             S_TSP_CONNECT           
0/0/1:23.16     h320s      -  S_CONNECT             S_TSP_CONNECT           
0/0/1:23.17     h320s      -  S_CONNECT             S_TSP_CONNECT           
0/0/1:23.18     h320s      -  S_CONNECT             S_TSP_CONNECT           
0/0/1:23.19     -          -  -                    
0/0/1:23.20     -          -  -                    
0/0/1:23.21     -          -  -                    
0/0/1:23.22     -          -  -                    
0/0/1:23.23     -          -  -                   


Apr 11 02:16:25.329: %ISDN-6-CONNECT: Interface Serial0/0/1:17 is now connected to 19782922853 N/A
Apr 11 02:16:26.973: %ISDN-6-DISCONNECT: Interface Serial0/0/1:13  disconnected from 19782922853 , call lasted 6 seconds
Apr 11 02:16:26.977: %ISDN-6-DISCONNECT: Interface Serial0/0/1:14  disconnected from 19782922853 , call lasted 4 seconds
Apr 11 02:16:26.977: %ISDN-6-DISCONNECT: Interface Serial0/0/1:15  disconnected from 19782922853 , call lasted 3 seconds
Apr 11 02:16:26.977: %ISDN-6-DISCONNECT: Interface Serial0/0/1:16  disconnected from 19782922853 , call lasted 2 seconds
Apr 11 02:16:26.977: %ISDN-6-DISCONNECT: Interface Serial0/0/1:17  disconnected from 19782922853 , call lasted 1 seconds

Apr 11 02:16:26.985: %ISDN-6-DISCONNECT: Interface Serial0/0/1:12  disconnected from 19782922853 , call lasted 10 seconds

Cause No. 47 - Resource Unavailable, Unspecified

This cause is  used to report a resource unavailable event only when no other cause in the  resource unavailable class applies.

i am following the two below docs, but still not working

http://cisco.com/en/US/tech/tk1077/technologies_configuration_example09186a00807ca099.shtml

http://www.ciscosystems.sc/en/US/docs/video/milticomm/h320Bonding.html

appreciate any input

thanks

3 Replies 3

paolo bevilacqua
Hall of Fame
Hall of Fame

You will likely need TAC support and much patience to have this working.

If you want a sure solution, convert tandberg2 to IP.

will ask TAC help

but according the doc, it should work

another thing, convert Tanberg2 is not always possible, we don't necessary control all Tanberg in the world

thanks for your reply

It should, but it's new in 12.4T, and few people uses it in this IP world of today.

Consequently, chances of running into bugs or interop issues are higher than with other features.