Monday, September 25, 2017

Delete user extension from NICE perform application server

Delete user from NICE user Administrator
1.       Login to the application server and open the link:

2.       Click on Accessories->User Administrator
User Adminitration.JPG

3.       Locate the user and double click to view the details

All users.JPG

user details.JPG

4.       Click on Agent

Click on Agent.JPG

5.       Make a note of the extension and delete the extension from NICE after that


6.       Delete user

Delete user.JPG

Delete extension and free the channel from System Administrator
1.       Go to Accessories-> System Administrator

System Administrator.JPG 

2.       Click on settings and check Technician Mode

Technician Mode.JPG

3.       Go to master Site-> CTI Interfaces -> Drivers -> Cisco Driver


4.       Click on Interfaces, Locate the extension and move it from left to right                Select in left.JPGMove to Right.JPG

5.       Click on Save and Update configuration

6.       Go to master Site-> CTI Interfaces ->CTI Interfaces->Cisco TAPI interface

CTI Interfaces Devices.JPG

7.       Click on devices, Locate the device and delete the extension, after deleting click on save and update configuration

8.       Click on Master Site -> CLS definition -> Channel Mapping -> Static Mapping

Static Mapping Summary.JPG

9.       Click on Summary select extension and click on detach
(This will detach the channel and you will have one free channel)

Detach Static Mapping.JPG

10.    Click on Master Site -> CLS definition -> Channel Mapping ->Sources Definition

Sources Definition.JPG

11.   Locate Extension and Delete the extension

Thursday, February 28, 2013

Understanding the Difference Between Restart and Reset

You can reset or restart a phone in Cisco CallManager Administration. What is the
difference between resetting and restarting?


Basically, the reset command causes the IP phone to completely power-cycle and begin again as if it had just been plugged in.


The restart command tells the IP phone to unregister and then reregister with CallManager.

Tuesday, June 12, 2012

SRST testing

Test the SRST configuration: 

## Take down the WAN interface or add a static route to null 0 for any ip packets coming from Unified CallManager ## 

ip route null 0

Tuesday, April 17, 2012

Loop start


When loop start signaling is used, a gateway's FXO interface looks like a phone to
the switch (PBX, PSTN, Key-System) it is connecting to. The FXO interface closes the
loop to indicate off-hook, just as an analog phone does when it is physically lifted
off-hook. The switch always provides battery, so there is no disconnect supervision
from the switch side. Because a switch expects a phone user (which an FXO interface
behaves like) to hang up the phone when the call is terminated (on either side), it
also expects the FXO port on the router to hang up. This "human intervention" is not
built into the router. The FXO port expects the switch to tell it when to hang up (or
remove battery to indicate on-hook). Because of this, it cannot be guaranteed that a
near-end or far-end FXO port will disconnect the call after either end of the call has
hung up.

Tuesday, January 10, 2012

Disable toll fraud feature on IOS 15

Router# conf t
Router(conf)# voice service voip
Router(voice-ser-voip)# no ip address trusted authenticate

Thursday, January 5, 2012

Difference between Unicast and Multicast MOH

MOH server is commanded to generate a stream to the IP address of the endpoint receiving the stream. The endpoint is told to listen to the stream, which includes various messages depending on the protocol and the type of endpoint. When the call is to be taken off hold, the MOH server is told to stop streaming, and the held party is connected to the appropriate endpoint.

MOH server is always streaming the multicast stream. As such, CallManager doesn't need to tell the MOH server to do anything. The endpoint is simply told to listen to the multicast stream.

Wednesday, December 28, 2011

Database replication states

0—This value indicates that replication did not start. Either no subsequent nodes (subscribers) exist, or the Cisco Database Layer Monitor service is not running and has not been running since the subscriber was installed.

1—This value indicates that replicates have been created, but their count is incorrect.

2—This value indicates that replication is good.

3—This value indicates that replication is bad in the cluster.

4—This value indicates that replication setup did not succeed.