I rebooted my CCM server and now the routing is working fine. After a TON of reading i think i figured out how to get the tracelogs from CCM. Here is where the error appears to occur:
10/25/2006 17:30:21.899 CCM|MediaResourceCdpc::waiting_MrmAllocateMtpResourceReq|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> 10/25/2006 17:30:21.899 CCM|MediaResourceCdpc::findDeviceGivenList|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> 10/25/2006 17:30:21.899 CCM|MediaResourceCdpc::mtpErrorResponseToManager|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> 10/25/2006 17:30:21.899 CCM|MediaResourceCdpc::waiting_MrmAllocateMtpResourceReq|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> 10/25/2006 17:30:21.899 CCM|MediaResourceCdpc::findDeviceGivenList|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> 10/25/2006 17:30:21.899 CCM|MediaResourceCdpc::mtpErrorResponseToManager|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> 10/25/2006 17:30:21.899 CCM|MediaResourceManager::waiting_MrmAllocateMtpResourceErr|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> 10/25/2006 17:30:21.899 CCM|MtpNoMoreResourcesAvailable - No more MTP resources available. App ID:Cisco CallManager Cluster ID:CM01-Cluster Node ID:cm01|<CLID::CM01-Cluster><NID::cm01><CT::Alarm> 10/25/2006 17:30:21.899 CCM|MRM::waiting_AllocateMtpResourceErr - ERROR - no resources are available -- ci = 16777229|<CLID::CM01-Cluster><NID::cm01><CT::1,100,111,3.2><IP::192.168.10.80><DEV::Port 10001> I'm looking this up now. -----Original Message----- From: [EMAIL PROTECTED] on behalf of Dan Austin Sent: Wed 10/25/2006 3:44 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [asterisk-users] Callmanager 3.3(5) and Asterisk with ooh323 PJ Wrote: > Dan, can you supply your ooh323.conf for me? I would like resolve my > issue with not recognizing dtmf by ooh323 from callmanager > my ooh323 is quite simple, also on callmanager config page for gateway > to asterisk is nothing special, no faststart, no mtp; ccm v4.1.3sr3a There's nothing secret about it, but I think I can skip that if the settings below are what you are using- > [general] > disallow=all > allow=alaw > ;faststart=no > ;h245tunneling=no > [ccm] > type=peer > ip=192.168.40.7 > port=1720 > ;dtmfmode=rfc2833 > ;dtmfmode=h245signal > ;h245tunneling=no > ;faststart=no I tend to use type=friend since I want calls in both directions. >From the list above, you have not set the dtmfmode in [general], which is where I set it, or in the peer. The sample ooh323.conf shows that the default is RFC2833, which does not work with CCM. Either uncomment ;dtmfmode=h245signal in the peer, or uncomment it and move it to [general]. > Dan Austin wrote: >> >> On the DTMF issues with chan_ooh323, I've used the channel with >> CCM 4.0, 4.1 and 5.0 with no issues. At one point I tested all >> of the DTMF methods ooH323 provides. CCM definately works with >> h245signal, and in the past has worked with q931keypad and >> h245alphanumeric. Cisco's support of RFC2833 in CCM has not >> been impressive. It works OK as of CCM 5.0 with SIP, but still >> not so solid with H323. Dan _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
<<winmail.dat>>
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
