Monitoração de Portas IVR

Ola Pessoal,
Meu Cliente tem uma solução de CUCM e UCCX, versões 8.6.2 e 8.0.2 respectivamente. Gostariamos de saber se o CUCMS é capaz de monitorar a utilização das Portas IVR. Abri um TAC e fui informado que somente a partir da versão 9.x do UCCX é isso é possivel, através do CUIC. Tenho acesso ao CUCMS, mas, como não tenho familiaridade com a Plataforma não consegui encontrar nada neste sentido.
Obrigado,
Wilson

Oi Wilson
TAC é mais correta. Não há construído em forma, padrão, apoiado por você para monitorar a atividade portuária.
No entanto, você pode fazer uma de duas coisas, que eu não recomendo, mas para o bem do argumento, são eles:
1. Use Indicadores luminosos de ocupado para monitorar o CTI do Porto DN
2. Use a terceiros integração CTI, onde você associar suas portas CTI para ele, e ele solicita o estado da linha e, em seguida, exibe os resultados em uma página web ou tela do cliente de espessura.
Eu entendo que Cuic é um grande reforço para todos nós, no entanto, eu não usei, e não pode falar com a sua capacidade de executar uma visão em tempo real dos Portos CTI.
Tenha um bom dia,
Anthony Holloway
Por favor, use as classificações de estrelas para ajudar a impulsionar um grande conteúdo para o topo das buscas.
Translated with Google Translate

Similar Messages

How to connect an external hard drive and monitor a single port thuderbolt

how to connect an external hard drive and monitor a single port thuderbolt

Yu connect the HDD to your Mac and then the monitor to the HDD.
The HDD should have TWO T-Bird ports on the enclosure.
Its called daisy chaining and up to five devices can be connected in this fashion.

Can the last link in a thunderbolt daisy-chain be a non-thunderbolt monitor using miniDisplay port?

Can the last link in a thunderbolt daisy-chain be a non-thunderbolt monitor, using miniDisplay port?
For example, Mac mini <--> external SSD <--> apple cinema display 30" (using miniDisplay port adaptor plugged into the SSD's second thunderbolt port)

TechnoMax wrote:
for instance STAE122 or STAE 127?
FWIW, STAE129 is the current version TB adapter
that is self powered and has TB daisy chain port.
STAE122 and STAE127 are older versions and
not the current model, though there may be stock of
these around. As to whether this will solve your issue,
I don't know.
Can I trick the Mac under Bootcamp as OS to use HDMI for the monitor? Dell officially says that the monitor can only accept 1900x1080 over HDMI, but some have fiddled wth different computers with custom settings that worked with some Monitors but mostly under Linux and to Dell 2711.
The MacMini HDMI port is hardware limited to 1980x1200.

Will an X220 drive a Dell UP2414Q 4K 3840 x 2160 Monitor via Display Port?

I've not been able to find any information about this on the web and there is definitely some confusion about DisplayPort versions - could some one answer the question will an X220 drive a Dell UP2414Q 4K IPS Monitor at it's native resolution of 3840 x 2160 Monitor via Display Port? Would that be at 30Hz rather than 60Hz?
Many thanks, Mark.
Solved!
Go to Solution.

The X220 will drive the Dell UP2414Q 4K resolution through Displayport. I have tested this on the Pro2840m LCD which has the same resolution. But only on 30 hz refresh rate.
The X220 with the Series 3 Workstation Dock will drive 2 of the Pro2840m through 2 separate displayport.
The X201 will also drive this 4K resolution, as long as the LCD's 4K can accept Displayport 1.1 standard (on the 1.2 standard, the LCD will stay blank).
https://www.flickr.com/photos/lead_org/14671257827/in/set-72157645860787090
the above image confirms the 4K resolution and my X220 driving that resolution @ 30 hz.
For 60 hz refresh rate on the 4K resolution with integrated Intel GPU, you need Haswell CPU with the HD5000 graphics card, anything below that will only drive the 4K resolution at 30 Hz.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Need to setup monitoring aon multiple ports for IDS

I have a cisco 3845. I need to need to setup monitoring aon multiple ports for IDS on 2 ports. How do I do this.
Also,
Is there a way to make ports on the switch portion act like hubs.
Thanks

I assume that you are referring to the Ethernet Switch Module in the 3845. If so it should support SPAN. Here is a SPAN configurations guide:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122z/122zj15/fz1636nm.htm#1820129

Monitor a UDP port

Hi,
I could find a solution for my problem. I need to monitor a UDP port.
For the TCP ports i'm using MP template TCP Port, but for the UDP i don't find any tool.
My question is. It's possible to monitor UPD ports in SCOM 2012 R2? If yes, how?
Thank you,
Rui

