search for: callqueu

> -- Started music on hold, class 'default', on > SIP/193.111.200.67-0815c790 > -- outgoing agentcall, to agent '1001', on 'Local/201@sip-0add,1' > -- Called Agent/1001 > -- Executing Dial("Local/201@sip-0add,2", "SIP/101|20|tr") in new > stack > -- Called 101 > -- Agent/1001 is ringing > --

Hi, I am using * to guide my callers throught my company's support menu. But I have problem when the caller has a "pulse dial" telephony. Could * detect digits dialed on pulse telephones? Daniel

Does anyone have some decent Nagios scripts out there that do more than monitor the proc itself? Rather than reinvite the wheel, figured I'd ask. I already saw the one on the wiki. Matt

...mmediate=no > group = 1 > channel => 1-15 > channel => 17-31 > /etc/asterisk/extensions.conf relevant part > /etc/asterisk/extensions.conf > [dolaz] > exten => s,1,NoOp(${CALLERIDNUM}) > exten => s,2,Wait(1) > exten => s,3,Answer > exten => s,4,Queue(callqueue|thH) ; here are logged agents waiting for > calls > exten => s,5,Hangup /etc/init.d/zaptel restart gave me this : > Loading zaptel framework: done. > Waiting for zap to come online...OK > Loading zaptel hardware modules: wcte11xp. > Running ztcfg: done. > Even when...

We're moving a somewhat complicated call center over to an Asterisk system, and I'm looking for documentation on queue/agent configuration. So far I haven't found anything on the Digium or Asterisk websites, and I was hoping that someone could point me in the right direction. Thanks, Devon

...ext->queuePairArray, + tempHandle); + } + tempHandle = + vmci_handle_arr_get_entry(context->queuePairArray, 0); + } + + /* + * It is fine to destroy this without locking the callQueue, as + * this is the only thread having a reference to the context. + */ list_for_each_safe(curr, next, &context->datagramQueue) { + dqEntry = + list_entry(curr, struct vmci_datagram_queue_entry, listItem); + list_del(curr);...

...ext->queuePairArray, + tempHandle); + } + tempHandle = + vmci_handle_arr_get_entry(context->queuePairArray, 0); + } + + /* + * It is fine to destroy this without locking the callQueue, as + * this is the only thread having a reference to the context. + */ list_for_each_safe(curr, next, &context->datagramQueue) { + dqEntry = + list_entry(curr, struct vmci_datagram_queue_entry, listItem); + list_del(curr);...

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with