06-02-2020 09:26 AM
Hello,
My organization has a number of users who now utilize the Jabber app on their mobile devices to make\receive calls while working remotely. These same users are also members of Hunt Groups in CUCM (ver 11.5.1).
While receiving inbound calls in the Jabber app (ver 12.8.0) on their mobile phones, the Jabber app does not specify if this is a call from the Hunt Group or a direct call to the users extension. It only displays the callers info & number. The users would like the ability to identify inbound Hunt Group calls in the Jabber app.
I have verified the "Alerting Name" field is populated for the Hunt Group in CUCM. I have tried inserting an identifier in the prefix digit field under Calling Party Transformations in CUCM. I also tried inserting the last 4 digits of the Hunt Group in the Calling Party Transformation Mask field in CUCM but no change.
Is there a configuration\setting in Cisco CUCM for the Hunt Groups which would distinguish them from regular inbound calls in the mobile Jabber app?
Thanks in advance
06-02-2020 06:30 PM
Hi,
In order to know whether the call is for particular hunt group, you can utilize "Alerting Name" field under Hunt Pilot configuration. For example, if you configure this field as "Finance Hunt Group" then your Jabber App will display "<Caller_ID> for Finance Hunt Group"...Here is the test result from my device:
If you leave "Alerting Name" field blank then Jabber App will display "<Caller_ID> for <Hunt_Pilot_Number>".... Here is test result for this scenario:
And here is the screenshot of call history:
I hope this will help you.
06-03-2020 09:17 AM
Vaijanath,
~Thanks very much for your response (and screenshots)
As stated in my original post, the "Alerting Name" field under the Hunt Pilot configuration was already populated. Per your suggestion, I cleared the Alerting Name field as well as the ASCII Alerting Name field and placed more test calls to the Hunt Group extension but there was no change - Jabber only displays the inbound callers name.
If you can think of any other suggestions to try, please let me know.
Again, thank you very much for your quick & thorough reply.
06-03-2020 05:43 PM - edited 06-03-2020 05:45 PM
Hi,
Other than "Alerting Name" field, there is no other configuration needed for what you are trying to achieve. I tested the scenario with below versions:
CUCM Version: 12.5
Expressway Version: 12.5
Jabber for iPhone: Latest from App Store
I couldn't find any software bug for this issue but it may be possible. I would recommend to open Cisco TAC case or upgrade the CUCM to later release.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide