TAPI - CallingParty and MGCP Prefixes

Unanswered Question
Dec 10th, 2007
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Hi


Typically we deploy callmanager using the CallManager MGCP Service Parameters to prefix a 90 to national numbers and 900 to international numbers inbound from the PSTN. This gives users a missed calls list that includes the correct prefixes needed to access the PSTN (9) and national numbers (0) or int'l numbers (00).


Several TAPI applications don't seem to heed this prefix - it seems they read the 'UnmodifiedCallingPartyNumber' from TSP, instead of the 'CallingParty'. Please see the example TSP log below, where CallingParty =9079xx278xxx but UnmodifiedCallingParty =79xx278xxx later in the trace :


09/18/2007 14:08:34.734 CiscoTSP001.tsp| NewCallEvent::Trace

bLineHandleSpecified =0x00000001

dwDeviceNameOffset =0x0000012C

dwDeviceNameSize =11

DeviceName =ARC-CT6231

dwCallingPartyOffset =0x00000137

dwCallingPartySize =13

CallingParty =9079xx278xxx

dwCalledPartyOffset =0x00000144

dwCalledPartySize =5

CalledParty =6231

dwOriginalCalledPartyOffset =0x00000149

dwOriginalCalledPartySize =5

OriginalCalledParty =6231

dwCallingPartyNameOffset =0x0000014E

dwCallingPartyNameSize =1

CallingPartyName =

dwCalledPartyNameOffset =0x0000014F

dwCalledPartyNameSize =1

CalledPartyName =

09/18/2007 14:08:34.734 CiscoTSP001.tsp| NewCallEvent::Trace

CallHandle.callManagerId =1

CallHandle.callLegId =0x01004112

09/18/2007 14:08:34.734 CiscoTSP001.tsp| NewCallEvent::Trace

GlobalCallHandle.callManagerId =1

GlobalCallHandle.callLegId =0x00005AAD

09/18/2007 14:08:34.734 CiscoTSP001.tsp| NewCallEvent::Trace

UserData:size = 0

09/18/2007 14:08:34.734 CiscoTSP001.tsp| NewCallEvent::Trace

HeldCallHandle.callManagerId =0

HeldCallHandle.callLegId =0x00000000

09/18/2007 14:08:34.734 CiscoTSP001.tsp| NewCallEvent::Trace

dwUnmodifiedCallingPartyOffset =0x00000164

dwUnmodifiedCallingPartySize =11

UnmodifiedCallingParty =79xx278xxx

dwUnmodifiedCalledPartyOffset =0x0000016F

dwUnmodifiedCalledPartySize =5

UnmodifiedCalledParty =6231

dwUnmodifiedOriginalCalledPartyOffset =0x00000174

dwUnmodifiedOriginalCalledPartySize =5

UnmodifiedOriginalCalledParty =6231

dwUnmodifiedLastRedirectingPartyOffset =0x00000179

dwUnmodifiedLastRedirectingPartySize =1

UnmodifiedLastRedirectingParty =



Has anyone seen this or have experience of Cisco TAPI development and know what would be involved in retrieving the 'Unmodified' variant of the CallingNumber?


Thanks


Aaron


Useful responses will be rated...

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion