Caller ID from VCS Jabber Video over SIP Trunk to Phone

Answered Question
Jun 8th, 2012

Hello, Netpros.

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

ttp://www.tandberg.com/collateral/documentation/Deployment_Guides/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_6-1_7_8_and_X5-1.pdf

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. 1234@mydomain.com) through the VCSE, we see the caller ID name.

Thanks, all!

Joshua

I have this problem too.
0 votes
Correct Answer by gubadman about 1 year 10 months ago

Hi Joshua,

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.

Thanks,

Guy

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (2 ratings)
Correct Answer
gubadman Mon, 06/11/2012 - 01:13

Hi Joshua,

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.

Thanks,

Guy

joshuamarsh Mon, 06/11/2012 - 09:45

Thanks for the response, Guy.

Is there any way to force something in as it traverses the trunk?  Even a general number temporarily would be better than unknown.

Thanks,

Joshua

gubadman Tue, 06/12/2012 - 00:58

Hi Joshua,

There isn't anything that could be done from the VCS side. But maybe on your ISDN GW?

We use a Cisco Router as our ISDN GW and have voice translation-rule settings to change numbers as we want to. Though at the moment we mostly do that inbound. I believe BT (as we are in the UK) put on our default presentation number when our calls go out to the PSTN. I couldn't find a way to change from a specific sip userpart we were sending it - e.g. guybadman to a number using the rules, but there maybe a way to put a default one in. There is some more information here -

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a0080325e8e.shtml - you might be able to use a .* match pattern and then put in a default number

Thanks,

Guy

Actions

Login or Register to take actions

This Discussion

Posted June 8, 2012 at 3:12 PM
Stats:
Replies:3 Avg. Rating:5
Views:482 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard