Re: [asterisk-dev] Deadlock in pthread_exit due to lazy binding with libgcc

Here is the difference in loading time (on Intel i5 machine): The default (with lazy linking): 1.422 seconds With non-lazy linking: 1.852 seconds On Fri, Jul 17, 2015 at 6:04 PM, Mark Michelson wrote: > On 07/15/2015 08:41 AM, Yousf Ateya wrote: > > Dear, > > I started to

[asterisk-dev] Deadlock in pthread_exit due to lazy binding with libgcc

57a523 in pbx_thread (data=data@entry=0x2acf0c171588) at pbx.c:6773 #14 0x005d734a in dummy_start (data=) at utils.c:1237 #15 0x2ace66626182 in start_thread (arg=0x2acfc684b700) at pthread_create.c:312 #16 0x2ace6708747d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- You

[asterisk-dev] [RTP] Detecting that a packet is SRTP

In res_rtp_asterisk.c, to detect that a packet is SRTP (not RTP), this check is done (link to gitweb ): if ((*in >= 20) && (*in <= 64)) {

[asterisk-dev] IAX different reentrant locks depth in the same function

other components)? -- Yousf Ateya, StarkBits www.starkbits.com -- This e-mail message is intended only for the use of the intended recipient(s). The information contained therein may be confidential or privileged, and its disclosure or reproduction is strictly prohibited. If you are not the i

[asterisk-dev] [IAX] ping time calculations

packet retry, not because the network is slow. Is it better to calculate ping time = pong_receiption_time - last_poke_send_time? So we get **actual** network ping time instead of network_ping_time + packet_retry_time. -- Yousf Ateya, -- This e-mail message is intended only for the use of the

[asterisk-dev] [IAX] Sending VNAK for out of order fr->iseqno

terisk.org/jira/browse/ASTERISK-24873?focusedCommentId=225569&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-225569 Is is better that the peer sends VNAK when it receives out-of-order fr->inseqno? -- Yousf Ateya, -- This e-mail message is intended only f

[asterisk-dev] [IAX] Need for LAGRQ and LAGRP

nality (calculate lag) can be achieved using PING/PONG. Is it left for RFC-compatability only? Or there something I didn't notice? -- Yousf Ateya, -- This e-mail message is intended only for the use of the intended recipient(s). The information contained therein may be confidential or privileg

Re: [asterisk-dev] [IAX] Separate QoS settings for signaling, voice and video packets

alls. NOTE: code is not multi-threading protected and calling getsockopt/setsockopt shall be removed in production code. Is there any measurements to ensure that this doesn't break something else? (increase CPU load insanely, doesn't scale up after x connections, ...) I have a runn

[asterisk-dev] [IAX] Separate QoS settings for signaling, voice and video packets

chance than voice packets. Is this a useful feature? Will it make any difference in IAX connection quality? -- Yousf Ateya -- This e-mail message is intended only for the use of the intended recipient(s). The information contained therein may be confidential or privileged, and its disclos

Re: [asterisk-dev] How to catch the source of a deadlock?

Asterisk loaded the default timing modules (timerfd and pthreaf), but only res_timing_timerfd is used. On Tue, Jan 27, 2015 at 7:45 PM, Matthew Jordan wrote: > On Tue, Jan 27, 2015 at 11:04 AM, Yousf Ateya > wrote: > > > > Yes, and I supplied the debug logs in the issue ASTE

[asterisk-dev] IAX: why iax2_poke_noanswer timeout set to DEFAULT_MAXMS * 2 instead peer->pokefreqok?

instead of *peer->pokefreqok *? I think it is better to be: - client1 sends POKE, wait for PONG. - client2 sends PONG. - If PONG packet is dropped retry it couple of times, until giving up. -- Yousf Ateya, StarkBits www.starkbits.com -- This e-mail message is intended only for the use of t

Re: [asterisk-dev] How to catch the source of a deadlock?

ot any way to catch the cause of dead locks. On Tue, Jan 27, 2015 at 3:43 PM, Russell Bryant wrote: > On Tue, Jan 27, 2015 at 7:01 AM, Yousf Ateya > wrote: > >> Dear, >> >> While investigating iax2 bug ASTERISK-24478 >> <https://issues.asterisk.org/jira/browse/A

[asterisk-dev] How to catch the source of a deadlock?

Dear, While investigating iax2 bug ASTERISK-24478 ; I found some dead locks. Which happens very often in my setup. I tried to debug