cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
469
Views
0
Helpful
5
Replies
Beginner

CTI Port as Silent Monitoring Initiator

Hi,

i am trying to use CTIPort as Monitor Initiator rather than IP phones. I believe CTIPort can be used. I get error as below. Please advise.

2018/05/30 10:08:06.457 EDT,INFO,Call event: 108, State: ACTIVE, Cause: CAUSE_DEST_NOT_OBTAINABLE, Addr: 5140001130[ state: FAILED] , callid: 44769/1, conf call? false

2018/05/30 10:08:06.457 EDT,INFO,Calling Terminal: RSMCTIPort

2018/05/30 10:08:07.419 EDT,INFO,Call event: 103, State: ACTIVE, Cause: CAUSE_NORMAL, Addr: 5140001100[ state: CONNECTED] 2xxxxxxxxx [ state: CONNECTED] , callid: 44768/1, conf call? false

2018/05/30 10:08:07.420 EDT,INFO,Calling Terminal: RSMCTIPort

2018/05/30 10:08:07.420 EDT,INFO,Call Object: (P1-jtapiuser) GCID=(1,44769)->ACTIVE

2018/05/30 10:08:07.420 EDT,INFO,Call Active: 33

2018/05/30 10:08:07.420 EDT,INFO,Call event: 103, State: ACTIVE, Cause: CAUSE_NORMAL, Addr: 5140001130[ state: FAILED] , callid: 44769/1, conf call? false

com.cisco.jtapi.InvalidPartyExceptionImpl: Invalid monitor destination.

    at com.cisco.jtapi.CallImpl.startMonitor(CTQF)

    at com.cisco.jtapi.CallImpl.startMonitor(CTQF)

Note: I am able to establish call connection between CTIPort and IPPhones

Thank You

Everyone's tags (1)
5 REPLIES 5
Beginner

Re: CTI Port as Silent Monitoring Initiator

Adding JTAPI Logs:

370: May 31 17:55:11.929 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.queueEvents: queuing asynchronously

371: May 31 17:55:11.929 EDT %JTAPI-JTAPI-7-UNK:[5140001130:ALL-P-GLOBAL-DEVICES:1]Request: addCallObserver(test.CTIPort@7bacb9c3)

372: May 31 17:55:11.929 EDT %JTAPI-JTAPIIMPL-7-UNK:RSMCTIPort deviceInService(): This terminal: name=RSMCTIPort, isOpen=true. This device: Type=72, RegistrationType=2, isRegistered=true, isRegisteredExtendByThisApp=false, Protocol=1, isOpen=true

373: May 31 17:55:11.929 EDT %JTAPI-CTIIMPL-7-UNK:(P1-10.38.244.135) EventThread handling event com.cisco.cti.protocol.LineInServiceEvent[27]

374: May 31 17:55:11.929 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser)[ObserverThread(test.CTIPort@7bacb9c3)][RSMCTIPort]Request: getObservers()

375: May 31 17:55:11.929 EDT %JTAPI-JTAPIIMPL-7-UNK:Address [RSMCTIPort:5140001130:ALL-P-GLOBAL-DEVICES:(1,14320)]  in service

376: May 31 17:55:11.929 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser)[ObserverThread(test.CTIPort@7bacb9c3)][RSMCTIPort]Request: getCallObservers()

377: May 31 17:55:11.929 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser) [5140001130:ALL-P-GLOBAL-DEVICES] CiscoAddrInServiceEv [#47] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12

378: May 31 17:55:11.929 EDT %JTAPI-JTAPI-7-UNK:[5140001130:ALL-P-GLOBAL-DEVICES:1]Request: getObservers

379: May 31 17:55:11.929 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.queueEvents: queuing asynchronously

380: May 31 17:55:11.929 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser)[ObserverThread(test.CTIPort@7bacb9c3)][5140001130:ALL-P-GLOBAL-DEVICES:1]Request: getCallObservers()

381: May 31 17:55:11.929 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser)[ObserverThread(test.CTIPort@7bacb9c3)][5140001130:ALL-P-GLOBAL-DEVICES:1]Request: getCallObservers()

382: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.deliverEvents() completed

383: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:ObserverThread(test.CTIPort@7bacb9c3): delivering JAES[1]

384: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.deliverEvents()

385: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]delivering to addressChangedEvent

386: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.deliverEvents() completed

387: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:ObserverThread(test.CTIPort@7bacb9c3): delivering JAES[1]

388: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.deliverEvents()

389: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]delivering to addressChangedEvent

390: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:Request:getAutoAcceptStatus: Terminal=RSMCTIPort

391: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:Request:getAutoAcceptStatus: Address=RSMCTIPort:5140001130:ALL-P-GLOBAL-DEVICES:(1,14320)

392: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:[5140001130:ALL-P-GLOBAL-DEVICES:1]Request: setAutoAcceptStatus 1Terminal=RSMCTIPort

