Passing CPNDigits in AttributeExtensions on Alcatel

[gcollins]

executing

update extension add key CPNDigits = 888-888-8888
troute(routetypedefault,thisdn:x|otherdn:y)

in strategy running against RSI Alcatel Omni

result in the CPNDigits being overwritten.  It appears that a new call is generated by the switch that does not include the pdata:callerlineident:8888888888.

Anyway, if there are any Alcatel Tserver experts out there that could share how to pass CPN digits in the TRoute function I would be tickled to death.

Navy88@gmail.com

[cavagnaro]

CPNDigits is a KVP, how does Alcatel can change them?
This is available only from TServer A4400 7.5, which OXE version are you running?
Sorry the question, but, for what is used this option? I have seen it but never needed it.

[gcollins]

This client is using Proactive Interactin Routing where Push Preview Interaction are routed the GAD.  When the interaction is accepted they can push connect to dial the customer.

The requirement is to associated CPN digits to each campaign.  Unlike Progressive or Predictive Dialing the call is originated from the station not a routepoint/RSI.

The approach is to have the agents dial a routepoint that will assign a CPN based on some attached data and attach this to AttributeExtensions key CPNDigits=8884442222.  Then a troute would be executed to the external customer number with the CPN attached.

In summary the approach is to enable the client to dynamically assign CPN for outbound calls initiated from a station.

P.S.
CPNDigits does work with MakeCall but attaching the CPNDigits would require a modification to the baseline GAD code.

I guess this brings up another question .... can GAD be customized with this functionality via use of custom.xml and not the core GAD .jsps.

[gcollins]

Canagnaro,
Thank you for the reply.  CPNDigits can be passed to the Alcatel(ver. 7.6).

What happens in the logs is a RequestRouteCall is sent to the link and it generates a CSTA RouteSelectRequest with PData:CallLineIdent <the CPN i set in strategy>.

Then a new call is generated that is the outdial to the external number .. this new call does not include the PData:CallLineIdent.

Puzzled why the new leg of the call does not inherit the CPN/CallLineIdent.

Thanks for any help.