UCCE v8.5 with CIPC8.6 agent greeting and Whisper annoucement

Dear networkers,
We do have UCCEv8.5 deployed with CVP 8.5, CUCM 8.5 and CAD 8.5.
We have Cisco IP Communicators(CIPC) v8.6 installed we would like to implement the follwoing two features:
- Agent Greeting
- Whisper Announcement
As far as the documentation says, we need a phones with Built in bridge. Does CIPC support uch feature ?? Can the above two features be deployed using CIPC ?
thanks in advance.
Best Reagrds.

Hi ,
You can deploy those two features with cipc 8.6 ....first you need to enable Built-in-Bridge in CUCM for the perticular cipc..
For more info refer the below url
http://www.google.co.in/#hl=en&safe=active&tbo=d&spell=1&q=agent+greeting+%26+whisper+announcement+configuration&sa=X&ei=Yg8iUZj8LsXE0QHPl4GYCQ&ved=0CCsQvwUoAA&bav=on.2,or.r_gc.r_pw.r_qf.&bvm=bv.42553238,d.dmg&fp=ca85679e4aaec60f&biw=1366&bih=651
Message was edited by: Silambarasan K

Similar Messages

  • Record Agent Greeting and the DTMF Phone Pad

    Strange behaviour here.
    If I use a 7960 phone and press the icon to record an agent greeting, the Phone Pad pops up and I can press the buttons to navigate the menus. I can also use the hard phone. Of course, this phone has no BIB, so I connected another couple of phones.
    If I use a 7961 phone, pressing the keys on the Phone Pad does nothing - but I can use the hard phone. That''s strange.
    If I use a 7971, pressing the keys on the Phone Pad does nothing and neither does pressing the keys on the IP phone!!! I created a similar app outside of the Recording process and attached it to a Route Point and get the same behaviour. Must be a phone setting that is not allowing DTMF.
    Regards,
    Geoff

    please share CVP and VXML application logs, but i think you must place agent greeting type variable in recording script. after CED just set greeting type.
    regards
    Chintan

  • UCCE Record Agent Greeting Exaple Script Fails at first Run Ext Script Node

    I am deploying Agent Greeting and trying to get the recording piece completed. When the example script gets to the run ext script node it fails.

    I am running 9.0 for UCCE, CUCM, and CVP.....When I press the record button on CTIOS agent I get a 101707 error with somthing about the route. Then I do a script monitor I notice the flow stops at the first run ext script node
    I have attached the PG Logs
           Sorry about the vagueness in the first post just seeing if any knew of this issue with the example scripts.

  • Agent greeting delay

    Dear Community,
    My UCCE 8.5 setup is experiencing agent greeting delay, where once the call is connected to agent, there are 2secs delay (silent) before the agent greeting file played (heard). The setup is centralized servers with VG and IP phones reside at remote sites. The remote sites are connected via MPLS to the central site.
    The agent greeting wav files are cached on VG, however, TAC analysis presents that the delay on the signaling also causes the delay of agent greeting being played.
    Does anyone have the similar setup but not experiencing agent greeting delay? or also experiencing same delay. Kindly please share your experience.
    Thank you for your attention.
    .wan

    Yes, I've trimmed the begining silence of each greetings wav files.
    .wan

  • Agent Greeting with Genesys CTI/Desktop

    Hello everybody!
    Is it possible to use agent greeting if the customer has integration with the Genesys Cisco T-Server.
    The deployment - Unified CCE with Genesys CTI/Desktop Only.
    He has:
    - CVP 9.0;
    - UCM 9.1;
    - ICM 9.0.3;
    - Genesys T-Server 8.0;

    Hi,
    Agent greeting does not support Genesys Cisco T-Server.
    It supports only with the out of box CTI toll kit.
    Regards,
    Srinivasan

  • Agent Greeting with Precsion Queueing anf Finesse

        Hello all
    I am wanting to know if I can add Agent Greeting to a PQ and if someone has a snapshot example ICM script. Has anyone created a gadget to allow the Agent greeting to be recorded from Finesse agent desktop.

    please share CVP and VXML application logs, but i think you must place agent greeting type variable in recording script. after CED just set greeting type.
    regards
    Chintan

  • CVP Record Agent Greeting Failing

    I'm setting up the default Record Agent Greeting application with CVP 10.0, UCCE 10.0, Finesse 10.5.  I can dial the entry point number from Finesse and it goes to the ICM script.  I hear the message "Please select the greeting you wish to hear or record..." I then press the greeting number hear the next message "Press 1 to hear the greeting, 2 to record..." and then it runs the RecordAgentGreeting VXML application.  It immediately states that a greeting filename was not provided.  Do I need to set the session data for this somewhere or is the agentname supposed to populate automatically?  At least I think that's my issue.  

    please share CVP and VXML application logs, but i think you must place agent greeting type variable in recording script. after CED just set greeting type.
    regards
    Chintan

  • CTI OS answer call but not play agent greeting

    hello everyone
    i config agent greeting in UCCE
    now i can record the greeting 
    and i config a DN like 60002 with PlayAgentGreeting call type,and the call type associate PlayAgentGreeting script
    i dial 60002 from my CTI OS client i can hear the greeting .
    but when i enable agent greeting on CTI OS,and answer a call in number ,it can't play greeting.
    i look the script but no run this script .
    i look the log with CTI OS server and find the client can't sent the dialed number ....
    can i loss some config with play script? like CTI OS client config?

    hi
    next is rtr log
    Events from February 17, 2015:
    00:01:41:617 rb-rtr Trace: (35 x 0 : 0 0) NewCall: CID=(151257,301), DN=60000, ANI=1079, CED=, RCID=5001, MRDID=1, CallAtVRU=1, OpCode=0 
    00:01:41:617 rb-rtr Trace: (35 x 33 : 0 0) TransferToVRU: Label=1231231234567890, CorID=33, VRUID=5002, RCID=5001 
    00:01:41:781 rb-rtr Trace: (35 36 33 : 0 0) RequestInstr: CID=(151257,301), CallState=1 
    00:01:50:439 rb-rtr Trace: (35 36 33 : 0 0) ATR rule not found for agent 5001 at ext 1001. Device target had label 1001 (ID 5026). 
    00:01:50:439 rb-rtr Trace: (35 36 33 : 0 0) DeviceTargetPreCall_V11: CID=(151257,301), PerID=5000, SGSTID=5003, AGSTID=5001 NetworkCallFlags=0, InvokeID=18, GREET= 
    00:01:50:439 rb-rtr Trace: (35 36 33 : 0 0) Connect: CID=(151257,301), EventSelect=0, ServiceType=0, RCID=5001, Label(s)=1001 
    00:01:50:439 rb-rtr Trace: (35 36 33 : 0 0) Deleting Dialog. 
    next is CUCM pg pim log
    Events from February 17, 2015:
    00:01:27:095 PG1A-pim1 Trace: CSTASetAgentState: Peripheral::ProcessCSTAThirdPartyServiceRequest InvokeID=0xf0000046 Dev=1001 AgentMode=READY AGID=1000 SG=-1(0xffffffff)) 
    00:01:27:095 PG1A-pim1 Trace: PrivateData: EventReasonCode=0 WorkMode=0 NumAdditionalGroups=0 PositionID= SupervisorID= ClientAddress= 
    00:01:27:095 PG1A-pim1 Trace: CSTASetAgentStateConfEvent: TPServices::CSTASetAgentStateConfEvent InvokeID=0xf0000046 
    00:01:50:619 PG1A-pim1 Trace: DeviceTargetPreCallInd: PreLock: RTRCallKey=151257.301 NTID: 5035 dialed number=60000 CED= ASTID=5001, AG=, CustomerDefinitionID=1, AW=0 
    00:01:50:619 PG1A-pim1 Trace: DeviceTargetPreCallInd: PostLock: RTRCallKey=151257.301 ASTID: 5001 NTID: 5035 Ext: 1001 AG= AW=0 
    00:01:50:619 PG1A-pim1 Trace: CheckWhisperECCWithIPIVR: ECC.user.media.id8CF741800001000000000713F901A8C0 and Customer Call ID: -1 
    00:01:50:619 PG1A-pim1 Trace: AddPreRoutedCall: Inst: N1001 CreatedByPreCall: T PeriphCID: -1 Queue Count: 1 RouterCallKey=(151257/301) preCallRouteCrossRefID: 0, SkTT:0, GREET: DialedNumber:60000 CustID:1 AW=0 
    00:01:50:782 PG1A-pim1 Trace: Delivered: CID=16779291 ConnDevID=1079/1  AlertDevID=/0 CallingDev=1079/0 CalledDev=1001/0 LastRedDev=/0 LocalConn=1 Cause=22OrgTrk=-1 OrgTrkGrp=-1 TermTrk=-1 TrmTrkGrp=-1UniqueID= 000000000000081B016B9CB400000000 ANI=1079 DevTgDevStr=1001 
    00:01:50:782 PG1A-pim1 Trace: RetreivePreRoutedCall: Head Inst: N1001 CreatedByPreCall: T PeriphCID: -1 Queue Count: 1 RouterCallKey=(151257/301)  
    00:01:50:782 PG1A-pim1 Trace: MatchPendingCall (DeskLinkCall) : Inst: N1001 CreatedByPreCall: T PeriphCID: -1 RouterCallKey=(151257/301)  
    00:01:50:782 PG1A-pim1 Trace: Offered matched PreCall for CID: 16779291 Ext: 1001 SecondsPending: 0 
    00:01:50:783 PG1A-pim1 Trace: FreePreRoutedCall: Head Inst: N1001 CreatedByPreCall: T PeriphCID: -1 Queue Count: 0 RouterCallKey=(151257/301)  
    00:01:50:783 PG1A-pim1 Trace: CSTA DELIVERED, TelephonyDriver::Offered: SENT TO OPC
    CallID      = 16779291  DeviceID = 1079  DeviceType = Dynamic
    Alerting    = 
    Calling     = 1079
    Called      = 1001
    Redirection = 
    LocalState  = INITIATE
    Cause       = EC_NEW_CALL 
    00:01:50:783 PG1A-pim1 Trace: Delivered: CID=16779291 ConnDevID=1079/1  AlertDevID=1001/0 CallingDev=1079/0 CalledDev=1001/0 LastRedDev=/0 LocalConn=2 Cause=-1OrgTrk=-1 OrgTrkGrp=-1 TermTrk=-1 TrmTrkGrp=-1UniqueID= 000000000000081B016B9CB400000000 DevTgDevStr=1001 
    00:01:50:783 PG1A-pim1 Trace: GetAgentWhispePrimaryCallID: Unable to find PreRoutedCallPending 16779291 
    00:01:50:783 PG1A-pim1 Trace: CSTA DELIVERED, TelephonyDriver::Delivered: SENT TO OPC
    CallID      = 16779291  DeviceID = 1079  DeviceType = Dynamic
    Alerting    = 1001
    Calling     = 1079
    Called      = 1001
    Redirection = 
    LocalState  = ALERTING
    Cause       = EC_NONE 
    00:01:53:081 PG1A-pim1 Trace: CSTAAnswerCall: Peripheral::ProcessCSTAThirdPartyServiceRequest InvokeID=0xf0000047 AlertingCall(CID=16779291,Dev=1079,Type=Dynamic) 
    00:01:53:081 PG1A-pim1 Trace: PRIVATE_DATA: AnsweringDevice=1001 
    00:01:53:092 PG1A-pim1 Trace: Established: CID=16779291 ConnDevID=1001/0  AnsDevID=1001/0 CallingDev=1079/0 CalledDev=1001/0 LastRedDev=/0 LocalConn=3 Cause=-1OrgTrk=-1 OrgTrkGrp=-1 TermTrk=-1 TrmTrkGrp=-1UniqueID= 000000000000081B016B9CB400000000 DevTgDevStr=1001 
    00:01:53:092 PG1A-pim1 Trace: Checking for agent whisper enabled. Ext=1001 CallID=16779291 AW enabled=0 ReqEnbld:0 ReqSt=0 
    00:01:53:092 PG1A-pim1 Trace: Checking for RNA Requery. Ext=1001 CallID=16779291 RNA=0 Qtime=4 ReqEnbld:0 DNID:0 ReqSt:0 
    00:01:53:092 PG1A-pim1 Trace: CSTA ESTABLISHED, TelephonyDriver::Established: SENT TO OPC
    CallID      = 16779291  DeviceID = 1001  DeviceType = Static
    Answering   = 1001
    Calling     = 1079
    Called      = 1001
    Redirection = 
    LocalState  = CONNECT
    Cause       = EC_NONE 
    00:01:53:092 PG1A-pim1 Trace: Checking for AgentGreeting. GREET:  CustID: 1 
    00:01:53:093 PG1A-pim1 Trace: AnswerCallConf: InvokeID=121322 
    00:01:53:093 PG1A-pim1 Trace: CSTAAnswerCallConfEvent: TPServices::CSTAAnswerCallConfEvent InvokeID=0xf0000047 
    00:01:54:137 PG1A-pim1 Trace: RTPStarted: CID=16779291, ConnDevID=1001/0, Addr=10.0.0.159:24582, Direction=IN, RtpType=Audio, BitRate=1, EchoCan=ON, PktSize=20, Payload=4 , UniqueID=000000000000081B016B9CB400000000 
    00:01:54:232 PG1A-pim1 Trace: RTPStarted: CID=16779291, ConnDevID=1001/0, Addr=10.0.0.159:20664, Direction=OUT, RtpType=Audio, BitRate=1, EchoCan=ON, PktSize=20, Payload=4 , UniqueID=000000000000081B016B9CB400000000 
    00:01:57:537 PG1A-pim1 Trace: CSTAClearConnection: Peripheral::ProcessCSTAThirdPartyServiceRequest InvokeID=0xf0000048 Call(CID=16779291,Dev=1001,Type=Static) 
    00:01:57:537 PG1A-pim1 Trace: PRIVATE_DATA: CompoundRequestType=Unknown CSTA Event Type SubjectDevice=1001 
    00:01:57:546 PG1A-pim1 Trace: RTPStopped: CID=16779291, ConnDevID=1001/0, Addr=10.0.0.159:24582, Direction=IN, UniqueID=000000000000081B016B9CB400000000 
    00:01:57:547 PG1A-pim1 Trace: RTPStopped: CID=16779291, ConnDevID=1001/0, Addr=10.0.0.159:20664, Direction=OUT, UniqueID=000000000000081B016B9CB400000000 
    00:01:57:547 PG1A-pim1 Trace: ConnectionCleared: CID=16779291 ConnDevID=1001/0 ReleasingDev=1001/0 LocalConn=-1 Cause=-1UniqueID=000000000000081B016B9CB400000000 DevTgDevStr=1001 
    00:01:57:547 PG1A-pim1 Trace: CSTA CONNECTION CLEARED, TelephonyDriver::ConnectionCleared: SENT TO OPC
    CallID          = 16779291  DeviceID = 1001  DeviceType = Static
    ReleasingDevice = 1001
    LocalState      = NONE
    Cause           = EC_NONE 
    00:01:57:547 PG1A-pim1 Trace: CallCleared: CID=16779291 ConnDevID=/0 LocalConn=-1 Cause=-1UniqueID=000000000000081B016B9CB400000000  
    00:01:57:547 PG1A-pim1 Trace: CSTA CALL CLEARED, TelephonyDriver::CallCleared: SENT TO OPC
    CallID     = 16779291 DeviceID =   DeviceType = Static LocalState = NONE
    Cause      = EC_NONE 
    00:01:57:548 PG1A-pim1 Trace: ClearConnectionConf:  InvokeID=121323 
    00:01:57:548 PG1A-pim1 Trace: CSTAClearConnectionConfEvent: TPServices::CSTAClearConnectionConfEvent InvokeID=0xf0000048 
    i ues UCCE 9 and all CTI OS version is 10

  • Whisper and Agent Greeting

    Hi ,
    I had a query  on whisper and Personalised Agent Greeting supported in UCCE 8.5.
    Can't we configure both the above features and make them work simultaneously for call which is landing to agent?
    regds,
    aman

    Yes you can ...
    You can use Agent Greeting along with the Whisper Announcement feature. Here are some things to consider when using them together:
    - On the call, the Whisper Announcement always plays first, before the Agent Greeting.
    - To shorten your call-handling time, you may want to use shorter Whisper Announcements and Agent Greetings than you might if you were using either feature by itself. A long Whisper Announcement followed by a long Agent Greeting equals a long wait before an agent is actively handling a call.
    - If you use a Whisper Announcement, your agents probably handle different types of calls: for example, “English-Gold Member-Activate Card,” “English-Gold Member-Report Lost Card,” “English-Platinum Member-Account Inquiry.” Therefore, you may want to ensure the greetings your agents record are generic enough to cover the range of call types.
    source: http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_5_1/configuration/guide/agwa85fg.pdf
    (page 18)
    Brian
    Please rate helpful posts.

  • Agent Greeting / Agent Recording error

    Agent greeting enabled
    DailNumber created for CM routing client as PlayAgentGreeting, RecordAgentGreeting
    CallTypes created as same
    Script mapped.
    it is failed at Ext VRU Script node in RecordGreeting script.
    Not sure about any other configuration is request like (call manager route pattern, cvp ops console change or any other script changes.
    I am getting the error message Error [10170] Routing error while recording Agent Greeting
    with Regards,
    Manivannan

    Chintan,
    thanks for explanation it is very clear. I got stuck in below config
    router sends VRU label to PG (this will be configured under network VRU explorer, and it will be for your CM peripheral), and label will be always appended with corr id.
    Now it is passing the send to vru node and playing the menu. but now it is failured at 
    Run Ext. Script node (Audium, GS,Server,V), i am using the default media server (cvpcall server+vxmlserver+mediaserver)
    when i checked the activity log of RecordAgentGreeting vxml application nothing is there, that means it is not hitting the application.
    I am suspecting that what ever variables ECC created recently is not taken effect. becuase i found the following error in cvp call server logs
    CONNECT message, sending EVT RPT back to ICM -  >>HEADERS: (JMSType)=MsgBus:CONNECT (JMSDestination)=Topic(CVP.ICM.CC.RESP.SYS_SIP2) (JMSTimestamp)=1402823524903 (ServerID)=WIN-PBC34IB91T5.SYS_ICM2:ICM:ICM2:WIN-PBC34IB91T5.MsgBus002 >>BODY: callguid=0B527E56F3A411E3987E78DA6E493500 RouterCallKey=1113 floatingvars=>>HEADERS: (JMSType)=MsgBus:FLOATINGVARS >>BODY: callvars=[, , , , , , , , , ] user.microapp.app_media_lib=app user.microapp.media_server=media user.media.id=0B527E56F3A411E3987E78DA6E493500 user.microapp.FromExtVXML=[null, null, null, null] user.microapp.ToExtVXML=[null, null, null, null, null] user.microapp.locale=en-us user.microapp.input_type=D  >>STATE: isTabular=false isWriteable=true cursor=-1 dnis=8015 correlationid=26711 timezone=Asia/Riyadh RouterCallKeySequenceNumber=0 version=CVP_10_0 RouterCallKeyDay=151010 labeltype=-1 label=8111126711 localOffset=180 calllegid=B527E56-F3A411E3-90EDEE36-70AFD42F  >>STATE: isTabular=false isWriteable=false cursor=-1 [id:5005] 
    kindly guide me. how to proceed further.
    with Regards,
    Manivannan

  • Agent Greeting

    Hello
    i am hoping that someone might be able to help me with agent greeting. i have most of the components in place and working. i can record and playback agent greetings without issue in the recording script. my problem is with a live call the play agent greeting script kicks off but no audio plays and CVP complains about UCM ending the call instead of CCE. in reviewing traces and logs it looks like the play agent script is not passing the the agent info.
    CVP Call Server log
    2562: 10.7.16.101: Mar 03 2015 19:32:11.293 -0500: %CVP_10_5_SIP-3-SIP_CALL_ERROR:  Agent Greeting disconnected via UCM instead of CCE playback script: CALLGUID = E326D00000010000000000280510070A LEGID = e326d000-4f615289-167ac-510070a - [INBOUND] DURATION (msecs) = 8875 - DIALOG TERMINATED. null [id:5004]
    CVP PIM
    9:30:19:053 PG2A-pim1 Trace: ProcessConnect:CONNECT  RCID=5001 PID=5001 DID=143 DIDRelSeq#=0 CRS(RtrDate=151271,RtrCID=289) RCKSeq#=3 ErrorCode=0 TRTargetID=-1 CorrID=372 EventSel=119 SvcType=4 NICCallID={PCID=5001,RCID=5001,Remote=0,0,DID=0x8f,RemDID=0x0,Grp=0,Data=0,RtrData=0,CCID=x00000001/x00000000} PGCallID={N/A} OperationCode=CLASSIC OperationFlags=COOP_NONE NetworkTransferEnabled=F Label(Type=8)=8111111111 NICCalledParty#=PlayAgentGreeting SGSTID=-1 SvcSTID=-1 AGSTID=-1 AGInfo= CallGUID=E326D00000010000000000280510070A.
    19:30:19:054 PG2A-pim1 Trace: ToVRU_vruTemporaryConnect:Set ECCVar:
    ECCVar:6=D
    ECCVar:12=N
    ECCVar:2=0
    ECCVar:7=en-us/microapp/ag_gr
    ECCVar:10=http://10.7.16.101
    ECCVar:0=041CFD63C13B11E4B2F187873ED96234.
    19:30:19:054 PG2A-pim1 Trace: PG->VRU:TEMPORARY_CONNECT(216 bytes):DID=143 SendSeq#=1 Label=8111111111 CorrID=372 RCK=289 RCKDay=151271 RCKSeq#=3 CallGUID=E326D00000010000000000280510070A AgentGreetingHint=1.
    19:30:19:078 PG2A-pim1 Trace: VRU->PG:EVENT_REPORT(16 bytes):DID=143 SendSeq#=2 EventCode=Answer(4).
    19:30:19:175 PG2A-pim1 Trace: VRU->PG:EVENT_REPORT(16 bytes):DID=141 SendSeq#=3 EventCode=Answer(4).
    19:30:19:175 PG2A-pim1 Trace: ToRouter_CallEventReport:CALL_EVENT_REPORT  RCID=5001 PID=5001 DID=141 DIDRelSeq#=2 LabelIndex=0 Event=4 DialogEnds=0 Cause=1.
    19:30:27:924 PG2A-pim1 Trace: VRU->PG:EVENT_REPORT(22 bytes):DID=141 SendSeq#=4 EventCode=Disconnect(6) CauseCode=NormalComplete(1).
    19:30:27:925 PG2A-pim1 Trace: ToRouter_CallEventReport:CALL_EVENT_REPORT  RCID=5001 PID=5001 DID=141 DIDRelSeq#=3 LabelIndex=0 Event=6 DialogEnds=1 Cause=1.
    19:30:27:931 PG2A-pim1 Trace: VRU->PG:EVENT_REPORT(22 bytes):DID=143 SendSeq#=3 EventCode=Disconnect(6) CauseCode=NormalComplete(1).
    19:30:27:932 PG2A-pim1 Trace: ToRouter_CallEventReport:CALL_EVENT_REPORT  RCID=5001 PID=5001 DID=143 DIDRelSeq#=2 LabelIndex=0 Event=6 DialogEnds=1 Cause=1.
    19:30:27:934 PG2A-pim1 Trace: ProcessDialogFail:DIALOG_FAIL  RCID=5001 PID=5001 FailureType=2 NumOfEvents=1 DID=143 DIDRelSeqNo=1 ReasonCode=18.
    UCM PIM
    19:30:19:028 PG1A-pim1 Trace: Unqueuing RTPEventMsg for callid= 16783427 and device id= 1021.
    19:30:19:028 PG1A-pim1 Trace: Checking for AgentGreeting. GREET: 1 CustID: 1.
    19:30:19:029 PG1A-pim1 Trace: CSTA ROUTE REQUEST, TelephonyDriver::RequestPostRoute: by PIM for the DNP SENT TO OPC
         CallID            = 2130706515  DeviceID = 1021  DeviceType = Static
         RoutingCrossRefID = 65616
         CurrentRoute      = PlayAgentGreeting
         CallingDevice      = 1021
         RequestType       = 59
         AG                = 1
         CustomerID        = 1
         PreferredASTID    = 5013.
    19:30:19:030 PG1A-pim1 Trace: ProcessCSTARouteSelect: crossRefID=65616, RTRCallKey=151271.289, label 7111111111371 callID=2130706515.
    19:30:19:031 PG1A-pim1 Trace: TelephonyDriver::SendMediaStreamRequest - AgentCallID=16783427, AgentCallConnectionDeviceID=1021,AgentCallConnectionDeviceIDType=0, InvokeID=815003.
    19:30:19:031 PG1A-pim1 Trace: TelephonyDriver::ProcessCSTARouteSelect: Agent Greeting Service, Route End SENT TO OPC.
    19:30:19:031 PG1A-pim1 Trace: CSTA CALL CLEARED, TelephonyDriver::CallCleared:
         CallID     = 2130706515 DeviceID =   DeviceType = Static     LocalState = NONE
         Cause      = EC_NONE.
    19:30:19:114 PG1A-pim1 Trace: RTPStarted: CID=16783427, ConnDevID=1021/0, Addr=10.7.3.28:25222, Direction=IN, RtpType=Audio, BitRate=1, EchoCan=ON, PktSize=20, Payload=4 , UniqueID=0000000000001843012E0A3200000000.
    19:30:19:130 PG1A-pim1 Trace: addMediaStreamConf:  InvokeID=815003.
    19:30:19:130 PG1A-pim1 Trace: MsgCallAgentGreetingEvent: CallID=16783427 ConnDevID=1021/0 EventCode=0.
    19:30:19:131 PG1A-pim1 Trace: CSTA Call Agent Greeting, RecvCallAgentGreetingEventMsg: SENT TO OPC
         CallID = 16783427  DeviceID = 1021  DeviceType = Static
         EventCode = EC_AGENT_GREETING_STARTED GreetingType = 1 PeripheralErrorCode=0x0(0).
    19:30:19:177 PG1A-pim1 Trace: dtRequeryResultInd: RTRCallKey=151271.289 netTargID=0 ASTID=5013 Result=11 CallID=16783427.
    19:30:27:925 PG1A-pim1 Trace: MsgCallAgentGreetingEvent: CallID=16783427 ConnDevID=1021/0 EventCode=-1932787441.
    19:30:27:927 PG1A-pim1 Failed to play agent greeting type: 1, for call ID: 16783427, to agent ID: 2105, with the extension: 1021, due to original call dropped.
    19:30:27:929 PG1A-pim1 Trace: CSTA Call Agent Greeting, RecvCallAgentGreetingEventMsg: SENT TO OPC
         CallID = 16783427  DeviceID = 1021  DeviceType = Static
         EventCode = EC_AGENT_GREETING_ERROR GreetingType = 1 PeripheralErrorCode=0x4f2f(20271).
    19:30:27:929 PG1A-pim1 Trace: RTPStopped: CID=16783427, ConnDevID=1021/0, Addr=10.7.3.28:25222, Direction=IN, UniqueID=0000000000001843012E0A3200000000.
    19:30:27:930 PG1A-pim1 Trace: RTPStopped: CID=16783427, ConnDevID=1021/0, Addr=10.7.16.253:32294, Direction=OUT, UniqueID=0000000000001843012E0A3200000000.
    19:30:27:930 PG1A-pim1 Trace: ConnectionCleared: CID=16783427 ConnDevID=1021/0 ReleasingDev=1021/0 LocalConn=-1 Cause=-1UniqueID=0000000000001843012E0A3200000000 DevTgDevStr=1021.
    19:30:27:931 PG1A-pim1 Trace: CSTA CONNECTION CLEARED, TelephonyDriver::ConnectionCleared: SENT TO OPC

    i added the send to VRU node and the script aborts the "send to VRU" node. should i see the FeatureParam step on the CVP Pim log. it looks like ICM is not telling CVP the agent info or greeting type. but i do have the call.agentgreetingtype in my queue script.

  • Play Agent Greeting

    I am configuring agent greeting in a lab environment and to this point, I have been unable to get this process to work.  Using CCE 9.0 with an IP Communicator with Built-In-Bridge enabled.
    Record agent greeting works just fine.  We can record and review the agent greetings.  We are able to locate the agent greeting in the media server and using our browser we can get execute the agent greeting.  When we execute the ICM script to play the agent greeting we see it successfully pass through the ICM node of Set Variable for AgentGreetingType.  We have a dialed number defined for call manager to PlayAgentGreeting.  In our ICM script we can see the calls successfully execute the PlayAgentGreeting DN and Script execute successfully and exit the PM microapp. 
    We are now at a loss of where to start to finalize this process.  Looking in the Dumplog for our CM PIM we see the following output.
    I am no expert but this looks like agent greeting was successful however, we are not able to hear the media file.
    12:11:50:469 PG1A-pim1 Trace: Checking for AgentGreeting. GREET: 1 CustID: 1
    12:11:50:469 PG1A-pim1 Trace: CSTA ROUTE REQUEST, TelephonyDriver::RequestPostRoute: by PIM for the DNP SENT TO OPC
    CallID            = 2130706482  DeviceID = 7591  DeviceType = Static
    RoutingCrossRefID = 65584
    CurrentRoute      = PlayAgentGreeting
    CallingDevice            = 7591
    RequestType       = 59
    AG                = 1
    CustomerID        = 1
    PreferredASTID    = 5048
    12:11:50:471 PG1A-pim1 Trace: ProcessCSTARouteSelect: crossRefID=65584, RTRCallKey=150783.231, label 8888888888179 callID=2130706482
    12:11:50:471 PG1A-pim1 Trace: TelephonyDriver::SendMediaStreamRequest - AgentCallID=33567498, AgentCallConnectionDeviceID=7591,AgentCallConnectionDeviceIDType=0, InvokeID=100603
    12:11:50:471 PG1A-pim1 Trace: TelephonyDriver::ProcessCSTARouteSelect: Agent Greeting Service, Route End SENT TO OPC
    12:11:50:471 PG1A-pim1 Trace: CSTA CALL CLEARED, TelephonyDriver::CallCleared:
    CallID     = 2130706482 DeviceID =   DeviceType = Static           LocalState = NONE
    Cause      = EC_NONE
    12:11:51:129 PG1A-pim1 Trace: RTPStarted: CID=33567498, ConnDevID=7591/0, Addr=172.24.104.183:24636, Direction=IN, RtpType=Audio, BitRate=1, EchoCan=ON, PktSize=20, Payload=4 , UniqueID=000000000000330A02C7D4D700000000
    12:11:51:154 PG1A-pim1 Trace: RTPStarted: CID=33567498, ConnDevID=7591/0, Addr=172.28.36.5:17006, Direction=OUT, RtpType=Audio, BitRate=1, EchoCan=ON, PktSize=20, Payload=4 , UniqueID=000000000000330A02C7D4D700000000
    12:11:51:156 PG1A-pim1 Trace: addMediaStreamConf:  InvokeID=100603
    12:11:51:156 PG1A-pim1 Trace: MsgCallAgentGreetingEvent: CallID=33567498 ConnDevID=7591/0 EventCode=0
    12:11:51:156 PG1A-pim1 Trace: RecvCallAgentGreetingEventMsg: AG Greeting Start delay is 686 MS for CallID 33567498
    12:11:51:156 PG1A-pim1 Trace: CSTA Call Agent Greeting, RecvCallAgentGreetingEventMsg: SENT TO OPC
    CallID = 33567498  DeviceID = 7591  DeviceType = Static
    EventCode = EC_AGENT_GREETING_STARTED GreetingType = 1 PeripheralErrorCode=0x0(0)
    12:11:56:917 PG1A-pim1 Trace: MsgCallAgentGreetingEvent: CallID=33567498 ConnDevID=7591/0 EventCode=1
    12:11:56:917 PG1A-pim1 Trace: CSTA Call Agent Greeting, RecvCallAgentGreetingEventMsg: SENT TO OPC
    CallID = 33567498  DeviceID = 7591  DeviceType = Static
    EventCode = EC_AGENT_GREETING_DONE GreetingType = 1 PeripheralErrorCode=0x0(0)
    12:12:00:103 PG1A-pim1 Trace: RTPStopped: CID=33567498, ConnDevID=7591/0, Addr=172.24.104.183:24636, Direction=IN, UniqueID=000000000000330A02C7D4D700000000
    12:12:00:103 PG1A-pim1 Trace: RTPStopped: CID=33567498, ConnDevID=7591/0, Addr=172.28.36.5:17006, Direction=OUT, UniqueID=000000000000330A02C7D4D700000000
    12:12:00:103 PG1A-pim1 Trace: ConnectionCleared: CID=33567498 ConnDevID=7591/0 ReleasingDev=7591/0 LocalConn=-1 Cause=-1UniqueID=000000000000330A02C7D4D700000000 DevTgDevStr=7591
    12:12:00:103 PG1A-pim1 Trace: CSTA CONNECTION CLEARED, TelephonyDriver::ConnectionCleared: SENT TO OPC
    CallID          = 33567498  DeviceID = 7591  DeviceType = Static
    ReleasingDevice = 7591
    LocalState      = NONE
    Cause           = EC_NONE
    12:12:00:103 PG1A-pim1 Trace: CallCleared: CID=33567498 ConnDevID=/0 LocalConn=-1 Cause=-1UniqueID=000000000000330A02C7D4D700000000 
    12:12:00:103 PG1A-pim1 Trace: CSTA CALL CLEARED, TelephonyDriver::CallCleared: SENT TO OPC
    CallID     = 33567498 DeviceID =   DeviceType = Static           LocalState = NONE
    Cause      = EC_NONE
    12:13:30:857 PG1A-pim1 Trace: ConfigureRoutingClient - PID=5000 RID=5000 Timeout=1500 Late=500 Limit=10 ConfigStr=
    12:13:30:857 PG1A-pim1 Trace: DeskLinkPeripheral::ProcessRCConfig() RCTimoutThreshold=0

    I am configuring agent greeting in a lab environment and to this point, I have been unable to get this process to work.  Using CCE 9.0 with an IP Communicator with Built-In-Bridge enabled.
    Record agent greeting works just fine.  We can record and review the agent greetings.  We are able to locate the agent greeting in the media server and using our browser we can get execute the agent greeting.  When we execute the ICM script to play the agent greeting we see it successfully pass through the ICM node of Set Variable for AgentGreetingType.  We have a dialed number defined for call manager to PlayAgentGreeting.  In our ICM script we can see the calls successfully execute the PlayAgentGreeting DN and Script execute successfully and exit the PM microapp. 
    We are now at a loss of where to start to finalize this process.  Looking in the Dumplog for our CM PIM we see the following output.
    I am no expert but this looks like agent greeting was successful however, we are not able to hear the media file.
    12:11:50:469 PG1A-pim1 Trace: Checking for AgentGreeting. GREET: 1 CustID: 1
    12:11:50:469 PG1A-pim1 Trace: CSTA ROUTE REQUEST, TelephonyDriver::RequestPostRoute: by PIM for the DNP SENT TO OPC
    CallID            = 2130706482  DeviceID = 7591  DeviceType = Static
    RoutingCrossRefID = 65584
    CurrentRoute      = PlayAgentGreeting
    CallingDevice            = 7591
    RequestType       = 59
    AG                = 1
    CustomerID        = 1
    PreferredASTID    = 5048
    12:11:50:471 PG1A-pim1 Trace: ProcessCSTARouteSelect: crossRefID=65584, RTRCallKey=150783.231, label 8888888888179 callID=2130706482
    12:11:50:471 PG1A-pim1 Trace: TelephonyDriver::SendMediaStreamRequest - AgentCallID=33567498, AgentCallConnectionDeviceID=7591,AgentCallConnectionDeviceIDType=0, InvokeID=100603
    12:11:50:471 PG1A-pim1 Trace: TelephonyDriver::ProcessCSTARouteSelect: Agent Greeting Service, Route End SENT TO OPC
    12:11:50:471 PG1A-pim1 Trace: CSTA CALL CLEARED, TelephonyDriver::CallCleared:
    CallID     = 2130706482 DeviceID =   DeviceType = Static           LocalState = NONE
    Cause      = EC_NONE
    12:11:51:129 PG1A-pim1 Trace: RTPStarted: CID=33567498, ConnDevID=7591/0, Addr=172.24.104.183:24636, Direction=IN, RtpType=Audio, BitRate=1, EchoCan=ON, PktSize=20, Payload=4 , UniqueID=000000000000330A02C7D4D700000000
    12:11:51:154 PG1A-pim1 Trace: RTPStarted: CID=33567498, ConnDevID=7591/0, Addr=172.28.36.5:17006, Direction=OUT, RtpType=Audio, BitRate=1, EchoCan=ON, PktSize=20, Payload=4 , UniqueID=000000000000330A02C7D4D700000000
    12:11:51:156 PG1A-pim1 Trace: addMediaStreamConf:  InvokeID=100603
    12:11:51:156 PG1A-pim1 Trace: MsgCallAgentGreetingEvent: CallID=33567498 ConnDevID=7591/0 EventCode=0
    12:11:51:156 PG1A-pim1 Trace: RecvCallAgentGreetingEventMsg: AG Greeting Start delay is 686 MS for CallID 33567498
    12:11:51:156 PG1A-pim1 Trace: CSTA Call Agent Greeting, RecvCallAgentGreetingEventMsg: SENT TO OPC
    CallID = 33567498  DeviceID = 7591  DeviceType = Static
    EventCode = EC_AGENT_GREETING_STARTED GreetingType = 1 PeripheralErrorCode=0x0(0)
    12:11:56:917 PG1A-pim1 Trace: MsgCallAgentGreetingEvent: CallID=33567498 ConnDevID=7591/0 EventCode=1
    12:11:56:917 PG1A-pim1 Trace: CSTA Call Agent Greeting, RecvCallAgentGreetingEventMsg: SENT TO OPC
    CallID = 33567498  DeviceID = 7591  DeviceType = Static
    EventCode = EC_AGENT_GREETING_DONE GreetingType = 1 PeripheralErrorCode=0x0(0)
    12:12:00:103 PG1A-pim1 Trace: RTPStopped: CID=33567498, ConnDevID=7591/0, Addr=172.24.104.183:24636, Direction=IN, UniqueID=000000000000330A02C7D4D700000000
    12:12:00:103 PG1A-pim1 Trace: RTPStopped: CID=33567498, ConnDevID=7591/0, Addr=172.28.36.5:17006, Direction=OUT, UniqueID=000000000000330A02C7D4D700000000
    12:12:00:103 PG1A-pim1 Trace: ConnectionCleared: CID=33567498 ConnDevID=7591/0 ReleasingDev=7591/0 LocalConn=-1 Cause=-1UniqueID=000000000000330A02C7D4D700000000 DevTgDevStr=7591
    12:12:00:103 PG1A-pim1 Trace: CSTA CONNECTION CLEARED, TelephonyDriver::ConnectionCleared: SENT TO OPC
    CallID          = 33567498  DeviceID = 7591  DeviceType = Static
    ReleasingDevice = 7591
    LocalState      = NONE
    Cause           = EC_NONE
    12:12:00:103 PG1A-pim1 Trace: CallCleared: CID=33567498 ConnDevID=/0 LocalConn=-1 Cause=-1UniqueID=000000000000330A02C7D4D700000000 
    12:12:00:103 PG1A-pim1 Trace: CSTA CALL CLEARED, TelephonyDriver::CallCleared: SENT TO OPC
    CallID     = 33567498 DeviceID =   DeviceType = Static           LocalState = NONE
    Cause      = EC_NONE
    12:13:30:857 PG1A-pim1 Trace: ConfigureRoutingClient - PID=5000 RID=5000 Timeout=1500 Late=500 Limit=10 ConfigStr=
    12:13:30:857 PG1A-pim1 Trace: DeskLinkPeripheral::ProcessRCConfig() RCTimoutThreshold=0

  • Too  Slow - Domino 6.5.4  with access manager agent 2.2 ?

    I don't know how to tune Domino 6.5.4 with access manager agent 2.2?
    I think AMAgent.properties is not good for SSO.
    Please help me to tune it.
    # $Id: AMAgent.properties,v 1.103 2005/09/19 22:08:34 madan Exp $
    # Copyright ? 2002 Sun Microsystems, Inc. All rights reserved.
    # U.S. Government Rights - Commercial software. Government users are
    # subject to the Sun Microsystems, Inc. standard license agreement and
    # applicable provisions of the FAR and its supplements. Use is subject to
    # license terms. Sun, Sun Microsystems, the Sun logo and Sun ONE are
    # trademarks or registered trademarks of Sun Microsystems, Inc. in the
    # U.S. and other countries.
    # Copyright ? 2002 Sun Microsystems, Inc. Tous droits r閟erv閟.
    # Droits du gouvernement am閞icain, utlisateurs gouvernmentaux - logiciel
    # commercial. Les utilisateurs gouvernmentaux sont soumis au contrat de
    # licence standard de Sun Microsystems, Inc., ainsi qu aux dispositions en
    # vigueur de la FAR [ (Federal Acquisition Regulations) et des suppl閙ents
    # ? celles-ci.
    # Distribu? par des licences qui en restreignent l'utilisation. Sun, Sun
    # Microsystems, le logo Sun et Sun ONE sont des marques de fabrique ou des
    # marques d閜os閑s de Sun Microsystems, Inc. aux Etats-Unis et dans
    # d'autres pays.
    # The syntax of this file is that of a standard Java properties file,
    # see the documentation for the java.util.Properties.load method for a
    # complete description. (CAVEAT: The SDK in the parser does not currently
    # support any backslash escapes except for wrapping long lines.)
    # All property names in this file are case-sensitive.
    # NOTE: The value of a property that is specified multiple times is not
    # defined.
    # WARNING: The contents of this file are classified as an UNSTABLE
    # interface by Sun Microsystems, Inc. As such, they are subject to
    # significant, incompatible changes in any future release of the
    # software.
    # The name of the cookie passed between the Access Manager
    # and the SDK.
    # WARNING: Changing this property without making the corresponding change
    # to the Access Manager will disable the SDK.
    com.sun.am.cookie.name = iPlanetDirectoryPro
    # The URL for the Access Manager Naming service.
    com.sun.am.naming.url = http://sportal.yjy.dqyt.petrochina:80/amserver/namingservice
    # The URL of the login page on the Access Manager.
    com.sun.am.policy.am.login.url = http://sportal.yjy.dqyt.petrochina:80/amserver/UI/Login
    # Name of the file to use for logging messages.
    com.sun.am.policy.agents.config.local.log.file = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAgent
    # This property is used for Log Rotation. The value of the property specifies
    # whether the agent deployed on the server supports the feature of not. If set
    # to false all log messages are written to the same file.
    com.sun.am.policy.agents.config.local.log.rotate = true
    # Name of the Access Manager log file to use for logging messages to
    # Access Manager.
    # Just the name of the file is needed. The directory of the file
    # is determined by settings configured on the Access Manager.
    com.sun.am.policy.agents.config.remote.log = amAuthLog.Dominoad.yjy.dqyt.petrochina.80
    # Set the logging level for the specified logging categories.
    # The format of the values is
    #     <ModuleName>[:<Level>][,<ModuleName>[:<Level>]]*
    # The currently used module names are: AuthService, NamingService,
    # PolicyService, SessionService, PolicyEngine, ServiceEngine,
    # Notification, PolicyAgent, RemoteLog and all.
    # The all module can be used to set the logging level for all currently
    # none logging modules. This will also establish the default level for
    # all subsequently created modules.
    # The meaning of the 'Level' value is described below:
    #     0     Disable logging from specified module*
    #     1     Log error messages
    #     2     Log warning and error messages
    #     3     Log info, warning, and error messages
    #     4     Log debug, info, warning, and error messages
    #     5     Like level 4, but with even more debugging messages
    # 128     log url access to log file on AM server.
    # 256     log url access to log file on local machine.
    # If level is omitted, then the logging module will be created with
    # the default logging level, which is the logging level associated with
    # the 'all' module.
    # for level of 128 and 256, you must also specify a logAccessType.
    # *Even if the level is set to zero, some messages may be produced for
    # a module if they are logged with the special level value of 'always'.
    com.sun.am.log.level =
    # The org, username and password for Agent to login to AM.
    com.sun.am.policy.am.username = UrlAccessAgent
    com.sun.am.policy.am.password = LYnKyOIgdWt404ivWY6HPQ==
    # Name of the directory containing the certificate databases for SSL.
    com.sun.am.sslcert.dir = c:/Sun/Access_Manager/Agents/2.2/domino/cert
    # Set this property if the certificate databases in the directory specified
    # by the previous property have a prefix.
    com.sun.am.certdb.prefix =
    # Should agent trust all server certificates when Access Manager
    # is running SSL?
    # Possible values are true or false.
    com.sun.am.trust_server_certs = true
    # Should the policy SDK use the Access Manager notification
    # mechanism to maintain the consistency of its internal cache? If the value
    # is false, then a polling mechanism is used to maintain cache consistency.
    # Possible values are true or false.
    com.sun.am.notification.enable = true
    # URL to which notification messages should be sent if notification is
    # enabled, see previous property.
    com.sun.am.notification.url = http://Dominoad.yjy.dqyt.petrochina:80/amagent/UpdateAgentCacheServlet?shortcircuit=false
    # This property determines whether URL string case sensitivity is
    # obeyed during policy evaluation
    com.sun.am.policy.am.url_comparison.case_ignore = true
    # This property determines the amount of time (in minutes) an entry
    # remains valid after it has been added to the cache. The default
    # value for this property is 3 minutes.
    com.sun.am.policy.am.polling.interval=3
    # This property allows the user to configure the User Id parameter passed
    # by the session information from the access manager. The value of User
    # Id will be used by the agent to set the value of REMOTE_USER server
    # variable. By default this parameter is set to "UserToken"
    com.sun.am.policy.am.userid.param=UserToken
    # Profile attributes fetch mode
    # String attribute mode to specify if additional user profile attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user profile attributes will be introduced.
    # HTTP_HEADER - additional user profile attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user profile attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.profile.attribute.fetch.mode=NONE
    # The user profile attributes to be added to the HTTP header. The
    # specification is of the format ldap_attribute_name|http_header_name[,...].
    # ldap_attribute_name is the attribute in data store to be fetched and
    # http_header_name is the name of the header to which the value needs
    # to be assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.profile.attribute.map=cn|common-name,ou|organizational-unit,o|organization,mail|email,employeenumber|employee-
    number,c|country
    # Session attributes mode
    # String attribute mode to specify if additional user session attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user session attributes will be introduced.
    # HTTP_HEADER - additional user session attributes will be introduced into HTTP header.
    # HTTP_COOKIE - additional user session attributes will be introduced through cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.session.attribute.fetch.mode=NONE
    # The session attributes to be added to the HTTP header. The specification is
    # of the format session_attribute_name|http_header_name[,...].
    # session_attribute_name is the attribute in session to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.session.attribute.map=
    # Response Attribute Fetch Mode
    # String attribute mode to specify if additional user response attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user response attributes will be introduced.
    # HTTP_HEADER - additional user response attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user response attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.response.attribute.fetch.mode=NONE
    # The response attributes to be added to the HTTP header. The specification is
    # of the format response_attribute_name|http_header_name[,...].
    # response_attribute_name is the attribute in policy response to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.response.attribute.map=
    # The cookie name used in iAS for sticky load balancing
    com.sun.am.policy.am.lb.cookie.name = GX_jst
    # indicate where a load balancer is used for Access Manager
    # services.
    # true | false
    com.sun.am.load_balancer.enable = false
    ####Agent Configuration####
    # this is for product versioning, please do not modify it
    com.sun.am.policy.agents.config.version=2.2
    # Set the url access logging level. the choices are
    # LOG_NONE - do not log user access to url
    # LOG_DENY - log url access that was denied.
    # LOG_ALLOW - log url access that was allowed.
    # LOG_BOTH - log url access that was allowed or denied.
    com.sun.am.policy.agents.config.audit.accesstype = LOG_DENY
    # Agent prefix
    com.sun.am.policy.agents.config.agenturi.prefix = http://Dominoad.yjy.dqyt.petrochina:80/amagent
    # Locale setting.
    com.sun.am.policy.agents.config.locale = en_US
    # The unique identifier for this agent instance.
    com.sun.am.policy.agents.config.instance.name = unused
    # Do SSO only
    # Boolean attribute to indicate whether the agent will just enforce user
    # authentication (SSO) without enforcing policies (authorization)
    com.sun.am.policy.agents.config.do_sso_only = true
    # The URL of the access denied page. If no value is specified, then
    # the agent will return an HTTP status of 403 (Forbidden).
    com.sun.am.policy.agents.config.accessdenied.url =
    # This property indicates if FQDN checking is enabled or not.
    com.sun.am.policy.agents.config.fqdn.check.enable = true
    # Default FQDN is the fully qualified hostname that the users should use
    # in order to access resources on this web server instance. This is a
    # required configuration value without which the Web server may not
    # startup correctly.
    # The primary purpose of specifying this property is to ensure that if
    # the users try to access protected resources on this web server
    # instance without specifying the FQDN in the browser URL, the Agent
    # can take corrective action and redirect the user to the URL that
    # contains the correct FQDN.
    # This property is set during the agent installation and need not be
    # modified unless absolutely necessary to accommodate deployment
    # requirements.
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    # See also: com.sun.am.policy.agents.config.fqdn.check.enable,
    # com.sun.am.policy.agents.config.fqdn.map
    com.sun.am.policy.agents.config.fqdn.default = Dominoad.yjy.dqyt.petrochina
    # The FQDN Map is a simple map that enables the Agent to take corrective
    # action in the case where the users may have typed in an incorrect URL
    # such as by specifying partial hostname or using an IP address to
    # access protected resources. It redirects the browser to the URL
    # with fully qualified domain name so that cookies related to the domain
    # are received by the agents.
    # The format for this property is:
    # com.sun.am.policy.agents.config.fqdn.map = [invalid_hostname|valid_hostname][,...]
    # This property can also be used so that the agents use the name specified
    # in this map instead of the web server's actual name. This can be
    # accomplished by doing the following.
    # Say you want your server to be addressed as xyz.hostname.com whereas the
    # actual name of the server is abc.hostname.com. The browsers only knows
    # xyz.hostname.com and you have specified polices using xyz.hostname.com at
    # the Access Manager policy console, in this file set the mapping as
    # com.sun.am.policy.agents.fqdn.map = valid|xyz.hostname.com
    # Another example is if you have multiple virtual servers say rst.hostname.com,
    # uvw.hostname.com and xyz.hostname.com pointing to the same actual server
    # abc.hostname.com and each of the virtual servers have their own policies
    # defined, then the fqdnMap should be defined as follows:
    # com.sun.am.policy.agents.fqdn.map = valid1|rst.hostname.com,valid2|uvw.hostname.com,valid3|xyz.hostname.com
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    com.sun.am.policy.agents.config.fqdn.map =
    # Cookie Reset
    # This property must be set to true, if this agent needs to
    # reset cookies in the response before redirecting to
    # Access Manager for Authentication.
    # By default this is set to false.
    # Example : com.sun.am.policy.agents.config.cookie.reset.enable=true
    com.sun.am.policy.agents.config.cookie.reset.enable=false
    # This property gives the comma separated list of Cookies, that
    # need to be included in the Redirect Response to Access Manager.
    # This property is used only if the Cookie Reset feature is enabled.
    # The Cookie details need to be specified in the following Format
    # name[=value][;Domain=value]
    # If "Domain" is not specified, then the default agent domain is
    # used to set the Cookie.
    # Example : com.sun.am.policy.agents.config.cookie.reset.list=LtpaToken,
    # token=value;Domain=subdomain.domain.com
    com.sun.am.policy.agents.config.cookie.reset.list=
    # This property gives the space separated list of domains in
    # which cookies have to be set in a CDSSO scenario. This property
    # is used only if CDSSO is enabled.
    # If this property is left blank then the fully qualified cookie
    # domain for the agent server will be used for setting the cookie
    # domain. In such case it is a host cookie instead of a domain cookie.
    # Example : com.sun.am.policy.agents.config.cookie.domain.list=.sun.com .iplanet.com
    com.sun.am.policy.agents.config.cookie.domain.list=
    # user id returned if accessing global allow page and not authenticated
    com.sun.am.policy.agents.config.anonymous_user=anonymous
    # Enable/Disable REMOTE_USER processing for anonymous users
    # true | false
    com.sun.am.policy.agents.config.anonymous_user.enable=false
    # Not enforced list is the list of URLs for which no authentication is
    # required. Wildcards can be used to define a pattern of URLs.
    # The URLs specified may not contain any query parameters.
    # Each service have their own not enforced list. The service name is suffixed
    # after "# com.sun.am.policy.agents.notenforcedList." to specify a list
    # for a particular service. SPACE is the separator between the URL.
    com.sun.am.policy.agents.config.notenforced_list = http://dominoad.yjy.dqyt.petrochina/*.nsf http://dominoad.yjy.dqyt.petrochina/teamroom.nsf/TROutline.gif?
    OpenImageResource http://dominoad.yjy.dqyt.petrochina/icons/*.gif
    # Boolean attribute to indicate whether the above list is a not enforced list
    # or an enforced list; When the value is true, the list means enforced list,
    # or in other words, the whole web site is open/accessible without
    # authentication except for those URLs in the list.
    com.sun.am.policy.agents.config.notenforced_list.invert = false
    # Not enforced client IP address list is a list of client IP addresses.
    # No authentication and authorization are required for the requests coming
    # from these client IP addresses. The IP address must be in the form of
    # eg: 192.168.12.2 1.1.1.1
    com.sun.am.policy.agents.config.notenforced_client_ip_list =
    # Enable POST data preservation; By default it is set to false
    com.sun.am.policy.agents.config.postdata.preserve.enable = false
    # POST data preservation : POST cache entry lifetime in minutes,
    # After the specified interval, the entry will be dropped
    com.sun.am.policy.agents.config.postcache.entry.lifetime = 10
    # Cross-Domain Single Sign On URL
    # Is CDSSO enabled.
    com.sun.am.policy.agents.config.cdsso.enable=false
    # This is the URL the user will be redirected to for authentication
    # in a CDSSO Scenario.
    com.sun.am.policy.agents.config.cdcservlet.url =
    # Enable/Disable client IP address validation. This validate
    # will check if the subsequent browser requests come from the
    # same ip address that the SSO token is initially issued against
    com.sun.am.policy.agents.config.client_ip_validation.enable = false
    # Below properties are used to define cookie prefix and cookie max age
    com.sun.am.policy.agents.config.profile.attribute.cookie.prefix = HTTP_
    com.sun.am.policy.agents.config.profile.attribute.cookie.maxage = 300
    # Logout URL - application's Logout URL.
    # This URL is not enforced by policy.
    # if set, agent will intercept this URL and destroy the user's session,
    # if any. The application's logout URL will be allowed whether or not
    # the session destroy is successful.
    com.sun.am.policy.agents.config.logout.url=
    #http://sportal.yjy.dqyt.petrochina/amserver/UI/Logout
    # Any cookies to be reset upon logout in the same format as cookie_reset_list
    com.sun.am.policy.agents.config.logout.cookie.reset.list =
    # By default, when a policy decision for a resource is needed,
    # agent gets and caches the policy decision of the resource and
    # all resource from the root of the resource down, from the Access Manager.
    # For example, if the resource is http://host/a/b/c, the the root of the
    # resource is http://host/. This is because more resources from the
    # same path are likely to be accessed subsequently.
    # However this may take a long time the first time if there
    # are many many policies defined under the root resource.
    # To have agent get and cache the policy decision for the resource only,
    # set the following property to false.
    com.sun.am.policy.am.fetch_from_root_resource = true
    # Whether to get the client's hostname through DNS reverse lookup for use
    # in policy evaluation.
    # It is true by default, if the property does not exist or if it is
    # any value other than false.
    com.sun.am.policy.agents.config.get_client_host_name = false
    # The following property is to enable native encoding of
    # ldap header attributes forwarded by agents. If set to true
    # agent will encode the ldap header value in the default
    # encoding of OS locale. If set to false ldap header values
    # will be encoded in UTF-8
    com.sun.am.policy.agents.config.convert_mbyte.enable = false
    #When the not enforced list or policy has a wildcard '*' character, agent
    #strips the path info from the request URI and uses the resulting request
    #URI to check against the not enforced list or policy instead of the entire
    #request URI, in order to prevent someone from getting access to any URI by
    #simply appending the matching pattern in the policy or not enforced list.
    #For example, if the not enforced list has the value http://host/*.gif,
    #stripping the path info from the request URI will prevent someone from
    #getting access to http://host/index.html by using the URL http://host/index.html?hack.gif.
    #However when a web server (for exmample apache) is configured to be a reverse
    #proxy server for a J2EE application server, path info is interpreted in a different
    #manner since it maps to a resource on the proxy instead of the app server.
    #This prevents the not enforced list or policy from being applied to part of
    #the URI below the app serverpath if there is a wildcard character. For example,
    #if the not enforced list has value http://host/webapp/servcontext/* and the
    #request URL is http://host/webapp/servcontext/example.jsp the path info
    #is /servcontext/example.jsp and the resulting request URL with path info stripped
    #is http://host/webapp, which will not match the not enforced list. By setting the
    #following property to true, the path info will not be stripped from the request URL
    #even if there is a wild character in the not enforced list or policy.
    #Be aware though that if this is set to true there should be nothing following the
    #wildcard character '*' in the not enforced list or policy, or the
    #security loophole described above may occur.
    com.sun.am.policy.agents.config.ignore_path_info = false
    # Override the request url given by the web server with
    # the protocol, host or port of the agent's uri specified in
    # the com.sun.am.policy.agents.agenturiprefix property.
    # These may be needed if the agent is sitting behind a ssl off-loader,
    # load balancer, or proxy, and either the protocol (HTTP scheme),
    # hostname, or port of the machine in front of agent which users go through
    # is different from the agent's protocol, host or port.
    com.sun.am.policy.agents.config.override_protocol =
    com.sun.am.policy.agents.config.override_host =
    com.sun.am.policy.agents.config.override_port =
    # Override the notification url in the same way as other request urls.
    # Set this to true if any one of the override properties above is true,
    # and if the notification url is coming through the proxy or load balancer
    # in the same way as other request url's.
    com.sun.am.policy.agents.config.override_notification.url =
    # The following property defines how long to wait in attempting
    # to connect to an Access Manager AUTH server.
    # The default value is 2 seconds. This value needs to be increased
    # when receiving the error "unable to find active Access Manager Auth server"
    com.sun.am.policy.agents.config.connection_timeout =
    # Time in milliseconds the agent will wait to receive the
    # response from Access Manager. After the timeout, the connection
    # will be drop.
    # A value of 0 means that the agent will wait until receiving the response.
    # WARNING: Invalid value for this property can result in
    # the resources becoming inaccessible.
    com.sun.am.receive_timeout = 0
    # The three following properties are for IIS6 agent only.
    # The two first properties allow to set a username and password that will be
    # used by the authentication filter to pass the Windows challenge when the Basic
    # Authentication option is selected in Microsoft IIS 6.0. The authentication
    # filter is named amiis6auth.dll and is located in
    # Agent_installation_directory/iis6/bin. It must be installed manually on
    # the web site ("ISAPI Filters" tab in the properties of the web site).
    # It must also be uninstalled manually when unintalling the agent.
    # The last property defines the full path for the authentication filter log file.
    com.sun.am.policy.agents.config.iis6.basicAuthentication.username =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.password =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.logFile = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAuthFilter

    Hi,
    I installed opensso (so Sun Java(TM) System Access Manager 7.5) and the agent for Domino 6.5.4 and I have the message in logs "amAgent"
    2007-07-11 18:40:16.119 Error 1708:3dbcf768 PolicyAgent: render_response(): Entered.
    I have the box to identify but it doesnot connect me on my opensso server.
    It still identify with Domino's server
    Thanks for your response
    Thomas

  • ApplicationUnderTest.CloseOnPlaybackCleanup property doesn't work as intended with MS Test Agent 2010

    Hi All, 
    I launch the application which I need to test by using ApplicationUnderTest.Launch() method and I need to keep the application open for the rest of the tests so I tried to set ApplicationUnderTest.CloseOnPlaybackCleanup = false to achieve that. 
    1) I use MS Test Agent 2010 to run my Coded UI Tests in a server machine and without running tests it threw an error which said "Method not found: 'Void Microsoft.VisualStudio.TestTools.UITesting.ApplicationUnderTest.set_CloseOnPlaybackCleanup(Boolean)".
    Then I replaced UITesting.dll in the server machine with the one used by Visual Studio 2010 SP 1 which is located in my machine. Then it started to run tests. 
    2) Even though I have set  ApplicationUnderTest.CloseOnPlaybackCleanup = false Coded UI Test closes the application at the end of the test which was really strange. It sounds like that disregard
    of the value I have set, CUIT always close the application when running with MS Test Agent. 
    3) Then I noticed that on my machine it happens completely other way around most of the time. Irrelevant of the value it always keep the application open after the test. Which means even I set  ApplicationUnderTest.CloseOnPlaybackCleanup = true that
    will keep open the application. But if I can remember correctly this didnt happen when I first tried this approach, it worked perfectly. 
    Is this a a bug that should be fixed? Or am I missing something obvious?
    Thanks in advance, 
    /Rakitha

    Hi Rakitha,
    As far as I know, this issue has been resolved in VS2012.
    http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/08/using-same-applicationundertest-browserwindow-across-multiple-tests.aspx
    Best Regards,
    Jack
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Issue with re-skilling agents in bulk

    We tried to re-skill about 30 agents in bulk and change the competence level at the same time. Uccx took the change but, we noticed that agents were in a ready state even with calls were in the queue.
    We went back and one by one re-skilled them again and at that point I'm told it worked...agents received calls.
    Anyone ever had any issues with re-skilling agents in bulk?
    We are on UCCX 8.5.1 SU3
    Thanks,
    Dan

    Hi PARADOX-RED,
    Based on the error messages that you provided, please remove the connector software from Control Panel completely. Then, in the problematic computer, please locate
    to: Control Panel-> System-> select Change settings. And select the Computer Name tab in the System Properties dialog box, click
    change button. Then in the Computer Name/Domain Changes dialog box, please take the computer out of the domain as a workgroup, and rejoin in new domain.
    Please check if this issue can be solved. If it still exists, please don’t hesitate to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

