Trying to Create a HW conference bridge with 4 sessions and up to 32 particapents per conference. Call Manager version 7.1.2
Created a hardware conference bridge on Cisco 2811.
The problem is, that when I add this DSP farm to the media resource group, all looks good. I see the resources being used when initiating a conference but there is no voice.
Here are the PVDM's installed on the router.
NAME: "PVDMII DSP SIMM with three DSPs on Slot 0 SubSlot 4", DESCR: "PVDMII DSP SIMM with three DSPs" PID: PVDM2-48 , VID: NA , SN: FOC09411T4N
NAME: "PVDMII DSP SIMM with one DSP on Slot 0 SubSlot 5", DESCR: "PVDMII DSP SIMM with one DSP" PID: PVDM2-16 , VID: NA , SN: FOC093626P7
Configuration for the DSP farm on the router
dsp services dspfarm
sccp local FastEthernet0/0.16
sccp ccm 10.13.16.50 identifier 2 priority 2 version 7.0
sccp ccm 10.13.16.51 identifier 1 priority 1 version 7.0
sccp ccm group 1
bind interface FastEthernet0/0.16
associate ccm 1 priority 1
associate ccm 2 priority 2
associate profile 1 register MeetMe_CFB
dspfarm profile 1 conference
description Conferencing for MeetMe
maximum conference-participants 32
maximum sessions 4
associate application SCCP
WIN_DSPFARM#show dspfarm all Dspfarm Profile Configuration
Profile ID = 1, Service = CONFERENCING, Resource ID = 1 Profile Description : Conferencing for MeetMe Profile Service Mode : Non Secure Profile Admin State : UP Profile Operation State : ACTIVE Application : SCCP Status : ASSOCIATED Resource Provider : FLEX_DSPRM Status : UP Number of Resource Configured : 4 Number of Resource Available : 4 Codec Configuration Codec : g711ulaw, Maximum Packetization Period : 30 , Transcoder: Not Required Codec : g711alaw, Maximum Packetization Period : 30 , Transcoder: Not Required
SLOT DSP VERSION STATUS CHNL USE TYPE RSC_ID BRIDGE_ID PKTS_TXED PKTS_RXE
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...