FreePBX | Register | Issues | Wiki | Portal | Support

S505 + EXP100 - (REQUEST: NOTIFY, Event: 27)

bug
Tags: #<Tag:0x00007fafc7881980>

(Steve) #1

I’ve been having random problems with one of our phones which is an S505. The phone has an EXP100 attached to it. The type of problems are normally related to random call quality issues and issues with transferring calls. The problems do not happen every time.

I’ve look at this problem from the network and usage is pretty “normal” and no other phones have the problem.

Whilst checking the log file on the S505 I noticed it is filled with thousands of lines similar to the following:

[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130662, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130663, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130664, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130665, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130666, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130667, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130668, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130669, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130670, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130671, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130672, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130673, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130674, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####
[08-07 17:45:33 52:04:32] SIP: aid 0, cid 0, tid 130675, did 0, REQUEST: NOTIFY, Event: 27
[08-07 17:45:33 52:04:32] SIP: NOTIFY Event: message-summary#####

Can anyone advise if this is normal behaviour?

I’ve checked the logs on other devices (S500s and S505s) and none of them show a similar pattern.


(Lorne Gaetz) #2

This is actually not a phone problem, but an Asterisk issue. If you change the MWI Subscription on the Advanced tab of the Extension away from ‘Auto’, the NOTIFY flood should stop.


(Steve) #3

Thanks @lgaetz

I have just changed MWI Subscription Type to “Unsolicited”. Seemed like the closes one to “NOTIFY”

Will check logs and report back.


(Steve) #4

Looks like the logs look “normal” now.

Do you think this type of problem could cause random issues like call quality, etc? Maybe CPU usage is high on the phone because of it?


(Lorne Gaetz) #5

There are a host of symptoms that might manifest as a result. If you were seeing issues prior to the change, continue to monitor, you will likely see them resolved now.


(Steve) #6

Thanks I’ll keep an eye on it for the next few days.

Are there any downsides to settings MWI as “Unsolicited”?

Am I safe to set this for all my other extensions?


(Lorne Gaetz) #7

No downsides and is safe. If for some reason MWI stops working a a specific device, you can set to solicited.


(system) closed #8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.