When the upstream formatting changed, going from something like:
Alert-Info: foo
to something like:
Alert-Info: <http://127.0.0.1>;info=foo
the D-Series phones were saddened. At some point in the past (more than 4 years ago), we’d made a change that extracted contents of <> if they were present and that was evaluated. Thus, nothing was getting matched. We’ve got a beta 2_7_4 firmware available for non-D80 models. You can find the 2_7_4 beta at:
http://dphone.dl.digium.com/firmware/beta/2_7_4/
There’s a beta 1_9_7 firmware available for the D80. You can find the 1_9_7 beta at:
http://dphone.dl.digium.com/firmware/beta/1_9_7/
Note that with this update, Alert-Info strings are explicitly matched. So if the server’s sending:
Alert-Info: <http://127.0.0.1>;info=ring=answer
Then the phone’s config line is going to have to look exactly like:
<alert alert_info="<http://127.0.0.1>;info=ring-answer" ringtone_id="Digium" ring_type="ring-answer" />
which if you’re doing old-style DPMA key-value pairs, would be:
alert_info=<http://127.0.0.1>\;info=ring-answer
and where your dialplan is something like:
exten => addheader,1,Set(PJSIP_HEADER(add,Alert-Info)=<http://127.0.0.1>\;info=ring-answer)