'version' used to be an optional command which I believe defaulted to 3.1 in days past. As of 12.4(22)T the version is now required. The version numbers themselves correlate to feature support, though I do not have an exhaustive list for each. Ad Hoc/MeetMe hardware conferencing in cme requires the version to be set to 4.0 or later; 4.1 was added to support software MTP; 7.0 was added to support ipv6, etc.
It appears the ip address is off in the 3rd octet; should be 10.10.210.10 and 11 On Sat, Oct 3, 2009 at 1:29 PM, Michael Ciarfello <mciarfe...@iplogic.com>wrote: > Should the version be 7.0+ ??? > sccp ccm 10.10.110.10 identifier 2 version 5.0.1 > > What does this command actually do under the hood? > > ------------------------------ > *From:* ccie_voice-boun...@onlinestudylist.com [ > ccie_voice-boun...@onlinestudylist.com] On Behalf Of ABIOLA ADEFILA [ > adefilabi...@gmail.com] > *Sent:* Saturday, October 03, 2009 10:06 AM > *To:* manishankar pandey > *Cc:* OSL Group > *Subject:* Re: [OSL | CCIE_Voice] conference bridge regisration > > Hello, > i checked my config the bind was there but still the conference bridge is > not registering > i did > no sccp > sccp > > the command is as shown below > hostname BR1-RTR > ! > boot-start-marker > warm-reboot > boot-end-marker > ! > logging message-counter syslog > ! > no aaa new-model > memory-size iomem 20 > network-clock-participate wic 0 > network-clock-select 1 T1 0/0/0 > ! > dot11 syslog > ip source-route > ! > ! > ip cef > ! > ! > ip domain name proctorlabs.com > no ipv6 cef > ! > multilink bundle-name authenticated > ! > ! > isdn switch-type primary-ni > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > voice-card 0 > no dspfarm > dsp services dspfarm > ! > ! > ! > ! > ! > archive > log config > hidekeys > ! > ! > ! > ! > ! > controller T1 0/0/0 > framing esf > linecode b8zs > pri-group timeslots 1-3,24 service mgcp > ! > controller T1 0/0/1 > framing esf > linecode b8zs > channel-group 0 timeslots 1-24 > ! > ! > ! > ! > ! > interface Loopback0 > ip address 10.10.110.2 255.255.255.255 > ip ospf network point-to-point > ! > interface FastEthernet0/0 > no ip address > shutdown > duplex auto > speed auto > ! > interface FastEthernet0/1 > no ip address > shutdown > duplex auto > speed auto > ! > interface Serial0/0/0:23 > no ip address > encapsulation hdlc > isdn switch-type primary-ni > isdn incoming-voice voice > isdn bind-l3 ccm-manager > isdn bchan-number-order ascending > isdn outgoing display-ie > no cdp enable > ! > interface Serial0/0/1:0 > no ip address > encapsulation frame-relay IETF > frame-relay lmi-type ansi > ! > interface Serial0/0/1:0.1 point-to-point > ip address 10.10.111.2 255.255.255.0 > ip ospf mtu-ignore > snmp trap link-status > frame-relay interface-dlci 101 > ! > interface FastEthernet1/0 > switchport trunk native vlan 130 > switchport mode trunk > switchport voice vlan 240 > ! > interface FastEthernet1/1 > ! > interface FastEthernet1/2 > ! > interface FastEthernet1/3 > ! > interface FastEthernet1/4 > ! > interface FastEthernet1/5 > ! > interface FastEthernet1/6 > ! > interface FastEthernet1/7 > ! > interface FastEthernet1/8 > switchport trunk native vlan 130 > switchport mode trunk > switchport voice vlan 240 > ! > interface FastEthernet1/9 > ! > interface FastEthernet1/10 > ! > interface FastEthernet1/11 > ! > interface FastEthernet1/12 > ! > interface FastEthernet1/13 > ! > interface FastEthernet1/14 > ! > interface FastEthernet1/15 > ! > interface Vlan1 > no ip address > ! > interface Vlan130 > ip address 10.10.101.1 255.255.255.0 > ! > interface Vlan240 > ip address 10.10.201.1 255.255.255.0 > ip helper-address 10.10.210.10 > ! > router ospf 1 > router-id 10.10.101.1 > log-adjacency-changes > network 10.10.0.0 0.0.255.255 area 0 > ! > no ip forward-protocol nd > no ip http server > no ip http secure-server > ! > ! > ! > ! > ! > ! > ! > ! > ! > ! > control-plane > ! > rmon event 33333 log trap AutoQoS description "AutoQoS SNMP traps for Voice > Drops" owner AutoQoS > ! > ! > voice-port 0/0/0:23 > ! > ccm-manager switchback immediate > ccm-manager fallback-mgcp > ccm-manager redundant-host 10.10.210.10 > ccm-manager mgcp > ! > mgcp > mgcp call-agent 10.10.210.11 service-type mgcp version 0.1 > mgcp dtmf-relay voip codec all mode out-of-band > mgcp bind control source-interface Loopback0 > mgcp bind media source-interface Loopback0 > ! > mgcp profile default > ! > sccp local Vlan240 > sccp ccm 10.10.110.10 identifier 2 version 5.0.1 > sccp ccm 10.10.110.11 identifier 1 version 5.0.1 > sccp > ! > sccp ccm group 1 > bind interface Vlan240 > associate ccm 1 priority 1 > associate ccm 2 priority 2 > associate profile 2 register br-cfb > associate profile 1 register br1-xcoder > ! > dspfarm profile 1 transcode > codec g711ulaw > codec g711alaw > codec g729ar8 > codec g729abr8 > maximum sessions 1 > associate application SCCP > shutdown > ! > dspfarm profile 2 conference > codec g711ulaw > codec g711alaw > codec g729ar8 > codec g729abr8 > codec g729r8 > codec g729br8 > maximum sessions 1 > associate application SCCP > ! > ! > ! > ! > ! > gatekeeper > shutdown > ! > ! > line con 0 > exec-timeout 0 0 > logging synchronous > line aux 0 > line vty 0 4 > exec-timeout 0 0 > logging synchronous > no login > length 0 > transport preferred none > transport input telnet > line vty 5 15 > exec-timeout 0 0 > privilege level 15 > logging synchronous > no login > transport preferred none > transport input telnet > ! > scheduler allocate 20000 1000 > end > BR1-RTR(config)# > > > > > On Sat, Oct 3, 2009 at 8:49 AM, ABIOLA ADEFILA <adefilabi...@gmail.com>wrote: > >> Hello, >> >> I think i did not put the bind command, will fix it and get back to you >> >> Regards >> >> >> >> >> On Sat, Oct 3, 2009 at 2:59 AM, manishankar pandey < >> manishankar...@yahoo.com> wrote: >> >>> Pl check that the name used on the Router config and on the CCM. Both >>> needs to match. Yes, it wil be interesting to see your config on router. >>> >>> Regards >>> >>> >>> --- On *Sat, 10/3/09, Sivakumar Mahalingam <sima...@gmail.com>* wrote: >>> >>> >>> From: Sivakumar Mahalingam <sima...@gmail.com> >>> Subject: Re: [OSL | CCIE_Voice] conference bridge regisration >>> To: "Cristobal Priego" <cristobalpri...@gmail.com> >>> Cc: "OSL Group" <ccie_voice@onlinestudylist.com> >>> Date: Saturday, October 3, 2009, 7:18 AM >>> >>> >>> >>> Hi, >>> >>> Can you post your SCCP configuration on the router ??? >>> >>> Regards, >>> Simah78 >>> On Fri, Oct 2, 2009 at 9:22 PM, Cristobal Priego < >>> cristobalpri...@gmail.com<http://mc/compose?to=cristobalpri...@gmail.com> >>> > wrote: >>> >>>> did you configure the bind command under the group ? >>>> >>>> 2009/10/2 ABIOLA ADEFILA >>>> <adefilabi...@gmail.com<http://mc/compose?to=adefilabi...@gmail.com> >>>> > >>>> >>>>> Hello, >>>>> >>>>> I have configured the conference bridge on the router >>>>> sccp is up and the dsp is up too >>>>> >>>>> it does not register to the callmanager, does any one have an idea why >>>>> this is >>>>> egards >>>>> >>>>> _______________________________________________ >>>>> For more information regarding industry leading CCIE Lab training, >>>>> please visit www.ipexpert.com >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> For more information regarding industry leading CCIE Lab training, >>>> please visit www.ipexpert.com >>>> >>>> >>> >>> -----Inline Attachment Follows----- >>> >>> _______________________________________________ >>> For more information regarding industry leading CCIE Lab training, please >>> visit www.ipexpert.com >>> >>> >>> >>> _______________________________________________ >>> For more information regarding industry leading CCIE Lab training, please >>> visit www.ipexpert.com >>> >>> >> > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
