For anyone who wants a challenge...
We've upgraded our CCM6/CUPS6 to CCM7/CUPS7 environment and are now experiencing issues with the Remote Call Control from OCS to Call Manager.
Essentially, the situauation is such that if you initiate a call using a Cisco handset, MOC is aware of the call (on screen controls appear etc) and you can even initiate another call from MOC (which puts the 1st one on hold). It seems SIP uses a "consultative_call" command to intiative a second call whilst on the 1st call and everything works fine.
Howeverâ¦ if you are NOT in a call and try to initiate a call from MOC, you get 'Call not completed or has ended' and the attached errors appear in the logs.
The attached logs show the CTI Manager log and the SIP Proxy logs at the time of making a call and you will see that the CTI manager is returning an 'Invalid Feature Priority' error.
This features worked fine under CCM6 and CUPS6 with OCS2007, however we upgraded to 7 to test call forking and E.164 support for our customers.
I've checked the configs many times, following Cisco and MS documentation, checking and re-checking.
I'm open to suggestions as I've spent hours reading debug logs, CSTA documents and SIP information online... it's probably something minor and I just can't see the forest for the trees.
I know MSFT is working on getting OCS to work with CUCM directly. Which does not do much for RCC, but could have direct SIP trunks for dialing. It sort of works now, but there many problems with simple SIP commands like hold, transfer, hang up, (are there more???) The reason is that Cisco followed the RFC standard for SIP and MSFT decided they did not like the RFC standard and staggered away from it to make it work for OCS. Little did they know they would be re-writing code for OCS to make SIP RFC standard again on their products because so many of their customers have CUCM in place and want to use IM OCS and CUCM. Anyways.. interesting always good to hear how its working elsewhere!