I installed the xmpp license and set-up 2 extensions using the User Management module, I left the default localhost setting. all seem to set-up properly, I am using pidgin client for windows, I set the user for 201 host as localhost and server as pbx address 192.168.123.161 The client seem to register and unregister, here are some log file from prosody.log & pidgin debug. If anyone can help it would be greatly appreciated, I have not been able to find a thread were someone has successfully set-up a xmpp client with freepbx.
gary
Apr 14 14:46:04 mod_posix warn Received SIGTERM
Apr 14 14:46:04 general info Shutting down: Received SIGTERM
Apr 14 14:46:04 general info Shutting down…
Apr 14 14:46:04 general info Shutdown status: Cleaning up
Apr 14 14:46:04 general info Shutdown complete
Apr 14 14:46:04 general info Hello and welcome to Prosody version 0.9.1
Apr 14 14:46:04 general info Prosody is using the select backend for connection handling
Apr 14 14:46:04 portmanager info Activated service ‘s2s’ on []:5269
Apr 14 14:46:04 portmanager info Activated service ‘component’ on [127.0.0.1]:5347
Apr 14 14:46:04 modulemanager error The mod_console plugin has been renamed to mod_admin_telnet. Please update your config.
Apr 14 14:46:04 portmanager info Activated service ‘console’ on [127.0.0.1]:5582
Apr 14 14:46:04 portmanager info Activated service ‘http’ on []:5280
Apr 14 14:46:04 portmanager info Activated service ‘https’ on []:5281
Apr 14 14:46:04 portmanager info Activated service ‘c2s’ on []:5222
Apr 14 14:46:04 portmanager info Activated service ‘legacy_ssl’ on no ports
Apr 14 14:46:04 mod_posix info Prosody is about to detach from the console, disabling further console output
Apr 14 14:46:04 mod_posix info Successfully daemonized to PID 30794
Apr 14 14:46:04 localhost:groups info Groups loaded successfully
Apr 14 14:46:06 jcp9aeda00 info Incoming Jabber component connection
Apr 14 14:46:06 asterisk.localhost:component info External component successfully authenticated
Apr 14 14:47:10 mod_posix warn Received SIGTERM
Apr 14 14:47:10 general info Shutting down: Received SIGTERM
Apr 14 14:47:10 general info Shutting down…
Apr 14 14:47:10 general info Shutdown status: Cleaning up
Apr 14 14:47:10 general info Shutdown complete
Apr 14 14:47:11 general info Hello and welcome to Prosody version 0.9.1
Apr 14 14:47:11 general info Prosody is using the select backend for connection handling
Apr 14 14:47:11 portmanager info Activated service ‘s2s’ on []:5269
Apr 14 14:47:11 portmanager info Activated service ‘component’ on [127.0.0.1]:5347
Apr 14 14:47:11 modulemanager error The mod_console plugin has been renamed to mod_admin_telnet. Please update your config.
Apr 14 14:47:11 portmanager info Activated service ‘console’ on [127.0.0.1]:5582
Apr 14 14:47:11 portmanager info Activated service ‘http’ on []:5280
Apr 14 14:47:11 portmanager info Activated service ‘https’ on []:5281
Apr 14 14:47:11 portmanager info Activated service ‘c2s’ on []:5222
Apr 14 14:47:11 portmanager info Activated service ‘legacy_ssl’ on no ports
Apr 14 14:47:11 mod_posix info Prosody is about to detach from the console, disabling further console output
Apr 14 14:47:11 mod_posix info Successfully daemonized to PID 30859
Apr 14 14:47:11 localhost:groups info Groups loaded successfully
Apr 14 14:47:12 jcp8e3cb28 info Incoming Jabber component connection
Apr 14 14:47:12 asterisk.localhost:component info External component successfully authenticated
Apr 14 14:47:41 c2s8e57bc0 info Client connected
Apr 14 14:47:49 c2s8e57bc0 info c2s stream for <192.168.123.123> closed: session closed
Apr 14 14:47:49 c2s8e57bc0 info Client disconnected: connection closed
Apr 14 14:47:52 c2s8c1ab50 info Client connected
Apr 14 14:47:54 c2s8c1ab50 info c2s stream for <192.168.123.123> closed: session closed
Apr 14 14:47:54 c2s8c1ab50 info Client disconnected: connection closed
Apr 14 14:48:04 c2s8e33350 info Client connected
Apr 14 14:48:04 c2s8e33350 info c2s stream for <192.168.123.123> closed: session closed
Apr 14 14:48:04 c2s8e33350 info Client disconnected: connection closed
Apr 14 14:48:38 c2s8e029d8 info Client connected
Apr 14 14:48:38 c2s8e029d8 info c2s stream for <192.168.123.123> closed: session closed
Apr 14 14:48:38 c2s8e029d8 info Client disconnected: connection closed
(14:48:29) account: Connecting to account 201@localhost/.
(14:48:29) connection: Connecting. gc = 068274A0
(14:48:29) dnsquery: Performing DNS lookup for 192.168.123.161
(14:48:29) dnsquery: IP resolved for 192.168.123.161
(14:48:29) proxy: Attempting connection to 192.168.123.161
(14:48:29) proxy: Connecting to 192.168.123.161:5222 with no proxy
(14:48:29) proxy: Connection in progress
(14:48:29) proxy: Connecting to 192.168.123.161:5222.
(14:48:29) proxy: Connected to 192.168.123.161:5222.
(14:48:29) jabber: Sending (201@localhost): <?xml version='1.0' ?>
(14:48:29) jabber: Sending (201@localhost): <stream:stream to=‘localhost’ xmlns=‘jabber:client’ xmlns:stream=‘http://etherx.jabber.org/streams’ version=‘1.0’>
(14:48:29) jabber: Recv (361): <?xml version='1.0'?><stream:stream xmlns:stream=‘http://etherx.jabber.org/streams’ version=‘1.0’ from=‘localhost’ id=‘97d77c16-4f40-459a-92cd-09c411f2c19f’ xml:lang=‘en’ xmlns=‘jabber:client’>stream:featuresSCRAM-SHA-1DIGEST-MD5</stream:features>
(14:48:29) sasl: Mechs found: SCRAM-SHA-1 DIGEST-MD5
(14:48:29) jabber: Sending (201@localhost):
(14:48:29) jabber: Recv (208): cmVhbG09ImxvY2FsaG9zdCIsbm9uY2U9ImI5ZWM5MDE4LWY0YmQtNGUyYS05ZTRlLTA0NjFlNDE4ZjZmZSIscW9wPSJhdXRoIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==
(14:48:29) sasl: DIGEST-MD5 client step 2
(14:48:29) sasl: DIGEST-MD5 parse_server_challenge()
(14:48:29) sasl: DIGEST-MD5 ask_user_info()
(14:48:29) sasl: DIGEST-MD5 make_client_response()
(14:48:29) jabber: Sending (201@localhost): dXNlcm5hbWU9IjIwMSIscmVhbG09ImxvY2FsaG9zdCIsbm9uY2U9ImI5ZWM5MDE4LWY0YmQtNGUyYS05ZTRlLTA0NjFlNDE4ZjZmZSIsY25vbmNlPSI3UnlSV2tORHY5YUlyWU15bk9IMmQrWE90ZHc3dGJJMWc2UXJhSGZkVzRvPSIsbmM9MDAwMDAwMDEscW9wPWF1dGgsbWF4YnVmPTQwOTYsZGlnZXN0LXVyaT0ieG1wcC9sb2NhbGhvc3QiLHJlc3BvbnNlPWI4MjNmNzMwOTMzNzY1MTg1NmQ1MTNlNzgyNmJhMTE4LGNoYXJzZXQ9dXRmLTg=
(14:48:29) jabber: Recv (77):
(14:48:29) sasl: DIGEST-MD5 client mech dispose
(14:48:29) sasl: DIGEST-MD5 common mech dispose
(14:48:29) sasl: Mechs found: SCRAM-SHA-1
(14:48:29) sasl: No worthy mechs found
(14:48:29) connection: Connection error on 068274A0 (reason: 2 description: Not Authorized)
(14:48:29) account: Disconnecting account 201@localhost/ (04E2CD68)
(14:48:29) connection: Disconnecting connection 068274A0
(14:48:29) jabber: Sending (201@localhost): </stream:stream>
(14:48:29) connection: Destroying connection 068274A0