What's happening here?

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

 



I took the plunge and am trying to bring in version 2.0.1
It built OK and linked into my project with no problem.
Everything runs up to the point where the log reads:

*11:15:00.174    pjsua_acc.c  Adding account: id=
sip:remote_12027 at rmt1-srq.star2star.net*

*
*

*It crashes with a memory violation in psjua_acc_add:*

*
*

*
*

*The code is the same as that which worked in version 1.10:*

**

*    static pjsua_acc_config xcfg;*
*

    pjsua_acc_config_default(&xcfg);



    //Setting the registration timeout value

    xcfg.reg_timeout = 600;  //backgrounding reccommends 600 seconds not
300 as is the default

    xcfg.id = pj_str((char *)[pjID UTF8String]);

    xcfg.reg_uri = pj_str((char *)[pjRegistrar UTF8String]);

    xcfg.cred_count = 1;

    xcfg.cred_info[0].realm = pj_str((char *)[sipRealm UTF8String]);

    xcfg.cred_info[0].scheme = pj_str("digest");

    xcfg.cred_info[0].username = pj_str((char *)[pjUsername UTF8String]);

    xcfg.cred_info[0].data_type = PJSIP_CRED_DATA_PLAIN_PASSWD;

    xcfg.cred_info[0].data = pj_str((char *)[pjPassword UTF8String]);



    pjsua_acc_id p_acc_id;

    pj_status_t status = pjsua_acc_add(&xcfg, PJ_TRUE, &p_acc_id);

Blows up here with EXC_BAD_ACCESS (not very useful but its trying to do a
memmove()

0x33b4ef48:  beq    0x33b4ef60                ; memmove$VARIANT$CortexA8 +
576

0x33b4ef4a:  ldrb   r3, [r1], #1

0x33b4ef4e:  sub.w  r2, r2, #1

Platform is iPhone 4

*

Could you please tell me why the problem is?


On Fri, Jul 13, 2012 at 8:53 AM, Benny Prijono <bennylp at teluu.com> wrote:

> On Mon, Jul 9, 2012 at 7:58 PM, Tom Merriewether <
> tmerriewether at star2star.com> wrote:
>
>> I am writing an iPhone application. We are using a TCP proxy for SIP so
>> that we can use iOS voip socket handling.
>> Everything seems to be going well until the io_select activity starts.
>>  Somehow this is triggering too many background wake events and killing the
>> application.
>> So my question is:  what exactly is going on when the following occurs?
>>
>>
>
> Haven't we discussed this in
> http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2012-June/014836.html
> ?
>
> The "UDP has been replaced.." is triggered by the wake up, not the other
> way around. You need to find what is causing the wake up, and it's
> described in the ticket that I mentioned there.
>
> Cheers
>  Benny
>
>
> PLOG --> 2012-07-06 17:49:01.375 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.374     ioq_select  UDP has been replaced successfully!
>>
>> PLOG --> 2012-07-06 17:49:01.375 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.375     ioq_select  Attempting to replace UDP socket 41
>>
>> PLOG --> 2012-07-06 17:49:01.376 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.376     ioq_select  UDP has been replaced successfully!
>>
>> PLOG --> 2012-07-06 17:49:01.377 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.376     ioq_select  Attempting to replace UDP socket 42
>>
>> PLOG --> 2012-07-06 17:49:01.377 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.377     ioq_select  UDP has been replaced successfully!
>>
>> PLOG --> 2012-07-06 17:49:01.378 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.377     ioq_select  Attempting to replace UDP socket 43
>>
>> PLOG --> 2012-07-06 17:49:01.379 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.379     ioq_select  UDP has been replaced successfully!
>>
>> PLOG --> 2012-07-06 17:49:01.379 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.379     ioq_select  Attempting to replace UDP socket 44
>>
>> PLOG --> 2012-07-06 17:49:01.381 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.381     ioq_select  UDP has been replaced successfully!
>>
>> PLOG --> 2012-07-06 17:49:01.381 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.381     ioq_select  Attempting to replace UDP socket 45
>>
>> PLOG --> 2012-07-06 17:49:01.382 Star2Star[977:750f] SIP PJSIP message:
>>  17:49:01.382     ioq_select  UDP has been replaced successfully!
>>
>> Somehow at the end of this sequence the application is killed with too
>> many background wake ups.  The crux of the matter is that this is not due
>> to inbound traffic on the SIP socket as I have verified that the SIP server
>> is not generating traffic to the phone at this time.  So what's up and how
>> do I fix this?
>>
>>
>>
>> --
>> Thomas Merriewether
>> Star2Star Communications
>>
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>


-- 
Thomas Merriewether
Star2Star Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120713/0a800819/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux