CallReferenceID blank in BEGIN_CALL_EVENT with UCCE 10.5 GED-188 Protocol Version 16

[upchaurasia]

Hi All,

We are developing CTI Bridge application using UCCE GED-188 protocol version 16 , UCCE Version is 10.5.

We are able to receive all events and unpack successfully except UNSPEC datatype parameter like UserToUserInfo, CallReferenceID both are blanl.

CallReferenceID is important for us as it is CUCM CallId (as per GED-188 document) -

CallReferenceID (optional) - For Unified CCE systems where the Unified CM provides it, this will be a unique call identifier.   - UNSPEC 32

------------------------------------------------
MsgType: BEGIN_CALL_EVENT, BodyLength: 280
MonitorId: 0
PeripheralID: 5000
PeripheralType: 17
NumCTIClients: 0
NumNamedVars: 6
NumNamedArrays: 0
CallType: 2
ConnectionDeviceType: 1
CallID: 17803302
CalledPartyDisposition: 0
ConnectionDeviceID: 2029
ANI: 2029
DNIS: 2009
DialedNumber: 1003
CallerEnteredDigits: 1111111
CallWrapupData:
UserToUserInfo:
CallVar[1]:
CallVar[2]:
CallVar[3]:
CallVar[4]:
CallVar[5]:
CallVar[6]:
CallVar[7]:
CallVar[8]:
CallVar[9]:
CallVar[10]:
NamedVar[user.microapp.app_media_lib]: test
NamedVar[user.microapp.input_type]: D
NamedVar[user.microapp.locale]: en-us
NamedVar[user.microapp.media_server]: http://192.168.4.175
NamedVar[user.ecc.lookupType]: 1
NamedVar[user.ecc.lookupValue]: 1111111
RouterCallKeyDay: 152868
RouterCallKeyCallID: 229
RouterCallKeySeqNo: 2
CallReferenceID:
COCConnectionCallID: -842150451

--------------------------------------------------

Can anyone suggest us either UCCE CTI Server sets CallReferenceID in BEGIN_CALL_EVENT or not?

Thanks & Regards,

Umesh

[upchaurasia]

Waiting for response from Cisco team or any other member of this forum.

Regards,

Umesh

[dekwan]

Hi,

Sorry, is your question whether UCCE sets the CallReferenceID in the BEGIN_CALL event? As specified in the specs, it is optional so sometimes it can be set and sometimes it is not. A lot of times, a CALL_DATA_UPDATE event will be sent after the BEGIN_CALL with more information. Have you checked those events? 

Also, I believe that most of the time the callId value is the same call id as the one from CUCM. You can double check that by testing it out to confirm.

Thanx,

Denise

[upchaurasia]

Thanks Denise. I will check in CALL_DATA_UPDATE_EVENT.

Regards,

Umesh

[upchaurasia]

Hello Denise,

I checked with CALL_DATA_UPDATE_EVENT and CallReferenceId is blank in CALL_DATA_UPDATE also. Here is the event details - 

received bytes - 376MsgType: 25
Param Tag: 25
Param Tag: 47
Param Tag: 12
Param Tag: 82
Param Tag: 82
Param Tag: 82
Param Tag: 82
Param Tag: 82
Param Tag: 82
Param Tag: 23
Param Tag: 24

MsgType: CALL_DATA_UPDATE_EVENT, BodyLength: 282
MonitorId: 0
PeripheralID: 5000
PeripheralType: 17
NumCTIClients: 1
NumNamedVars: 6
NumNamedArrays: 0
CallType: 2
ConnectionDeviceIDType: 1
CallID: 17806227
CalledPartyDisposition: 0
CampaignID: -1
QueryRuleID: -1
ConnectionDeviceID: 2029
ANI:
CallerEnteredDigits: 111111111
UserToUserInfo:
CallVar[1]:
CallVar[2]:
CallVar[3]:
CallVar[4]:
CallVar[5]:
CallVar[6]:
CallVar[7]:
CallVar[8]:
CallVar[9]:
CallVar[10]:
WrapupData:
NamedVar[user.microapp.app_media_lib]: test
NamedVar[user.microapp.input_type]: D
NamedVar[user.microapp.locale]: en-us
NamedVar[user.microapp.media_server]: http://192.168.4.175
NamedVar[user.ecc.lookupType]: 1
NamedVar[user.ecc.lookupValue]: 111111111
AccountNumber:
PhoneNumber:
CallReferenceID:

Actually I don't see param tag 223 in event.

Is it possible for you to check in your lab and let me know if you are getting this value in any event? Protocol version is 16.

Thanks & Regards,

Umesh

[dekwan]

Hi,

Unfortunately, I don't have access to a UCCE 10.5 system. As I mentioned earlier, these fields are optional so its possible they won't be set.

Thanx,

Denise