02-11-2025 07:36 AM
This is a new cluster setup of Jabber for Android, I have many other clusters working successfully.
In short I can't get the BOT file to serve up files on port 6972 i.e. https://tftp01.domain.com:6972/BOT5900.cnf.xml would be for extension 5900 on Jabber for Android. I can do a tftp get BOT5900.cnf.xml over tftp fine. This works on like 14 other clusters I have, but not this one. Can't get any Jabber for Android BOT devices to register on this one cluster. Don't have any Jabber for Windows to test etc. I run a Utils network capture eth0 file packet count 10000 size all port 6972 and can seeing traffic going back and forth, followed by tcp reset, there is no firewall, and the client log shows;
2025-02-10 09:43:28,341 INFO [0x0000006ce2006cb0] [ls/src/http/BasicHttpClientImpl.cpp(675)] [csf.httpclient] [performRequest] - *-----* HTTP response code 0 connect code 0 for request #9 to PII_CED_Exception{https://tftp01.domain.com:6972/BOT5900.cnf.xml}
2025-02-10 09:43:28,341 ERROR [0x0000006ce2006cb0] [ls/src/http/BasicHttpClientImpl.cpp(568)] [csf.httpclient] [executeImpl] - There was an issue performing the call to curl_easy_perform for request #9: CONNECTION_TIMEOUT_ERROR
2025-02-10 09:43:28,341 INFO [0x0000006ce2006cb0] [s/impl/ucm-config/http/HttpUtils.cpp(80)] [csf.config] [mapToHttpUtilsResult] - csf::http::HttpClientResult=[CONNECTION_TIMEOUT_ERROR] HttpUtilsResult=[CONNECTION_TIMEOUT_ERROR]
2025-02-10 09:43:28,342 WARN [0x0000006ce2006cb0] [mpl/ucm-config/tftp/TftpFileSet.cpp(114)] [csf.config] [fetchInitialTftpFile] - Failed to connect to Tftp server : result : CONNECTION_TIMEOUT_ERROR
2025-02-10 09:43:28,342 INFO [0x0000006ce2006cb0] [mpl/ucm-config/tftp/TftpFileSet.cpp(101)] [csf.config] [fetchInitialTftpFile] - Tftp File Attempt 1 using url : PII_CED_Exception{https://tftp02.domain.com:6972/BOT5900.cnf.xml}
If I use a Web Browser on Androd device for https://tftp01domain.com:6972/BOT5900.cnf.xml it fails, works fine on other clusters. I have also tried other BOT device names like BOT802.cnf.xml etc
CallManager 14SU1
Jabber for Android 15.0.2
I am 100% confident problem is CallManager related around port 6972
02-11-2025 07:37 AM
I made a typo in subject line, files are BOTXXXX.cnf.xml nothing to do with XNF
02-11-2025 08:13 AM
Have you tried deleting the BOT device and adding it again? Additionally, have you restarted the TFTP service and checked?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide