Registration Alerts
A registration alert notifies you when an identity loses connection unexpectedly. Optionally, you can receive a follow-up email when the identity re-registers, or a timeout email if it does not re-register within a set period.
Reg Alert Subscription
Log into Byphone, and go to reseller.byphone.co.uk
Search for the business you want to add registration alerts to and click Show
Now click Registrations in the top left corner
Click Alerts in the top Right
Followed by New Alert
Provide the following:
Subscriber email address
Identities/Username to subscribe (all or specific)
Whether you want a resolution email (on re-registration)
Whether you want a timeout email (no re-registration within threshold)
Timeout threshold: 1h, 2h, 6h, 12h, or 24h
Behaviour
When you receive an alert, it includes details about the identity involved.
The identity that has lost registration, this includes the last section of digits of the org ID
Which Public IP address the Identity was associated with when the connection was lost
The user agent, the type of device that the identity lost registration on (sometimes including the mac address, device dependent)
If you have subscribed to resolution emails and time out emails, you will receive a similar email letting you know when the device has connected, or if the device has not registered within the time out threshold
Ongoing Alerts
Within the organisation Alerts page, you will be able to view all ongoing alerts within the time out
This will show the following:
Label - Friendly name of the identity affected
Identity - Identity name
Source IP - Public IP address the Identity was associated with when the connection was lost
User Agent - The device which triggered the alert
Email - the email which receives the alerts
Timeout Limit - How long the alert is monitored
Send Timeout Email - Determines if a time out email will be sent when the limit is hit
Started - Which time the alert started
Limitations
To trigger the initial email, the device will have to have been previously registered for at least 60 seconds, it will then need to have failed 3 concurrent keepalive checks at 30 seconds intervals (1 min 30 seconds) to trigger an email
Transport
Transport that identities are currently using need to be either TCP or TLS
Recommendations
SIP ALG
SIP ALG/STUN should be disabled (as has always been the case) due to the negative impact on Byphone registrations.
Device Count
We would currently suggest using one identity per device
If a device with a subscribed identity goes offline, but it's currently registered elsewhere, a resolution email be sent with a different user agent (device)
This may lead to confusion and limit the feature's usefulness if the user agent is similar to the triggering device.
For example the Snom D735 user agent will be the same if it is on the same firmware version.
Compare this to a Fanvil ATA which has it’s MAC address added to the user agent.
If you need to change your subscription later, please raise a new support ticket and our team will update the settings for you.