asterisk users - Nov 2012 - Asterisk crashing when trying to start a Jabber session with ejabberd

I have tried today to change my Jabber server from OpenFire to
ejabberd. Unfortunately I have not been able to get Asterisk logged in
to Jabber since. If SASL is not enabled, then ejabberd rejects the
connection as it does not support non-SASL authentication. However, if
SASL is enabled, Asterisk crashes when it logs in.

I've had this conversation with the ejabberd chatroom people:
http://chatlogs.jabber.ru/ejabberd at
conference.jabber.ru/2012/11/10.html#21:28:10.522550

I really do not know how to proceed on this.

Asterisk logged in successfully on OpenFire using SASL. On an earlier
version I saw a similar crash if the Jabber server was Prosody.

I am using ejabberd 2.1.10-3 and asterisk 1:1.8.13.1~dfsg.1 from Debian
wheezy. I am happy to try to obtain any logs that are helpful but may
need guidance on how to do it.

-- 
Phil Reynolds
mail: phil-asterisk at tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

On Sat, 10 Nov 2012 18:08:58 +0000
Phil Reynolds <phil-asterisk at tinsleyviaduct.com> wrote:
> I have tried today to change my Jabber server from OpenFire to
> ejabberd. Unfortunately I have not been able to get Asterisk logged in
> to Jabber since. If SASL is not enabled, then ejabberd rejects the
> connection as it does not support non-SASL authentication. However, if
> SASL is enabled, Asterisk crashes when it logs in.
This is what appears in CLI when the crash occurs:

JABBER: asterisk OUTGOING: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='jabber:client' to='firthpark.tinsleyviaduct.com'
version='1.0'>

JABBER: asterisk INCOMING: <?xml version='1.0'?><stream:stream
xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' id='2662035953'
from='firthpark.tinsleyviaduct.com' version='1.0'
xml:lang='en'><stream:features><starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>SCRAM-SHA-1</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><c
xmlns='http://jabber.org/protocol/caps' hash='sha-1'
node='http://www.process-one.net/en/ejabberd/'
ver='TQ2JFyRoSa70h2G1bpgjzuXb2sU='/><register
xmlns='http://jabber.org/features/iq-register'/></stream:features>

JABBER: asterisk OUTGOING: <starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>

JABBER: asterisk INCOMING: <proceed
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>

JABBER: asterisk OUTGOING: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='jabber:client' to='firthpark.tinsleyviaduct.com'
version='1.0'>

JABBER: asterisk INCOMING: <?xml version='1.0'?><stream:stream
xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' id='1069044991'
from='firthpark.tinsleyviaduct.com' version='1.0'
xml:lang='en'>

JABBER: asterisk INCOMING: <stream:features><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>SCRAM-SHA-1</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><c
xmlns='http://jabber.org/protocol/caps' hash='sha-1'
node='http://www.process-one.net/en/ejabberd/'
ver='TQ2JFyRoSa70h2G1bpgjzuXb2sU='/><register
xmlns='http://jabber.org/features/iq-register'/></stream:features>

JABBER: asterisk OUTGOING: <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
mechanism='PLAIN'>AGFzdGVyaXNrAGNsaWQvaW0=</auth>

JABBER: asterisk INCOMING: <success
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'/>

JABBER: asterisk OUTGOING: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='jabber:client' to='firthpark.tinsleyviaduct.com'
version='1.0'>

JABBER: asterisk INCOMING: <?xml version='1.0'?><stream:stream
xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' id='3920780923'
from='firthpark.tinsleyviaduct.com' version='1.0'
xml:lang='en'>

JABBER: asterisk INCOMING: <stream:features><bind
xmlns='urn:ietf:params:xml:ns:xmpp-bind'/><session
xmlns='urn:ietf:params:xml:ns:xmpp-session'/><c
xmlns='http://jabber.org/protocol/caps' hash='sha-1'
node='http://www.process-one.net/en/ejabberd/'
ver='TQ2JFyRoSa70h2G1bpgjzuXb2sU='/><register
xmlns='http://jabber.org/features/iq-register'/></stream:features>

JABBER: asterisk OUTGOING: <iq type='set'
id='aaaaa'><bind
xmlns='urn:ietf:params:xml:ns:xmpp-bind'><resource>asterisk</resource></bind></iq>

JABBER: asterisk OUTGOING: <iq type='set'
id='auth'><session
xmlns='urn:ietf:params:xml:ns:xmpp-session'/></iq>

JABBER: asterisk INCOMING: <iq id='aaaaa'
type='result'><bind
xmlns='urn:ietf:params:xml:ns:xmpp-bind'><jid>asterisk at
firthpark.tinsleyviaduct.com/asterisk</jid></bind></iq>

JABBER: asterisk OUTGOING: <presence from='asterisk at
firthpark.tinsleyviaduct.com/asterisk'><status>asterisk
running</status><priority>0</priority><c
node='http://www.asterisk.org/xmpp/client/caps'
ver='asterisk-xmpp' ext='voice-v1'
xmlns='http://jabber.org/protocol/caps'/></presence>

