On Mon, Oct 13, 2014 at 12:57 PM, ricky gutierrez
<[email protected]> wrote:
> I think asterisk does not respect this, I have added several within
> xmpp.conf buddy
>
> Client: ejabberd
> Buddy: [email protected]
> Resource: asterisk-xmpp
> node: http://www.asterisk.org/xmpp/client/caps
> version: asterisk-xmpp
> Google Talk capable: no
> Jingle capable: yes
>
> Client: operadora
> Buddy: [email protected]
> Resource: asterisk-xmpp
> node: http://www.asterisk.org/xmpp/client/caps
> version: asterisk-xmpp
> Google Talk capable: no
> Jingle capable: yes
> Buddy: [email protected]
> Buddy: [email protected]
> Resource: asterisk-xmpp
> node: http://www.asterisk.org/xmpp/client/caps
> version: asterisk-xmpp
> Google Talk capable: no
> Jingle capable: yes
>
The error message is pretty explicit about what you asked it to look for:
{quote}
acf_jabberstatus_read: Resource alcides of buddy [email protected]
was not found.
{quote}
Do you have a buddy [email protected] with a resource of alcides?
Based on the provided output, it does not appear as if you have that
buddy/resource combination, in which case the result of "7" is what I
would expect.
--
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
