Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Scripts work wrong with DN of Attendant Console

I have a IPCC Express 5.0(2)_Build064 server with Unified CCX Premium Package and a CCM

6.1.2.1002-1 server.

In CCM I have configured a Cisco Unified CM Attendant Console with a pilot point.

In UCX I also have created a script in which the incoming call after several steps in the

script is forwarded to the pilot point of the Attendant Console. The extension or DN of

the pilot point in the script is a variable of type string.

In the step CallRedirect the output branch are: successful, busy, invalid and

Unsuccessful.

My problem is that when the call incoming to the step CallRedirect and the script forwards

the call to the Attendant Console pilot point always is forwarded to the branch

successful and does not execute the following steps of this branch and it does not also

detect if this pilot point is busy (in case all the operators of the attendant console are

busy).

When I debug the script when the call incoming to the step CallRedirect-Successful the

system shows me the following message:

-contact id: x

-contact is inactive when getting channel

The version of Attendant Console is

6.1.(1c)

IPCC Express is running on model server 7816

1 REPLY
Silver

Re: Scripts work wrong with DN of Attendant Console

CRS has no way to confirm from pilot point that all the phones are busy as the pilot point does not maintain the status.

A script will not ever work properly with a Pilot Point (DN) of an Attendant Console because by default the Pilot Point does not have any configuration parameter as what to do with a call if all the phones are busy.

180
Views
0
Helpful
1
Replies
CreatePlease to create content