Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I've written a new java class with one method that performs a calculation, and returns an int. The idea is that my UCCX 10.6 script will pass in two integers, perform the random number generator function based on these two integers as high/low, then ...
I'm not new to ASA firewalls at all, also know L2/L3 very well, but I'm having a terrible time getting an ASA 5500 config pulled together.
I have a lab where I'm testing an ASA 5520 active/standby failover pair prior to rolling this out, and need to ...
I have a new install of an MX800 registered to TPaaS in the cloud, and the unit is constantly receiving calls from 100@ and its IP address. This started over the weekend and is occurring every 30 seconds like clockwork. Is there any way in the MX800 ...
I have a CUBE deployment Cisco 2911 15.41T1 running fine, sip trunks to UCM 10.5.1 and to the SIP provider, again running fine. The designers of this project specified that a 2-port FXO is installed in this cube to support a Bogen TAMB unit, not the ...
ok, I know these are old phones, but ran into something with UCCX 8.5.1 SU4 when the agents are IPPA on M7960 phones. The CCM is 8.6.2 SU3, phone load is 8.1.2 on a relatively new UCCX lab installation.IPPA agents works fine, no issues, but post call...
failoverfailover lan unit primaryfailover lan interface failover GigabitEthernet0/2failover polltime unit 2 holdtime 6failover polltime interface 2 holdtime 10failover replication httpfailover link stateful GigabitEthernet0/3failover interface ip fai...
exact opposite behavior - it follows the designated primary firewall. If I change the failover config so that ASA-PRI (forget the name for a moment) acts as failover standby, the issue follows.
Its almost like no matter what, the default gateway nev...
client tested it late yesterday afternoon and it worked great! I didn't see anything in the logs that indicated where this was coming from, so my impression is that this was from a spoofed IP making these probing calls.
The TPaaS provider has been u...
I changed the BIPPA user to that of the RmCmUser and password, worked great.$&%&%*%$*%Had no effect on newer phones, the older 794x/796x was the problem child.Thanks, Jeff