Re: [OSL | CCIE_Voice] Transcoding Issues
Jose, Yeah I did. I had the allow-connections h323 to h323 under the voice service voip on the CME router, and that didn't work either. The call was connected but it was silence. I did a show call active voice brief, and it turned out that there was only one active H323 call leg, and that was it. The total call leg was only one. Transcoder was not transcoding any call leg. The transcoder resources were up. So i had no idea why it didn't work. Does anyone know of any good source for a technical documentation on how transcoder works? JD From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: RE: [OSL | CCIE_Voice] Transcoding IssuesDate: Thu, 6 Mar 2008 01:38:15 + Hi JD: Actually I tested and worked, what I had was: CCM -- h323 G729 (GK Controlled) --- CME -- H323 Dial-peer G711 to B-ACD I just configured the transcodec resources and the IPIPGW feature, do you have the allow H323 to H323 command under the voice service? Do a debug voip dialpeer to see what dial-peers are matched by the call. Regards, Jose From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Wed, 5 Mar 2008 13:41:29 -0800Subject: [OSL | CCIE_Voice] Transcoding Issues Hello, On CME router, I have an inbound G.279/H323 dialpeer for 3xxx and an outbound G.711/SIP dialpeer for CUE. Directed and forwarded calls from HQ or BR1 to CUE worked because of the local transcoder resource that transcoded the 2 different call legs. However, if i had an inbound G.729/H323 dialpeer for 3xxx and an outbound G.711/H323 dialpeer for the AA pilot number, the call from HQ or BR1 did not go through because the 2 different call legs did not get transcoded. So my question is it not possible to transcode between 2 different codecs for the same protocol? On the CUE case, the transcoder worked because of the 2 different codecs and different protocols. On the AA case, the transcoder did not work, so i assumed it had something to do with the same protocol. Does anyone know? JD Connect and share in new ways with Windows Live. Get it now! Express yourself instantly with MSN Messenger! MSN Messenger _ Shed those extra pounds with MSN and The Biggest Loser! http://biggestloser.msn.com/
Re: [OSL | CCIE_Voice] CCM 6.x Virtual Machine
Hi, I have successfully run CCM in VMware register the IP Phone thanks a lot for your guidance. I have one NIC card [but it is not connected to switch] and one windows loop back ipaddress can I able to run PUB, SUB and unity at the same time with one loopback IPAddress or Could you please guide me to run 3 instance at a time in VMware. Thanks, Vovan L [EMAIL PROTECTED] wrote: sounds like you ethernet interface which is in bridge group are not connected to network. you can greate loopback interface and bind VMnet0 to it instead of physical ethernet interface. google loopback in Windows assuming that your VM runs on Microsoft OS. cheers - Original Message - From: Balamurugan Singaram To: ccie_voice@onlinestudylist.com Sent: Wednesday, March 05, 2008 12:03 AM Subject: [OSL | CCIE_Voice] CCM 6.x Virtual Machine Hi, I have tried accessing CCM 6.x Pre-configured Virtual Machine, However when I power on the image it gives the following error: The network bridge on device VMnet 0 is temporarily down because the bridged ethernet interface is down. Could please let me know how to assign the IPaddress to Pre-configured Virtual CCM 6.x image. Thanks, Bala. Send instant messages to your online friends http://uk.messenger.yahoo.com Send instant messages to your online friends http://uk.messenger.yahoo.com
[OSL | CCIE_Voice] CUE error - Web JTAPI Login Failed
Hey guys, I have been getting this error on CUE when I try to integrate with the Call Manager [ver 4.3(3)] The error reads: *Saved successfully.* *Web Login Failed. Error while determining CCM version -1* *JTAPI Login Failed. Error while determining CCM version -1* Nothing has been changed I know of reading somewhere about this being a bug, but I wish, I could have closely looked at the resolution for the error. Has any one of you experienced this or know how to resolve this. Will appreciate all your responses in this regard. Thanks in advance, Priyank.
Re: [OSL | CCIE_Voice] Gatekeeper to CCM
Hi Edward: One way could be registering the CCM with a technology prefix, it could be 1#, 2# wichever number, and do the same with the CME, the CME tech prefix could be the same as the CCM, if you decide to register the CCM and the CME with different tech prefix the other site hast to append this tech prefix in order to complete the call, what I mean is, if you register the CCM with 2# for example, when the CME calls CCM, it should append 2# to the number dialed, for example if you dialed 1001 from CME you should append the 2# to this number in order to make the gatekeeper to receive 2#1001 and knows this number belongs to CCM. If you use the same tech prefix for CCM and CME you can use the zone prefiz gw priority command. Hope this help. Regards, Jose Date: Thu, 6 Mar 2008 12:19:15 -0800From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: [OSL | CCIE_Voice] Gatekeeper to CCM I am trying to get CCM to accept gatekeeper controller calls from CME I hav the HQ-RTR configured as followsgatekeeper zone local HQ-RTR ipexpert.com 172.22.100.1 enable-intrazone zone local CCM ipexpert.com enable-intrazone zone local CME ipexpert.com enable-intrazone zone remote PSTN-WAN ipexpert.com 10.22.200.2 1719 zone prefix PSTN-WAN 011* zone prefix CCM 1... zone prefix CCM 2... gw-type-prefix 1#* default-technology bandwidth remote 64 no shutdownI have CME configured as:dial-peer voice 1200 voip destination-pattern [12]... session target ras dtmf-relay h245-alphanumeric no vadCall manager is registered as tech-prefix 1#Zone CCMThe above configuration works. However if i change anything it stops working. My question is how can i accept calls into Call Manager without:gw-type-prefix 1#* default-technologyeven if I change the Tech-Prefix to 2# and change the gw-type-prefix 2#* default-technologyit will failAny ideas on the best way to receive incoming calls to CCM from a gatekeeper without using def ault-technologyThanksEd _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: [OSL | CCIE_Voice] Gatekeeper to CCM
Also, you need ! dial-peer voice 1200 voip destination-pattern [12]... session target ras dtmf-relay h245-alphanumeric no vad * tech-prefix 1#* ! So that you do not need gw-type-prefix 1#* default-technology in your gatekeeper. Of course, do make sure your CallManager Trunk is configured with the correct zone, and tech-prefix of 1# Thanks. On Fri, Mar 7, 2008 at 5:34 AM, Jose Linero Welcker [EMAIL PROTECTED] wrote: Hi Edward: One way could be registering the CCM with a technology prefix, it could be 1#, 2# wichever number, and do the same with the CME, the CME tech prefix could be the same as the CCM, if you decide to register the CCM and the CME with different tech prefix the other site hast to append this tech prefix in order to complete the call, what I mean is, if you register the CCM with 2# for example, when the CME calls CCM, it should append 2# to the number dialed, for example if you dialed 1001 from CME you should append the 2# to this number in order to make the gatekeeper to receive 2#1001 and knows this number belongs to CCM. If you use the same tech prefix for CCM and CME you can use the zone prefiz gw priority command. Hope this help. Regards, Jose -- Date: Thu, 6 Mar 2008 12:19:15 -0800 From: [EMAIL PROTECTED] To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Gatekeeper to CCM I am trying to get CCM to accept gatekeeper controller calls from CME I hav the HQ-RTR configured as follows gatekeeper zone local HQ-RTR ipexpert.com 172.22.100.1 enable-intrazone zone local CCM ipexpert.com enable-intrazone zone local CME ipexpert.com enable-intrazone zone remote PSTN-WAN ipexpert.com 10.22.200.2 1719 zone prefix PSTN-WAN 011* zone prefix CCM 1... zone prefix CCM 2... gw-type-prefix 1#* default-technology bandwidth remote 64 no shutdown I have CME configured as: dial-peer voice 1200 voip destination-pattern [12]... session target ras dtmf-relay h245-alphanumeric no vad Call manager is registered as tech-prefix 1# Zone CCM The above configuration works. However if i change anything it stops working. My question is how can i accept calls into Call Manager without: gw-type-prefix 1#* default-technology even if I change the Tech-Prefix to 2# and change the gw-type-prefix 2#* default-technology it will fail Any ideas on the best way to receive incoming calls to CCM from a gatekeeper without using def ault-technology Thanks Ed -- Express yourself instantly with MSN Messenger! MSN Messengerhttp://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/
