Event | Category | Triggering event | Description |
|---|---|---|---|
Long Call | .Common | Session Completion Success Session Completion Failure | Reported if session duration is greater or equal than SessionDurationThreshold UDP |
MO Calls | .Common | Session Attempt | MO device identifier (SIP Invite received in downlink) |
MT Calls | .Common | Session Attempt | MT device identifier (SIP Invite sent in uplink) |
Short Call | .Common | Session Completion Success Session Completion Failure | Reported if session duration is less than SessionDurationThreshold UDP |
Unknown Call Type | .Common | Session Attempt | Reported in case it can't be determined if call is short or long (i.e. session duration not available) |
No Audio Received | Audio | NoAudioReceivedTimeout UDP timer expiry | Reported if no RTP packets are received within NoAudioReceivedTimeout UDP seconds and at least one RTP packet is sent in the last 1 second. Event is repeated every NoAudioReceivedTimeout if no new packets are received. |
Session Completion Failure, RTP Drop | Audio | SessionDropTimeout UDP timer expiry | Reported if no RTP packets are received within SessionDropTimeout UDP seconds and no RTP packets are sent in the last 1 second. |
Session Completion Failure | Call Ending | Multiple, see description | Session completion failure reported in the following cases: (1) SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Bye (2) SIP Bye logged indicating abnormal call release (i.e. reason field different than 101/user triggered, 105/eHRPD handover, 107/Voice mail or Q.850 with cause value 16 or 31 etc.) (3) SIP Invite with new Call Id is received for ongoing session; If UseNoRTPPacketsReceivedCriteria UDP is set to 1 no RTP packets must be sent within the last 1 second (4) Session RTP drop internal timer expired, i.e. no RTP packets are received within SessionDropTimeout UDP seconds and no RTP packets are sent within the last 1 second; The condition may be turned off by setting and UseNoRTPPacketsReceivedCriteria UDP to 0 (5) Session hang up internal timer expired, i.e. SIP 200 Ok not received within SessionHangupTimeout UDP of SIP Bye indicating normal call release (i.e. reason field not populated or it is equal to 101/user triggered or Q.850 with cause value 16 or 31 etc.) |
Session Completion Success | Call Ending | SIP 200 (Bye) | Session completion success |
MO Session Completion Failure | Call Ending MO | Multiple, see description | MO device session completion failure |
MO Session Completion Success | Call Ending MO | SIP 200 (Bye) | MO device session completion success |
MT Session Completion Failure | Call Ending MT | Multiple, see description | MT device session completion failure |
MT Session Completion Success | Call Ending MT | SIP 200 (Bye) | MT device session completion success |
Session Established | Call Established | SIP Ack | SIP Ack received following SIP 200 Ok (Invite) |
Session Establishment Failure | Call Established | SessionEstablishedFailureTimeout UDP timer expiry | Reported if no SIP Ack is received within SessionEstablishedFailureTimeout UDP seconds of SIP 200 Ok (Invite). |
MO Session Established | Call Established MO | SIP Ack | MO device session established |
MO Session Establishment Failure | Call Established MO | SessionEstablishedFailureTimeout UDP timer expiry | MO device session establishment failed |
MT Session Established | Call Established MT | SIP Ack | MT device session established |
MT Session Establishment Failure | Call Established MT | SessionEstablishedFailureTimeout UDP timer expiry | MT device session establishment failed |
Session Setup Aborted | Call Setup Aborted | SIP Cancel | Session setup aborted with SIP Cancel |
Session Setup Aborted (Client Initiated) | Call Setup Aborted | SIP Cancel | Session setup abort initiated by client (SIP Cancel sent in uplink) |
Session Setup Aborted (Network Initiated) | Call Setup Aborted | SIP Cancel | Session setup abort initiated by network (SIP Cancel received in downlink) |
Busy Here (response code 486) | Call Setup Results | SIP 486 (Invite) | SIP 486 logged in response to SIP Invite |
Session Redirection | Call Setup Results | SIP 300, 301, 302, 305 or 380 (Invite) | SIP 300, 301, 302, 305 or 380 logged in response to SIP Invite |
Session Setup Failure | Call Setup Results | Multiple, see description | Session setup failure reported in the following cases: (1) SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Invite (2) SIP 486 logged in response to SIP Invite and SessionSetupFailureOnResponse486 UDP is set to 1 (3) SIP 486 response to SIP Invite sent by client includes reason phrase 'Establishing Another Call' (4) Session aborted (SIP Cancel) by client and SessionSetupFailureOnSIPCancel UDP is set to 1 (5) Session setup failure internal timer expired, i.e. SIP 200 Ok not received within SessionSetupFailureTimeout UDP seconds of SIP Invite |
Session Setup Success | Call Setup Results | SIP 200 (Invite) | Session setup success |
MO Session Setup Failure | Call Setup Results MO | Multiple, see description | MO device session setup failure |
MO Session Setup Success | Call Setup Results MO | SIP 200 (Invite) | MO device session setup success |
MT Session Setup Failure | Call Setup Results MT | Multiple, see description | MT device session setup failure |
MT Session Setup Success | Call Setup Results MT | SIP 200 (Invite) | MT device session setup success |
Call Answer Failure | Call Start | Answer End | Call answer failure reported for 'Answer End' event status 'Failed' or 'Stopped by Timeout' or following 'Blocked Call' event |
Call Initiation Failure | Call Start | CallInitiationFailureTimeout UDP timer expiry | 'Call Initiation Failure' reported if CallInitiationFailureTimeout UDP expires before call attempt is made after 'Dial Start' was previously received (MO device). |
Session Attempt Retry | Call Start | SIP Invite | Repeated session attempt |
Session Attempt (SIP Invite) | Call Start | SIP Invite | Session attempt reported on initial SIP Invite |
Session Attempt Connected Mode | Call Start | Dial Start Answer Start | 'Dial Start' or 'Answer Start' logged in Connected Mode |
Session Attempt Idle Mode | Call Start | Dial Start Answer Start | 'Dial Start' or 'Answer Start' logged in Idle Mode |
Session Attempt Unknown Mode | Call Start | Dial Start Answer Start | Mode unknown at 'Dial Start' or 'Answer Start' |
MO Session Attempt (SIP Invite) | Call Start MO | SIP Invite | MO device session attempt reported on initial SIP Invite |
MO Session Attempt Retry | Call Start MO | SIP Invite | MO device repeated session attempt |
MT Session Attempt (SIP Invite) | Call Start MT | SIP Invite | MT device session attempt reported on initial SIP Invite |
MT Session Attempt Retry | Call Start MT | SIP Invite | MT device repeated session attempt |
MO Session Attempt (EOF) | EOF | SIP Invite | MO device session attempt logged in the case when data collection ends before session is setup |
MOSession Established (EOF) | EOF | SIP Ack | MO device session established (end of session missing in log file) |
MOSession Setup Success (EOF) | EOF | SIP 200 (Invite) | MO device session setup success (end of session missing in log file) |
MT Session Attempt (EOF) | EOF | SIP Invite | MT device session attempt logged in the case when data collection ends before session is setup |
MT Session Established (EOF) | EOF | SIP Ack | MT device session established (end of session missing in log file) |
MT Session Setup Success (EOF) | EOF | SIP 200 (Invite) | MT device session setup success (end of session missing in log file) |
Session Attempt (EOF) | EOF | SIP Invite | Session attempt logged in the case when data collection ends before session is setup |
Session Established (EOF) | EOF | SIP Ack | Session established (end of session missing in log file) |
Session Setup Success (EOF) | EOF | SIP 200 (Invite) | Session setup success (end of session missing in log file) |
MESSAGE Delivery Report Attempt | IM | SIP Message | SIP Message sent in uplink by MT device following 'MESSAGE Received Ack' |
MESSAGE Delivery Report Failure | IM | Multiple, see description | SIP registration failure reported in the following cases: (1) MT device received SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Message (2) Message sent internal timer expired, i.e. SIP 202 Accepted not received by MT device within MessageDeliveryReportTimeout UDP seconds of SIP Message (3) SIP Message received by MT device before receiving SIP 202 Accepted on 'MESSAGE Delivery Report Attempt' |
MESSAGE Delivery Report Success | IM | SIP 202 Accepted (Message) | SIP 202 Accepted received in downlink by MT device in response to 'MESSAGE Delivery Report Attempt' |
MESSAGE Received | IM | SIP Message | SIP Message received in downlink by MT device |
MESSAGE Received Ack | IM | SIP 200 Ok (Message) | SIP 200 Ok sent in uplink by MT device in response to 'MESSAGE Received' |
MESSAGE Received Ack Failure | IM | Multiple, see description | SIP registration failure reported in the following cases: (1) MT device sent SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Message (2) Message received Ack internal timer expired, i.e. SIP 200 Ok not sent by MT device within MessageReceivedAckTimeout UDP seconds of SIP Message (3) New SIP Message received by MT device before responding to 'MESSAGE Received' |
MESSAGE Sent Attempt | IM | SIP Message | SIP Message sent in uplink by MO device |
MESSAGE Sent Failure | IM | Multiple, see description | SIP registration failure reported in the following cases: (1) MO device received SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Message (2) Message sent internal timer expired, i.e. SIP 202 Accepted not received by MO device within MessageSentTimeout UDP seconds of SIP Message (3) SIP Message received by MO device before receiving SIP 202 Accepted on 'MESSAGE Sent Attempt' |
MESSAGE Sent Success | IM | SIP 202 Accepted (Message) | SIP 202 Accepted received in downlink by MO device in response to 'MESSAGE Sent Attempt' |
MESSAGE Submitted | IM | SIP Message | SIP Message received in downlink by MO device following 'MESSAGE Sent Success' |
MESSAGE Submitted Ack | IM | SIP 200 Ok (Message) | SIP 200 Ok sent in uplink by MO device in response to 'MESSAGE Submitted' |
MESSAGE Submitted Ack Failure | IM | Multiple, see description | SIP registration failure reported in the following cases: (1) MO device sent SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Message (2) Message submitted Ack internal timer expired, i.e. SIP 200 Ok not sent by MO device within MessageSubmittedAckTimeout UDP seconds of SIP Message (3) New SIP Message sent by MO device before responding to 'MESSAGE Submitted Ack' |
Activate Dedicated EPS Bearer Context Request | LTE | ESM Activate dedicated EPS bearer context request | Activate dedicated EPS bearer context request |
Bearer Resource Allocation Reject | LTE | ESM Bearer resource allocation reject | Bearer resource allocation reject received with EPS identity of QCI 1, QCI 6 or QCI 8 bearer |
Deactivate EPS Bearer Context Request | LTE | ESM Deactivate EPS bearer context request | Deactivate EPS bearer context request received with EPS identity of QCI 1, QCI 6 or QCI 8 bearer |
EPS Bearer Drop | LTE | Session Completion Failure | EPS bearer drop reported with session completion failure due to SIP 503 including 'loss of bearer' tag or SessionDropTimeout internal timer expiry. |
SRVCC Handover | LTE | SRVCC Handover Success | SRVCC handover success |
SRVCC Handover (During On-going Call) | LTE | SRVCC Handover Success | SRVCC handover completed after session setup success |
SRVCC Handover (During Setup) | LTE | SRVCC Handover Success | SRVCC handover completed prior to session setup |
SRVCC Handover Failure | LTE | Inter-System Handover To WCDMA Failure | Inter-System Handover To WCDMA Failure' event received for ongoing session |
Call End Initiated From 2G/3G | Miscellaneous | SIP Bye | SIP Bye logged with reason field 16 or 31 indicating normal call clearing from 2G/3G side |
Presence Subscription Failure | Presence | Multiple, see description | Subscribe request failure reported in the following cases: (1) SIP 412, 423 or 489 logged in response to SIP Subscribe (2) Session setup registration internal timer expired, i.e. SIP 200 Ok not received within PresenceSubscriptionTimeout UDP seconds of SIP Subscribe Reported only when initial SIP Subscribe message Event field includes ‘presence’. |
Presence Subscription Not Authorized | Presence | SIP 202 (Subscribe) | SIP 202 response received on Subscribe request. Reported only when initial SIP Subscribe message Event field includes ‘presence’. |
Presence Subscription Success | Presence | SIP 200 (Notify) | Subscribe request success reported for SIP 200 (Notify) sent in downlink. Reported only when initial SIP Subscribe message Event field includes ‘presence’. |
Publish Request | Presence | SIP Publish | SIP Publish request sent in uplink with Event field including 'presence'. |
Publish Request Failure | Presence | Multiple, see description | Publish request failure reported in the following cases: (1) SIP 412, 423 or 489 logged in response to SIP Publish (2) Session setup registration internal timer expired, i.e. SIP 200 Ok not received within PublishTimeout UDP seconds of SIP Subscribe Reported only when initial SIP Publish message Event field includes ‘presence’. |
Publish Request Success | Presence | SIP 200 (Publish) | Subscribe request success reported for SIP 200 (Publish) received in downlink. Reported only when initial SIP Publish message Event field includes ‘presence’. |
Subscribe Request | Presence | SIP Subscribe | SIP Subscribe request sent in uplink with Event field including 'presence'. |
Subscribe Request Failure | Presence | Multiple, see description | Subscribe request failure reported in the following cases: (1) SIP 412, 423 or 489 logged in response to SIP Subscribe (2) Session setup registration internal timer expired, i.e. SIP 200 Ok not received within PresenceSubscriptionTimeout UDP seconds of SIP Subscribe Reported only when initial SIP Subscribe message Event field includes ‘presence’. |
Subscribe Request Success | Presence | SIP 200 (Subscribe) | Subscribe request success reported for SIP 200 (Subscribe) received in downlink. Reported only when initial SIP Subscribe message Event field includes ‘presence’. |
SIP Deregistration | Registration | SIP Register | SIP Register logged with Expires field value equal to 0 |
SIP Registration Attempt (SIP Register) | Registration | SIP Register | SIP Register logged with Expires field value other than 0 |
SIP Registration Failure | Registration | Multiple, see description | SIP registration failure reported in the following cases: (1) SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Register (2) Session setup registration internal timer expired, i.e. SIP 200 Ok not received within SIPRegistrationFailureTimeout UDP seconds of SIP Register |
SIP Registration Success | Registration | SIP 200 (Register) | SIP registration success |
SIP Registration Success C1 (401 Unauthorized) | Registration | SIP 200 (Register) | SIP 200 (Register) received after SIP 401 (Unauthorized) response on initial SIP Register request |
SIP Registration Success C2 (Re-registration) | Registration | SIP 200 (Register) | SIP re-registration success |
SIP Registration Success C3 (Notify) | Registration | SIP 200 (Register) | SIP registration success with SIP Notify and SIP 200 Ok (Notify) logged between SIP Register request and SIP 200 (Register) answer |
180 Ringing | Ringing | SIP Ringing (Invite) | Ringing indication logged for ongoing session |
MO 180 Ringing | Ringing | SIP Ringing (Invite) | MO device ringing indication received for ongoing session |
MT 180 Ringing | Ringing | SIP Ringing (Invite) | MT device ringing indication sent for ongoing session |
No RTP Packets Received (~1s) | RTP | Recurring timer (1s) | No RTP packets received within the last 1 second |
Media Stream Addition Attempt | Session | SIP Invite | SIP Invite indicating an addition of media (e.g. video stream) with Call Id matching ongoing session |
Media Stream Addition Failure | Session | SIP error code received, see description | SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Invite indicating an addition of media. |
Media Stream Addition Success | Session | SIP 200 (Invite) | New media (e.g. video stream) added to existing session |
Media Stream Removal Attempt | Session | SIP Invite | SIP Invite indicating a removal of media (e.g. video stream) with Call Id matching ongoing session |
Media Stream Removal Failure | Session | SIP error code received, see description | SIP 400, 403, 404, 405, 406, 408, 413, 415, 420, 480, 481, 487, 488, 500, 501, 503, 504, 600, 603, 604 or 606 logged in response to SIP Invite indicating a removal of media. |
Media Stream Removal Success | Session | SIP 200 (Invite) | A media (e.g. video stream) removed from existing session |
Moved to eHRPD | Session | SIP Bye | SIP Bye logged with reason field 105 (eHRPD handover) |
ViLTE End | Video | Session Completion Success | Reported for completed session including video media type |
ViLTE Error | Video | Session Setup Failure Session Establishment Failure Session Completion Failure | Reported for failed session including video media type |
ViLTE Start | Video | SIP Invite | Reported for session setup or session modification attempt including video media type |
Voice Mail Call | Voice Mail | SIP Bye | SIP Bye logged with reason field 107 (Voice mail) and SIP 183 Session Progress was received previously with P-Asserted-Identity field including 'voicemail' tag |