Travis Hawkins Posted September 4, 2015 Report Posted September 4, 2015 Forgive me if this has been mentioned before, but I couldn't find anything on it. We recently setup a new customer using the Monster UI and about half of their devices are soft phones on laptop/tablet devices. Now we're getting emails all day and night every time one of the soft phone devices un-registers. In the previous interface there was a checkbox on the device configuration page for "Notify when unregistered" which would prevent these notifications when unchecked. I don't see that option in Monster anywhere. Was that an intentional change or is there an option elsewhere that I haven't stumbled upon yet? Thanks. Travis
2600Hz Employees lazedo Posted September 4, 2015 2600Hz Employees Report Posted September 4, 2015 Hi,the check box you mentioned is available in kazoo ui, and within monster is accessible with "Advance Callflows" app in the Device submodule.
Travis Hawkins Posted September 4, 2015 Author Report Posted September 4, 2015 Perfect, thanks for your help! Do you know if it will eventually be added back to the normal device config page for quicker access?
2600Hz Employees Aaron Gunn Posted September 14, 2015 2600Hz Employees Report Posted September 14, 2015 Travis, Thanks for the suggestion. We'll look into getting it added back.
Anthony Goss Posted March 26, 2016 Report Posted March 26, 2016 I am unable to find it. I have a client that uses a lot of Soft Phones and I am unable to find the "Notify when unregistered" option. I see it for VOIP PHONE but not for Soft Phone. So.. I am getting a lot of unregistered emails. This option is not available in Kazoo nor Monster for Softphone
Administrators Darren Schreiber Posted March 26, 2016 Administrators Report Posted March 26, 2016 So actually when you select Soft Phone we inherently know that the phone is probably going to roam. So we are supposed to disable, by default, and without option, the notify on de-register. So it sounds like maybe there is a bug or the GUI team did not understand this when it was coded up. It may have been missing from the spec or engineering design discussions.I will talk to Aaron and see if we can get that resolved.
Recommended Posts