Call Parking causing massive notices in console

I have a parking lot set up with the parking extension of 700 and the parking positions of 701-799.

Each phone has a blf button watching the first 3 positions 701-703. The work great. Park a call and everyones button lights up but…

Whenever a call is parked or picked up the following shows on the command line:

[Apr 13 09:01:20] NOTICE[26019]: res_pjsip/pjsip_distributor.c:525 log_failed_request: Request ‘NOTIFY’ from ‘sip:701@192.168.2.2’ failed for ‘127.0.0.1:5060’ (callid: 2047610347-5060-95@A.A.A.A) - No matching endpoint found
[Apr 13 09:01:20] NOTICE[22458]: res_pjsip/pjsip_distributor.c:525 log_failed_request: Request ‘NOTIFY’ from ‘sip:701@192.168.2.2’ failed for ‘127.0.0.1:5060’ (callid: 520544449-5060-3@BJC.BGI.C.BBB) - No matching endpoint found
[Apr 13 09:01:14] NOTICE[32757]: res_pjsip/pjsip_distributor.c:525 log_failed_request: Request ‘NOTIFY’ from ‘sip:701@192.168.2.2’ failed for ‘127.0.0.1:5060’ (callid: 1185289998-5060-19@A.A.A.A) - No matching endpoint found
[Apr 13 09:01:14] NOTICE[31316]: res_pjsip/pjsip_distributor.c:525 log_failed_request: Request ‘NOTIFY’ from ‘sip:701@192.168.2.2’ failed for ‘127.0.0.1:5060’ (callid: 1491845903-5060-55@A.A.A.A) - No matching endpoint found
[Apr 13 09:01:14] NOTICE[31316]: res_pjsip/pjsip_distributor.c:525 log_failed_request: Request ‘NOTIFY’ from ‘sip:701@192.168.2.2’ failed for ‘127.0.0.1:5060’ (callid: 537019714-5060-47@A.A.A.A) - No matching endpoint found

Hundreds of times.

It looks like this corresponds to all of the lights on the phones changing.

What am i missing in my configuration?

It almost seems as though Asterisk is sending NOTIFY messages to itself. This is not something that is normally done. The only thing that comes to mind is subscriptions telling Asterisk to send NOTIFY requests to itself instead of to the device that did the subscription. Looking at the SUBSCRIBE messages from devices would confirm if this is true or not (a device may be putting 127.0.0.1 in when it should not).

I’m not exactly sure what you mean but… All other blf features in the system works. Our receptionist has a blf buttons for all phones and they work correctly (button indicates BUSY and RINGING which I use for DND) This only acts this way for Parking. How do I check the “SUBSCRIBE messages from devices”

Doing “pjsip set logger on” will output the SIP traffic and looking at the “Contact” header for each SUBSCRIBE request will tell you where the device is saying to send NOTIFY requests.

This is what is showing in the log for each phone

<— Received SIP response (502 bytes) from UDP:192.168.2.156:5060 —>
SIP/2.0 481 Subscription Does Not Exist
Via: SIP/2.0/UDP 192.168.2.2:5060;rport=5060;branch=z9hG4bKPjfc4939fd-de2c-48c5-92ed-5e9e190439b6
From: sip:701@192.168.2.2;tag=d205f110-67ba-4fd3-8257-5578f5c23b9c
To: sip:356@192.168.2.2;tag=1297552404
Call-ID: 1055032608-5060-3@BJC.BGI.C.BFG
CSeq: 14798 NOTIFY
Supported: replaces, path, timer
User-Agent: Grandstream GXP2130 1.0.7.99
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
Content-Length: 0

<— Received SIP response (380 bytes) from UDP:127.0.0.1:5060 —>
SIP/2.0 481 Call/Transaction Does Not Exist
Via: SIP/2.0/UDP 127.0.0.1:5060;rport=5060;received=127.0.0.1;branch=z9hG4bKPjd27f0b6a-fcb0-4b3b-a214-81b6661ac8b4
Call-ID: 1457220481-5060-27@A.A.A.A
From: sip:701@192.168.2.2;tag=81b8b5e1-aae6-482e-b32c-53b73a48b419
To: sip:356@192.168.2.2;tag=1354549291
CSeq: 5195 NOTIFY
Server: Asterisk PBX 14.3.0
Content-Length: 0