Hi Rui,
I have found a possibility to do this. Hope you understand this and it is helpful. This is a two step process but guess will definitely server the purpose.
Scope: We will be running a tool which will monitor a port (TCP or UDP) for a specific host / IP and will throw a log file.
SCOM will monitor the log file and will throw a alert if the log file contains the string NOT LISTENING (Port not working or unable to open the port) which the program will create the log with the results.
First download the program named: PortQry Command Line Port Scanner Version 2.0 from microsoft using the below link. It is a command line tool.
http://www.microsoft.com/en-in/download/details.aspx?id=17148
Run it using by making a batch file or powershell script using task scheduler as per your time requirement (Every 5 min or 1Hr).
Use this command to monitor a ip / hostname and its port with TCP or UDP.
I have pasted the command file of the program in C:\Port_checker directory so i am using the below syntax
C:\Port_checker\PortQry.exe -N 192.168.1.1 -e 5723 -p UDP -l C:\Port_checker\Result.log /y
-N = Hostname / FQDN of agent or Ip address
-E = Port # what you want to monitor
-P = Protocol (TCP or UDP)
-L = Generate log on the following location and name
/Y = To replace the existing log file name to fresh one without prompt.
The result in the log file will be as follows:
============================
For successful port open:
PortQry Version 2.0 Log File
System Date: Tue Oct 07 09:42:32 2014
Command run:
C:\PortQryV2\PortQry.exe -N 192.168.1.1 -e 5723 -p UDP -l C:\Portqryv2\Result.log /y
Local computer name:
192.168.1.2
Querying target system called:
192.168.1.1
Attempting to resolve name to IP address...
Name resolved to 192.168.1.1
querying...
UDP port 5723 (unknown service): LISTENING
========= end of log file =========
PortQry developed by Tim Rains
For failure port open:
PortQry Version 2.0 Log File
System Date: Tue Oct 07 09:42:32 2014
Command run:
C:\PortQryV2\PortQry.exe -N 192.168.1.1 -e 5723 -p UDP -l C:\Portqryv2\Result.log /y
Local computer name:
192.168.1.2
Querying target system called:
192.168.1.1
Attempting to resolve name to IP address...
Name resolved to 192.168.1.1
querying...
UDP port 5723 (unknown service): NOT LISTENING
========= end of log file =========
PortQry developed by Tim Rains
Now as per the above results NOT LISTENING Port is blocked or is not opened and LISTENING
means working or port is opened.
So now using SCOM you will monitor the log file Result.log
in the location C:\Port_checker\ saying if NOT LISTENING
comes in the log file throw me a alert in SCOM consle or via email.
To configure that alert you need to create a Generic text log alerting Rule which will throw a alert if any thing added in that log which is not to be added and if it is added like NOT LISTENING
then it will throw a alert.
Refer this link on how to open a Generic text log alerting Rule.
http://blogs.technet.com/b/kevinholman/archive/2009/06/20/using-a-generic-text-log-rule-to-monitor-an-ascii-text-file-even-when-the-file-is-a-unc-path.aspx
Gautam.75801

Error 1722: Failed to add port monitor HP Discovery Port Monitor (HP Officejet Pro 8600).

Error 1722: Failed to add port monitor HP Discovery Port Monitor (HP Officejet Pro 8600). Plus (64 bit.)
Is there a fix or do I go buy a different brand of printer?

Thanks, X-23, I'll try it when I get home from work!
Jim Stinson

OVM 3:Monitor a trunk port/create a dedicated NIC

Hi,
I need to monitor a trunk port from within a guest. Does OVM offer the ability to tie a network card directly to a guest? I don't want other guests to have access to the same nic at the same time.

Understood.
I have now setup a simple network with bonds/ports only and attached that to the NIC that is connected to the SPAN port on my Cisco switch. This SPAN port mirrors a trunk port and thus carries of course all the VLANs.
Next, I have setup a guest running ntop and that has a vnic attached to it, that is connected to the new network. Now, when I run tcpdump against that port I am only seeing broadcast and multicast traffic. Is there a way to capture the whole network traffic that is mirrored to the SPAN port?
I have also taken a look at the network with ports and vans, but that doesn't seem to fit either.

Monitor or Span port Vulnerablility

Is the CISCO IDS/IPS device connecting to Monitor or SPAN port Vulnerable? Is there a document which I can refer to ?

