Hunt pilot and calling number view at incoming call

[fhk-cseifert]

Hi folks,

I have a little strange question regarding the display view of the calling number at 8961-phone.

For the migration time, we are using the pstn-breakin and -breakout of an Alcatel-PBX. This works fine so long.

At first here our callflow from pstn to UCM:

PSTN <=s2m/E1=> Alcatel v9.1 <=s2m/qsig=> C2921 <=mgcp=> UCM v8.6

Then at UCM, normal doing...:

HuntPilot => Huntlist...LineGroup => CP-8961

Now we only see at an incoming call in the display "<calling name> for <huntpilot alerting name>"

The calling name is in our case the alerting name of the Alcatel-S2M/E1-interface "PBX), but it is not realy usable.

If you take the call, you see the correct (external) calling number.

In normal forwarding callflows, it can be adjusted at the line in section "Forwarded Call Information Display on Device".

But if the Huntpilot is involved, it seems to be with no effect and nothing changed.

Have anyone an idea, if it is possible to adjust the display view to "<calling number> for <huntpilot alerting name>"?

Thanks a lot for some hints.

Greetings, Chris

[shane.orr · Accepted solution]

I believe you are hitting this -

CSCth95017 Bug Details

Configurable parameter on how callingparty is displayed for hunt groups

Symptom:As of phone load 9.x and higher, calls to a hunt pilot show the following format for the calling party on the ringing phone.From 'Calling Party Name' for 'hunt pilot DN'i.e. From John Doe for XXXXThe previous format wasFrom 'Calling Party Name' ('Calling Party Number')i.e. From John Doe (XXX-XXX-XXXX)Need a configurable parameter to change the format to the previous format if the customer desires.Conditions:Occurs on phone loads 9.0(x) and above.Workaround:Downgrade to 8.4.x.

Status Fixed (Verified) Severity 2 - severe Last Modified In Last monthProduct Cisco Unified Communications Manager (CallManager)Technology 1st Found-In 8.6(2) Fixed-In 9.0(0.98000.21) 9.0(0.98000.74) 8.6(2.21023.1) 1.9(9.98000.16) 8.6(4.98000.21) Component(s) cp-huntlist

[fhk-cseifert]

Hey Shane,

Thanks for your hint. This bug describes exactly our problem. Hope it will be fixed in next ucm 8.6 release or 9.0. Back to 8.4 firmware is not realy a good solution.

5-Stars.

Chris.

Sent from Cisco Technical Support iPad App

[shane.orr]

No problem.  I ran into this recently so I dug into it a bit.

This functionality that was super important to one customer recently so we had to revert to Phone Firmware 8.4.4 on all the phones which in my case was 79XX series phones to get that behaviour working as they were accustom to.

I agree that this is not good because the first issue that crops up TAC is going to want us to upgrade.

I do not believe Cisco plans on making any changes to allow this to be modified at this time or in the near future, but I can not speak on their behalf.  The best thing you can do is pass this product feature enhancement along to your Cisco Account team to convey the importance of this issue.

Thanks,

Shane