Hi Purna,
What I'm trying to do is not the same, but very similar, as we're using TP endpoints instead of Jabber.
The CUCM version is above 8.6.2.21020, as we have MX300 in the supported endpoints list, without requiring a .cop installation, but I'll need to check the exact version. And, our MCU is 4500 series, instead of 5300. But, other than these, the topology seems to be very much like what you have.
The problem:
1) We can't do CUCM provisioning, as MX300 and EX90 with TC/TE6 software seems to require phone configuration files signed by CUCM (as in .cnf.xml.sgn) but we really don't want to mess with the production CM cluster, unless very necessaray. So we went on with manual provisioning of the SIP profiles on the endpoints, at least for now. (I'm not sure if this is a relevant issue or not.)
2) That said, our endpoints don't seem to have the means to "merge" two calls. Ie;
- I dial TP-B from TP-A as call-1
- I get call-1 on hold and dial TP-C from TP-A
- What I get is "swap", instead of "merge" on the interface.
- If I try to "add" a second device during a call is ongoing, I can only establish an audio call (which is something I'd expect, without an MCU).
For this, we just created device definition on CUCM for TP endpoints, and configured endpoints SIP profiles with External Manager IP address and URI, as well as setting SIP server type to Cisco.
If you can share what you did, in terms of configuration, it would be very nice, to see if we're missing something. (All current Cisco documentation seem to rely on CUCM provisioning, which as stated, is something we're having problem doing.)
And, if you (or anyone else) had any succcess / have any information on using DSP3 based conference bridge resources on CUCM for creating ad-hoc conferences through TP endpoints, I'd be glad to hear that...
Emre
