Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega Call CTI : How to change Routing type

SA-11076

Summary



User requires to know if they can change this Routing type to Route Request instead of Adjunct Request for the transferring of calls.


Resolution



For BlindTransfer, copy the ChannelServices-Device-Phone-UI. BlindTransfer activity into a custom ruleset.
  •          Modify the following in the BlindTransfer activity:
    •    For Step 2 (call to parent Blind Transfer) expand to see the parameters being passed in.
    •    Add  <PostRoute>true</PostRoute> to the XMLParams.  It should look like:
      •   “<pagedata><CallData><userOldCallId>" + .pyCTILinkSession.pyLinkDefinition.pySiteID + Param.CallId + "</userOldCallId></CallData><PostRoute>true</PostRoute></pagedata>”
    •    Save and test it.
  •          Modify  the other activities that support PostRoute as required by adding “<PostRoute>true</PostRoute>” to the XMLParms. 
The activities that support PostRoute are:
  •    ChannelServices-Device-Phone-UI.MakeCall
  •    ChannelServices-Device-Phone-UI.TransferInitiate
  •    ChannelServices-Device-Phone-UI.BlindTransfer
 
 
Verify the post route setting in the engine log for when it creates the request message. The debug log message for blind transfer that shows the post route flag.
 
Example Log Message only:
- Created Transfer Call Request for extension [6410] dialed Number [6415] active call id [5445] held call id [-1] peripheral id [5000] post route flag [false] number of named variables [3]

 
Suggest Edit

Published July 13, 2015 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us