[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] crashing in belle-sip linphone iOS

From: Jehan Monnier
Subject: Re: [Linphone-developers] crashing in belle-sip linphone iOS
Date: Wed, 2 Apr 2014 20:53:00 +0200

Hi Cam,

Nothing new in your finding. MD->username is null probably because the proxy_config is wrong.
Since we engineer out eXosip, we performed hundreds of commits.  So far, I don't see any evidence spotting belle-sip.


Le 2 avr. 2014 à 18:32, Cameron Ambrose <address@hidden> a écrit :

I logged the attributes that are being copied in the linphone_call_make_local_media_description routine and found the username is null.

I will trap for this, but any further ideas on why this would be getting nulled? This was never a problem until the codebase moved from libeXosip to belle-sip so I still wonder if there's something there.


Apr  2 10:09:45  RSP[134] <Warning>: incoming call ringing for 1 seconds
Apr  2 10:09:45  RSP[134] <Warning>: 2 calls
Apr  2 10:09:45  RSP[134] <Warning>: Pausing main call 0x1a95e00
Apr  2 10:09:45  RSP[134] <Warning>: MD->Addr :
Apr  2 10:09:45  RSP[134] <Warning>: MD->Username : (null)
Apr  2 10:09:45  RSP[134] <Warning>: Subject : (null)
Apr  2 10:09:46  ReportCrash[158] <Notice>: Formulating crash report for process RSP[134]

On 2014-03-30, at 1:19 PM, Cameron Ambrose <address@hidden> wrote:

I really don't touch the call once it's established. How can I best check the call's proxyconfig before the 2nd call is answered?



I don't see anything wrong from the parser standpoint.
Maybe your app has destroyed the proxyconfig associated to this call.


Linphone-developers mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]