[cisco-voip] Update: partially working configuration, Re: Polycom Video integrated to Cisco

[Robert Kulagowski]

Robert Kulagowski wrote:
> Here's a partially working configuration.  What works:  a single call at 
> 384K, either inbound or outbound.
> 
> What doesn't work:  I can't seem to get multiple inbound calls working, 
> and the TAC engineer is on vacation until 2008-10-22.  Can't seem to 
> make outbound call to Codian 3241 with more than one b-channel; 
> something that Codian and TAC are going back and forth about how 
> secondary b-channels are supposed to be exchanged.

If anyone is keeping track, the multiple calls issue has been partially 
resolved, but the TAC engineer is taking it back to the developers.

The issue is the "bandwidth max 1024" command that was in the config. 
Something is getting pre-allocated, and even if the first call comes in 
at 256K, dsp resources were set aside.  This meant that there wasn't 
enough for a second call, so you'd get a single b-channel and then a 
failure to sync an subsequent b-channels.

The new dial-peers look like this:

dial-peer voice 1 pots
  description Incoming video call pots leg
  translation-profile incoming Prepend_Sitecode
  information-type video
  incoming called-number 312705484[0-8]
  bandwidth maximum 896
  direct-inward-dial
dial-peer voice 2 voip
  description Incoming video call, H.323 leg.  Translation profile on 
POTS leg
  huntstop
  destination-pattern 213[78]..
  voice-class codec 3
  session target ras
dial-peer voice 3 voip
  description Outbound H.323 calls hit this DP
  voice-class codec 3
  incoming called-number .T
dial-peer voice 4 pots
  description Outbound H.320 leg.  Video units dial 1 or 011 for 
outbound call
  destination-pattern [01].T
  information-type video
  bandwidth maximum 1024
  port 0/0/0:23
  forward-digits all
dial-peer voice 10 pots
  description Incoming voice calls
  translation-profile incoming Prepend_Sitecode
  incoming called-number 31270548..
  direct-inward-dial
dial-peer voice 11 voip
  description Dialpeer to CallManager
  huntstop
  destination-pattern 21....
  progress_ind setup enable 3
  progress_ind progress enable 8
  voice-class codec 1
  voice-class h323 1
  session target ipv4:10.201.255.2
  dtmf-relay h245-alphanumeric
  fax-relay ecm disable
  ip qos dscp cs3 signaling
  no vad
dial-peer voice 12 voip
  voice-class codec 1
  voice-class h323 1
  incoming called-number 8.T
  dtmf-relay h245-alphanumeric
dial-peer voice 13 pots
  description Outbound dial-peer for voice calls
  destination-pattern 8.T
  port 0/0/0:23

This feature is looking to be a lot more feasible as far as an actual 
deployment goes.