Maybe you are looking for

  • Function extension vs override

    Hi everybody, First of all, I know it's possible to override the function and from there to call the function in the parent class. This is just to let you know that this is not a topic based on a whim or fancy. My question is, is there anybody out th

  • How to make spatial computations use more/all CPU power?

    Hi, In an service I'm calculating spatial data (using Microsoft.SqlServer.Types) in memory. These calculations often take 4-5 minutes but they are never, ever, using more than 50% CPU. I have tried this on a single core too (Azure) and still, CPU won

  • How to send embedded code to RightFax

    Dear All, I need to send a SAPscript form with RightFax embedded code to spool output. I add the following command in SAPscript form:- /: PRINT-CONTROL <WHO:ADMINISTRATOR> /: PRINT-CONTROL <RFSAP_TONAME:123> /: PRINT-CONTROL <RFSAP_TOCOMPANY:ABC> /:

  • My new Mini locks up daily.  Applecare thinks its 3rd party software, any guesses?

    I have completed a full erase and restore. Mac seemed to work fine. Then, I re-installed a minimum number of programs.  Mini is locking up again.  Are any of the following programs known for stalling out the OS? Spotify Pages Keynote Dropbox Logos bi

  • On linux, Acrobat Reader will not open files on SMB server

    I try double clicking a file on a network SMB server in Nautilus on Ubuntu and Acrobat reader starts but does not open the file. What's going on? Alex