Behaviour of Hunt Pilots

[harris.h]

Hello to all

Please can someone help with a hunt pilot issue.

We are transferring calls out of our CCX script using a call redirect step, the call redirect is placed to a hunt pilot number of 00000002.

This hunt pilot calls a number of sccp phones using the longest idle algorithm, these calls are recorded to our witness system.

The problem we have, when the endpoints are called by the hunt pilot, all calls are recorded against the hunt pilot number (00000002) not the endpoint numbers (phone dn's).

Is there any way to change this behaviour or can you think of any other workarounds for this.

Thanks

Rich

[Gajanan Pande]

Rich,

This appears to be working appropriate. In case you want to modify the destination against which the calls are getting recorded, may the question should be asked to Witness Support.

GP.

[harris.h]

Hello GP

If this is default behaviour I guess another way of call distribution is required other than a hunt group, each end called DN is required in witness not the hunt pilot number so we can easily filter calls.

What other call distribution mechanisms can we use?

Rich

[Rob Huffman]

Hi Rich,

Did you try setting this parameter?

Show Line Group Member DN in finalCalledPartyNumber CDR Field Service Parameter

This parameter determines whether the finalCalledPartyNumber field in CDRs shows

the directory number (DN) of the line group member who answered the call or the

hunt pilot DN. Valid values specify True (the finalCalledPartyNumber in CDRs will

show the DN of the phone that answered the call) or False

(the finalCalledPartyNumber in CDRs will show the hunt pilot DN).

The default value for this required field specifies False.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/7_1_2/car/caranrpt.pdf

Cheers!

Rob

Please remember to tag your threads and help support "Teachers without Borders"

https://supportforums.cisco.com/community/netpro/idea-center/communityhelpingcommunity

[harris.h]

Hi Rob

This setting has already been enabled, I guess this changes the stored CDR only, not the answer (called dn).

We require the endpoint DN as our recorded device id as we need to do pause/resume for taking Direct Debit credit card payments.

We essentially tie the DN to the user through this process.

Is there any other way rather than CCX agent desktop you can think of to distribute calls to our endpoints?

If I were to push the calls direct from CCX to the phones, they would record against the DN's of the phones; we would however lose the intelligent call routing.

Thanks again

Rich

[richb1971]

Rich,

We've got same problem with Witness. Did you resolve this?

Rich