Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
773
Views
0
Helpful
1
Replies

Consultation Call with lineMakeCall at UCM 10.5, call is dropped

Axel Becker
Level 1
Level 1

‎07-28-2014 05:42 AM

We see an issue at our UCM 10.5 tests at the consultation call with lineSetupTransfer and lineMakecall.

As an option we use lineMakeCall at the consultation call instead of lineDial. We use line MakeCall to hide the dtmf dialing tones for the consultation device.

But at 10.5 UCM the consultation call is immediatly dropped after ringback. It worked fine from UCM 3.x to 10.0.

Is there a change regarding  lineSetupTransfer / lineMakecall at UCM 10.5?

Her is the Scenario:

own device 584, an inbound  call from 590 is established.
Try to make a consultation call to 583

...

TsTapi1  09:27:35.248   L3  TAPI-Event:2  cID:67529  P1:100  P2:1  P3:0 
TsTapi1  09:27:35.248   L3      hDevice 107c9  PBX Link: 1
TsTapi1  09:27:35.249   L3  Device: 584
TsTapi1  09:27:35.250   L3  CallInfo: Caller: 590 Called: 584 Connected: 590 
TsTapi1  09:27:35.250   L4  dwOrigin = 4   dwReason = 40
TsTapi1  09:27:35.251   L3  LINECALLSTATE_CONNECTED


TsTapi1  09:27:45.218   L3  CTelTapi::ConsultationCall
TsTapi1  09:27:45.218   L3  consultationDevice = 583
TsTapi1  09:27:45.219   L4  calling lineSetupTransfer
TsTapi1  09:27:45.223   L3  lineSetupTransfer requested   requestId=10541

TsTapi1  09:27:45.257   L3  TAPI-Event:2  cID:67529  P1:2000  P2:0  P3:0 
TsTapi1  09:27:45.258   L3      hDevice 107c9  PBX Link: 1
TsTapi1  09:27:45.271   L3  Device: 584
TsTapi1  09:27:45.273   L3  CallInfo: Caller: 590 Called: 585 Connected: 590
TsTapi1  09:27:45.273   L4  dwOrigin = 4   dwReason = 40
TsTapi1  09:27:45.274   L3  LINECALLSTATE_ONHOLDPENDTRANSFER


TsTapi1  09:27:45.287   L3  TAPI-Event:12  cID:0  P1:10541  P2:0  P3:103ee 
TsTapi1  09:27:45.287   L3      hDevice 0  PBX Link: 1
TsTapi1  09:27:45.288   L3  LINE_REPLY

TsTapi1  09:27:45.300   L3  TAPI-Event:2  cID:66542  P1:8  P2:20  P3:0 
TsTapi1  09:27:45.300   L3      hDevice 103ee  PBX Link: 1
TsTapi1  09:27:45.302   L3  Device: 584
TsTapi1  09:27:45.304   L3  CallInfo: Caller: 584 
TsTapi1  09:27:45.304   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.305   L3  LINECALLSTATE_DIALTONE


TsTapi1  09:27:45.307   L4  UseMakeCallOnConsultationCall=YES
TsTapi1  09:27:45.308   L4  lineMakeCall requested  requestId=107F1

TsTapi1  09:27:45.312   L3  TAPI-Event:2  cID:66542  P1:4000  P2:1  P3:0 
TsTapi1  09:27:45.312   L3      hDevice 103ee  PBX Link: 1
TsTapi1  09:27:45.314   L3  Device: 584
TsTapi1  09:27:45.316   L3  CallInfo: Caller: 584 
TsTapi1  09:27:45.317   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.317   L3  LINECALLSTATE_DISCONNECTED

TsTapi1  09:27:45.319   L4  Device State = 113
TsTapi1  09:27:45.320   L4  OnConnectionCleared !

TsTapi1  09:27:45.322   L3  TAPI-Event:2  cID:66542  P1:1  P2:0  P3:0 
TsTapi1  09:27:45.324   L3      hDevice 103ee  PBX Link: 1
TsTapi1  09:27:45.327   L3  Device: 584
TsTapi1  09:27:45.330   L3  CallInfo: Caller: 584 
TsTapi1  09:27:45.330   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.331   L3  LINECALLSTATE_IDLE

TsTapi1  09:27:45.341   L3  TAPI-Event:12  cID:0  P1:107f1  P2:0  P3:1077d 
TsTapi1  09:27:45.343   L3      hDevice 0  PBX Link: 1
TsTapi1  09:27:45.345   L3  LINE_REPLY

