jabber dont work when I dont configure IMP address manually

[nicanor00]

Hi

I have CUCM and IMP 12.5

I mus configure manually the IP address of IMP server on jabber in other to connect

What should I do to no need to configure this adress manually on jabber and connect successfuly ?

Please help

[collinks2]

You need to set up dns service record to be able to login automatically.

[Nithin Eluvathingal]

You need to have below SRV

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide_chapter_010.html

The following is an example of the _cisco-uds SRV record:

_cisco-uds._tcp.example.com     SRV service location:
          priority       = 6
          weight         = 30
          port           = 8443
          svr hostname   = cucm3.example.com
_cisco-uds._tcp.example.com     SRV service location:
          priority       = 2
          weight         = 20
          port           = 8443
          svr hostname   = cucm2.example.com
_cisco-uds._tcp.example.com     SRV service location:
          priority       = 1
          weight         = 5
          port           = 8443
          svr hostname   = cucm1.example.com

[Roger Kallberg · Accepted solution]

Apart from the other answers you got, which are absolutely correct. If you use MRA to connect clients that are not on-prem or connected via VPN, you would need to create this SRV DNS record in your external DNS zone. It’s very important to not have this present in the internal DNS zone, just as it’s equally important to not have the other SRV record present in the external DNS zone.

External Records

The following table lists the SRV record you must provision on external name servers as part of the configuration for Expressway Mobile and Remote Access:

Service Record	Description
_collab-edge	Provides the location of the Cisco VCS Expressway or Cisco Expressway-Eserver. Note    You must use the fully qualified domain name (FQDN) as the hostname in the SRV record. The client requires the FQDN to use the cookie that the Cisco VCS Expressway or Cisco Expressway-E server provides.

The following is an example of the _collab-edge SRV record:

_collab-edge._tls.example.com   SRV service location:
          priority       = 3
          weight         = 7
          port           = 8443
          svr hostname   = vcse1.example.com
_collab-edge._tls.example.com   SRV service location:
          priority       = 4
          weight         = 8
          port           = 8443
          svr hostname   = vcse2.example.com
_collab-edge._tls.example.com   SRV service location:
          priority       = 5
          weight         = 0
          port           = 8443
          svr hostname   = vcse3.example.com