Video endpoint registerd to VCSc calling CUCM

Question

I have an EX90 registered to a VCSc with a SIP trunk connected to CUCM. An extension on CUCM can call the endpoint registered to the VCSc, but when a video endpoint  tries to call an extension on the CUCM the call fails, but the video endpoint can dial 9+10 digitit numberaor 9+1+!0 digits. i have set up a specific search rule to match an exact extension number in CUCM to match but the call still fails. In the call history of the VCSc the result is 404 not found - I am using SIP.

Answer 1

HI Michael.  Are you aslo using the CUBE in the same manner here also?  Reading the case it seems the call has to go out via PSTN and manages to go through a CUBE.  The CUBE is rejecting it because it has no valid caller id?  So I'm assuming that the PAI would need to be modified in this instance when the call is passed from VCS to CUCM. 
VCS can't manipulate that far down in the initial INVITE.  I'd have to check to see if a CPL would do this, but I'm doubting it, but will check around for you. 
if you have endpoints running TC6.3, you can ultimately try this to see if this will work for you. 
1) H323 protocol on endpoint - Remove the h323ID from the system. 
2) Verify E164 alias is programmed on the system and is registered to VCS.
3) Place call as H323 so that the interwork function (IWF) send call as SIP towards CUCM.  Since the h323ID is missing, IWF may pick up E164 alias in P-Asserted Identity (PAI) and send the call to CUCM. 
Now, you can test this...I can't guarantee it will work, but from reading the notes, they want something numeric versus alphanumeric and maybe if we place the E164 alias in the PAI it will help.  Can't guarantee it though...let us know..
Thanks.
VR
P2