System information

serverhost = jabber.shifteight.org
pubsub_node = pubsub.jabber.shifteight.org
username = server2@jabber.shifteight.org/astvoip2
secret = mypassword
distribute_events = yes
status = available
usetls = no
usesasl = yes
buddy = server1@jabber.shifteight.org/astvoip1
Testing
To ensure that everything is working properly, start by doing some verification of the
jabber.conf settings on each server. There are a couple of relevant Asterisk CLI com-
mands that can be used here. The first is the jabber show connected command, which
will verify that Asterisk has successfully logged in with an account on the jabber server.
The output of this command on the first server shows:
*CLI> jabber show connected
Jabber Users and their status:
User: server1@jabber.shifteight.org/astvoip1 - Connected
----
Number of users: 1
Meanwhile, if jabber show connected is executed on the second server, it shows:
*CLI> jabber show connected
Jabber Users and their status:
User: server2@jabber.shifteight.org/astvoip2 - Connected
----
Number of users: 1
The next useful command for verifying the setup is jabber show buddies. This command
allows you to verify that the other server is correctly listed on your buddy list. It also
lets you see if the other server is seen as currently connected. If you were to run this
command on the first server without Asterisk currently running on the second server,
the output would look like this:
*CLI> jabber show buddies
Jabber buddy lists
Client: server1@jabber.shifteight.org/astvoip1
Buddy: server2@jabber.shifteight.org
Resource: None
Buddy: server2@jabber.shifteight.org/astvoip2
Resource: None
Distributed Device States | 317