I have purchased and installed XMPP Pro and User Management on my FreePBX server.
When activating XMPP client on BRIA Android client (192.168.0.157) then I get “stream error” from the XMPP server (192.168.0.250). Looks like XMPP server IP address is not valid (see Prosody log file at the end of this post). What am I missing ?
this is the freepbx generated prosody_additional.conf file :
this is my – Do NOT edit this file as it is auto-generated by FreePBX. All modifications to –
– this file must be done via the web gui. There are alternative files to make –
– custom modifications, details at: http://freepbx.org/configuration_files –
–
modules_enabled = {
“admin_adhoc”;
“admin_telnet”;
“bosh”;
“console”;
“dialback”;
“disco”;
“groups”;
“legacyauth”;
“pep”;
“ping”;
“posix”;
“private”;
“roster”;
“saslauth”;
“tls”;
};
data_path = "/usr/com/prosody"
authentication = "internal_plain"
storage = "sql"
log = "/var/log/prosody/prosody.log"
pidfile = “/var/run/prosody/prosody.pid”;
sql = { driver = “MySQL”, database = “asterisk”, username = “freepbxuser”, password = “xxxxxxxxxxxxxxx”, host = “localhost” }
VirtualHost "localhost"
groups_file = "/etc/asterisk/prosody_groups.txt"
Component “conf.localhost” "muc"
Component "asterisk.localhost"
component_secret = "asterisk"
validate_from_addresses = “false”
this is the prosody_groups.txt file after defining user “test” with password “test” via FreePBX User Management:
[user]
test@localhost
XMPP set to YES
I did not link any extension yet (I tried this also but it did not make any difference), to make things simple. I suppose iSymphony is to be used for presence updates from FreePBX extensions - that’s my next step. First I want to register a user to the XMPP server.
this is the FreePBX XMPP jabber setting:
domain = localhost
Finally I have configured a BRIA Counterpath Android client as follows:
Username : test
Password : test
Domain : IP adres of FreePBX server (192.168.0.250)
BRIA Account advanced settings: all default (empty resource, priority 0)
In the Prosody server logfile I get the following:
Sep 28 13:33:54 general info Hello and welcome to Prosody version 0.9.1
Sep 28 13:33:54 general info Prosody is using the select backend for connection handling
Sep 28 13:33:54 portmanager info Activated service ‘s2s’ on []:5269
Sep 28 13:33:54 portmanager info Activated service ‘component’ on [127.0.0.1]:5347
Sep 28 13:33:54 modulemanager error The mod_console plugin has been renamed to mod_admin_telnet. Please update your config.
Sep 28 13:33:54 portmanager info Activated service ‘console’ on [127.0.0.1]:5582
Sep 28 13:33:54 portmanager info Activated service ‘http’ on []:5280
Sep 28 13:33:54 portmanager info Activated service ‘https’ on []:5281
Sep 28 13:33:54 portmanager info Activated service ‘c2s’ on []:5222
Sep 28 13:33:54 portmanager info Activated service ‘legacy_ssl’ on no ports
Sep 28 13:33:54 mod_posix info Prosody is about to detach from the console, disabling further console output
Sep 28 13:33:54 mod_posix info Successfully daemonized to PID 19626
Sep 28 13:33:54 localhost:groups info Groups loaded successfully
Sep 28 13:33:55 jcp1a33aa0 info Incoming Jabber component connection
Sep 28 13:33:55 asterisk.localhost:component info External component successfully authenticated
Sep 28 13:34:01 c2s1a99690 info Client connected
Sep 28 13:34:01 c2s1a99690 info c2s stream for <192.168.0.157> closed: This server does not serve 192.168.0.250
Sep 28 13:34:01 c2s1a99690 info Client disconnected: connection closed