Blogs

Check out the new content on the Cisco Developer Network reflecting the New & Enhanced features in Cisco Unified Communication Manager 9.1.
See the new 9.1 TAPI Documentation ...Read More

 

The Unified Communications 9.0 Partner Bundle packages Cisco’s Collaboration application software for our Collaboration partner community to leverage for their internal lab or demonstration systems. The 9.0 version is now available for order. Learn More >> ...Read More

 

Cisco TAPI Developers:

Check out the new content on the Cisco Developer Network reflecting the New & Enhanced features in Cisco Unified Communication Manager 9.0(1).

...Read More

 

Developer Partners,

Cisco announces the availability of our 2012 Developer Partner presentations shared at CiscoLive San Diego.

Please log into the Cisco Developer Network using your Partner UserID to download this content.

Access these presentations here: http://developer.cisco.com/web/cdc/devforumpreso PARTNER LOGIN REQUIRED
...Read More

 

Developer Partners,

Cisco announces the availability of our 2012 Developer Partner presentations shared at CiscoLive London.

Please log into the Cisco Developer Network using your Partner UserID to download this content.

Access these presentations here: http://developer.cisco.com/web/cdc/devforumpreso PARTNER LOGIN REQUIRED
...Read More

 

Showing 1 - 5 of 32 results.
Items per Page 5
of 7
First Previous Last

Forums

« Back to Cisco TAPI Questions

TAPI CTi Port Monitor

Combination View Flat View Tree View
Threads [ Previous | Next ]
TAPI CTi Port Monitor
Answer
7/5/12 11:52 AM
Hello everybody,
 
i have a question about line monitoring. I have a process that works as an IVR with TSP and Cisco Wave Driver. It opens a set of Cti Ports with Privileges = LINECALLPRIVILEGE_OWNER | LINECALLPRIVILEGE_MONITOR.
 
On the other side I have another process, executing on another server, that tries to open the same device with privileges = LINECALLPRIVILEGE_MONITOR, in order to monitor the activity on the port. This process fails to open the device with the error LINEERR_ALLOCATED, but i think there's something wrong somewhere, because the line open with monitor only privileges should never fail.
 
Anyone has hits about this problem?
 
I'm testing this feature with CM System version: 8.5.1.10000-26, TSP 8.5(1.7) 64 Bit in monitor server and TSP 8.5(1.4) 32 bits + Cisco Wave Driver in IVR server.
 
I tried to use different Application Users for TSP and same application user, but the result is always the same.
 
It works only if the 2 processes runs under the same TSP on the same machine.
Flag

RE: TAPI CTi Port Monitor
Answer
7/5/12 5:03 PM as a reply to Davide Cocchi.
Ok, i've found all documentation about 3rd party monitoring for CtiPorts, but the TSP returns LINEERR_OPERATIONFAILED in line reply message associated with lineDevSpecific async request. In the TSP log i've found a line with the message

*ERROR* Invalid msg type 0x00462390

Here the log of my application and TSP

L1 17:48.39.935 - [CSmInterface:emoticonnNewMessage] Party List Item
Party: 401
Type: STATION
SubType: TAPI_WAVE
L3 17:48.39.935 - [CTapiLine::GetLineMediaModes] [401] SupportedMedia [AUTOMATEDVOICE,INTERACTIVEVOICE]
L1 17:48.39.935 - [CTapiLine:emoticonpen]
Name: Cisco Line: [CTi-Port-401] (401)
lineNegotiateExtVersion 0x800b0000
L1 17:48.39.937 - [CTapiLine:emoticonpen]
Name: Cisco Line: [CTi-Port-401] (401)
lineDevSpecific RequestId = 0x000100b0 (65712)
L3 17:48.39.937 - [CTapiEnvironment::ThreadGetMessage] Event Signaled from TAPI
L3 17:48.39.937 - [CTapiRequest::AddRequest] Request [65712] Added
L5 17:48.39.937 - [CTapiEnvironment::ThreadGetMessage] Message Queued
Type: LINE_REPLY
dwCallbackInstance 15
dwParam1 0x100b0
dwParam2 0x80000048
dwParam3 0x0
hDevice 0
L2 17:48.39.945 - [CTapiEnvironment::ThreadProcessMessage]
Ext: 401
Message: LINE_REPLY
L3 17:48.39.995 - [CTapiLine:emoticonnCommandReply] Command NOT Executed LINEERR_OPERATIONFAILED

this is TSP Log:

17:48:39.935 |-->TSPI_lineDevSpecific()
17:48:39.935 | TSPI_lineDevSpecific()
dwRequestID = 0x000100B0
hdLine = 0x05FC2370
dwAddressID = 0x00000000
hdCall = 0x00000000
lpParams = 0x00B659E8
dwSize = 4
17:48:39.935 |-->SelsiusTSP::TSPI_lineDevSpecific(0x05FC2370)
17:48:39.935 |-->CSelsiusTSPLineList::IsValidTapiLineHandle()
17:48:39.935 | CSelsiusTSPLineList::IsValidTapiLineHandle() Found mapping for line(0x05FC2370) to lineHandle(0x00000000)
17:48:39.935 |<--CSelsiusTSPLineList::IsValidTapiLineHandle()
17:48:39.935 | SelsiusTSP::TSPI_lineDevSpecific(0x05FC2370) LineHandle=0x05FC2370,LineDir=401
17:48:39.935 |-->CSelsiusTSPLine:emoticonevSpecific() [0x00000000]
17:48:39.935 | CSelsiusTSPLine:emoticonevSpecific() [0x00000000] *ERROR* Invalid msg type 0x00462390
17:48:39.935 |<--CSelsiusTSPLine:emoticonevSpecific() [0x00000000]
17:48:39.935 |<--SelsiusTSP::TSPI_lineDevSpecific(0x05FC2370)
17:48:39.935 | TSPI_lineDevSpecific() TSPI_lineDevSpecific returns = 0x80000048
17:48:39.935 |<--TSPI_lineDevSpecific()
Flag

Collateral


No files available