Hi,
I’m having a problem with notifications for BLF and Pickup. In version 22.6 (and ealier), the SDP body contained a “Remote” section and a ‘Local’ section. In version 22.11, the “Remote” section is missing.
A working example from 22.6:
<?xml version="1.0" encoding="UTF-8"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="11" state="full" entity="sip:245@192.168.10.70">
<dialog id="245" direction="recipient">
<remote>
<identity display="Katrin Wemheuer">sip:200@192.168.10.70</identity>
<target uri="sip:200@192.168.10.70" />
</remote>
<local>
<identity display="Max M..ller">sip:245@192.168.10.70</identity>
<target uri="sip:245@192.168.10.70" />
</local>
<state>early</state>
</dialog>
</dialog-info>
Here is an example from 22.11 (without Remote-Part):
<?xml version="1.0" encoding="UTF-8"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="8" state="full" entity="sip:245@192.168.10.70">
<dialog id="245" direction="recipient">
<local>
<identity>sip:245@192.168.10.70</identity>
<target uri="sip:245@192.168.10.70" />
</local>
<state>early</state>
</dialog>
</dialog-info>
Both examples were created using the same configuration.
Are there new configuration options between 22.6 and 22.11, or is that a bug?
Thanks
Best regards
Karsten
i think there is a pr up for this
master ← jcolp:master-issue-2186
opened 06:44PM - 29 Sep 26 UTC
When a legacy extension state callback registers it can optionally do so in a wa… y that it will receive the channel(s) that have caused a device to ring. This is used in PJSIP for the dialog-info+xml support so that phones can display who is calling the monitored extension.
An issue was introduced in the extension state rewrite where this did not occur for the actual device that caused the extension state update. It was only being done for additional devices that could be involved. This has been fixed so that it is now done for the causing device.
Fixes: #2186
Hi,
looks good to me, I’ll try that.
Thanks a lot
Karsten
Am Mittwoch, dem 07.10.2026 um 17:36 +0000 schrieb benphone:
Someone replied to a topic you are Watching.
benphone
October 7
i think there is a pr up for this
GitHub - asterisk/asterisk: The official Asterisk Project repository. · GitHub
extstate: Include causing device channel details in legacy
callbacks. (#2192 )
master ← jcolp:master-issue-2186
opened 06:44PM - 29 Sep 26 UTC
jcolp
+39 -9
When a legacy extension state callback registers it can optionally do
so in a wa…
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.
I’m seeing the same behavior with Asterisk 22.11. The difference between 22.6 and 22.11 strongly suggests this is related to the extension state rewrite rather than a configuration change.
The PR mentioned above, #2192 , looks relevant because it fixes the missing causing-device channel details used by dialog-info+xml.
I’ll test the patch as well. It would be useful to confirm whether applying this change restores the <remote> section for BLF/Pickup notifications.
jcolp
October 8, 2026, 9:19am
5
It does. Test coverage was also added[1] for the change, which is specifically for dialog-info+xml with the remote identity information.
[1] pjsip: Add test to cover dialog-info+xml with identity information. by jcolp · Pull Request #156 · asterisk/testsuite · GitHub