Getting dialled digits in tapi

[Angus]

I have written a TAPI application which I am testing on Avaya IP Office and a Panasonic KX-NCP switches. The application calls lineGetCallInfo on receiving a call a retrieves CalledID. The CalledID is reported on both switches as the hunt group called. So in the switch dialling plan a number called might be 0800 123456 and this call might be directed to group 200. It is "200" which is reported as the CalledID. I have been asked to extract the digits actually dialled by the caller - eg the 0800123456 string. Should it be possible to extract the dialled number? If so how.

On the Avaya I get no events if I monitor a group but I do on the Panasonic. but even doing lineOpen on the Panasonic group I don't see the dialled number reported (it reports the group number in CalledID).

anyone got any ideas?

Angus

[Andreas Marschall [exMVP TAPI]]

Post by Angus
I have written a TAPI application which I am testing on Avaya IP Office and a Panasonic KX-NCP switches. The application calls lineGetCallInfo on receiving a call a retrieves CalledID. The CalledID is reported on both switches as the hunt group called. So in the switch dialling plan a number called might be 0800 123456 and this call might be directed to group 200. It is "200" which is reported as the CalledID. I have been asked to extract the digits actually dialled by the caller - eg the 0800123456 string. Should it be possible to extract the dialled number? If so how.
On the Avaya I get no events if I monitor a group but I do on the Panasonic. but even doing lineOpen on the Panasonic group I don't see the dialled number reported (it reports the group number in CalledID).

Angus,
ideally the CalledID would be "0800 123456" and the RedirectionID would be "200" in this scenario.
But of course depending on the call info that is actually available within the PBX this may vary. So it PBX and TSP dependent what IDs are actually available on TSPI / TAPI.
I guess it is best to check this issue with the PBX / TSP manufactures whether it is possible to provide more call info.

BTW I guess you have already checked all ID fields of LINECALLINFO struct whether any one actually represents the info of interest...
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My Toto® Tools (a collection of free, mostly TAPI related tools):
http://www.i-b-a-m.de/Andreas_Marschall's_Toto_Tools.htm
* Please post all messages and replies to the group so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.

[Angus]

Post by Andreas Marschall [exMVP TAPI]
ideally the CalledID would be "0800 123456" and the RedirectionID would be "200" in this scenario.
But of course depending on the call info that is actually available within the PBX this may vary. So it PBX and TSP dependent what IDs are actually available on TSPI / TAPI.
I guess it is best to check this issue with the PBX / TSP manufactures whether it is possible to provide more call info.
BTW I guess you have already checked all ID fields of LINECALLINFO struct whether any one actually represents the info of interest...

On investigation, the Panasonic TAPI driver does in fact provide the DDI number dialled but in dwDevSpecific part of LINECALLINFO structure. So I can access - albeit is a custom bit of coding for that switch. Actually you only get the last six digits of the dial string, but I think that is ok.