I am trying to configure a conference bridge on a 2801 router, with a PVDM2-8.
No FXOs or FXSs are installed on this router.
The scenario I am trying is connecting from an IP Phone to a PSTN phone. Then calling another IP Phone in the LAN then trying a conference. The initiator's screen shows "Can not complete conference" and the PSTN call is dropped, sustaining only the call between the 2 IP Phones.
I have a callmanager 4.1, I created the Enhanced IOS conference Bridge, it's registered fine. I put this conference bridge in the MRG and the phones with the proper device pool and MRGL.
dsp services dspfarm
sccp local FastEthernet0/0
sccp ccm 192.168.0.34 identifier 1 version 4.0
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register HWCONFBRIDGE
dspfarm profile 1 conference
maximum sessions 1
associate application SCCP
ROUTER#sh dspfarm all
Dspfarm Profile Configuration
Profile ID = 1, Service = CONFERENCING, Resource ID = 1
Profile Description :
Profile Admin State : UP
Profile Operation State : ACTIVE
Application : SCCP Status : ASSOCIATED
Resource Provider : FLEX_DSPRM Status : UP
Number of Resource Configured : 1
Number of Resource Available : 1
Codec : g711ulaw, Maximum Packetization Period : 30 , Transcoder: Not Required
Codec : g711alaw, Maximum Packetization Period : 30 , Transcoder: Not Required
Codec : g729ar8, Maximum Packetization Period : 60 , Transcoder: Not Required
Codec : g729abr8, Maximum Packetization Period : 60 , Transcoder: Not Required
Codec : g729r8, Maximum Packetization Period : 60 , Transcoder: Not Required
Codec : g729br8, Maximum Packetization Period : 60 , Transcoder: Not Required
SLOT DSP VERSION STATUS CHNL USE TYPE RSC_ID BRIDGE_ID PKTS_TXED PKTS_RXED
0 1 1.1.1 UP N/A FREE conf 1 - - -
Total number of DSPFARM DSP channel(s) 1
SCCP Admin State: UP
Gateway IP Address: 192.168.0.1, Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 192.168.0.34, Port Number: 2000
Priority: N/A, Version: 4.0, Identifier: 1
Conferencing Oper State: ACTIVE - Cause Code: NONE
Active Call Manager: 192.168.0.34, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 1
Reported Max Streams: 8, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: g729r8, Maximum Packetization Period: 60
Supported Codec: g729br8, Maximum Packetization Period: 60
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
I did a couple of reloads even restarted the callmanager.
If you have CCM traces collected at the time the test is performed, they may give further insight into the cause of the problem. For example it could be that the CFB is allocated but there's insufficient bandwidth to connect one of the conference call participants, maybe due to Locations configuration. Or perhaps a different CFB resource is being allocated than the one we expect. Either way, if you can collect the CCM SDI traces, and search for 'Can not Complete Conference', then the lines of traces just before that will likely point to a definitive cause of the problem. Attach those traces here if need be.
It worked.... I just didn't get the chance to feedback you guys....
Not one thing in the configuration was changed. I double checked all of the configuration then I simply restarted everything, the router, the CCM, even resetted the IP Phones. Not sure exactly what was wrong!!...
but anyway thank you all for your support. Appreciate the help.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.