[email protected] constantly in my asterisk log

amygrant

Guru
Joined
Apr 4, 2010
Messages
132
Reaction score
3
I'm posting this because I am clueless as to why I am seeing this is my logs and in case anyone else encounters the same conundrum.

Fresh install of PIAF 1.8 purple using gv for calls. I was having a problem making outbound calls so I modified /etc/asterisk/jabber.conf by setting

Code:
[general]
debug=yes

So I got more verbose logging, great. While tailing my log, I saw recurring entries indicating inbound and outbound messages from/to [email protected]

Now, I know this has nothing to do with my outbound calling problem - which has been fixed. I am still running in debug mode as I try to figure out the purpose for these entries.

I also understand that email address belongs to the maintainer of the jabber tool we are all using. I see however, that it sends my gvoice email address and gets back a filler response. I am assuming this is a callback feature to the developer for ... reporting perhaps?

Anyone know?

Here is a sample of the entries:
Code:
JABBER: asterisk OUTGOING: <message type='chat' to='[email protected]' from='[email protected]/Talk93A783DC'><body>blahblah</body></message>
JABBER: asterisk INCOMING: <message type="error" to="[email protected]/Talk93A783DC" from="[email protected]"><body>blahblah</body><error code="404" type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message>
JABBER: asterisk OUTGOING: <message type='chat' to='[email protected]' from='[email protected]/Talk93A783DC'><body>blahblah</body></message>
JABBER: asterisk INCOMING: <message type="error" to="[email protected]/Talk93A783DC" from="[email protected]"><body>blahblah</body><error code="404" type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message>
JABBER: asterisk OUTGOING: <message type='chat' to='[email protected]' from='[email protected]/Talk97F77464'><body>blahblah</body></message>
JABBER: asterisk INCOMING: <message type="error" to="[email protected]/Talk97F77464" from="[email protected]"><body>blahblah</body><error code="404" type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message>
JABBER: asterisk OUTGOING: <message type='chat' to='[email protected]' from='[email protected]/Talk97F77464'><body>blahblah</body></message>
JABBER: asterisk INCOMING: <message type="error" to="[email protected]/Talk97F77464" from="[email protected]"><body>blahblah</body><error code="404" type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message>
JABBER: asterisk OUTGOING: <message type='chat' to='[email protected]' from='[email protected]/Talk97F77464'><body>blahblah</body></message>
JABBER: asterisk INCOMING: <message type="error" to="[email protected]/Talk97F77464" from="[email protected]"><body>blahblah</body><error code="404" type="cancel"><remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message>
 
While I won't comment on the chat requests, I can fill you in on why you're seeing them.

That's a default setting in the jabber.conf. mogorman is Matthew O'Gorman, the maintainer of res_jabber (the interface between Jabber and Asterisk). I'm not certain, but he might work for Digium.

Jabber, if you don't know, is the protocol Google Talk uses.

I don't run 1.8, but I can only assume that a comment isn't properly set in jabber.conf, and it's trying to buddy Matthew. I'm not saying this is your fault, this is just a guess on my part as to where the problem is originating from.

I'm sure Ward or others have more information about this.
 
I don't think it is a default setting in jabber.conf. When "jabber test" is run from the asterisk CLI, this line in res_jabber.c is called.

Code:
        /* XXX Does Matt really want everyone to use his personal address for tests? */ /* XXX yes he does */
        ast_aji_send_chat(client, "[EMAIL="[email protected]"][email protected][/EMAIL]", "blahblah");
 
I was just going by the default jabber.conf.sample from SVN:

Code:
1	[general]
2	;debug=yes                              ; Enable debugging (disabled by default).
3	;autoprune=yes                          ; Auto remove users from buddy list. Depending on your
4	                                        ; setup (ie, using your personal Gtalk account for a test)
5	                                        ; you might lose your contacts list. Default is 'no'.
6	;autoregister=yes                       ; Auto register users from buddy list.
7	;collection_nodes=yes                   ; Enable support for XEP-0248 for use with
8	                                        ; distributed device state.  Default is 'no'.
9	;pubsub_autocreate=yes                  ; Whether or not the PubSub server supports/is using
10	                                        ; auto-create for nodes.  If it is, we have to
11	                                        ; explicitly pre-create nodes before publishing them.
12	                                        ; Default is 'no'.
13	;auth_policy=accept                     ; Auto accept users' subscription requests (default).
14	                                        ; Set to deny for auto denial.
15	;[asterisk]
16	;type=client                            ; Client or Component connection
17	;serverhost=astjab.org                  ; Route to server for example, talk.google.com
18	;pubsub_node=pubsub.astjab.org          ; Node to use for publishing events via PubSub
19	;[email protected]/asterisk  ; Username with optional resource.
20	;secret=blah                            ; Password
21	;priority=1                             ; Resource priority
22	;port=5222                              ; Port to use defaults to 5222
23	;usetls=yes                             ; Use tls or not
24	;usesasl=yes                            ; Use sasl or not
25	;[email protected]              ; Manual addition of buddy to list.
26	                                        ; For distributed events, these buddies are
27	                                        ; automatically added in the whitelist as
28	                                        ; 'owners' of the node(s).
29	;distribute_events=yes                  ; Whether or not to distribute events using
30	                                        ; this connection.  Default is 'no'.
31	;status=available                       ; One of: chat, available, away, xaway, or dnd
32	;statusmessage="I am available"         ; Have custom status message for Asterisk
33	;timeout=5                              ; Timeout (in seconds) on the message stack, defaults to 5.
34	                                        ; Messages stored longer than this value will be deleted by Asterisk.
35	                                        ; This option applies to incoming messages only, which are intended to
36	                                        ; be processed by the JABBER_RECEIVE dialplan function.

Line 25 is what I was going by.

But your example is a much better explanation as to what's going on!
 

Members online

No members online now.

Forum statistics

Threads
26,687
Messages
174,411
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top