search for: betwwen

How can I made a 3-way conference betwwen IAX channels? My current version is: 1.4.21.1 Thanx, Daniel Arohuanca Lagos +51 1 3594122 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080722/f9612f97/attachment.htm

Hi all, Information on this topic seems a little scarce, so I thought I'd try the list.... Apart from the the coolness factor can anyone explain to me in what situation one would use TDMoE rather than IAX for communication betwwen 2 Asterisk servers?

Hi all CentOS users, How can i determine connection time during the package walking between two nodes ? But not in my network ! only any two network nodes in world ? For example: Get report time value betwwen www.abc.com and www.cde.com Thanks for all advice. -- Iyi calismalar.Basarilar... Semih Gokalp Istanbul/Turkiye

Thanks. I think our problem ca be similar. Have you tried to call from analog phone #1 to another analog phone #2? It works. But when you try to call vice versa from #2 to #1 it does not work. When you restart asterisk it works again - but only one direction. -David ________________________________ From: asterisk-users-bounces@lists.digium.com

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.