TsTapi1  09:27:45.360   L3  TAPI-Event:2  cID:67453  P1:10  P2:0  P3:0 
TsTapi1  09:27:45.360   L3      hDevice 1077d  PBX Link: 1
TsTapi1  09:27:45.363   L3  Device: 584
TsTapi1  09:27:45.365   L3  CallInfo: Caller: 584 Called: 583 
TsTapi1  09:27:45.366   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.367   L3  LINECALLSTATE_DIALING

TsTapi1  09:27:45.388   L3  TAPI-Event:2  cID:67453  P1:200  P2:0  P3:0 
TsTapi1  09:27:45.389   L3      hDevice 1077d  PBX Link: 1
TsTapi1  09:27:45.392   L3  Device: 584
TsTapi1  09:27:45.393   L3  CallInfo: Caller: 584 Called: 583 
TsTapi1  09:27:45.394   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.395   L3  LINECALLSTATE_PROCEEDING

TsTapi1  09:27:45.400   L3  TAPI-Event:23  cID:66457  P1:0  P2:103c3  P3:4 
TsTapi1  09:27:45.400   L3      hDevice 10399  PBX Link: 1
TsTapi1  09:27:45.401   L3  LINE_APPNEWCALL


TsTapi1  09:27:45.420   L3  TAPI-Event:2  cID:66499  P1:4  P2:0  P3:0 
TsTapi1  09:27:45.421   L3      hDevice 103c3  PBX Link: 1
TsTapi1  09:27:45.423   L3  Device: 583
TsTapi1  09:27:45.426   L3  CallInfo: Caller: 584 Called: 583 
TsTapi1  09:27:45.426   L4  dwOrigin = 2   dwReason = 1
TsTapi1  09:27:45.427   L3  LINECALLSTATE_ACCEPTED

TsTapi1  09:27:45.427   L3  TAPI-Event:8  cID:66457  P1:2  P2:0  P3:0 
TsTapi1  09:27:45.428   L3      hDevice 10399  PBX Link: 1
TsTapi1  09:27:45.429   L3  LINE_LINEDEVSTATE
TsTapi1  09:27:45.430   L3  Device: 583
TsTapi1  09:27:45.430   L3  RINGING

TsTapi1  09:27:45.434   L3  TAPI-Event:2  cID:67453  P1:20  P2:0  P3:0 
TsTapi1  09:27:45.434   L3      hDevice 1077d  PBX Link: 1
TsTapi1  09:27:45.436   L3  Device: 584
TsTapi1  09:27:45.438   L3  CallInfo: Caller: 584 Called: 583 
TsTapi1  09:27:45.438   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.439   L3  LINECALLSTATE_RINGBACK

now the call is dropped at ucm 10.5 ! 


TsTapi1  09:27:45.704   L3  TAPI-Event:2  cID:67453  P1:4000  P2:1  P3:0    LINEDISCONNECTMODE_NORMAL
TsTapi1  09:27:45.705   L3      hDevice 1077d  PBX Link: 1
TsTapi1  09:27:45.706   L3  Device: 584
TsTapi1  09:27:45.708   L3  CallInfo: Caller: 584 Called: 583 
TsTapi1  09:27:45.709   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.709   L3  LINECALLSTATE_DISCONNECTED

TsTapi1  09:27:45.720   L3  TAPI-Event:2  cID:67453  P1:1  P2:0  P3:0 
TsTapi1  09:27:45.722   L3      hDevice 1077d  PBX Link: 1
TsTapi1  09:27:45.725   L3  Device: 584
TsTapi1  09:27:45.728   L3  CallInfo: Caller: 584 Called: 583 
TsTapi1  09:27:45.730   L4  dwOrigin = 1   dwReason = 1
TsTapi1  09:27:45.731   L3  LINECALLSTATE_IDLE

Labels:
0 Helpful
1 Reply 1

Geevarghese Cheria
Cisco Employee
Cisco Employee

‎07-30-2014 01:45 AM

Hi,

In Cisco Unified Communications Manager, the Direct Transfer softkey lets users transfer the other end of one established call to the other end of another established call, while dropping the feature initiator from those two calls. Here, an established call refers to a call that is either in the on hold state or in the connected state. The "Direct Transfer" feature does not initiate a consultation call and does not put the active call on hold.

A TAPI application can invoke the "Direct Transfer" feature by using the TAPI lineCompleteTransfer() function on two calls that are already in the established state. This also means that the two calls do not have to be set up initially by using the lineSetupTransfer() function.

lineMakeCall: Beginning with Cisco Unified Communications Manager Release 10.01, applications can use lineMakeCall to create a Persistent Call or Announcement Call. For a Persistent Call or Announcement Call, the relevant data is provided in the LINECALLPARAMS structure pointed to by the lpLineCallParams parameter. All other lineMakeCall parameters are ignored in these cases

Reference - Features supported by TSP

Thanks and Regards,

Geevarghese

0 Helpful
Customers Also Viewed These Support Documents