Simply use time of day step in the CCX script and add branch defining 10 PM - whatever time you want, then under that branch add the step to play your announcement and whatever else you need to do. ... View more

a) Is UCCX licensed per individual agent OR on simultaneous/concurrent logins ? Concurrently logged in agents and supervisors b) Do agents usually login to PC and then EM into phone and then login to Finesse??? Is there a way to automate this or make it less than 3 logins ? Not aware of it, but one thing you could to to simplify EM login is it's the same user logging onto the same phone is to create EM single button login with a Service URL button defined to login that agent with click of a button. For Finesse as stated SSO would be an option to consider.       ... View more

Is the number in the call log showing with the * prefix?  ... View more

Really depends on how you want to use them, for inbound it's controller by telco, for outbound it is on you, and if you simply want to balance the outbound traffic across the 2 GWs and 2 PRIs on each then add both GWs/Trunks to common Route group with circular routing algorithm and then on the GW configure both PRI D-channels in the same trunk group with same priority (assuming SIP/H323 config). ... View more

Theoretically yes, if you run SIP load on these you should be able to register as 3rd party SIP device keeping in mind that those do not support all of the features Cisco endpoints registered as Cisco devices do. ... View more

I created a tool for something like this a while ago, you can access it from here: http://chrisderen.pythonanywhere.com you would select the first option and then upload a csv file with DID ranges you own and an export of all DNs in use on CUCM. You can download sample files from the webpage. ... View more

Why would you ever want to dial URIs from physical phone? The idea for URI dialing is to use it for devices that can easily dial URIs (i.e. video endpoints, Jabber clients, etc) and from physical phones you just dial the corresponding number. ... View more

Once you configure the controller as PRI the voice port will be created. ... View more

here is example:   trunk group Local-PRI description Local AT&T PRI circuits   interface Serial1/0:23 trunk-group Local-PRI 1 interface Serial1/1:23 trunk-group Local-PRI 2   dial-peer voice 1 pots trunkgroup Local-PRI description Local Trunks, Local calls destination-pattern 81[2-9]..[2-9]...... progress_ind setup enable 3 progress_ind progress enable 8 forward-digits 11   ... View more

Apologies for late response. For PRI connectivity you'll need E1-PRI cross-over cable connected between the devices, then the following config on Cisco side assuming you configure Cisco as ISDN network side:   network-clock-participate slot 0 network-clock-select 1 E1 0/0/0 <--- whichever slot your PRI is in   controller E1 0/0/0 <--- whichever slot your PRI is in pri-group timeslots 1-31   interface Serial0/0/0:15 no ip address encapsulation hdlc isdn switch-type primary-net5 isdn incoming-voice voice isdn protocol-emulate network isdn supp-service name calling no cdp enable   voice-port 0/0/0:15 cptone <country of choice> bearer-cap Speech   once connected issue "show isdn status" and look for multiple frames establisher status. Next configure dial-peers such these:   voice class codec 1 codec preference 1 g711ulaw codec preference 2 g711alaw codec preference 3 g729r8   dial-peer voice 1 pots description POTS inbound and outbound dial peer destination-pattern .... <--- whatever should point to other side of PRI progress_ind setup enable 3 progress_ind alert enable 8 incoming called-number . direct-inward-dial port 0/0/0:15 ! dial-peer voice 100 voip destination-pattern .... <--- whatever should point to CUCM session target ipv4:<IP of CUCM> session protocol sipv2 voice-class codec 1 dtmf-relay rtp-nte ip qos dscp cs3 signaling no vad ... View more

First of all you will need to get he E1 up first, are you planning on configuring it as PRI circuit? Is there a T1/E1 cross-over cable between the devices,  is ISDN L3 already up, or do you need assistance with this? Then as stated you'll need set of dial-peers on the GWs for POTS (incoming from Grandstream, outgoing to Grandstream ) call legs and VOIP call legs (incoming from CUCM, outgoing to CUCM) matching proper digits that need to go each destination. ... View more

This is all going to work as far as delivering calls to proper mailbox, but you will not get MWI on phones to work properly unless you have unique DNs in CUCM (which should be your goal), if you dont care for MWI then no issue here, but if you do you could set alternate MWI extension, but the issue is that those will be overlapping between your 4 digit DNs. ... View more