JABBER: asterisk OUTGOING: <iq type='get'
id='roster'><query
xmlns='jabber:iq:roster'/></iq>

JABBER: asterisk INCOMING: <iq type='result'
id='auth'><session
xmlns='urn:ietf:params:xml:ns:xmpp-session'/></iq>

JABBER: asterisk INCOMING: <iq from='firthpark.tinsleyviaduct.com'
to='asterisk at firthpark.tinsleyviaduct.com/asterisk'
id='1072575207' type='get'><query
xmlns='http://jabber.org/protocol/disco#info'
node='http://www.asterisk.org/xmpp/client/caps#asterisk-xmpp'/></iq>

JABBER: asterisk OUTGOING: <iq from='asterisk at
firthpark.tinsleyviaduct.com/asterisk'
to='firthpark.tinsleyviaduct.com' type='result'
id='1072575207'><query
xmlns='http://jabber.org/protocol/disco#info'><identity
category='client' type='pc'
name='asterisk'/><feature
var='http://www.google.com/xmpp/protocol/voice/v1'/><feature
var='http://jabber.org/protocol/disco#info'/></query></iq>




-- 
Phil Reynolds
mail: phil-asterisk at tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

On 11/11/2012 06:35 AM, Phil Reynolds wrote:
> On Sat, 10 Nov 2012 18:08:58 +0000
> Phil Reynolds <phil-asterisk at tinsleyviaduct.com> wrote:
> 
<snip>

Asterisk should not crash.  If you are using a supported version of
Asterisk (1.8+), please file an issue on the issue tracker:

https://issues.asterisk.org/jira

Please read the issue reporting guidelines on the wiki here:

https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

Since your issue involves a crash, you will be asked to obtain a
backtrace.  This page details how to go about getting a valid backtrace
for your issue:

https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

Thanks!


-- 
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

On Mon, 12 Nov 2012 09:49:37 -0600
Matthew Jordan <mjordan at digium.com> wrote:
> On 11/11/2012 06:35 AM, Phil Reynolds wrote:
> > On Sat, 10 Nov 2012 18:08:58 +0000
> > Phil Reynolds <phil-asterisk at tinsleyviaduct.com> wrote:
> > 
> <snip>
> 
> Asterisk should not crash.  If you are using a supported version of
> Asterisk (1.8+), please file an issue on the issue tracker:
> 
> https://issues.asterisk.org/jira
It turns out to be a known issue:

https://issues.asterisk.org/jira/browse/ASTERISK-19532

... and can be fixed by applying the patch at:

https://issues.asterisk.org/jira/secure/attachment/43441/xmpp_no_crash_with_ejabberd.patch

I will file the details with Debian too...

-- 
Phil Reynolds
mail: phil-asterisk at tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

On 11/13/2012 12:11 AM, Phil Reynolds wrote:
[snip]
> It turns out to be a known issue:
>
> https://issues.asterisk.org/jira/browse/ASTERISK-19532
>
> ... and can be fixed by applying the patch at:
>
>
https://issues.asterisk.org/jira/secure/attachment/43441/xmpp_no_crash_with_ejabberd.patch
>
> I will file the details with Debian too...
Is it an omission that this fix has not been applied to the 11 tree? 
 From the looks of ASTERISK-19532 it seems that the fix has only been 
applied to 1.8 and 10.

Regards,
Patrick

----- Original Message -----
> From: "Patrick Lists" <asterisk-list at puzzled.xs4all.nl>
> To: asterisk-users at lists.digium.com
> Sent: Tuesday, November 13, 2012 4:35:54 AM
> Subject: Re: [asterisk-users] Asterisk crashing when trying to start a
Jabber session with ejabberd
> 
> On 11/13/2012 12:11 AM, Phil Reynolds wrote:
> [snip]
> > It turns out to be a known issue:
> >
> > https://issues.asterisk.org/jira/browse/ASTERISK-19532
> >
> > ... and can be fixed by applying the patch at:
> >
> >
https://issues.asterisk.org/jira/secure/attachment/43441/xmpp_no_crash_with_ejabberd.patch
> >
> > I will file the details with Debian too...
> 
> Is it an omission that this fix has not been applied to the 11 tree?
>  From the looks of ASTERISK-19532 it seems that the fix has only been
> applied to 1.8 and 10.
> 
If you click on the link for ASTERISK-19532, there is a tab in the Activity
section labeled "Subversion".  It shows that the patch was applied to
1.8, 10, 11 and trunk.

Michael
(elguero)

On 11/13/2012 07:05 PM, Michael L. Young wrote:
[snip]
>> Is it an omission that this fix has not been applied to the 11 tree?
>>   From the looks of ASTERISK-19532 it seems that the fix has only been
>> applied to 1.8 and 10.
>>
>
> If you click on the link for ASTERISK-19532, there is a tab in the Activity
section labeled "Subversion".  It shows that the patch was applied to
1.8, 10, 11 and trunk.
Thanks Michael. Missed that one. Good to know.

Regards,
Patrick