Cisco 3521GW & Accord MGC100

[harleyryder]

Placing a 384k call from Cisco to MGC. Cisco opens 384k call but receives only 64k. MGC opens 1 channel but thinks it's sending 384k. MGC cannot dial out (not my idea). Both can communicate with other outside vendors but not w/each other.

Any thoughts/input would be greatly appreciated. :ponder:

[trapehzoid]

What is the actual call makeup?

A Cisco is a GW.. who is initiating the call.. and which side is ISDN?

Is it an IP endpiont calling through the GW to the ISDN MCU?

[harleyryder]

IP ep A-> Cisco GW -> ISDN -> Accord -> IP EP B

Since the Accord can't make outbound calls, the setup above is it. Accord can talk to other Accords & Tandberg ISDN GWs but not to Accord. The Cisco GW can talk to all - except this Accord.

Dialing String: EP A dials svc prfix & phone number of Accord - call connects only on 1 channel and comes in as audio "Unexpected Audio Call" is seen in Accord log.

[spkv]

Are you sure you are not dialing a service for an audio call? Check in both your GW and Gatekeeper to make sure the service you are dialing is a service for 384k Video.

[harleyryder]

Definitely a 384k video call is being dialed. Seems to be an issue with bonding . . . verifying with LEC that in & outbound data permitted

[Skylark]

If I remember correctly the Cisco 3521GW definse a 384k call as 320k+64k over head. So if your makeing a MGC Accord meeting of 384k and calling in with 320k signal you might run into problems.

Usualy this is not a problem with Gateways dialing out of IP over to ISDN because the endpoint will addjust to it, but In this case both the Accord and the Cisco are determining how the call should be.

Note: Im just theorizing her I have never had this problem myself.

[harleyryder]

Issue is the bonding delay between MGC & Cisco GW. Once Bonding Delay in Cisco was set for 50ms all is well ... Thanks much!