I'm trying to figure out how to show an E.164 caller ID when dialing from a Jabber video client to a UCM or PSTN phone.
VCSC/E 7.1; TMS 13.2, TMSPE configured.
We have a VCSC > SIP Trunk > UCM (8.6) > H.323 GW w/ a voice PRI configured for dialing to and from the PSTN. We do this so the Jabber video client can be used as a softphone, and so we can have seamless FindMe to voice and SNR to video in both directions. In TMS, we have a provisioning template configured with a video address, caller ID, and device address. It's pulling the Active Directory Office Phone Number for the Jabber video users.
From what I'm reading here:
http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_FindMe_Express_Deployment_Guide_X7-1.pdf, we should be able to see caller ID when sending the call out an ISDN GW.
"This section describes how to use FindMe with calls that are routed via an ISDN gateway (for example, when calling a mobile phone, or some other ISDN accessible destination). If the VCS has Caller ID (Applications > FindMe > Configuration) set to use the FindMe ID, the caller ID presented will be the user's E.164 phone number."
UCM SIP config is vanilla, per
However, when a Jabber video call is directed to a UCM registered phone, we get "Unknown Caller." When we call direct to the PSTN, we see only the BTN of the PRI.
What's strange is that if we call from another VCS Jabber client (with all the same problems), direct into a UCM phone via the Internet over URI (e.g. firstname.lastname@example.org) through the VCSE, we see the caller ID name.
At present the VCS will only send the E.164 caller id to a H.323 ISDN GW which is registered to the VCS.
There is a feature request in the backlog to be able to set if E.164 Caller ID or Name/Video Address on a per zone basis. This will also sove the issue when the call is going out over a SIP link, as in this case, to a remote ISDN GW.