Hello dear community,
I'm writing with issue in Jabber 9.1 for Windows in SoftPhone mode. The issue I'm describing doesn't exist in 9.0.5.
When I'm calling internaly to jabber in softphone mode. I have pop-up as below:
But when I'm calling to jabber in softphone mode from PSTN. I have following pop-up:
After changing from softphone to deskphone and calling form the same PSTN phone everything seem to work fine:
Only difference between internal and PSTN call in softphone mode in signalization between CUCM and Jabber is SIP "from" field:
where 172.16.30.10 is our CUCM IP address
Call from PSTN:
where ITSP.domain.com is our SIP ITSP domain.
Also when such call without proper ID happen it isn't put to jabber call history.
Have anyone encountered same problem?
@jeff.singh: It is opened a TAC SR for that issue. Currently case is at business unit responsible for Jabber for Windows. So stay tuned, I'll update the thread when there will be some new information.
What is your user extension number populated with in Jabber. Is this the full DDI : 0726XXXXX? It looks like you need to configure wither application dial rules of tranlsation pattern to map internal 5 digit extension to the numbers populated in AD.
Look at the number populated for users in Jabber..what is the extension there..Does it match the users Extension on the phone?
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
TAC opened new bug ID for that issue: CSCue68071.
Root cause of this bug is different string after @ than CUCM address in Remote-Party-ID SIP field.