search for: handovers

Hello guys, I'm wondering what is required and involved in order to provide a wifi/GSM handover to customers. After googling I haven't found any product/vendor. Do you have an idea ? Thanks in advance Patrick

Hi, Do you if a DECT-GAP (or DECT-CAP) compliant handset MUST or MAY support roaming and handover and are these functions transparent for handset (then, these functions are implemented in DECT base stations) ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080110/4254f602/attachment.htm

Hi, I'm trying to configure two APs with a Wifi phone to allow fast handover. I would like to know how to configure them. Should I use the same ESSID and Channel on both ? Suggestions about a good wifi sniffer ??? Is Commview the best option ? Thanks, Luis A P Barbosa -------------- next part -------------- An HTML attachment was scrubbed... URL:

Howdy, y'all I just got a GTX460 and I'm having a bit of trouble getting it running. In particular, when I modprobe "nouveau," the display goes black (but doesn't enter power saving, so there's a signal of some sort). After doing some searching, I found http://nouveau.freedesktop.org/wiki/KernelModeSetting If I unbind the nouveaufb driver, the console starts

Hi, I'm working on a Wifi VoIP project specification. It will have almost 8 APs and 20-30 wifi phones. And after some research, I still having some questions ... 1) Are Managed Access Points (and switch controllers) really important to implement good wifi woip (w/ low latency and acceptable handover time) ? 2) What is the difference between (3com WX1200 + 3com AP 3750) and (DES-1228P +

Hi, Line 762 of efi/main.c (git firmware branch) should be changed to if (hdr->version < 0x20b) { Without this change syslinux efi64 gives out "handover protocol unimplemented error" and fails to boot. With this change syslinux boots the kernels fine (tested with 3.6.9 and 3.7rc6 kernels). Please fix this. Thanks in advance. Regards. Keshav

If I understand correctly, a HVM domain''s network adapter gets a tapX device created for it in Dom0 for qemu to talk to, and a vifY.Z device for the PV drivers (which probably aren''t there) to talk to. How can I stop the qemu code creating the virtual Realtek driver? What will happen if I try and use PV and Realtek drivers at the same time? Will the Realtek driver just talk to

Actually your Syslinux config is less relevant than the kernel config file. Indeed Syslinux infers the method to use from the kernel image itself. I assume the .config is public. I will take a look as soon as I can Thomas Le 04/08/2015 14:09, intrigeri via Syslinux a ?crit : > Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : >> Are you using EFI Handover Protocol? >

On Mon, Nov 23, 2015 at 3:06 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > It saddens (me) > C'mon; really? As you asked. -- -Gene

Hello, I have two FXS port on my TDM card. channel 4 is attached with a telco line that I use frequently. And channel 3 have another telco line. but I dont publish that number to my friends. If I receive a call through channel 4, how can I handover that call to channel 3 ..so that I can keep channel 4 open for incoming call. Thanks,

> On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux > <syslinux at zytor.com> wrote: > > Hello, > > > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > > After boot linux sees only 2.5G of RAM while system has 32G installed. > > Why not use a 64-bit kernel with such a large machine? > > Do you have

1) At the end of main, there's attempt to free cur_part->record, which rarely comes from malloc. Only valid case is if gpt handover was performed and chaining was not successful (cur_part->record is overwritten with gpt specifc handover record). Freeing the handover area has been adjusted. 2) If our current iterator is ebr, parent wouldn't be freed at the end of main. Added generic

hello all, is there somewhere a comprehensive documentation for the (C) functions used for embedded R? (e.g. the functions which are used in the directory \tests\Embedding in the R source) or Are there somewhere many more examples for this? (especially handover of data between C and embedded R) thanks, Alex --

> On Mon, Nov 23, 2015 at 3:06 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > It saddens (me) > > > C'mon; really? > > As you asked. > > -- > -Gene I appreciate the replies. Hopefully someone might be able to come up with some contribution / answer. The Syslinux code has already received at some point some patches regarding the EFI

Hello Olivier Ive been testing the E61 phone for some days now, and we need to have an inhouse asterisk server, connected to our main asterisk server, to get it to work. That means, that you cant just walk down to your local airport, and use the IP part of the phone on their network. You have to have a non nat local server, to get it to run. Other than that, the phone can accept calls both

I just released 6.02-pre2 which includes support for booting 32-bit kernels from efi64. I know a number of people wanted this feature, so hopefully it will be tested in various environments. One thing to note is that it is not possible to boot a 32-bit kernel from efi64 via the EFI handover protocol (or from firmware via the EFI boot stub), but the kernel loader in Syslinux is smart enough to

This patch introduces extra functionality to chain.c, mainly with reference to BPB adjustments, but not only that. It expects 3 small patches I sent earlier (they are included for easy reference, patches 1-3/4). The changes introduced are: 1) file and boot sector use separate options to control load address and jump address (if applicable). Options are as described below: *

Hi > Maybe I'm missing something, but this has been working flawlessly for > us in Tails so far. What exactly fails? Are you using EFI Handover Protocol? It might explain the difference Thomas

Hello, I need to setup this configuration: - asterisk as IVR; - dect phones. So basically I need a "standard set" of features: - each dect phone has its extension so I can call it directly; - handover of a call with "R" key; - if a call is not replied by someone ring all phones. I have little budget. I can choose to buy a fritz!box or a gigasect dect/ip base station. Which

I have a custom built system based on LFS 6.6 with xen 4.1.0 & linux 2.6.39 built from source. The system boots correctly on one system (after a problem with the USB disk has been worked around), however when I try to boot the same system on another machine the screen corrupts shortly after handover from the bootloader. This happens on 2 out of the 3 machines I have tried it on. I was