Understand ICE signalling
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Both browsers exchange ICE candidates through the signal routes.
Where to goBrowser voice session
Before you start
- Verify the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide helps you do
Both browsers exchange ICE candidates through the signal routes. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to Browser voice session.
- Select the record or action required for understand ice signalling.
- Complete the displayed fields and choices described in this guide.
- Save, submit, approve or confirm the action as shown on screen.
- Refresh the relevant list, record or report and verify the expected result.
Fields and options
WorkspaceBrowser voice session
ActionBoth browsers exchange ICE candidates through the signal routes.
Rules and limits
- Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow.
- Core CRM record permissions and module permissions are both enforced where the code checks them.
Check it worked
- The understand ice signalling action completes without a validation or permission error.
- The affected record, stock balance, response, session or style reflects the saved state.
- Audit, notification, report or portal evidence appears only where the module code creates it.
Security, privacy and operational checks
- Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling.
- Grant only the minimum module and core CRM capabilities needed for the task.
Related guides
Was this guide useful?Your response is stored only in this browser.