[Home]

Summary:ASTERISK-07325: Segfault with Outbound Jingle Calls
Reporter:lmcdowel (lmcdowel)Labels:
Date Opened:2006-07-11 23:12:59Date Closed:2006-07-23 11:46:41
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Channels/chan_jingle
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Asterisk segfaults when making an outbound Jingle call when there are no buddies for the connection defined in jabber.conf.

The segfault occurs at line 677 of channels/chan_jingle.c.




****** ADDITIONAL INFORMATION ******

Sample configs:

extensions.conf:
exten => 1234,1,Dial(Jingle/jabtest/foo@foo.com)

jabber.conf:
[jabtest]
type=client
serverhost=im.bar.org
username=jabtest@bar.org/1234
secret=testjab
port=5222
usetls=yes
usesasl=yes
buddy=foo@foo.com

jingle.conf:
[footest]
username=foo@foo.com
disallow=all
allow=ulaw
context=default
connection=jabtest
Comments:By: Serge Vecher (serge-v) 2006-07-12 08:31:56

please review BUG GUIDELINES before posting bugs. All issues with 'crash' severity must be accompanied by a backtrace of Asterisk build with 'make dont-optimize'.

By: Matt O'Gorman (mogorman) 2006-07-13 11:31:52

okay im not saying this isnt a bug, but i have been trying like hell to replicate this bug and have been unable to can you please follow bug guidelines or even more info it would be appreciated.

By: lmcdowel (lmcdowel) 2006-07-13 12:33:30

I haven't had time to do the back trace yet. I'll complete it when I get a chance.

It may however have something to do with my instance of Asterisk not using the server side roster. I think your roster would have to be completely empty to trigger the crash.

Debug:
jabber reload
 == Parsing '/etc/asterisk/jabber.conf': Found
var->value: client
var->value: im.ntelos.net
var->value: testtest@ntelos.net/asterisk
var->value: *****
var->value: 5222
var->value: yes
USETLS = 1
var->value: yes
USESASL = 1

JABBER: testtest OUTGOING: <presence><status>im available</status><c node='http://www.asterisk.org/xmpp/client/caps' ver='asterisk-xmpp' ext='voice-v1' xmlns='http://jabber.org/protocol/caps'/></presence>

JABBER: testtest OUTGOING: <iq type='get' id='roster'><query xmlns='jabber:iq:roster'/></iq>
testserver*CLI>
JABBER: testtest INCOMING: <iq xmlns='jabber:client' id='roster' type='result'><query xmlns='jabber:iq:roster'><item subscription='both' jid='test2@ntelos.net'/><item subscription='both' jid='test2@gmail.com'/></query></iq>
testserver*CLI>
JABBER: testtest INCOMING: <presence xmlns='jabber:client' to='testtest@ntelos.net/asterisk' from='test2@ntelos.net/Gaim' type='unavailable'><status>Logged out</status></presence>
Jul 13 13:18:38 WARNING[23115]: res_jabber.c:1025 aji_handle_presence: Got presence packet from test2@ntelos.net, somone not in our roster!!!!
testserver*CLI>
JABBER: testtest INCOMING: <presence xmlns='jabber:client' to='testtest@ntelos.net/asterisk' from='test2@ntelos.net/Gaim'/>
Jul 13 13:18:43 WARNING[23115]: res_jabber.c:1025 aji_handle_presence: Got presence packet from test2@ntelos.net, somone not in our roster!!!!

By: Matt O'Gorman (mogorman) 2006-07-13 13:44:14

i have tested this with a user with out buddys, using server side roster and with out, it refuses to cause me any issues. please jabber me at mogorman@digium.com if you wish to discuss this further, but with recent code this is just not possible to break

By: lmcdowel (lmcdowel) 2006-07-22 18:43:32

This ticket can be closed.

I didn't see that new code wasn't going into the asterisk-xmpp branch anymore.

Thanks,
Landon

By: Clod Patry (junky) 2006-07-23 11:46:40

close like reporter asked.