cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1542
Views
15
Helpful
5
Replies

Jabber BOT Device have no Phone Service

plp_pnlr
Level 1
Level 1

We created Jabber BOT devices and sucessfully signed in, but no phone service. in cucm, device status is unregistered but we can do chat and so expcept calls. This is only for internal caonnection. if we register jabber thru MRA, it works fine.

5 Replies 5

plp_pnlr
Level 1
Level 1

partially solved the problem. problem is jabber cannot connect to cucm. It was solved by changes the server details in cucm from FQDN to IP. Now the phone services is active but still have issues. jabber BOT devices can't recieve calls but can make a call. and it can't recieve video when in a call. though the other end is fine

Have you created the needed SRV record for UDS to connect with CM for Jabber/Webex clients?



Response Signature


Vinod16
Level 1
Level 1

This was weird .

 Have you assign jabber bot profile to user properly in end user and bot profile ?

Please check dn partition also .

plp_pnlr
Level 1
Level 1

I think I have found the problem, but not  yet solved. I tried to change the CUCM info on Syste,>server to FQDN instead of IP address. Then the phone services work for external connected jabber. but now jabber connected intenally haven't the phones services. I know I have the correct uds SRV and PTR on our internal DNS.

You have to perform checklist before doing ip to fqdn changes otherwise this will impact database replication..

Refer this doc https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/211393-Change-CUCM-Server-Definition-from-IP-Ad.html

 

  1. Make sure you have to change ip to fqdn in enterprise parameter service url also...try searching http and https ...and correct entey in dns and create a record for each server.
  2. But your issue is not related to this ...something related to configuration only
  3. Srv record is related to only login ..there is no impact on any calls...so check configuration
  4.