That 481 to the NOTIFY is from Asterisk to itself. Based on the Call-ID it could very well be that a Grandstream phone is subscribing (or did subscribe) and saying “send notify messages to 127.0.0.1” which would then go back to Asterisk.

I think I follow. I rebooted a phone to get it to subscribe and for the sip messages corresponding to 701-

<— Received SIP request (660 bytes) from UDP:192.168.2.154:5060 —>
SUBSCRIBE sip:701@192.168.2.2 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.154:5060;branch=z9hG4bK1870406506;rport
From: sip:354@192.168.2.2;tag=1916389016
To: sip:701@192.168.2.2
Call-ID: 1282468612-5060-3@BJC.BGI.C.BFE
CSeq: 20010 SUBSCRIBE
Contact: sip:354@192.168.2.154:5060
X-Grandstream-PBX: true
Max-Forwards: 70
User-Agent: Grandstream GXP2130 1.0.7.99
Expires: 3600
Supported: replaces, path, timer, eventlist
Event: dialog
Accept: application/dialog-info+xml,multipart/related,application/rlmi+xml
Accept-Encoding: zlib+base64
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
Content-Length: 0

<— Transmitting SIP response (547 bytes) to UDP:192.168.2.154:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.154:5060;rport=5060;received=192.168.2.154;branch=z9hG4bK1870406506
Call-ID: 1282468612-5060-3@BJC.BGI.C.BFE
From: sip:354@192.168.2.2;tag=1916389016
To: sip:701@192.168.2.2;tag=a4ab09f9-9ca2-4943-98d0-1ebd21ef52af
CSeq: 20010 SUBSCRIBE
Expires: 3600
Contact: sip:192.168.2.2:5060
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFER
Supported: 100rel, timer, replaces, norefersub
Server: Asterisk PBX 14.3.0
Content-Length: 0

<— Transmitting SIP request (803 bytes) to UDP:192.168.2.154:5060 —>
NOTIFY sip:354@192.168.2.154:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.2:5060;rport;branch=z9hG4bKPjf922a084-936b-420b-ac88-9650f0eca9a8
From: sip:701@192.168.2.2;tag=a4ab09f9-9ca2-4943-98d0-1ebd21ef52af
To: sip:354@192.168.2.2;tag=1916389016
Contact: sip:192.168.2.2:5060
Call-ID: 1282468612-5060-3@BJC.BGI.C.BFE
CSeq: 21563 NOTIFY
Event: dialog
Subscription-State: active;expires=3599
Allow-Events: presence, dialog, message-summary, refer
Max-Forwards: 70
User-Agent: Asterisk PBX 14.3.0
Content-Type: application/dialog-info+xml
Content-Length: 228

<?xml version="1.0" encoding="UTF-8"?> terminated

<— Received SIP response (516 bytes) from UDP:192.168.2.154:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.2:5060;rport=5060;branch=z9hG4bKPjf922a084-936b-420b-ac88-9650f0eca9a8
From: sip:701@192.168.2.2;tag=a4ab09f9-9ca2-4943-98d0-1ebd21ef52af
To: sip:354@192.168.2.2;tag=1916389016
Call-ID: 1282468612-5060-3@BJC.BGI.C.BFE
CSeq: 21563 NOTIFY
Contact: sip:354@192.168.2.154:5060
Supported: replaces, path, timer
User-Agent: Grandstream GXP2130 1.0.7.99
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
Content-Length: 0

I have searched the grandstream settings and cannot find the culprit. You defiantly put me on the right track. Thank you.

If you can find something using “A.A.A.A” in the Call-ID header you may be able to isolate it to a specific device.