It's very unlikely, but not impossible. Snort's had a few and the general concept is applicable to any IDS. If you suck in data off the network and process it, there's the potential for vulnerabilities. If you're worried about it, put the management interface in a management dmz.
http://www.infoworld.com/article/03/03/04/HNsnort_1.html

Can I 'monitor session' trunk ports to a Cisco IDS?

I ran across an existing config that has two trunk ports on a 3560 being port monitored to another port which is plugged in to a port on an ids 4515. Will the IDS be able to interpret that trunk traffic? The customer is complaining that they aren't able to see events on a local network (VLAN 1) and this is suppose to be the port they get that traffic from.
Not sure why they chose to monitor trunk ports and I'm not sure it's even possible. I want to change the monitored port to some other local VLAN port that makes sense.
Here are the existing lines:
interface G0/47
switchport turn encap dot1q
switchport mode trunk
interface G0/48
switchport turn encap dot1q
switchport mode trunk
monitor session 2 source interface Gi0/47 - 48
monitor session 2 destination interface Gi0/20
...port 20 goes to the ids.

There are 3 modes of sensing supported on the sensors: promiscuous, inline interface pair, and inline vlan pair.
Each mode interacts with vlan headers slightly differently.
Promiscuous:
A promiscuous sensor is fully capable of analyzing 802.1q trunk packets. The vlan will also be reported in any alerts generated.
The trick when monitoring using a trunk is to ensure the span (or vacl capture) configuration is correct on the switch to get the packets you are expecting.
Many types of switches have special caveats when a trunk is a source or destination port in the span.
We also even support Vlan Group subinterfaces on the promiscuous interface.
This allows sets of vlans on the same monitoring port to be monitored by different virtual sensors.
So you could take vlans 1-10 and monitor with vs0, and then take vlans 11-20 and monitor with vs1, etc....
However, to use this feature the switch must be very consistent in how packets are sent to the sensor. When monitoring a connection the sensor needs to see both client and server traffic. And when using Vlan Groups the sensor needs to see the client and server traffic ON THE SAME VLAN. It is this on the same vlan requirement that is not always possible with some span configurations when the switch itself is routing between vlans. Most switches are deployed with routing between vlans by the switch, and so in many cases you won't see the client and server traffic on the same vlans. This is very switch code dependant so you would need to do some research on your specific switch.
Inline Interface Pair:
With an inline interface you are pairing 2 physical interfaces together. A common deployment is to place the inline interface pair in the middle of an existing 802.1q trunk port. Interface 1 would be plugged into the switch, and interface 2 plugged into the other switch or other type of device (like router or firewall).
In this setup the sensor is fully capable of monitoring these packets with 802.1q headers.
However, there is something to keep in mind in these deployments. Often that other device (router, firewall, or switch) will route packets between vlans. So a packet going through the sensor on vlan 10 could be routed right back through the sensor again on vlan 20. Seeing the same packet again can cause TCP tracking confusion on the sensor (especially when the other device is doing small modifications to the packet like sequence number randomization).
To address these we have 2 features.
On InLine Interface Pairs we have the same Vlan Group feature as I discussed above in Promiscuous mode. (Do not confuse Vlan Groups with InLine Vlan Pairs discussed later in this response).
So with Vlan Groups you could separate the vlans across virtual sensors. So if the packet gets routed back into the sensor you could configure it so that packet gets monitored by a separate virtual sensor and it will prevent the sensor confusion with state tracking.
However, there will still be some situations where the packet may still need to cross the same virtual sensor twice. For this deployment scenario we have a configuration setting where you can tell the sensor to track tcp sessions uniquely per vlan. So long as the return packet is on a different vlan this should prevent the tcp tracking confusion. BUT there is a bug this code right now. It should be fixed in an upcoming service pack. The workaround is to go ahead and create a unique Vlan Group for each vlan (one vlan per group instead of multiple vlans in a group), and assign all of the Vlan Groups to the virtual sensor(s).
And then you InLine Vlan Pairs:
With InLine Vlan Pairs the monitoring interface Must be an 802.1q trunk port.
Instead taking packets in one interface and passing to the next interface, the sensor actually takes packets in on one vlan and then sends it back on the other vlan of the pair on the same interface. It does this by modifying the vlan number in the 802.1q header.

How do I monitor two service ports in a server ?

The web service is alive when tcp port 80 and 8080 are both alive. How do I use script to monitor both ports at the same time ? Any example for this case ? Thanks.

