Preview Tool

Cisco Bug: CSCuo94065 - Jabber for TP does not allow TCP registration

Last Modified

Apr 02, 2018

Products (1)

  • Cisco Jabber Video for TelePresence (Movi)

Known Affected Releases

4.7 4.8

Description (partial)


Jabber for TelePresence does not register as TCP when provisioning information instructs it to. Instead the client registers as TLS.

Provisioning information is as follows;

<ProvData xmlns=""><Services item="1"><Encryption item="1">ForceTcpNoSrtp</Encryption><Sip item="1"><URL item="1"></URL><SignOnUri item="1">chmcmaho@matthews.local</SignOnUri></Sip><Presence item="1"><URL item="1">presence@matthews.local</URL></Presence><PhoneBook item="1"><URL item="1">phonebook@matthews.local</URL></PhoneBook></Services><Configuration item="1"><MultiWayConference item="1">multiway@matthews.local</MultiWayConference><DisplayName item="1">Chas test</DisplayName></Configuration></ProvData>|
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.