Channel bonding

[shortad]

Does anyone know if 1010288 should support channel bonding? We are PIC'ing our occasional interlata telephone calls with AT&T Local to another ld carrier, but this also catches my outbound video calls and the other carrier does not support bonding. My plan is to to preface my video calls in the trunk group setup on my pbx with 1010288, so they don't leave the AT&T network.

This worked with only one of my test numbers, and that one works consistently. None of the Polycom or Tandberg number would keep a connection. They would connect at anywhere from 1 to 6 channels, then disconnect immediately.

Before we added the PIC to the alternate ld carrier, the calls would route over the data-enabled AT&T Local route just fine. Unfortunately, circumstance forced us to add the PIC, even though it screws up our outbound video calls.

Any feedback would be appreciated,

Alan

[Joe Vallender]

The bonding is NOT done by the network carriers, unless your network connections are configured for that and you are requesting that bearer capability, which is very doubtful. The bonding is done by the video endpoints, imux'ing the data provided by the individual independent calls over the network making up your final bandwidth.

If you are having issues with bonding the channels, chances are you are not getting clean data through the network. There may be trunks being traversed which are not conditioned for data, have echo cancellers (for voice) which corrupts data, or there are circuits which have signalling or framing mismatch at either end. For 64K data, they need to be ESF/B8ZS and matching at both ends.

Also, the order your BRI lines (if used) are plugged into your IMUX, has to match the order they are configured in your codec. If there is a difference, you may not get bonding completed.

[shortad]

Perhaps I should have been more clear. We are sending calls from our Tandberg 5000, using its PRI connection, through our pbx, using route selection, to a specific PRI trunk group of 6 channels to be sent to AT&T Local. This AT&T circuit is conditioned for data, and has worked fine in the past. Since we now have all of our interLATA calls PIC-ed to an alternate LD carrier (which doesn't support bonded channels), I'm trying to use 1010288 to route the calls over AT&T circuits.

It sounds like you might be onto something concerning the possibility of the call hitting circuits that are not data conditioned. I find it very interesting that I do have one test number (different area code, but same state) that connects at 6 channels every time, but every other one has an issue.

Thanks for your response.

Alan