User Calls Table

cId

This is the call id used for link with others sections of the system information file. For instance it helps to identify which call is blinking on which shortcut.

seq

Call sequence type. This is not call type, it reflects only the user sequence on the call.

OCALL (Outbound call)

ICALL (Inbound call)

ACONF (adhoc conference): indicates that the device is currently in an ad-hoc conference operation (see application.global.telephony.conference). Basically a conference has been initiated. The conference may have been confirmed or the next step is to place a new call to confirm it. This sequence sets the state of the handset panel (with the Resume button...).

ACONFCH (adhoc conference, call changed): identical to the one above, but a Replace action has been received in the mean time.

SCONF(Standard conference): indicates that the device is currently in a standard conference operation (see application.global.telephony.conference). Basically a conference has been initiated. The conference may have been confirmed or the next step is to place a new call to confirm it. This sequence sets the state of the handset panel (with the Resume button...).

TRANS(Transfer): indicates that the device is currently in a transfer operation.

IINTER(Incoming intercom)

OINTER(outgoing intercom)

MCONF(Meet-me conference on initiator)

State

This reflects the call state in the internal state machine. Here is an extract of the most usual values:

1_IOPENING: an incoming call

1_IDOPENING: a distant incoming call (if you see distant call as local incoming call)

1_IACCEPTING: accepting a call

1_OPREPARING: preparing an outgoing call (the sip request is not sent yet)

1_OOPENING: opening an outgoing call (sip request sent)

1_ORINGING: outgoing call launched, the remote party is ringing

2_OPENED: call is established

2_HOLDING: call is currently put on hold (sip reinvite on progress)

2_HELD: call is on hold

2_THOLDING: call is currently put on hold (sip reinvite on progress). The hold purpose is a Transfer

2_THELD: call is on hold for a Transfer

2_DHOLDING: call is currently put on hold (sip reinvite on progress). The hold purpose is a Dispatch

2_DHELD: call is on hold for a Dispatch

2_DHOLDING: call is currently put on hold (sip reinvite on progress). The hold purpose is a Dispatch

2_DHELD: call is on hold for a Dispatch

2_CHOLDING: call is currently put on hold (sip reinvite on progress). The hold purpose is a Conference

2_CHELD: call is on hold for a Conference

5_CONFERENCE: when making a conference, the turret creates a fake 5_CONFERENCE call object that represents the whole conference.

6_CONFERENCING: The 5_CONFERENCE call is linked to several 6_CONFERENCING call objects. These calls are the real calls that are included in the conference (and thus they are the original participant calls that have just been switch to 6_CONFERENCING state). In ad-hoc mode, there is only one of such calls as the conference is hosted on the PBX.

Dvc

Device on which the call is currently hosted (see device table)

sUser

Remote party of the call

ddislot

Ddislot number on which the call appears

oldTalkState/oldLineState

Whether the call is public or private

sUId

Shortcut ID of the associated shortcut to this call

regId

The line id on which the call arise (see User Lines)

listnPrt

RTP port used to handle this call

listnHdl

Input stream index used to handle this call

recordingState

Whether the call is recorded or not