Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Name |
Description |
Field size in bytes |
|---|---|---|
Ipcs Id |
The unique ID that identifies Avaya SBC. |
4 |
Session Id |
The unique ID that identifies the call. |
4 |
Leg Id |
The unique ID for each leg of the call. |
4 |
RURI Domain |
The 32 last characters of host part that is IP address or Domain in Request URI. |
32 |
RURI Username |
The 16 last digits of the numeric user portion (Called Number) in Request URI. |
16 |
From Domain |
The 32 last characters of the host part of the From header. |
32 |
From Username |
The 16 last digits of the numeric user portion of the From header identifying the calling number. |
16 |
To Domain |
The 32 last characters of the host part of the To header. |
32 |
To Username |
The 16 last digits of the numeric user portion of the To header identifying the called number. |
16 |
Outgoing PAI Domain |
The 32 last characters of the host part of the P-Asserted-Identity header. |
32 |
Outgoing PAI Username |
The 16 last digits of the numeric user portion in the P-Asserted-Identity header. |
16 |
Call Id |
The CALL ID of the call leg. |
128 |
UCID |
The UCID, which is unique across Avaya solution for a call and can be used by other adjuncts for reporting, monitoring, and call recording. For recording in CDR, UCID must be administered in Avaya SBC or must come in signaling. The User-To-User header must contain the UCID portion. The User-To-User header containing user information is not part of this field. |
24 |
Calling Party Address |
The 32 last characters of the host part of contact of the far end calling User Agent (UA). |
32 |
Called Party Address |
The 32 last characters of the host part of contact of the far end called UA. |
32 |
Endpoint group policy |
The first 10 characters of the SIP Endpoint Policy administered on the Avaya SBC. |
10 |
Server Flow |
The first 10 characters of the SIP Server or Subscriber Flow administered on the Avaya SBC. |
10 |
Session Policy |
The first 10 characters of the session flow administered on the Avaya SBC. |
10 |
Routing Profile |
The first 10 characters of the Routing profile administered on the Avaya SBC. |
10 |
Alternate routes attempted |
The number of times Avaya SBC performs alternate routing. |
4 |
Redirected to domain |
The last 32 characters of the host part of the Contact header when Avaya SBC services enable redirection. |
32 |
Redirected to Username |
The last 16 digits of the numeric user portion of the User part from the Contact header when Avaya SBC services enable redirection. |
16 |
Refer to Domain |
The last 32 characters of the host part of the REFER-TO header. |
32 |
Refer to Username |
The 16 right-most digits of the numeric user portion of user part from the REFER-TO header. |
16 |
Refer from Domain |
The 32 right-most characters of host part of Referred-by header. |
32 |
Refer from Username |
The last 16 digits of the numeric user portion of the User part of the Referred-by header. |
16 |
Duration |
The duration of the call. The value is controlled by an administered flag so that duration is calculated from the connected to terminated time, or the initiated to terminated time. The administration is as per the policy of the operator. A seven-digit number indicates the duration of the call in hours, minutes, and seconds. First three digits indicate hours, the next two digits indicate minutes, and the last two digits indicate seconds . |
8 |
Setup time |
The timestamp of Initial INVITE ingressing / egressing from Avaya SBC. DO NOT use the slash |
8 |
Connect time |
The timestamp of ACK to Initial INVITE ingressing or egressing from Avaya SBC. |
8 |
Disconnect time |
The timestamp of the ingress BYE or any other session terminating message such as 4xx, 5xx, 6xx, and CANCEL. |
8 |
VLAN tag |
VLAN ID differentiates between traffic or calls coming from different tenants mapped with different VLAN IDs. |
4 |
Codec |
The codec negotiated for the call. The negotiated codec is obtained from the first common intersect between offer and answer messages. |
4 |
Bandwidth |
The highest bandwidth used by the call. The bandwidth values are rounded to the nearest multiple of 64000. The options are:
|
1 |
Endpoint type |
The type of Endpoint. The options are:
|
1 |
Feature flag |
The feature invoked at Avaya SBC, such as Transfer, Redirection, and SIPREC. This is set as bit mask with the following options:
|
1 |
Media flag |
The protocol used for media transport and media-related features. This field is set as bit mask with the following options :
|
1 |
Reason code |
The code for identifying the reason for call disconnect . The options are:
|
1 |
Media Type |
Identifies the type of media used for the call leg. This field is set as bit mask with the following options:
|
1 |
End to end secure signalling |
The status of security of the signaling of the call . If the originating and terminating call is SIPS, the call is assumed to be secured end-to-end on signaling. The options are:
|
1 |
Failover Detected |
Indicates, if Avaya SBC failover happened during call. |
1 |
Latency Progress |
Latency in 100 Trying for Avaya SBC timestamp from INVITE. Applicable to UAC and UAS. |
4 |
Latency Alert |
Latency in 180 or 183 for Avaya SBC timestamp from INVITE. Applicable to UAC and UAS. |
4 |
Latency Connect |
Latency in 200 OK for Avaya SBC timestamp from INVITE. Applicable to UAC and UAS. |
4 |
Latency Ack |
Latency in ACK for Avaya SBC timestamp from 200 OK. Applicable to UAC and UAS |
4 |
Incoming PAI Domain |
The 32 last characters of the host part of the P-Asserted-Identity header. |
32 |
Incoming PAI Username |
The 16 last digits of the numeric user portion in the P-Asserted-Identity header. |
16 |
Mean TTL |
The mean TTL value of data packets in the sequence number range, rounded off to the nearest integer. |
1 |
Begin Seq Num |
The first sequence number of the RTP data packets. |
2 |
End Seq Num |
The last sequence number of the RTP data packets. |
2 |
SSRC |
The SSRC of the RTP data packet source. |
4 |
Lost Pkt |
The number of lost packets in the sequence interval. |
4 |
Duplicate Pkt |
The number of duplicate packets in the sequence interval. |
4 |
Min Jitter |
The minimum relative transit time between two packets in the sequence interval. |
4 |
Max Jitter |
The maximum relative transit time between two packets in the sequence interval. |
4 |
Mean Jitter |
The mean relative transit time between two packets in the sequence interval. |
4 |
Loss Rate |
The fraction of RTP data packets lost from the source since the packets were received. It is expressed as a fixed point number. |
4 |
Discard Rate |
The fraction of RTP data packets discarded from the source since the packets were received, due to late or early arrival, under-run or overflow at the receiving jitter buffer. |
4 |
Round Trip Delay |
The round trip time between the RTP instance and the voice application in milliseconds. |
4 |
IsJoin |
Identifies if the call leg is part of conference. |
- |
JoinStatus |
The success or failure codes while joining the conference. |
- |
IsTransfer |
Identifies if the call leg is part of call transfer. |
- |
TransferStatus |
The success or failure codes on call transfer. |
- |
CallDirection |
The direction of the call. The possible values are Inbound and Outbound. |
- |
ExportMode |
The CDR mode configuration. The possible values are 3 for Radius and 4 for Radius with Summary. |
- |
PartnerId |
The Microsoft Partner Id configured. |
- |
CustomerId |
The Microsoft Customer Id configured. |
The P-Asserted Identity (PAI) in the SIP INVITE from the Call Server towards the Trunk will get stored in Outgoing PAI fields. Also, if the INVITE is from the Trunk Server, the response for this call from the Call Server will get stored in the Outgoing PAI fields.
The P-Asserted Identity (PAI) in the SIP INVITE from the Trunk Server towards Call Server will get stored in Incoming PAI fields. Also, If the INVITE is from the Call Server, the response for this call from the Trunk Server will get stored in Incoming PAI fields.