Log output
The Pexip Infinity Management Node collates the logs from itself and all Conferencing Nodes and compiles these into the support log and the administrator log (which is a subset of the events in the support log).
To view these logs from the Pexip Infinity Administrator interface, go to or . If required, you can export the logs to a text file by selecting .
You can also use a syslog server to collate logs remotely.
Log timestamps always use UTC.
The log is presented in the order the messages were received by the Management Node.
The log appears in the format:
syslog_time system originating_time level name details
where:
| Field | Description |
|---|---|
syslog_time
|
In the format:
The time that the event was logged by syslog on the originating system. |
system
|
The IP address or host name of the system that sent the log message. |
originating_time
|
In the format:
The time at which the event occurred on the originating system. |
level
|
The severity of the event. The levels, in order of increasing severity, are:
In the Pexip Infinity Administrator interface, warnings and errors are highlighted with an orange or blue background respectively. |
name
|
The system module producing the log output. |
details
|
Information about the event, as a series of name=value pairs. |
Administrator log system modules
The administrator log contains information about events occurring during the normal use of the system which may be of interest to a system administrator.
The following list shows typical events that are shown in the administrator log. In addition to these, logs may also contain one-off events, such as bulk configuration import and incident reports.
For the sake of brevity, the examples shown below feature only the name and details sections of the log message.
administrator.system
Logs when the Pexip Infinity application has started on this Conferencing Node. Also logs web-based activities such as:
- import of service configuration
- deployment of a Conferencing Node
- configuration synchronization towards Conferencing Nodes
- liveness status of Conferencing Nodes and connectivity paths between nodes (either a direct path, or via other nodes in some cases for Proxying Edge Nodes)
Examples
Name="administrator.system" Message="Starting Infinity application." Pid="6361" Version="15 (34498.0.0)"
Name="administrator.system" Message="Deploying conferencing node virtual machine." Address="192.168.0.2"
Name="administrator.system.configuration" Message="Conferencing node configuration updated." Node="conferencingnode1"
Name="administrator.system.connectivity" Message="Unable to contact node." Src-Node="192.168.0.5" Node="192.168.0.2"
Name="administrator.system.connectivity" Message="Connectivity re-established." Src-Node="192.168.0.5" Node="192.168.0.2" Path="Direct" Last-Reported="Wed Mar 22 23:13:50 2017"
Name="administrator.system.connectivity" Message="Connectivity established." Src-Node="10.47.2.17" Node="10.47.3.46" Path="10.47.3.4, 10.47.3.7" (in this last example there is an indirect connectivity path between the source node and the target node, which is 10.47.2.17 > 10.47.3.4 > 10.47.3.7 > 10.47.3.46)
administrator.configuration
This module logs when:
- configuration is added or changed
- a user logs in or logs out of the system, or fails to log in
- a participant is manually dialed into a conference
- license requests are processed
Messages
Configuration added Configuration changed Configuration deleted User logged in User logged out User login failed Initiated dial command License activation request stored for offline processing Processed license request
Parameters
| Parameter | Definition |
|---|---|
| User | The user who made the change. |
| Type | The resource that was changed/added. |
| ID | The ID of the resource that was changed/added. |
| Fields | The fields in the resource that were changed. Applies to "Configuration changed" logs only. |
| Remote-Address | The IP address of the system from which the request was received. |
| Remote-Port | The port on the system from which the request was received. |
Examples
Name="administrator.configuration" Message="User login failed" User="admins" Remote-Address="192.0.2.0" Remote-Port="53991"
Name="administrator.configuration" Message="Configuration added" User="schedulingservice" Type="Scheduled Alias" ID="123456@example.com" Remote-Address="192.0.2.0" Remote-Port="53991"
Name="administrator.configuration" Message="Configuration changed" User="admin" Type="Virtual Meeting Room" ID="Alice's VMR" Fields="Description, Show names of participants" Remote-Address="192.0.2.0" Remote-Port="53991"
administrator.conference
This module logs conference activity and break-in prevention policy triggers.
Parameters for messages related to conference activity
Each log entry includes information in the form of a series of name=value pairs. These are defined as follows:
| Parameter | Definition |
|---|---|
| Call-ID | An identifier that allows correlation of messages from the same call. |
| Conference | The name of the service being connected to. |
| ConferenceAlias | The alias that was dialed in order to connect to the service. |
| Conversation-Id | An identifier that allows correlation of messages across separate "calls" for video+audio, RDP, or chat. |
| Detail | The reason the call was disconnected (for disconnect events). For more information, see Disconnection reasons. |
| Direction |
Either:
|
| DisplayName | The display name of the participant. |
| Duration | The duration of the call (for disconnect events). |
| License-Type | The type of license used in the call ("port", "audio" or "None"). |
| Licenses | The number of licenses allocated for the call. |
| Location | The system location of the Conferencing Node that is handling the media processing for the call. |
| Media-Node | The IP address of the Conferencing Node handling the media processing for the call. |
| Participant | The name or alias of the conference participant. |
| Participant-Id | Allows correlation of messages from the same participant URI per connection type, for example an API connection will have a different Participant-Id from a WebRTC connection. |
| Protocol | The protocol of the call (may also indicate "BACKPLANE" when a backplane between Conferencing Nodes is established or removed). |
| Proxy-Location | The system location of the Proxying Edge Node. |
| Proxy-Node | The IP address of the Proxying Edge Node. |
| Remote-Address | The source IP address for the signaling for this call. |
| Requester | The Call ID of the participant requesting this operation. |
| Role |
The role of this participant:
|
| Service-Tag |
A unique identifier used to track usage of this service. |
| Service-Type |
The service type of the conference. This is one of the following:
|
| Signaling-Location | The name of the Pexip Infinity location handling the signaling for this call. |
| Signaling-Node | The IP address of the Conferencing Node handling the signaling for the call. |
| Vendor | System details about the endpoint of the participant, such as manufacturer name and version number for hard endpoints, or browser and operating system details for soft clients. |
Examples
| Trigger for the log message | Example log entry |
|---|---|
| A participant tries to connect to a conference (at this stage it is the conference alias that is logged). |
Message="Participant attempting to join conference." ConferenceAlias="sip:meet.alice@example.com" Participant="sip:alice@example.com" Protocol="SIP" Direction="in" Remote-Address="10.47.2.55" Participant-Id="44be63a0-...c52" Registered="False" Location="Europe" |
| A conference instance is created on a Conferencing Node. This occurs when the first participant attempts to join this conference on that Conferencing Node. The Conference parameter indicates the name of the service, not the alias being dialed. |
Message="Conference has been created." Conference="Meet Alice" Service-Tag="" Service-Type="conference" Conference-ID="cc7f6255-0986-447d-8ee9-561c5bbf4a24" |
| A participant joins the conference. This log message is issued before a role is assigned. |
Message="Participant has joined." Conference="Meet Alice" Service-Tag="" Service-Type="conference" ConferenceAlias="sip:meet.alice@example.com" Participant="sip:alice@example.com" DisplayName="Alice Smith" Protocol="SIP" Direction="in" Vendor="TANDBERG/257 (TE4.1.1.273710)" Call-Id="fe7107ba-...16c" Conversation-Id="fe7107ba-...16c" Participant-Id="44be63a0-...c52" Remote-Address="10.47.2.55" Location="London" Licenses="1" Signaling-Node="192.168.0.1" Signaling-Location="London" Media-Node="192.168.0.2" Conference-ID="cc7f6255-0986-447d-8ee9-561c5bbf4a24" Proxy-Node="10.47.2.46" Proxy-Location="London Proxy" |
| Conference creation fails. |
Message="Failed creating conference." Conference="meet" Service-Tag="" |
|
A participant cannot join the conference. The Reason may vary as appropriate. If the reason is "No direct route between Edge and Transcoding", the most likely cause is that local or external media policy is in place and it has nominated a Transcoding Conferencing Node that cannot be directly reached from the Proxying Edge Node that received the call. |
Message="Participant failed to join conference." ConferenceAlias="sip:meet.invalid@example.com" Participant="sip:bob@example.com" Protocol="SIP" Direction="in" Remote-Address="10.44.100.75" Participant-Id="6696b7fe-...2cb" Reason="Neither conference nor gateway found" other reasons include: Reason="No direct route between Edge and Transcoding" |
|
A participant leaves the conference. Includes the Duration (in seconds) for which they were present in the conference. This message provides the definitive record of the length of time a call was connected to a conference. For more information on the reasons given in the Detail field, see Disconnection reasons. |
Message="Participant has disconnected." Conference="Meet Alice" Service-Tag="" Service-Type="conference" ConferenceAlias="sip:meet.alice@example.com" Participant="sip:alice@example.com" DisplayName="Alice Smith" Protocol="SIP" Direction="in" Call-Id="fe7107ba-...16c" Conversation-Id="fe7107ba-...16c" Participant-Id="44be63a0-...c52" Remote-Address="10.47.2.237" Location="London" Licenses="1" License-Type="port" Signaling-Node="192.168.0.1" Signaling-Location="London" Media-Node="192.168.0.1" Conference-ID="cc7f6255-0986-447d-8ee9-561c5bbf4a24" Proxy-Node="10.47.2.46" Proxy-Location="London Proxy" Duration="63.123" Detail="Remote disconnect" |
| A conference stops on a particular Conferencing Node. The Duration of this conference is given in seconds. |
Message="Conference has been stopped." Conference="Meet Alice" Service-Tag="" Service-Type="conference" Duration="62.234" Conference-ID="cc7f6255-0986-447d-8ee9-561c5bbf4a24" |
| A participant starts/stops presenting. |
Message="Participant is presenting." Conference="meet" Service-Tag="" Participant="sip:chuck@example.com" Call-Id="e5dbd44b...243" Conversation-Id="e5dbd44b...243" Message="Participant has stopped presenting." Conference="meet" Service-Tag="" Participant="sip:chuck@example.com" Call-Id="e5dbd44b...243" Conversation-Id="e5dbd44b...243" |
|
A participant using a Connect app, or any third party using the Pexip Client API, controls participants in a conference. |
Message="Participant hold requested by API." Conference="meet" ... Message="Participant resume requested by API." Conference="meet" ... Message="Participant disconnect requested by API." Conference="meet" ..." Message="Participant mute requested by API." Conference="meet" ... Message="Participant unmute requested by API." Conference="meet" ... Message="Participant presentation receipt enabled by API." Conference="meet"... Message="Participant presentation receipt disabled by API." Conference="meet" ... Message="Outgoing call requested" Conference="meet" Participant="sip:carol@example.com" Protocol="SIP" Role="chair" Message="Sending DTMF to participant." Conference="meet" Service-Tag="" Participant="sip:alice@example.com" Call-Id="e5dbd44b...243" Conversation-Id="e5dbd44b...243" Digits="4" Message="Participant transfer requested by API." Conference="meet.alice" Service-Tag="" Requester="66eb0873-...8ce" Participant="sip:bob@example.com" Call-Id="d583e3a1...@10.44.26.36" Conversation-Id="2a8ea679-...8a8" To-Conference="3259oknfaoi" |
| A participant uses a Connect app or DTMF commands to control the conference. |
Message="Conference terminated by participant" Conference="meet" ... Message="Conference lock requested by participant" Conference="meet" ... Message="Conference unlock requested by participant" Conference="meet" ... Message="Mute all guests requested by participant" Conference="meet" ... Message="Unmute all guests requested by participant" Conference="meet" ... |
| Participants attempt to join a PIN-protected conference. |
Message="PIN entry correct." Participant="sip:bob@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="27efdd36...6be" Role="host" Detail="Participant entered correct conference PIN and will be placed into the conference." Message="Participant entered incorrect conference PIN" RetriesRemaining="2" Participant="sip:bob@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="27efdd36...6be" Message="Participant exceeded PIN entry retries. Call will be disconnected." Participant="sip:bob@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="27efdd36...6be" Message="PIN entry timed out." Participant="sip:bob@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="a15dc445-...dfc" Detail="The correct PIN has not been received. Call will be disconnected." |
| Participants are involved in a PIN-protected conference. |
Message="Host participant joining." Participant="sip:alice@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="4d3ad9a1-...833" Role="chair" Detail="Participant will be automatically placed into the conference." Message="Conference host timeout." Participant="sip:bob@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="4d3ad9a1-...833" Detail="The conference host has not joined. Call will be disconnected." Message="Guest participant waiting." Participant="sip:bob@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="50a86594-...797" Role="guest" Detail="Waiting until participant is allowed to join the conference." Message="Guest participant joining." Participant="sip:bob@example.com" ConferenceAlias="sip:meet@example.com" Call-Id="50a86594-...797" Role="guest" Detail="Participant will be automatically placed into the conference." |
| A conference is automatically ended. |
Message="Last host left the conference and has not re-joined; conference will be terminated." Conference="Meet Alice" Service-Tag="" Message="Removing participant due to conference termination" Participant="sip:bob@example.com" Conference="Meet Alice" Service-Tag="" |
Break-in prevention policy example log messages
The following examples show messages that may be logged by the break-in prevention policies.
Logged when PIN brute force resistance has temporarily disabled a service, and for all subsequent attempts while the service is blocked:
Message="Break-in prevention policy blocking all attempts to join this service." ConferenceAlias="alice" Service="Alice's VMR" Participant="Crooky McCrookface" Protocol="API" Direction="in" Remote-address="10.44.21.35" Reason="Service appears to be under PIN break-in attack" remaining_block_duration_seconds="525"
Logged when VOIP scanner resistance has temporarily blocked an address:
Message="Participant has been quarantined by Break-in prevention policy due to excessive failed join attempts." Participant="Crooky McCrookface" Protocol="API" Direction="in" Remote-address="10.44.21.35" Reason="Too many attempts to join non-existent aliases" remaining_block_duration_seconds="488"
and then any subsequent attempts generate messages such as:
Message="Break-in prevention policy rejecting call attempt from quarantined caller." Protocol="API" Direction="in" Local-alias="[u'alice']" Remote-address="10.47.250.169" Reason="Suspicious join attempt rejected" remaining_block_duration_seconds="519"
administrator.participantdialer
This module logs outbound calls placed from a conference or via the Infinity Gateway.
Examples
Logged when dialing out from a conference:
Message="Placing outbound call" ConferenceAlias="meet.alice@example.com" DisplayName="meet.alice" Participant-alias="sip:bob@example.com" Protocol="SIP" Role="host"
Logged when making a call via the Infinity Gateway:
Message="Placing outbound call" Conference="Route to London:423a18c5-b06c-4654-9d34-e6b82f308b64" ConferenceAlias="alice@example.com" DisplayName="Alice" Participant-alias="sip:carol@example.com" Protocol="SIP" Role="guest"
administrator.registration
This module logs endpoint registration activities.
Examples
Logged when a registration is added:
Message="Registration added" Alias="alice@example.com" Protocol="SIP" Registration-Id="8695ea23-66fb-41d2-9266-d16598f5d133" Natted="False" Location="Europe"
Logged when a registration is removed:
Message="Registration deleted" Alias="bob@example.com" Protocol="WebRTC" Registration-Id="6936f540-6dbc-40ac-9d55-5469bbf4e561" Location="Europe" Reason="Registration expired"
administrator.ldap.sync
This module logs VMR, device and user synchronization template activities.
Examples
Logged when a VMR template synchronization is initiated:
Message="Beginning VMR Sync" Template="All employees" Creating="219" Deleting="0" Modifying="0" Unchanged="0"
Logged when a VMR template synchronization finishes:
Message="Completed VMR Sync" Template="Europe" Status="sync_succeeded" Created="18" Deleted="10" Updated="5" Unchanged="34" Warnings="3" Last_warning="Conference clash: not overwriting manually created conference"
Logged when an alias clash occurs during VMR template synchronization:
Message="Sync detected alias clash: alias held by an existing conference has not been assigned to the newly synced conference." NewConference="Alice's VMR" ExistingConference="Bob's VMR" Alias="meet@example.com"
administrator.apps.cloudbursting
This module logs cloud bursting activities.
Examples
Logged when an overflow Conferencing Node is started up:
Message="On-prem location 'Oslo' is overloaded! Starting instance i-0043088a9073b57e6 (stopped) in location 'AWS eu-west-1'"
Logged when an overflow Conferencing Node is shut down:
Message="Shutting down idle worker i-597394d2 (running) (uptime: 50 minutes)"
administrator.alarm
This module logs all Alarm raised and Alarm lowered events.
Examples
Logged when a "connectivity lost" alarm is lowered:
"Message="Alarm lowered" Node="10.47.2.46" Alarm="connectivity_lost" Instance="Source=10.47.2.46, Destination=10.47.2.17"
administrator.web
This module logs activity relating to conference and participant control by an administrator using the Administrator interface.
Examples
Message="Initiated mute command." User="admin" Participant-alias="Alice" Participant-Id="25fca17e-...374"
Message="Initiated unmute command." User="admin" Participant-alias="Alice" Participant-Id="25fca17e-...374"
Message="Initiated transfer command." User="admin" Participant-alias="Alice" Participant-Id="25fca17e-...374" Conference-alias="meet.alice2" Role="chair"
Message="Initiated conference lock." User="admin" Conference="meet.alice2"
Message="Initiated conference unlock." User="admin" Conference="meet.alice2"
Message="Initiated disconnect command." User="admin" Participant-alias="Alice" Participant-Id="21300b40-...557"
Message="Initiated conference disconnect." User="admin" Conference="meet.alice"
administrator.scheduling
This module logs the activities of the VMR Scheduling for Exchange service.
Parameters
| Parameter | Definition |
|---|---|
| ExchangeConnectorID | The database ID of the Pexip Exchange Integration which is the cause of this log activity. |
| CorrelationID | A UUID which identities which specific item this log refers to. The logs can be searched for an item's CorrelationID to easily find all logs pertaining to that item. |
| Name | The name of the VMR associated with the scheduled conference. |
| VmsID | The database ID of the VMR associated with the scheduled conference. |
| ScheduledAliasID | The database ID of the scheduled alias associated with the scheduled conference. |
| UUID | The UUID which identifies the Alias associated with the scheduled conference (this is the UUID used for the PXPS tag). |
| Alias | The full alias of the VMR associated with the scheduled conference, including the domain part |
| NumericAlias | The alias of the VMR associated with the scheduled conference, without the domain part |
| ScheduledConferenceID | The database ID of the single conference. |
| RecurringConferenceID | The database ID of the recurring conference. |
| OccurrenceScheduledConferenceIDs | The database IDs of the individual conference occurrences associated with the recurring conference. This is a list of values separated by commas. |
Examples
| Trigger for the log message | Example |
|---|---|
| New scheduled alias created. | Message="Scheduled Alias added" ScheduledAliasID="4983" UUID="5b195574-d8e0-4f5a-b07e-7826f419db7f" Alias="8359689@rd.pexip.com" NumericAlias="8359689" ExchangeConnectorID="2" |
| New single meeting created. | Message="Scheduled Conference added" VmsID="35111" Name="Example new meeting (Toby)" ScheduledConferenceID="5001" ScheduledAliasID="4983" ExchangeConnectorID="2" CorrelationID="4d566414-a1d3-5c3f-aa08-67fda6737fa7" |
|
Recurring meeting changed to a single meeting. The RecurringConferenceID is deleted and the new ScheduledConferenceID assigned. |
Message="Recurring Conference changed to Scheduled Conference" VmsID="35000" Name="Example meeting (Jim Bob)" RecurringConferenceID="1" ScheduledConferenceID="10" ExchangeConnectorID="1" CorrelationID="e55af8b7-ec66-4376-8521-16a41de918eb" |
| Single meeting updated. | Message="Scheduled Conference changed" VmsID="35111" Name="Example edited meeting (Toby)" ScheduledConferenceID="5001" ExchangeConnectorID="2" CorrelationID="4d566414-a1d3-5c3f-aa08-67fda6737fa7" |
| New recurring meeting created. | Message="Recurring Conference added" VmsID="1234" Name="Example new recurring meeting (John Smith)" RecurringConferenceID="1000" OccurrenceScheduledConferenceIDs="501, 502" ScheduledAliasID="2000" ExchangeConnectorID="1" CorrelationID="5a304f92-6705-4f45-87b3-428d8a7261ef" |
|
Single meeting changed to a recurring meeting. The ScheduledConferenceID is deleted and the new RecurringConferenceID assigned. |
Message="Scheduled Conference changed to Recurring Conference" VmsID="10" Name="Another example meeting (Darth Vader)" ScheduledConferenceID="12" RecurringConferenceID="14" OccurrenceScheduledConferenceIDs="13, 14, 15" ExchangeConnectorID="1" CorrelationID="ab40e1f4-5a46-494a-a39f-8156eded538e" |
|
Recurring meeting updated. The OccurrenceScheduledConferenceIDs replace any occurrences which already exist. |
Message="Recurring Conference changed" VmsID="1234" Name="Example edited recurring meeting (John Smith)" RecurringConferenceID="1000" OccurrenceScheduledConferenceIDs="503" ExchangeConnectorID="1" CorrelationID="5a304f92-6705-4f45-87b3-428d8a7261ef" |
|
An individual occurrence of an existing recurring conference is updated but the occurrence is not currently in the database. Modified occurrences are always added to the database. |
Message="Occurrence Scheduled Conference added" VmsID="1234" Name="Example edited recurring meeting (John Smith)" OccurrenceScheduledConferenceID="504" RecurringConferenceID="1000" ExchangeConnectorID="1" CorrelationID="5a304f92-6705-4f45-87b3-428d8a7261ef" |
|
An individual occurrence of an existing recurring conference is updated and the occurrence is already in the database. |
Message="Occurrence Scheduled Conference changed" VmsID="1234" Name="Example edited recurring meeting (John Smith)" OccurrenceScheduledConferenceID="504" ExchangeConnectorID="1" CorrelationID="5a304f92-6705-4f45-87b3-428d8a7261ef" |
|
Meeting canceled — this normally happens when a single meeting or entire recurring meeting is canceled, but it may also happen if an item is rejected because an update to it was invalid. Note that deleting the conference also causes the associated single conference or recurring conference and any related aliases to be deleted at the same time. |
Message="Conference deleted" VmsID="35111" ExchangeConnectorID="2" CorrelationID="4d566414-a1d3-5c3f-aa08-67fda6737fa7" |
|
Occurrence canceled — this normally happens when an individual occurrence in a recurring series is canceled, but it may also happen if the occurrence is rejected because an update to it was invalid. Note that the VmsID is left unchanged. |
Message="Occurrence Scheduled Conference deleted" VmsID="35111" OccurrenceScheduledConferenceID="504" ExchangeConnectorID="1" CorrelationID="5a304f92-6705-4f45-87b3-428d8a7261ef" |
| Single meeting recovered while running the Scheduling Recovery tool. This means a single meeting was added back to the database with a new alias. | Message="Scheduled Conference recovered" VmsID="10" Name="Example recovered meeting (Fred)" ScheduledConferenceID="12" ScheduledAliasID="12" ExchangeConnectorID="1" CorrelationID="1b770df6-d27f-4c32-b499-1e3104c2f45b" |
| Recurring meeting recovered while running the Scheduling Recovery tool. This means a recurring meeting was added back to the database with a new alias. | Message="Recurring Conference recovered" VmsID="2" Name="Example recovered recurring meeting" RecurringConferenceID="2" OccurrenceScheduledConferenceIDs="2, 3" ScheduledAliasID="3" ExchangeConnectorID="2" CorrelationID="65dc5d19-c8fb-4040-9dd5-447ef196eda2" |
|
The scheduling background tasks successfully updated a recurring conference. NewOccurrenceScheduledConferenceIDs can be empty if no new occurrences were added at this point. IsDepleted indicates whether there are any more occurrences left in this recurring series. |
Message="Background tasks updated Recurring Conference" VmsID="42" Name="Meaning of life" RecurringConferenceID="42" NewOccurrenceScheduledConferenceIDs="" CurrentIndex="3" IsDepleted="False" ExchangeConnectorID="1" CorrelationID="79e4ee44-3a05-41b2-b988-4e6d98c15072" |
|
The scheduling background tasks encountered an error when updating a recurring conference. This can happen if we can no longer update a recurring series. For example, the room/equipment resource could have been changed and this was a recurring series stored on the old resource. |
Message="Recurring Conference deleted because it can no longer be processed" VmsID="13" RecurringConferenceID="13" ExchangeConnectorID="2" CorrelationID="e86b9fca-c0ba-4ef2-8b56-8f75fcb60d12" |
| The scheduling background tasks successfully deleted an expired single meeting. | Message="Background tasks deleted expired Scheduled Conference" VmsID="101" ScheduledConferenceID="201" ExchangeConnectorID="1" CorrelationID="359803da-f34f-4515-b505-313b3c9f53fc" |
|
The scheduling background tasks successfully deleted an expired meeting occurrence. Note that when an individual occurrence expires, it is only the corresponding OccurrenceScheduledConferenceID that gets deleted. There may still be other occurrences which are not expired. |
Message="Background tasks deleted expired Occurrence Scheduled Conference" VmsID="14" OccurrenceScheduledConferenceID="15" ExchangeConnectorID="1" CorrelationID="375c005e-5edc-4a44-876c-43c8cedf6657" |
| The scheduling background tasks successfully deleted an expired recurring conference. | Message="Background tasks deleted expired Recurring Conference" VmsID="53" RecurringConferenceID="33" ExchangeConnectorID="3" CorrelationID="a874129f-da34-4bfb-8422-211711af52d0" |
| The scheduling background tasks successfully deleted a used scheduled alias. | Message="Background tasks deleted expired used Scheduled Alias" ScheduledAliasID="5" ExchangeConnectorID="2" |
| The scheduling background tasks successfully deleted an unused scheduled alias. | Message="Background tasks deleted expired unused Scheduled Alias" ScheduledAliasID="7" ExchangeConnectorID="2" |
administrator.otj
This module logs the activities of the One-Touch Join service when:
- a One-Touch Join meeting is created
- a One-Touch Join meeting is deleted
- a One-Touch Join meeting is changed.
Parameters
| Parameter | Definition |
|---|---|
| OTJProfileName | The name of the OTJ Profile associated with this meeting. |
| OTJProfileID | The ID of this OTJ Profile. |
| Room | The email address of the room resource in whose calendar the meeting has been scheduled. |
| Subject | The text that appears in the subject line of the meeting invitation. |
| OrganizerEmail | The email address of the person who created the meeting invitation. |
| StartTime | The scheduled start time of the meeting. |
| EndTime | The scheduled end time of the meeting. |
| Alias | The alias that the endpoint will use to dial in to the meeting. |
| OTJRuleName | The name of the meeting processing rule that was matched and used to process this meeting. |
Examples
| Trigger for the log message | Example |
|---|---|
| New OTJ meeting created | Message="OTJ Meeting Created" OTJProfileName="Test MJX integration0" OTJProfileID="1" Room="roomresource@resource.calendar.google.com" Subject="Test Meeting" OrganizerEmail="jack@pexip.com" StartTime="2020-02-05 15:00:00" EndTime="2020-02-05 16:00:00" Alias="1234567890@pexip.com" OTJRuleName="Pexip Rule" |
| Existing OTJ meeting changed | Message="OTJ Meeting Changed" OTJProfileName="Test MJX integration0" OTJProfileID="1" Room="roomresource@resource.calendar.google.com" Subject="Test Meeting" OrganizerEmail="jack@pexip.com" StartTime="2020-02-05 15:30:00" EndTime="2020-02-05 16:30:00" Alias="1234567890@pexip.com" OTJRuleName="Pexip Rule" |
| Existing OTJ meeting deleted | Message="OTJ Meeting Deleted" OTJProfileName="Test MJX integration0" OTJProfileID="1" Room="roomresource@resource.calendar.google.com" Subject="Test Meeting" OrganizerEmail="jack@pexip.com" StartTime="2020-02-05 15:30:00" EndTime="2020-02-05 16:30:00" Alias="1234567890@pexip.com" OTJRuleName="Pexip Rule" |
Support log system modules
Support logs provide a more detailed record of activity on the Pexip Infinity system:
| Module | Contains |
|---|---|
| support.bfcp | BFCP signaling. |
| support.conference |
Logs the aliases that are matched against Call Routing Rules. The parsed or unparsed alias match type depends upon the rule's Match against full alias URI setting. For example: Message="Alias matched gateway rule" Rule="Route calls from London" Description="" Service-Tag="" Unparsed-alias="alice@example.com" Parsed-alias="alice@example.com" Matched-alias-Type="Parsed-alias" |
| support.conferenceservice | Logs when a participant has sent a chat message (but does not include the message contents). |
| support.dns | DNS lookups associated with SIP signaling. |
| support.events | Errors when attempting to connect to an external event sink server. |
| support.externalpolicy | Requests sent to an external policy server and the associated response. |
| support.gms | Gateway calls into Google Meet. |
| support.h323.q931, support.h323.ras, support.h323.h245 |
H.323 signaling. |
| support.jinja2 | Messages generated by the pex_debug_log filter when inserted into local policy jinja2 scripts. |
| support.otj | Messages related to One-Touch Join. |
| support.participant |
Details about conference participants, including presentation stream activation, loss of incoming video, and call media statistics when a call is completed. An example of end-of-call media statistics is as follows:
Message="Media Stream destroyed" Participant="sip:alice@example.com" Call-Id="890b38520c27737c@192.168.0.1" Conversation-Id="1238035a...a2de" Detail="Stream 0 (audio) |
| support.pulse |
Logs scheduled maintenance events in Azure. For example: New scheduled maintenance event: {'Description': 'The system will Reboot', 'EventId': '2262d851-75e0-11eb-92d9-000d3abdf5e0', 'EventSource': 'Platform', 'EventStatus': 'Scheduled', 'EventType': 'Reboot', 'NotBefore': '2021-01-06T11:10:18+00:00', 'ResourceType': 'VirtualMachine', 'Resources': ['azure-mcu001']} |
| support.rest | Messages to and from the Pexip Client API (used by the Connect apps, and other third parties). |
| support.rtmp | Calls (streaming) to an RTMP device. |
|
support.scheduled_maintenance_events |
Logs actions taken by Pexip Infinity resulting from detecting scheduled maintenance events in Azure. For example: Message="Scheduled maintenance event affecting MCU node has been detected. System will be placed into maintenance mode." Message="Maintenance event completed. Maintenance mode will be unset." |
| support.sip | SIP signaling. |
| support.teams | Gateway calls into Microsoft Teams. |
Content of signaling messages
All log lines for signaling-related messages contain source and destination IP addresses and ports.
Multi-line messages are encoded on a single line with the character sequence ^M representing a linebreak.
In addition to observing remote IP addresses, for H323 logging, a Uuid is present for H.225 (RAS) and H.245 signaling messages. These come from the same IP address but different ports, and the Uuid allows you to identify that they relate to the same call.
For BFCP signaling, all log lines are tied to a SIP Call-Id.
Most of the content of the support log is the signaling messages themselves; however it also includes logging such as TCP and TLS connection attempts, successes, and failures.