CDR and line group member DN

Answered Question
May 26th, 2010
User Badges:

Hi,


On a CallManager 7.0.2 I have to make statistics on line group members answering calls.

In service parameters I changed the option "Show Line Group Member DN in finalCalledPartyNumber CDR Fields" to enabled but in fact, in the CDR

appears the phone "external phone number mask" instead of the DN.

The doc I read : http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/5_1_3/car/caranrpt.html

This a big issue for my customer because lot of phone have the same external phone number mask.


Question; Is there a mistake in the doc or is my CallManager bugging ?

Correct Answer by Rob Huffman about 6 years 12 months ago

Hi Guy,


I believe that 99% of the build/upgrades will still use the

Restricted version. Have a look at this good thread;


http://www.gossamer-threads.com/lists/cisco/voip/129991?do=post_view_flat#129991


So, you could go to CUCM 7.1(5) without the .cop file


Cheers!

Rob

Correct Answer by Rob Huffman about 6 years 12 months ago

Hi Guy,



It's buggy


CSCsm42428            Bug Details



External Phone Number Mask Applied to finalcalledparty  in Hunt-List CDR

Symptom:

The "finalcalledparty" field in the  calldetail record found on a Cisco Unified Communications Manager server  is populated with the value of an external phone number mask after a  call is placed to a hunt list.

Conditions:

This  will occur if the "Show Line Group Member DN in finalCalledPartyNumber"   is set to true and a calls is made to a hunt list.

Workaround:

Remove  the external mask from the DN in the hunt list
StatusStatus
Fixed             

Severity Severity
6 - enhancement

Last Modified Last Modified
In Last 7 Days        

Product Product
Cisco Unified Communications Manager (CallManager)         

Technology Technology


1st Found-In 1st Found-in
4.3
7.0(1)
6.1(2.1000.13)       
           
Fixed-In Fixed-in
8.5(0.94040.36)
7.1(4.98000.135)
7.1(4.18)
7.1(4.19)
7.1(4.21)
7.1(4.22)
7.1(4.23)
7.1(4.24)
6.1(5.11006.1)
7.1(5.10000.12)
8.0(2.11001.3)
8.0(1.11005.1)




Cheers!

Rob



Please support CSC Helps Haiti


https://supportforums.cisco.com/docs/DOC-8895


https://supportforums.cisco.com/docs/DOC-8727

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Rob Huffman Wed, 05/26/2010 - 06:38
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Guy,



It's buggy


CSCsm42428            Bug Details



External Phone Number Mask Applied to finalcalledparty  in Hunt-List CDR

Symptom:

The "finalcalledparty" field in the  calldetail record found on a Cisco Unified Communications Manager server  is populated with the value of an external phone number mask after a  call is placed to a hunt list.

Conditions:

This  will occur if the "Show Line Group Member DN in finalCalledPartyNumber"   is set to true and a calls is made to a hunt list.

Workaround:

Remove  the external mask from the DN in the hunt list
StatusStatus
Fixed             

Severity Severity
6 - enhancement

Last Modified Last Modified
In Last 7 Days        

Product Product
Cisco Unified Communications Manager (CallManager)         

Technology Technology


1st Found-In 1st Found-in
4.3
7.0(1)
6.1(2.1000.13)       
           
Fixed-In Fixed-in
8.5(0.94040.36)
7.1(4.98000.135)
7.1(4.18)
7.1(4.19)
7.1(4.21)
7.1(4.22)
7.1(4.23)
7.1(4.24)
6.1(5.11006.1)
7.1(5.10000.12)
8.0(2.11001.3)
8.0(1.11005.1)




Cheers!

Rob



Please support CSC Helps Haiti


https://supportforums.cisco.com/docs/DOC-8895


https://supportforums.cisco.com/docs/DOC-8727

guy.richard Wed, 05/26/2010 - 07:23
User Badges:

Hi Rob,


Thanks so much for your answer.

In fact I need external mask on my DNs because of my outbound calls policies and all phones in a given line group have the same external mask so I have to upgrade. I tried to remove the mask and effectively I could see the change in the CDR.

Strangely when a user intercept a call in the line group the CDR is ok but not if he answers directly.


Kind regards


Guy

Rob Huffman Wed, 05/26/2010 - 09:24
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hey Guy,


You are most welcome my friend! Yes, that is a pretty weak

work-around I must say. If you can hold off for a little bit before

upgrading to 7.1(5) I would do so Stay away from 8.0 for sure.


Cheers!

Rob

guy.richard Wed, 05/26/2010 - 09:42
User Badges:

Hi Rob


I am confusing while downloading my upgrade files . It is talked about "restricted" and "unrestricted" 7.1.5 version.

The customer is a private end-customer in France which one is allowed ?

I do not want to upgrade under 7.1.5.

guy.richard Wed, 05/26/2010 - 09:58
User Badges:

Hi Rob


Sorry please forget my question about restricted I have found information about that


I think I'll upgrade to 7.1(3b)su2.


guy.richard Wed, 05/26/2010 - 10:04
User Badges:

Hi Rob,


The bug is not fixed in 7.1(3b) and there are no more 7.1.4 downloadable on CCO and 7.1.5 have this restriction policy and no path to 8.0.


What can I do ?

Correct Answer
Rob Huffman Wed, 05/26/2010 - 10:13
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Guy,


I believe that 99% of the build/upgrades will still use the

Restricted version. Have a look at this good thread;


http://www.gossamer-threads.com/lists/cisco/voip/129991?do=post_view_flat#129991


So, you could go to CUCM 7.1(5) without the .cop file


Cheers!

Rob

guy.richard Wed, 05/26/2010 - 10:43
User Badges:

Thanks Rob,


Because I am not sure of the impact of such an "experimentation" on my customer life cycles I really wonder what do I do.

Rob Huffman Wed, 05/26/2010 - 12:08
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hey Guy,


I'm totally with you here my friend


I would take my time here before I made any decisions on an

upgrade path. CUCM 7.1(5) is pretty new and although I haven't seen or heard

any truly distressing war stories about it, I'd want to do my normal

"due diligence".


It wouldn't seem like this type of issue should be "mission critical" and force

a quick move forward. Open a TAC case to see if they have an ES that addresses

this issue as a first step.Discuss with your management the pros/cons of such a

change if you must move to 7.1(5).


I know this doesn't answer your immediate concerns, but................

"patience is a virtue" especially with CUCM upgrades


Cheers!

Rob

Actions

This Discussion