My C40 is connected using H.323 in MCU 8510 with H.225 Trunk (Gatekeeper Controlled) to CM 8.6.2, and also we have intercluster ICT to another CM 8.6.2.
Is it possible to use Cisco Jabber for Windows version 9.6.0 with video with C40 with intercluster?
If not, can I have this C40 connected to the MCU and at the same time direclty to CM 8.6? If so, with this topology will work video using cisco jabber for windows?
Any help is much appreciate.
Video wise all your components are compatible (jabber to MCU/C40), but jabber is SIP based. You'd be better off setting up the C40 and 8510 with SIP as well.
I know that the C40s are dual stack and i might be getting muddled here, but it it possible to register the C series CODEC direct to CUCM using SIP, AND have H.323 enabled at the same time?
I know this works if you registered to other devices (such as the VCS-C), but I can't remember what I have read about what happens when you register one to CUCM. We don't use CUCM and so I don't truly know the answer to this.
I thought so. IMHO, this is not good, would not work for us, and is another reason why I doubt we will use CUCM. I'm sure others will not find this an issue.
CUCM is more than a simple registar for the device - the device is now managed through CUCM.
And why do you want your endpoints to end-around your infrastructure by having the endpoint bypass your call admission and policy engines by registering to some 'alt' infrastructure?
You should be connecting to the H323 systems as a valid path through the registar.
Dual stack has always been a transition technology, but as the core infrastructure supports SIP/H323 interworking, there is less reason to have the edge devices do it. That's why you see it being phased down.
It also simplifies the User Experience, testing, and more. Effectively, the endpoints will reduce their complexity and so you will see improvements in consistency and time to market of features.
Yes Steve, I do understand Cisco reasoning, but for us H.323 is the de-facto standard and will be for an awful long time to come. The VCS-E/C pair to a great job of allowing for call routing, albeit not quite a slick as CUCM, but functional enough, and things like interworking between SIP and H.323 is not always perfect. Have the option to fall back to H.323 and register direct to the VCS-C would be required - for us at least.
Chris, ironically your message sounds exactly like the arguments for why people didn't want to register to gatekeepers 10+ years ago :)
CUCM vs VCS is not about choosing between different registars type A and B - but far more. That is still on the early side of life... but H.323 is sunsetting.
We were SIP first long before the CUCM came into play.. and with the teething of BFCP behind us... it's generally smooth sailing. Encryption changes a good bit in H323 vs SIP because it's dependent more on the transports used vs device-to-device.
The less choices in call parameters that are presented to admins and users.. the better IMO.
First thank you all to contributed with this topic.
As I'm new with video, and I just learned maybe the right question for this is.
As my C40 is registered as H323 at VCS. Can I create a transform call routing in the VCS in order to allow calls between H.323 and SIP devices?
If this theory is right, I should be able to use my cisco Jabber for Windows (SIP) makes call/video to my existing C40 H.323 VCS?!
Let me know if you can point me in the right direction.
Once again thank you!
Your Jabber client will be on UCM, so your primary issue is you need to route calls between UCM and VCS. Check out the deployment guide for VCS and CUCM together - http://www.cisco.com/c/en/us/support/unified-communications/telepresence-video-communication-server-vcs/products-installation-and-configuration-guides-list.html
That will help introduce to you the topics needed to setup the trunks and transforms to route calls between your VCS and UCM.
Steve, thanks a lot for sharing this doc...it is helping me to understand better video environment.
So now here I'm:
I was able to dial 4 digits extension from my cisco jabber for windows to C40 H323 via intercluster. However after the first ring with auto answer C40 the call dropped. If I disable the auto answer it keeps ring until someone picks it up and then the call dropped with " fast busy tone". Like some mismatch codec, etc...
The VCS is setup to interwork between H323 and SIP. However under call history I was able to see this call as H.323/H.323 with cause: Resource unavailable.
I though would be SIP/H.323.
Here are some possibilities way to find out from my perspective:
1. VCS settings (which is my first time using it, so not sure what it might be a problem). One suggestion, can I also have a sip trunk between the cluster I'm connected directly to VCS known that VCS has already a GK trunk to the other cluster without breaking anything?
2. I'm not in the cluster where I have the VCS/MCU, registered. So I'm using intercluster ICT, not SIP to connect to another Cluster. Also I checked this cluster and in fact they are using GK H.225 instead SIP Trunk as it is mentioned in your doc you sent me. So not sure if that might be a problem as well.
Someone can see any problem with this call flow topology and point me in the right direction to make that work?
Any help is much appreciate. Thanks!
The first issue was solved between cisco jabber, CM, VCS, C40.
The problem is when someone picks it up from C40 side the call dropped, and I hear a fast busy tone.
Does anyone know to decipher this message? mPendingOutgoingUpdate = 0|4,100,13,303068.6^10.248.154.10^*
The 10.248.154.10 is the CM cluster where the VCS has directly connected to.
Here is the SDI logs I was able to capture, but no way how to pinpoint where is the issue. I called from 4122107 to 7504 C40 at 14:37. The 10.223.25.11 is my CM where I'm connected to. Let me know if anyone can point me to the right direction: