cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
866
Views
20
Helpful
13
Replies

running windows jabber barebones requirement

baselzind
Level 6
Level 6

is it possible to get windows jabber to work without IMP and without srv records? like if i created a csf device on cucm and on jabber software i pinpoint the cucm ip the jabber will log in and work?

1 Accepted Solution

Accepted Solutions

Hi,

what i observed from the given logs as ;
login as test@google.com
172.19.3.2 - call manager IP.

Based on the logs, could you please perform below and share the information and test results.

Can you please open the below url and share the results;
https://172.19.3.2:8443/cucm-uds/version
https://cucm-a:8443/cucm-uds/user/test
https://cucm-a:8443/cucm-uds/servers

The system unable to resolve the hostname cucm-a, if you don't have any DNS entry / FQDN configured, could you please make localhost file entry for cucm-a to your call manager IP address and try again to jabber after clearing the unified communication folder from C:\Users\admin\AppData\Local\Cisco and C:\Users\admin\AppData\Roaming\Cisco

Regards,
Shalid

View solution in original post

13 Replies 13

Jonathan Schulenberg
Hall of Fame
Hall of Fame
Yes. Jabber can be configured to run in phone-only mode without IM&P. You can also specify the DNS FQDN of CUCM at the initial login dialog of Jabber if Service Discovery is not an option

is it possible without DNS or a domain configured? I tried creating a user and assigning a CSF to it , assigned required privileges to the user , created a CSF and assigned the user to it but it wont work?
is it necessary to create a jabber-config.xml file to get it to work?

Jabber is intended to work with DNS; the product documentation says it’s required but in a lab scenario you may be able to get it going without. You would need to have all server-side references listed by IP address, especially on the UC Services & Profile.

I created a UC profile and added a CTI point which is the cucm and then created a service profile which listed the CTI point however the jabber still wont log in ?
is it necessary to create and upload a jabber-config.xml?

CTI Route Points have nothing to do with Jabber.
No, a jabber-config.xml is not mandatory to deploy Jabber in most cases.

by the way I don't have a domain or dns so when I open the jabber and pinpoint the cucm address I dunno what should the username be? like username@what? I put username@something-random then I get to put the username and password but it doesn't log in anyways

please can someone help?

Hi, 



what domain the CUCM is configured?

I assume you are using CUCM local user for this jabber login!

I hope you are selecting the call manager option for authentication from advance option available in the jabber home page. insert the IP address of the call manager,  instead of FQDN. 

put the call manager domain when jabber prompt for the user, username@cucmdomain

and end-user password. 

---
See what the logs say in the PRT. if possible share along with the error that you receive.



Regards,

Shalid 

i have yet to configure the cucm with a domain , is it necessary to configure a domain to get jabber to work locally?
also how do i find these logs in PRT? what is the PRT?

It is the best practice to follow.

I tested now with giving some random domain(user@google.com) while login in jabber and it allowed me to login successfully.

PRT - problem report. to generate the problem report please follow below;

[extracted from https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/jabber-windows/116334-trouble-jabber-problem-00.html]
Stop the jabber.exe process.
Delete all logs for your OS; they are located in these folders:
Windows XP:
C:\Documents and Settings\username\Local Settings\Application Data\Cisco\Unified Communications\Jabber\CSF\Logs
Windows Vista:
C:\Users\username\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs
Windows 7:
C:\Users\username\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Log
Restart the jabber.exe process.
Reproduce the issue once in order to allow for easier investigation.

Note: Record the name of your Cisco contact, as well as the time of the interaction, and include this information in the summary for the problem report.

From the Jabber help menu, select the Report a problem option in order to launch the reporting tool.
Follow the instructions on how to report a problem.
The problem report does not include the database file for issues related to contact resolution on the Call History tab. The database files are located in these folders:

Windows XP:
C:\Documents and Settings\username\Local Settings\Application Data\Cisco\Unified Communications\Jabber\CSF\History
Windows Vista:
C:\Users\username\AppData\Local\Cisco\Unified Communications\Jabber\CSF\History
Windows 7:
C:\Users\username\AppData\Local\Cisco\Unified Communications\Jabber\CSF\History
For media issues (such as one way audio or video or missing audio or video), get Wireshark traces.

Regards,
Shalid

i have attached the logs , the user is "test" and the call timing is 4:27pm , and the cucm is 172.19.3.2

Hi,

what i observed from the given logs as ;
login as test@google.com
172.19.3.2 - call manager IP.

Based on the logs, could you please perform below and share the information and test results.

Can you please open the below url and share the results;
https://172.19.3.2:8443/cucm-uds/version
https://cucm-a:8443/cucm-uds/user/test
https://cucm-a:8443/cucm-uds/servers

The system unable to resolve the hostname cucm-a, if you don't have any DNS entry / FQDN configured, could you please make localhost file entry for cucm-a to your call manager IP address and try again to jabber after clearing the unified communication folder from C:\Users\admin\AppData\Local\Cisco and C:\Users\admin\AppData\Roaming\Cisco

Regards,
Shalid

creating a local dns records "172.19.3.2 cucm-a" on the machine got it to work ! thanks alot for the help

 

but just wondering what does these link show?

https://172.19.3.2:8443/cucm-uds/version
https://cucm-a:8443/cucm-uds/user/test
https://cucm-a:8443/cucm-uds/servers