Caller ID between Cisco CM 6X and OCS 2007 R2 RRS feed

  • Question

  • We currently have OCS 2007 R2 installed running with Cisco Sip from CM 6X. The issue i have is when i call people in my offices all they see is my extension number without any name. This also applies when i call someone outside like my cell Phone. The only Called Id information i get is my 4 digit extension but nothing else. No name or complete Number. When people call me i get the correct caller Id information extention and name if they are calling from internal. If calling from one of my contacts i get there name and nubmer etc.

    I am assumign that it is something in the normalization that is causing the issues.

    Thursday, June 18, 2009 5:58 PM

All replies

  • Hi Pat,

    Pretty common question and currently caller name information is stripped by the mediation server in both directions, support is coming for this function but no idea when. Your 4 digit caller id issue is a slightly different issue that can be solved by your gateway appending your leading digits on your outbound calls or you can just use the 11 digit E164 number on your users and make changes to your normalization rules to accommodate abbreviated dialing (this is probably your best solution, always best to use E164 within the OCS enviroment, so line URI = tel:+1xxxxxxxxxx). If you dont have inbound DID's for your users this could be a little hard of course so it depends on what your situation is. Best to use the trunk ID or Company DID if you are using private extensions anyway which can be configured in CUCM on outbound trunks.


    Thursday, June 18, 2009 6:49 PM
  • As always, good info from Chris.  Another option is SmartSIP, which can add your Active Directory display names to the caller ID that is presented to your Cisco phones.  It can also do things like pass your 4 digit caller ID to Cisco but a full 10 digit caller ID to the PSTN if it's not possible to get your Cisco config to do what you need.  Plus, when you're ready, you can reuse your Cisco phones as OCS endpoints instead of buying new hardware to move your users to OCS Enterprise Voice.
    Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike
    Friday, June 19, 2009 2:56 AM
  • This issue is now resolved with the July rollup patches for OCS R2. it requires patching on mediation and front end servers. please read the following for changes required on the mediation server:


    • Edited by VoIPnorm Tuesday, August 4, 2009 6:47 PM Update
    Tuesday, August 4, 2009 5:25 PM