Phone Server Flooding Phones with SIP NOTIFY packets?

Running FreePBX 14 (Asterisk 13.22.0)

I have 18 locations with a total of ~100 phones. Some locations have as few as 2 phones and some locations have upwards of 14 phones.

All the locations are using identical routers (FreeBSD boxes), identical switches (UniFi 24-port and 48-port PoE switches), and identical phones (Digium D60). The routers are all literally identical except for their IP addresses and are configured via automation to ensure no one forgets a setting. Most locations use Comcast as their internet provider.

Every location works perfectly…except one. I’ll refer to it as ‘Oregon’.

This one location will work fine for days or weeks, and then all of sudden I start getting complaints from every location that phone service is ‘choppy’ or ‘robotic’. Looking at the VoIP server I see 3-4 phones from Oregon receiving about 10 mbit/sec of traffic from the phone server.

Opening a packet analyzer at the phone server, I see a huge flood of SIP Notify messages from the phone server to each of the 3-4 phones in Oregon.

Here’s a snippet. The Oregon phones are 10.133.12.x, the phone server is 10.142.0.230.

NOTIFY sip:[email protected]:5060;ob SIP/2.0
Via: SIP/2.0/UDP 10.142.0.230:5060;rport;branch=z9hG4bKPj2e90eae4-85a4-487a-8937-18fedca60551
From: <sip:[email protected]>;tag=48ef06ea-5cd5-4f45-ba84-e397e648c4cc
To: <sip:[email protected];ob>
Contact: <sip:[email protected]:5060>
Call-ID: 2eb2394a-75fc-4179-a69c-754c5006e6d6
CSeq: 9792 NOTIFY
Subscription-State: terminated
Event: message-summary
Allow-Events: presence, dialog, message-summary, refer
Max-Forwards: 70
User-Agent: FPBX-14.0.11(13.22.0)
Content-Type: application/simple-message-summary
Content-Length:    48

Messages-Waiting: no
Voice-Message: 0/0 (0/0)
NOTIFY sip:[email protected]:5060;ob SIP/2.0
Via: SIP/2.0/UDP 10.142.0.230:5060;rport;branch=z9hG4bKPj3893b583-51a6-4228-b004-d0eb1b11fd63
From: <sip:[email protected]>;tag=5fd0ac39-3bf5-48d0-98fc-d777bcc50312
To: <sip:[email protected];ob>
Contact: <sip:[email protected]:5060>
Call-ID: b82db2b9-7f3d-4abb-b491-f0917e247903
CSeq: 60843 NOTIFY
Subscription-State: terminated
Event: message-summary
Allow-Events: presence, dialog, message-summary, refer
Max-Forwards: 70
User-Agent: FPBX-14.0.11(13.22.0)
Content-Type: application/simple-message-summary
Content-Length:    48

Messages-Waiting: no
Voice-Message: 0/0 (0/0)
NOTIFY sip:[email protected]:5060;ob SIP/2.0
Via: SIP/2.0/UDP 10.142.0.230:5060;rport;branch=z9hG4bKPj8427b4cd-da50-4968-ad14-7a41cd65d37f
From: <sip:[email protected]>;tag=d0efb2fa-8e5e-4218-939e-ed33d6602f1b
To: <sip:[email protected];ob>
Contact: <sip:[email protected]:5060>
Call-ID: d1b24c03-0b3f-4420-8d51-30fa54bc631e
CSeq: 32052 NOTIFY
Subscription-State: terminated
Event: message-summary
Allow-Events: presence, dialog, message-summary, refer
Max-Forwards: 70
User-Agent: FPBX-14.0.11(13.22.0)
Content-Type: application/simple-message-summary
Content-Length:    48

Messages-Waiting: no
Voice-Message: 0/0 (0/0)
NOTIFY sip:[email protected]:5060;ob SIP/2.0
Via: SIP/2.0/UDP 10.142.0.230:5060;rport;branch=z9hG4bKPj32b87885-4571-445c-a821-35f0ccd21a40
From: <sip:[email protected]>;tag=dd086364-a8b3-4c24-a134-1826926cb70a
To: <sip:[email protected];ob>
Contact: <sip:[email protected]:5060>
Call-ID: 8d36568e-756f-4549-bb77-1ca97d973d3b
CSeq: 34007 NOTIFY
Subscription-State: terminated
Event: message-summary
Allow-Events: presence, dialog, message-summary, refer
Max-Forwards: 70
User-Agent: FPBX-14.0.11(13.22.0)
Content-Type: application/simple-message-summary
Content-Length:    48

Messages-Waiting: no
Voice-Message: 0/0 (0/0)
NOTIFY sip:[email protected]:5060;ob SIP/2.0
Via: SIP/2.0/UDP 10.142.0.230:5060;rport;branch=z9hG4bKPje957f289-7039-49ef-bc56-a163dddfb604
From: <sip:[email protected]>;tag=05a090f3-fb96-45d8-a61a-a4b1b94287ad
To: <sip:[email protected];ob>
Contact: <sip:[email protected]:5060>
Call-ID: 6b4dcea3-f463-4f2c-8038-a43ce09de59b
CSeq: 43382 NOTIFY
Subscription-State: terminated
Event: message-summary
Allow-Events: presence, dialog, message-summary, refer
Max-Forwards: 70
User-Agent: FPBX-14.0.11(13.22.0)
Content-Type: application/simple-message-summary
Content-Length:    48

Messages-Waiting: no
Voice-Message: 0/0 (0/0)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.142.0.230:5060;rport=5060;received=10.142.0.230;branch=z9hG4bKPj2e90eae4-85a4-487a-8937-18fedca60551
Call-ID: 2eb2394a-75fc-4179-a69c-754c5006e6d6
From: <sip:[email protected]>;tag=48ef06ea-5cd5-4f45-ba84-e397e648c4cc
To: <sip:[email protected];ob>;tag=z9hG4bKPj2e90eae4-85a4-487a-8937-18fedca60551
CSeq: 9792 NOTIFY
Content-Length:  0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.142.0.230:5060;rport=5060;received=10.142.0.230;branch=z9hG4bKPj3893b583-51a6-4228-b004-d0eb1b11fd63
Call-ID: b82db2b9-7f3d-4abb-b491-f0917e247903
From: <sip:[email protected]>;tag=5fd0ac39-3bf5-48d0-98fc-d777bcc50312
To: <sip:[email protected];ob>;tag=z9hG4bKPj3893b583-51a6-4228-b004-d0eb1b11fd63
CSeq: 60843 NOTIFY
Content-Length:  0

Rebooting the affected phones does not resolve the issue.
Restarting Asterisk resolves the issue for a few days or weeks.

The endpoints are all configured to use PJSIP.
The logs don’t appear to contain any relevant errors or warnings.

This is a bit outside my wheelhouse. Does anyone have advice on troubleshooting this?

Thanks,

-A

1 Like

Thanks @lgaetz!
That definitely sounds like what I’m running into. I’ll give it a shot and report back next week!

1 Like

Probably should update endpoints to not use unsolicited MWI by default.

1 Like

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