393: May 31 17:55:11.939 EDT %JTAPI-JTAPIIMPL-7-UNK:Request:setAutoAcceptStatus: Address=RSMCTIPort:5140001130:ALL-P-GLOBAL-DEVICES:(1,14320)

394: May 31 17:55:11.979 EDT %JTAPI-CTIIMPL-7-UNK:(P1-10.38.244.135) EventThread handling event com.cisco.cti.protocol.LineAutoAcceptStatusEvent[28]

395: May 31 17:55:11.979 EDT %JTAPI-JTAPIIMPL-7-UNK:Address [RSMCTIPort:5140001130:ALL-P-GLOBAL-DEVICES:(1,14320)] AutoAcceptStatusChanged: Status =1

396: May 31 17:55:11.979 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.deliverEvents() completed

397: May 31 17:55:11.979 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser) [5140001130:ALL-P-GLOBAL-DEVICES] CiscoAddrAutoAcceptStatusChangedEv [#48] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12

398: May 31 17:55:11.979 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.queueEvents: queuing asynchronously

399: May 31 17:55:11.979 EDT %JTAPI-JTAPIIMPL-7-UNK:ObserverThread(test.CTIPort@7bacb9c3): delivering JAES[1]

400: May 31 17:55:11.979 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.deliverEvents()

401: May 31 17:55:11.979 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]delivering to addressChangedEvent

402: May 31 17:55:11.979 EDT %JTAPI-JTAPIIMPL-7-UNK:[test.CTIPort@7bacb9c3]ObserverProxy.deliverEvents() completed

403: May 31 17:55:12.429 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser)[main][(P1-jtapiuser) GCID=(1,44850)->IDLE]Request: startMonitor ([SEP5140001100/[5140001100:ALL-P-GLOBAL-DEVICES:1/(P1-jtapiuser) GCID=(1,44849)->ACTIVE]->ESTABLISHED]->TALKING)

