<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi Dane,<BR>
<BR>
As far as I understood, you don't have to use hardware conference resource. If it was like that, please choose 3 test ip phones then create a new media resource group (add the specific soft resources to it) then create a new media resource group list, too. Then please assign this MRGL to the regarded ip phones. Then please, test it.<BR>
<BR>
Regards,<BR>
<BR>
Ahmet Can KETEN<BR> <BR>> Date: Mon, 13 Jul 2009 14:25:13 -0500<BR>> From: dane@pktloss.net<BR>> To: mlinsemier@apassurance.com<BR>> CC: cisco-voip@puck.nether.net<BR>> Subject: Re: [cisco-voip] Conference Bridging Issues - 6509 with CMM-ACT<BR>> <BR>> You know thats what I was wondering and thinking.<BR>> <BR>> All the phones are 7960's and all use the same codec throughout.<BR>> <BR>> I always thought the phones themselves were suppose to be able to do<BR>> basic conference bridging like that.<BR>> <BR>> However this issue did not occur until after I removed some old 6608's<BR>> that I didn't realize some resources on them had been configured for<BR>> the conference bridging.<BR>> <BR>> I thought for basic conf. bridging (say three phones like I described)<BR>> would use the phones resources and not resources defined in<BR>> CallManager. I 'thought' those resources didn't come into play until<BR>> you tried to setup a meet-me conference or something along those lines<BR>> that involved more then the few resources the phones can provide.<BR>> <BR>> Guess its time I go read up on conferencing again. Every time I think<BR>> I know something I am reminded just how little I know.<BR>> <BR>> <BR>> <BR>> <BR>> On Mon, Jul 13, 2009 at 1:54 PM, Matthew<BR>> Linsemier<mlinsemier@apassurance.com> wrote:<BR>> > Are the 7960's that your are calling all running the same codec? Correct me<BR>> > if I'm wrong, but I am pretty sure you should be able to do a three-party<BR>> > conference (just like you described), without using any conferencing<BR>> > resources (as the 7960 can mix two other media streams).<BR>> ><BR>> ><BR>> > On 7/13/09 1:03 PM, "Dane" <dane@pktloss.net> wrote:<BR>> ><BR>> >> Having some trouble getting the conference bridging moved over to the<BR>> >> CMM's in my 6509s. CallManager is running 4.1(3)<BR>> >><BR>> >> I thought I setup everything correctly but adhoc conferencing from<BR>> >> phones isn't working.<BR>> >><BR>> >> I guess the first question I have is to make sure I am not confusing<BR>> >> things. The conferencing I am attempting is from my 7960. I call one<BR>> >> user, press the confrn softkey on phone and it places user on hold and<BR>> >> provides me dialtone to call another user. I do that and other user<BR>> >> picks up and I then hit confrn. softkey one more time.<BR>> >><BR>> >> When I do that it hangs up on both users and says "Can Not Join Calls".<BR>> >><BR>> >> I think I had three basic things I needed to do in order to get these<BR>> >> CMM-ACT's working.<BR>> >><BR>> >> 1. Configure the CMM IOS side to support the conference bridging<BR>> >> 2. Add the new conference bridges in CallManager (also removed the old<BR>> >> ones point to 6608s)<BR>> >> 3. Add the new conference bridge media resources to the existing media<BR>> >> resource group and remove the old ones.<BR>> >><BR>> >> All of these steps were done but obviously I either did something<BR>> >> incorrectly or I am missing something.<BR>> >><BR>> >> Here is my config on the CMM:<BR>> >><BR>> >><BR>> >> mediacard 3<BR>> >> resource-pool conf_bridging dsps 2<BR>> >> !<BR>> >> !<BR>> >> sccp local GigabitEthernet1/0<BR>> >> sccp ccm 10.61.100.71 identifier 2 version 4.1<BR>> >> sccp ccm 10.61.100.70 identifier 1 version 4.1<BR>> >> sccp<BR>> >> !<BR>> >> sccp ccm group 1<BR>> >> bind interface GigabitEthernet1/0<BR>> >> associate ccm 1 priority 2<BR>> >> associate ccm 2 priority 1<BR>> >> associate profile 1 register C05001a6c0368d6<BR>> >> !<BR>> >> dspfarm<BR>> >> !<BR>> >> dspfarm profile 1 conference adhoc<BR>> >> rtp timeout 600<BR>> >> codec g711ulaw packetization-period 30<BR>> >> codec g711alaw packetization-period 30<BR>> >> codec g729r8 packetization-period 30<BR>> >> codec g729ar8 packetization-period 30<BR>> >> codec g723r63 packetization-period 30<BR>> >> codec g723r53 packetization-period 30<BR>> >> vad override off<BR>> >> associate resource-pool conf_bridging<BR>> >><BR>> >><BR>> >><BR>> >> On CallManager I added the conference bridge as follows and it does<BR>> >> show as registered:<BR>> >><BR>> >> Type: Cisco Conference Bridge (WS-SVC-CMM)<BR>> >> Name: C05001A6C0368D6<BR>> >> MAC: 001A6C0368D6<BR>> >> Subunit: 3<BR>> >> Max Capacity: 32 ---> This was default, doesn't 1 dsp handle 32?<BR>> >> Resource pool shows 2 dsps, matter?<BR>> >> RTP Timeout: 600<BR>> >><BR>> >><BR>> >> Appreciate any thoughts or suggestions about this.<BR>> >><BR>> >> Regards,<BR>> >> Dane<BR>> >> _______________________________________________<BR>> >> cisco-voip mailing list<BR>> >> cisco-voip@puck.nether.net<BR>> >> https://puck.nether.net/mailman/listinfo/cisco-voip<BR>> ><BR>> ><BR>> > CONFIDENTIALITY STATEMENT<BR>> > This communication and any attachments are CONFIDENTIAL and may<BR>> > be protected by one or more legal privileges. It is intended<BR>> > solely for the use of the addressee identified above. If you<BR>> > are not the intended recipient, any use, disclosure, copying<BR>> > or distribution of this communication is UNAUTHORIZED. Neither<BR>> > this information block, the typed name of the sender, nor<BR>> > anything else in this message is intended to constitute an<BR>> > electronic signature unless a specific statement to the<BR>> > contrary is included in this message. If you have received this<BR>> > communication in error, please immediately contact me and delete<BR>> > this communication from your computer. Thank you.<BR>> ><BR>> _______________________________________________<BR>> cisco-voip mailing list<BR>> cisco-voip@puck.nether.net<BR>> https://puck.nether.net/mailman/listinfo/cisco-voip<BR><br /><hr />check out the rest of the Windows Live™.
More than mail–Windows Live™ goes way beyond your inbox.
<a href='http://www.microsoft.com/windows/windowslive/' target='_new'>More than messages</a></body>
</html>