07-07-2021 04:42 AM
Hi Community, I have one issue, where I need a help.
I have CUCM 12.5SU4, Jabber Version 14. If I call the user, jabber is registered as a softphone I will get in logs a proper information about the calling party number. The calling party number is shown and Im able to call back.
2021-07-07 11:03:27,340 DEBUG [0x00000aa8] [p\sipcc\core\sipstack\ccsip_core.c(2101)] [csf.sip-call-control] [ccsip_check_set_privacy_screen] - ccsip_check_set_privacy_screen:uri=,number=+499XXXXXX74,name=+499XXXXXX74
If im running Jabber in CTI Mode, I can control the deskphone, but the DN is not shown properly.
2021-07-07 11:03:53,700 DEBUG [0x00003784] [c\src\deskphoneprovider\DPCall.cpp(2300)] [csf.ecc] [CDPCall::UpdateParticipant] - CDPCall::UpdateParticipant, strName=+49XXXXXXXX74, strUnmodifiedDN=+49XXXXXXXX74, strDN=+49XXXXXXXX74, strHuntMemberDN=, strUri=+49XXXXXXXX74@nonat.XXXXX.net, bNamePi=1, bNumberPi=1, CMID=0, callID=0, isSelf=0, isDestination=1
The App knows the str.DN number but in the end the calling party number will not be shown.
2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(427)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyName] - [id=8] getCallingPartyName() 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(429)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyName] - [id=8] CallingPartyName: +49XXXXXXXX474 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(436)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyNumber] - [id=8] getCallingPartyNumber() 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(438)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyNumber] - [id=8] CallingPartyNumber: 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(445)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyTranslatedNumber] - [id=8] getCallingPartyTranslatedNumber() 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(447)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyTranslatedNumber] - [id=8] CallingPartyTranslatedNumber: 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(454)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyUri] - [id=8] getCallingPartyUri() 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(456)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyUri] - [id=8] CallingPartyUri: +49XXXXXXXX474 @noXXXXXX.net 2021-07-07 11:03:53,701 WARN [0x00003784] [deskphonewrapper\CC_DPCallInfo.cpp(1634)] [csf.ecc] [csf::ecc::CC_DPCallInfo::generateP2PParticipants] - [id=8] No self participant identified in call participants 2021-07-07 11:03:53,701 WARN [0x00003784] [deskphonewrapper\CC_DPCallInfo.cpp(1637)] [csf.ecc] [csf::ecc::CC_DPCallInfo::generateP2PParticipants] - [id=8] other participant size:1 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(427)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyName] - [id=8] getCallingPartyName() 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(429)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyName] - [id=8] CallingPartyName: +49XXXXXXXX474 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(436)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyNumber] - [id=8] getCallingPartyNumber() 2021-07-07 11:03:53,701 DEBUG [0x00003784] [\deskphonewrapper\CC_DPCallInfo.cpp(438)] [csf.ecc.api] [csf::ecc::CC_DPCallInfo::getCallingPartyNumber] - [id=8] CallingPartyNumber:
CallingPartyName and CallingPartyUri will be shown....
Do you have any idea why the dn is not shown?
The issue is that we can not call back from Jabber in CTI mode, bcs the URI is not routed and the number is not shown in the app.
Thank you for you reply!
Solved! Go to Solution.
07-13-2021 05:06 AM
I opened a tac case..
Version 14 is buggy CSCvy95249 raised.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy95249
Downgrade as workaround.
07-13-2021 05:06 AM
I opened a tac case..
Version 14 is buggy CSCvy95249 raised.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy95249
Downgrade as workaround.
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