Here is a script I have written for this - you can test as many ports as you want on one server with this script.
To run just add under the service as:
service test
keepalive type script socket-test.txt "172.17.10.10 8080 80 443"
Hope this helps,
Regards,
Darren.
-------------- Begin Script -----------------------------
!======================================================
! Filename: socket-test.txt
! Parameters: Host port1 port2 port3
! This script does the following:
! Connects to a remote host on a specified tcp sockets,
! waits for X seconds and then disconnects.
! Failure Upon:
! Not establishing a connection with the host. If one connection
! fails, the script fails.
! Usage to run manually:
! script play socket-test.txt
! Useage to run automaticlly:
! cmd-sched
! cmd-sched record 1 * * * * * "script play socket-test.txt"
! Written by Darren Page, Dimension Data
!======================================================
!no echo
! Make sure the user has a qualified number of arguments
if ${ARGS}[#] "LT" "2"
echo "Usage: socket-test.txt \'host socket1 socket2 socket3 ...'"
exit script 1
endbranch
set host "${ARGS}[1]"
! get the first tcp port ready from the ARGS array
var-shift ARGS
while ${ARGS}[#] "GT" "0"
set EXIT_MSG "Connect: Failed to connect to ${host}"
! Connect to remote host on specified port
socket connect host ${host} port ${ARGS}[1] tcp 2000
! Wait one second
pause 1
! disconnect from remote host with a TCP FIN
socket disconnect ${SOCKET} graceful
! Wait one second
pause 1
!get the next port from the array
var-shift ARGS
no set EXIT_MSG
! Demarcation of the end of the loop
endbranch
exit script 0
-------------End of Script ------------------

Macbook Pro 15" with two 27"+ high res. monitor trough thunderbolt port

Hi all,
I just looking for a solution, to make it work: With a thunderbolt port MB Pro 15" (2011-eraly, 2011 late, 2012 mid NOT RETINA version), which has only one thunderbolt port. How its possible to plug two (min. 2560x1440) high resolution NOT APPLE Display (daisy chain). I got now one Dell 3011 and I plan to plug a second one. BUT how?
It is any HUB or something like that, which create from the one thunderbolt port »» two mini or standard diplay port, or dual DVI, so two separate connector which can handle the high resolution?
I saw lot of solution up to 1920x1200 (dualhead2go, etc.), but nowhere found any idea to handle with a MB Pro 15" thunderbolt version multiple (dual) external HIGH Resolution monitor 27-30" (2560x1440, or 2560x1600).

Try Googling "macbook pro thunderbolt dual display adapter" - there are a number of hits (even a YouTube video). See if you can find what might work best for you. I'm sure that someone around here has acheived this - they're jut not chiming in at the moment. Also check with OWC and see if they have anything. You can call them at 1.800.275.4576.
Good luck,
Clinton

Portege R930 - BSOD when connecting high resolution monitor to HDMI port

Hello.
I have the Portege R930 (pt331a-01w001) running window 7. Everything on the laptop works as expected, however when I plug the laptop into a high resolution monitor (2560x1440) via the HDMI port I get blue screen of death.
I can use the HDMI port to connect to my 1080p LCD TV and my work monitor which is a lower resolution and it works ok.
I have tried multiple cables and different monitors of the same resolution.
Can anyone assist?

Hello,
Yes that is correct. When my laptop is connected to a monitor with a lower resolution that 2560x1440 (such as my work monitor (1680x1050) or my TV (1080p)) everything works as expected.
Once I plug it into the 2560x1440 monitor I get BSOD.
The monitor only has a DVI-D Dual link port, so I am using a HDMI to DVI-D Dual link cable to connect the laptop HDMI port to the monitor.
I was getting this fault with the original display driver (not sure of the version), I then updated to the Toshiba driver (v8.15.10.2712) and also tried the Intel Driver (9.17.10.2932) and still get the same problem.

Can my T530 connect to an external 4K monitor via DVI port?

I connect a 4K monitor to my T530 via the DVI port in the docking station, but the max. resolution I can adjust is 1920x1080. Is there any way to change to 4K? Thank you.

You might be able to get 3840x2160 on DVI by setting a custom resolution at 30Hz using Intel Control Panel or NVIDIA Control Panel (depending on whether you have Optimus).
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Connect monitor w/ thunderbolt port and monitor w/ Firewire or ?

I have an iMac with a thunderbolt port. I was recently given a much older iMac with a port that looks like a fat "U" with a flat top, several USB pots, and 2 firewire ports. I would like to use the older Mac as a second monitor. I've searched and searched, but for the life of me, I can't find the combination of cables that will connect them.
This is what the old Mac looks like in the back.

Only the late model iMac's support > Target Display Mode or display input.
One option might be > ScreenRecycler

Monitoração de Portas IVR

Similar Messages

Maybe you are looking for