404: May 31 17:55:12.429 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser)[main][(P1-jtapiuser) GCID=(1,44850)->IDLE]Request: startMonitor (RSMCTIPort, 5140001130 , 18670808, 5140001100, SEP5140001100, 1 3

405: May 31 17:55:12.479 EDT %JTAPI-CTIIMPL-7-UNK:(P1-10.38.244.135) EventThread handling event com.cisco.cti.protocol.NewCallEvent[29]

406: May 31 17:55:12.479 EDT %JTAPI-JTAPIIMPL-7-UNK:(P1-jtapiuser) getCallManager() Found existing CallManager

407: May 31 17:55:12.479 EDT %JTAPI-JTAPIIMPL-7-UNK:CallInfo for = (P1-jtapiuser) GCID=(1,44850)->IDLE CurIng :5140001130:ALL-P-GLOBAL-DEVICES:1 Cured :null LRP :null ing :5140001130:ALL-P-GLOBAL-DEVICES:1 ed :null ModEd :null Moding :5140001130:ALL-P-GLOBAL-DEVICES:1

408: May 31 17:55:12.479 EDT %JTAPI-JTAPI-7-UNK:[(P1-jtapiuser) GCID=(1,44850)->IDLE]InvalidPartyExceptionImpl caught: Invalid monitor destination.

409: May 31 17:55:12.479 EDT %JTAPI-JTAPI-7-UNK:[[5140001130:ALL-P-GLOBAL-DEVICES:1/(P1-jtapiuser) GCID=(1,44850)->INVALID]->IDLE]creating internal connection for 5140001130:ALL-P-GLOBAL-DEVICES:1

410: May 31 17:55:12.479 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser) 44850/1 ConnCreatedEv 5140001130:ALL-P-GLOBAL-DEVICES:1 [#49] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12

411: May 31 17:55:12.479 EDT %JTAPI-JTAPI-7-UNK:{ CcnCall=Call:[GCID=(44850/1),CID=18670809] Connection=[5140001130:ALL-P-GLOBAL-DEVICES:1/(P1-jtapiuser) GCID=(1,44850)->INVALID]->IDLE: creating new Connection for CCNCall }

412: May 31 17:55:12.479 EDT %JTAPI-JTAPIIMPL-7-UNK:{(P1-jtapiuser) GCID=(1,44850)->INVALID} Initializing to DIALTONE for 5140001130:ALL-P-GLOBAL-DEVICES:1

413: May 31 17:55:12.479 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser) 44850/1 ConnConnectedEv 5140001130:ALL-P-GLOBAL-DEVICES:1 [#50] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:12

414: May 31 17:55:12.479 EDT %JTAPI-JTAPI-7-UNK:(P1-jtapiuser) 44850/1 CallCtlConnInitiatedEv 5140001130:ALL-P-GLOBAL-DEVICES:1 [#51] Cause:100 CallCtlCause:100 CiscoCause:0 FeatReason:12

415: May 31 17:55:12.479 EDT %JTAPI-JTAPIIMPL-7-UNK:Adding CCNCall Call:[GCID=(44850/1),CID=18670809] to TermConn:[RSMCTIPort/[5140001130:ALL-P-GLOBAL-DEVICES:1/(P1-jtapiuser) GCID=(1,44850)->INVALID]->INITIATED]->IDLE

Contributor

Re: CTI Port as Silent Monitoring Initiator

Are you able to dial monitored phone from CTI Port?

Regards,

Umesh

Beginner

Re: CTI Port as Silent Monitoring Initiator

Hi Umesh,

Yes. I am able to make calls from CTI port to another CIPC / SIP phone.

Thanks

Mayil

Highlighted
Contributor

Re: CTI Port as Silent Monitoring Initiator

Please check your CTI Port CSS. Agent number should be valid and reachable from CTI Port DN.

Regards,

Umesh

Beginner

Re: CTI Port as Silent Monitoring Initiator

Here the call log between Agent and CTI Port in a normal call scenario. 5140001130 - is CTI Port DN and 5140001100 is Agent device.

CSS is set to MONITOREDDEVICES for all agent devices and CTI Port as well.

2018/05/29 18:30:07.408 EDT,INFO, Got CTI Port terminal:: RSMCTIPort
2018/05/29 18:30:07.499 EDT,INFO, TerminalChangedEvent Invoked

2018/05/29 18:30:07.499 EDT,INFO,Connection to terminal: RSMCTIPort is TERMINAL OUT OF SERVICE
2018/05/29 18:30:07.859 EDT,INFO, TerminalChangedEvent Invoked

2018/05/29 18:30:07.859 EDT,INFO,Connection to terminal: RSMCTIPort is TERMINAL IN SERVICE
2018/05/29 18:30:07.859 EDT,INFO,terminal RSMCTIPort has 1 terminal observers and 1 callobservers
2018/05/29 18:30:07.859 EDT,INFO,address 5140001130 has 1 address observers and 1 callobservers
2018/05/29 18:30:07.869 EDT,INFO,AddressChangeEvent Invoked..

2018/05/29 18:30:07.869 EDT,INFO,CiscoAddrEv activated
2018/05/29 18:30:07.869 EDT,INFO,CiscoAddress out of service: 5140001130
2018/05/29 18:30:07.869 EDT,INFO,AddressChangeEvent Invoked..

2018/05/29 18:30:07.869 EDT,INFO,CiscoAddrEv activated
2018/05/29 18:30:07.910 EDT,INFO,AutoAccept set for address 5140001130
2018/05/29 18:30:07.910 EDT,INFO,CiscoAddress in service: 5140001130
2018/05/29 18:30:07.910 EDT,INFO,AddressChangeEvent Invoked..

2018/05/29 18:30:07.910 EDT,INFO,CiscoAddrEv activated
2018/05/29 18:30:07.910 EDT,INFO,AutoAccept status changed on address 5140001130
2018/05/29 18:30:29.856 EDT,INFO,CallChangedEvent Invoked

2018/05/29 18:30:29.856 EDT,INFO,CALL ACTIVE on Address: 5140001130
2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001130 is CREATED
2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001130 is INPROGRESS
2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001130 is CallCtlConnOfferedEv
2018/05/29 18:30:29.856 EDT,INFO,5140001130is OFFERED!!!
2018/05/29 18:30:29.856 EDT,INFO,Exception accepting 5140001130 Did not meet pre-conditions.
2018/05/29 18:30:29.856 EDT,INFO,Error in pre-conditions check if autoPickup is false in CM service parameters configurations
2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001100 is CREATED
2018/05/29 18:30:29.856 EDT,INFO,CallChangedEvent Invoked

2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001100 is CONNECTED
2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001100 is CallCtlConnEstablishedEv
2018/05/29 18:30:29.856 EDT,INFO,CallChangedEvent Invoked

2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001130 is ALERTING
2018/05/29 18:30:29.856 EDT,INFO,Connection to address: 5140001130 is CallCtlConnAlertingEv
2018/05/29 18:30:29.856 EDT,INFO,CallCtlTermConnEv: RSMCTIPort is  Ringing
2018/05/29 18:30:39.929 EDT,INFO,CallChangedEvent Invoked

2018/05/29 18:30:39.929 EDT,INFO,Connection to address: 5140001130 is CONNECTED
2018/05/29 18:30:39.929 EDT,INFO,Connection to address: 5140001130 is CallCtlConnEstablishedEv
2018/05/29 18:30:39.929 EDT,INFO,CallCtlTermConnEv: RSMCTIPort is  Talking
2018/05/29 18:30:39.929 EDT,INFO, TerminalChangedEvent Invoked

2018/05/29 18:30:39.929 EDT,INFO,Connection to terminal: RSMCTIPort is RECEIVING RTP STARTED

2018/05/29 18:30:39.929 EDT,INFO, CTI Port RTP packet size 20
2018/05/29 18:30:39.929 EDT,INFO, CTI Port  MediaConnectionMode  : TRANSMIT_AND_RECEIVE
2018/05/29 18:30:39.939 EDT,INFO,RTPInput Local IP: 10.99.0.124 RTPInput Local Port: 12345 Cisco GlobalCallID: 44758

Thanks

Mayil

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards