Tandberg ISDN VTC Not Bonding Channels with SIP Trunk

[CChambleeJr]

Has anyone ever used a Tandberg ISDN VTC unit to place a 6-channel bonded 384K VTC call successfully to another VTC unit on the other end of an Avaya SIP trunk? I can place a voice call to the other end of the SIP trunk, but when I try to place a video call to the same destination, the origination VTC unit never bonds the additional five channels, and I get no video. If I call another local ISDN VTC terminal on this side of the Avaya system, I get a six-channel 384K video call with no problems. I'm hearing from some SME's that the SIP trunk can't pass the bonding tones, preventing the bonding process from happening. Workarounds? Comments? Suggestions? The Avaya switch is a CM 6.0.1, SIP trunk is TCP/5060 to Polycom DMA7000 controller.

===
Chuck Chamblee
ACSS (CM) | CTP | A+

 

[lopes1211]

Seems like a messy way of making a video call in an environment that has IP connectivity between sites. Any reason not to initiate the video call as IP to IP?

-CL

 

[CChambleeJr]

That would be great, if all of our users had IP video terminals. Most here are still ISDN, while others on the opposite side of the SIP trunk are IP.

===
Chuck Chamblee
ACSS (CM) | CTP | A+

 

[lopes1211]

Got it. VOIP is not the same as 64K x 6 isdn. Apples and oranges so what you're trying to do wont work. Your video unit is trying to bond 6 dedicated 64K data channels. Your SIP trunk is a data link with compression designed to accurately transmit a recognizable representation of voice to the human ear.


-CL

 

[CChambleeJr]

Surely the SIP trunk can transport video. Is the issue with the actual "bonding" process, due to the SIP trunk not being able to pass bonding tones used by the ISDN terminal?

===
Chuck Chamblee
ACSS (CM) | CTP | A+